Scan

Beta

GET

/patient-merge/v1/updates/scan

GET

/patient-merge/v1/updates/scan

$ curl -G https://pre-api.joincandidhealth.com/patient-merge/v1/updates/scan \
>      -H "Authorization: Bearer <token>" \
>      --data-urlencode since=2024-01-15T09:30:00Z

200Retrieved

1 [
2   {
3     "alternative_patient_mrn": "alternative_patient_mrn",
4     "deactivated": true,
5     "id": "id",
6     "organization_id": "organization_id",
7     "primary_patient_mrn": "primary_patient_mrn",
8     "updated_at": "2024-01-15T09:30:00Z",
9     "updating_user_id": "updating_user_id",
10     "version": 1
11   },
12   {
13     "alternative_patient_mrn": "alternative_patient_mrn",
14     "deactivated": true,
15     "id": "id",
16     "organization_id": "organization_id",
17     "primary_patient_mrn": "primary_patient_mrn",
18     "updated_at": "2024-01-15T09:30:00Z",
19     "updating_user_id": "updating_user_id",
20     "version": 1
21   }
22 ]

Scans up to 1000 patient merge updates. The since query parameter is inclusive, and the result list is ordered by updatedAt ascending.

Polling Pattern: To continuously poll for updates without gaps:

Make your initial request with a since timestamp (e.g., since=2020-01-01T13:00:00.000Z)
The API returns 100 by default and up to 1000 patient merge records, sorted by updated_at ascending
Find the updated_at value from the last record in the response
Use that updated_at value as the since parameter in your next request
Repeat steps 2-4 to ingest updates until you receive an empty list

Important Notes:

The since parameter is inclusive, so you may receive the last record from the previous batch again (you can deduplicate by ID and version)
All patient merge records include updated_at, id, version, deactivated, and updating_user fields for tracking changes
Timestamps have millisecond resolution for precise ordering

Scans up to 1000 patient merge updates. The since query parameter is inclusive, and the result list is ordered by updatedAt ascending. **Polling Pattern:** To continuously poll for updates without gaps: 1. Make your initial request with a `since` timestamp (e.g., `since=2020-01-01T13:00:00.000Z`) 2. The API returns 100 by default and up to 1000 patient merge records, sorted by `updated_at` ascending 3. Find the `updated_at` value from the last record in the response 4. Use that `updated_at` value as the `since` parameter in your next request 5. Repeat steps 2-4 to ingest updates until you receive an empty list **Important Notes:** - The `since` parameter is inclusive, so you may receive the last record from the previous batch again (you can deduplicate by ID and version) - All patient merge records include `updated_at`, `id`, `version`, `deactivated`, and `updating_user` fields for tracking changes - Timestamps have millisecond resolution for precise ordering

Authentication

AuthorizationBearer

OAuth authentication of the form <token>.

Query parameters

sincedatetimeRequired

maxResultsintegerOptional

Response

This endpoint returns a list of objects.

alternative_patient_mrnstring

The MRN of the patient that was merged.

deactivatedboolean

True if the object is deactivated. Deactivated objects are not returned in search results but are returned in all other endpoints including scan.

idstring

The unique identifier for a PatientMerge record.

organization_idstring

The organization that owns this object.

primary_patient_mrnstring

The MRN of the patient that is getting a patient merged into them.

updated_atdatetime

updating_user_idstring

The user ID of the user who last updated the object.

versioninteger

The version of the object. Any update to any property of an object object will create a new version.