Allscripts FHIR Integration: Veradigm and Altera EHR APIs Explained

Older documentation, code samples and even some developer portal URLs still use the Allscripts name. When a partner says they have ‘Allscripts experience’, ask which product and which side of the split.

Veradigm’s developer portal documents its FHIR APIs and a registration process with distinct steps:

1. Review the API documentation.
2. Register the app, choosing an app type (Patient, Provider or System), purpose of use and matching scopes.
3. Request sandbox credentials and test.
4. Request production access once testing is complete.
5. Be licensed by client organizations. Veradigm states patient apps are licensed automatically, while provider and system apps are licensed by each client.

Veradigm documents FHIR R4 support aligned with USCDI and US Core (it lists US Core 3.1.1 and 6.1), states that DSTU2 is no longer supported, and describes FHIR access as read-only. Write-back and practice management integration use Veradigm’s proprietary Unity API.

GET [base]/metadata
Accept: application/fhir+json

Altera Digital Health now owns Sunrise, Paragon and TouchWorks. Some FHIR documentation for these products was historically published alongside Veradigm’s, and FHIR API support and launch capabilities differ by product. Confirm with Altera which developer program, portal and documentation currently apply to the product your customer runs, and whether the use case you need (for example SMART launch inside the EHR or write-back) is supported for that product and version.

On Veradigm EHR, a common architecture reads clinical data through FHIR R4 and uses the Unity API for operations FHIR does not cover, such as write-back and practice management functions. This keeps standards-based reads portable to other EHRs while isolating proprietary calls behind an adapter.

• Keep a single internal data model and map both FHIR and Unity payloads into it.
• Isolate Unity-specific code so it can be replaced if FHIR write support expands.
• Test how and when data written through Unity appears in subsequent FHIR reads.

Our FHIR API integration guide discusses adapter patterns for hybrid integrations.

• Patient-facing apps reading US Core data through FHIR with patient authorization; on Veradigm EHR these are licensed automatically.
• Provider-facing apps that read clinical data via FHIR, with launch and SSO options depending on the product. Check product-specific SMART support; see our SMART on FHIR guide.
• System integrations using backend authorization with a signed client assertion for read access, combined with Unity API (Veradigm) or other interfaces for writes.
• HL7 v2 interfaces for real-time events, especially at Altera hospital sites.

• Veradigm documents its FHIR APIs as read-only; writes need Unity or other interfaces.
• Product ownership changes mean documentation and support routes may differ from older guidance.
• Provider and system apps require licensing by each client organization.
• Feature support differs significantly between Veradigm EHR and the Altera products.

Timelines depend mainly on which product you target, whether you need write-back (and therefore Unity or other interfaces), and how quickly each client licenses provider or system apps. See FHIR integration cost for planning.

• Which specific products (Veradigm EHR, Sunrise, Paragon, TouchWorks) have you integrated with since the 2022 divestiture?
• Have you used the Unity API for write-back, and how do you combine it with FHIR reads?
• How do you manage client licensing and onboarding?
• How will you track documentation and program changes on both the Veradigm and Altera sides?

Browse EHR integration vendors filtered by Allscripts / Altera.