Scan
Scans up to 1000 patient 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
sincetimestamp (e.g.,since=2020-01-01T13:00:00.000Z) - The API returns 100 by default and up to 1000 patient records, sorted by
updated_atascending - Find the
updated_atvalue from the last record in the response - Use that
updated_atvalue as thesinceparameter in your next request - Repeat steps 2-4 to ingest updates until you receive an empty list
Important Notes:
- The
sinceparameter is inclusive, so you may receive the last record from the previous batch again (you can deduplicate by ID and version) - All patient records include
updated_at,id,version,deactivated, andupdating_userfields for tracking changes - Timestamps have millisecond resolution for precise ordering
Authentication
OAuth authentication of the form <token>.
Query parameters
Response
The biological sex of the patient. This corresponds to the HL7 AdministrativeGender https://www.hl7.org/fhir/valueset-administrative-gender.html
The medical record number for the patient. Human-friendly Candid generated MRNs are of the form “YYMMDDXXXX”, where “YYMMDD” is the date of patient creation and “XXXX” is a zero-padded incrementing integer.
Custom key/value metadata attached to this patient, grouped by the MetadataSchema that defines the keys’ types. Configure schemas via the metadata-schemas API. Values are validated against the referenced schema on write.
ORCON (Originator Controlled) - When set to true, the Candid system will hide this patient from downstream integrations. Updates made in the Candid UI will unset this flag. Defaults to false.
Use electronic_communication_consent for granular channel-level consent. This field is kept in sync automatically but should not be used for new integrations.