Scan

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