If user attempts to create another PatientConnection authorization request, PatientConnection.Create() returns as exception which states
"The connect request already exists, and cannot be recreated."

I have attempted to call PatientConnection.DeletePending() with the applicationPersonID, but the exception in #5 is still thrown - Presumable because the PatientConnection request isn't pending but in fact validated.

Calling PatientConnection.GetValidatedConnections() still shows the original PatientConnection authorization request that was created in #1. My hunch is that this is why creation of a new PatientConnection authorization request fails (since a PatientConnection
request with a duplicate applicationPersonID exists in HealthVault).

Questions

Is it correct that the ValidatedPatientConnection returned by PatientConnection.GetValidatedConnections() will be automatically deleted by HealthVault after 90 days?

Is there a way to remove the ValidatedPatientConnection? If not, is there a way to create a new PatientConnection request with a applicationPersonID that was previously used?

If Application User attempts to create another PatientConnection authorization request, PatientConnection.Create() returns as exception which states "The
connect request already exists, and cannot be recreated."

Step 4 in this scenario is not required ( by design ).

A connect request can be used multiple times until it is deleted from HealthVault. This is useful in the following scenarios:

The user deauthorizes the app and then wants to reauthorize it. The user ID and record ID values are preserved during reauthorization, so the app doesn't have to update its store.

The user wants to select a different record. The app will remain authorized to the original record as well as the new one. Your app needs to be able to handle this scenario.

If Application User attempts to create another PatientConnection authorization request, PatientConnection.Create() returns as exception which states "The
connect request already exists, and cannot be recreated."

Step 4 in this scenario is not required ( by design ).

A connect request can be used multiple times until it is deleted from HealthVault. This is useful in the following scenarios:

The user deauthorizes the app and then wants to reauthorize it. The user ID and record ID values are preserved during reauthorization, so the app doesn't have to update its store.

The user wants to select a different record. The app will remain authorized to the original record as well as the new one. Your app needs to be able to handle this scenario.