Veradigm (Allscripts)
Access
Section titled “Access”- Register through Veradigm’s developer portal; endpoints are listed in a public directory.
- SMART Backend Services with a JWT,
system/*.readscopes, base and token URLs per practice.
Extraction approach
Section titled “Extraction approach”In practice the data has arrived as Bulk Data export files delivered by the practice (over SFTP or upload) rather than pulled live:
- Files are per-resource NDJSON shards in lower case (
patient_013.ndjson, …), sometimes nested one directory down. - Route each line by its own
resourceTyperather than trusting the file name, since there can be many shards per type. - Inject missing reference
types. - Scope the panel to encounters with a provider that has an NPI — skipping that step if no NPI provider is found at all.
Known behaviour
Section titled “Known behaviour”Unlike Practice Fusion, screening reports arrive as real DiagnosticReport resources. Do not
apply a “screenings stored as Conditions” workaround here, or you will double-count numerator hits.
Status
Section titled “Status”The live API connection is registered but has had little production use, so contributions from teams pulling from Veradigm live are especially welcome.