Allscripts / Veradigm / Altera Integration
Integration consulting for the Allscripts product lineage — now split between Veradigm (Veradigm EHR, Practice Fusion, Veradigm Connect) and Altera Digital Health (TouchWorks, Sunrise, Paragon, Helios FHIR Platform). Unity API, FHIR R4, HL7 v2, marketplace apps, and migration support.
Unity API, FHIR R4, partner programs, and HL7 v2
Four integration surfaces spanning both vendors of record — Veradigm and Altera Digital Health. Pick the one that matches what you're building.
Unity API — the Allscripts-lineage integration surface
Unity API exposes clinical, scheduling, demographic, and practice management functions across the Allscripts product lineage. After the 2022 split, Unity exists as two separate surfaces — one operated by Veradigm (Veradigm EHR, Practice Fusion) and one operated by Altera (TouchWorks, Sunrise, Paragon). Both mix SOAP and REST endpoints with an action-based dispatch model that catches teams unfamiliar with the platform. We handle UnityToken authentication against either vendor, action mapping, per-customer rate-limit budgeting, and the long tail of edge cases — empty result handling, retry logic for transient HTTP 500s, audit logging.
- Unity API client development against Veradigm EHR or Altera TouchWorks / Sunrise
- UnityToken authentication + per-customer rate-limit handling (both vendors)
- Clinical data retrieval, scheduling, demographics, billing actions
- Custom middleware that fronts Unity for downstream consumers
FHIR R4 — Cures Act patient access + US Core
Both Veradigm and Altera offer FHIR R4 APIs to meet 21st Century Cures Act patient-access requirements. Veradigm exposes FHIR endpoints for Veradigm EHR and Practice Fusion. Altera offers FHIR through its Helios FHIR Platform across TouchWorks, Sunrise, and Paragon. Both implementations cover standard resources (Patient, Encounter, Condition, Observation, AllergyIntolerance, MedicationRequest, Procedure, DiagnosticReport, DocumentReference) conforming to US Core FHIR profiles. We build FHIR consumers, validate against profile conformance, handle OAuth 2.0 SMART app launch flows, and instrument the FHIR side of patient-data-portability use cases against either vendor.
- FHIR R4 client development against Veradigm or Altera Helios endpoints
- US Core conformance testing + vendor-specific extension handling
- SMART on FHIR app launch flows + OAuth 2.0 token handling
- Bulk FHIR export workflows for population-level data
Partner programs — Veradigm Connect + Altera developer paths
Two separate partner programs after the split. Veradigm Connect is the marketplace path for ISVs distributing into Veradigm-side customers (Veradigm EHR, Practice Fusion). Altera runs its own developer program for partners targeting TouchWorks, Sunrise, and Paragon customers. The technical requirements, certification gates, and marketplace mechanics are independent — a Veradigm Connect listing does not give you distribution into Altera products, and vice versa. We handle developer enrollment, sandbox provisioning, technical certification, and production-deployment readiness for whichever side fits your target customer base.
- Veradigm Connect enrollment + certification (Veradigm EHR, Practice Fusion)
- Altera developer program work for TouchWorks / Sunrise / Paragon ISVs
- Marketplace listing preparation + production rollout support
- Ongoing partner-program compliance for version migrations
HL7 v2 — the workhorse for clinical message flow
HL7 v2 interfaces remain the primary path for real-time clinical data exchange between Allscripts-lineage products and adjacent systems (labs, imaging, hospital ADT feeds, scheduling brokers, billing). We design v2 message specs, build the interfaces in Mirth Connect or your existing engine (Cloverleaf, Rhapsody, Corepoint), and validate against the message-structure quirks inherited from each product line — Altera TouchWorks and Sunrise have different segment expectations than Veradigm EHR and Practice Fusion, and the interface specs need to match the product you're talking to.
- HL7 v2 ADT, ORM, ORU, SIU, MDM, DFT interface development
- Mirth Connect channels purpose-built for Altera or Veradigm message structures
- Bidirectional interfaces with hospital ADT + lab + imaging systems
- Migration of legacy v2 interfaces during platform consolidation
Two vendors of record, one integration team
Saga IT is a healthcare IT consulting firm with deep experience across the Allscripts product lineage — the platforms that now sit with Veradigm (Veradigm EHR, Practice Fusion, Veradigm Connect Marketplace) and with Altera Digital Health (TouchWorks, Sunrise, Paragon, dbMotion, Helios FHIR Platform). We work both sides of the 2022 split: Unity API development against either vendor's surface, FHIR R4 for Cures Act patient access, HL7 v2 interfaces for real-time clinical message exchange, and partner-program builds — Veradigm Connect on the Veradigm side and Altera's developer program on the Altera side.
The Allscripts brand carried weight for two decades, so buyers still call these "Allscripts" platforms even when the legal entity behind the contract is now Altera or Veradigm. That's where most integration scoping goes wrong — assuming Veradigm Connect distributes to TouchWorks, or that Sunrise stayed with the rename, or that a single FHIR endpoint covers both portfolios. We map each product you run to its current vendor-of-record before any technical design starts, so the integration plan accounts for the right partner program, the right API surface, and the right roadmap.
Allscripts-Lineage Integration Services
End-to-end connectivity across both vendors of record — from Unity API and FHIR R4 development to HL7 v2 interfaces, Veradigm Connect + Altera partner-program work, data migration, and production managed services.
Unity API client + middleware development
Build robust Unity API clients against either vendor's Unity surface — Veradigm-side (Veradigm EHR, Practice Fusion) or Altera-side (TouchWorks, Sunrise, Paragon). We handle UnityToken authentication, per-customer rate-limit budgeting, action-based dispatch, and the long tail of edge cases that come from a 20-year-old API surface — empty-set responses, transient HTTP 500s during platform updates, schema variations between customer instances. Every integration includes structured logging, audit trail, retry logic, and dead-letter queueing for production reliability.
- Unity API
- Veradigm EHR
- Altera TouchWorks
- Middleware
- UnityToken authentication against either Veradigm or Altera Unity
- Action mapping across hundreds of Unity API actions (clinical, financial, scheduling)
- Per-customer rate-limit budgeting + backoff/retry behavior
- Custom middleware that fronts Unity for downstream consumers
- Production-grade reliability: audit logs, dead-letter queues, retries
FHIR R4 development — Veradigm + Altera Helios
Develop against either FHIR R4 surface across the Allscripts lineage — Veradigm's FHIR endpoints for Veradigm EHR and Practice Fusion, or Altera's Helios FHIR Platform for TouchWorks, Sunrise, and Paragon. We implement FHIR resources including Patient, Encounter, Observation, Condition, AllergyIntolerance, MedicationRequest, Procedure, DiagnosticReport, and DocumentReference with US Core profile conformance. Both vendors' FHIR capabilities support the patient-access use case mandated by the 21st Century Cures Act and provider-to-provider data exchange through interoperability frameworks.
- FHIR R4
- US Core
- Helios FHIR
- Bulk FHIR
- FHIR resource coverage: Patient, Encounter, Observation, Condition, AllergyIntolerance, MedicationRequest
- US Core profile conformance + vendor-specific extension handling
- 21st Century Cures Act patient-access compliance builds
- SMART on FHIR app launch flows + OAuth 2.0 token handling
- Bulk FHIR export for population-level data extraction
Partner-program enrollment + certification
Two separate partner-program paths after the 2022 split. Veradigm Connect distributes apps to Veradigm EHR and Practice Fusion customers — the supported revenue path for ISVs targeting those products. Altera runs its own developer program for TouchWorks, Sunrise, and Paragon customers. We handle developer enrollment, sandbox provisioning, technical certification, and production-deployment readiness for whichever side fits your target customer base. The certification gate has real technical requirements at each vendor that we work through as part of the build, not as an afterthought.
- Veradigm Connect
- Altera dev program
- Certification
- ISV-ready
- Veradigm Connect developer enrollment + sandbox setup (Veradigm-side)
- Altera developer program work for TouchWorks / Sunrise / Paragon ISVs
- Integration certification against each vendor's technical requirements
- Marketplace listing preparation + go-to-market collateral
- Ongoing partner-program compliance for version migrations
HL7 v2 interfaces across Veradigm + Altera
Build and maintain HL7 v2 interfaces for Allscripts-lineage environments including ADT feeds, ORM/ORC order messages, ORU lab results, SIU scheduling updates, MDM clinical document notifications, and DFT financial transactions. We configure bidirectional v2 flows between Veradigm EHR, Altera TouchWorks, or Altera Sunrise and adjacent systems (labs, imaging, pharmacies, hospital ADT feeds) using Mirth Connect or your existing integration engine. Interfaces include message validation, ack/nack handling, error queueing, and monitoring — with channel mappings tuned to each vendor's segment expectations.
- Mirth Connect
- ADT · ORM · ORU
- Bidirectional
- Monitoring
- Message-type coverage: ADT, ORM/ORC, ORU, SIU, MDM, DFT against either vendor
- Mirth Connect channel development with Veradigm- or Altera-specific field mappings
- Bidirectional flows: orders out, results in, document acknowledgment
- Message validation + ack/nack handling + dead-letter queueing
- Production monitoring + alerting on message-level SLAs
Allscripts-lineage data migration + go-live
Migrate clinical, demographic, and financial data into or out of any Allscripts-lineage product with comprehensive data mapping, terminology normalization, and validation workflows. We support both directions: bringing data INTO Veradigm EHR or Altera TouchWorks/Sunrise from legacy systems during platform consolidations, and extracting data OUT for organizations migrating to Epic, athenahealth, or other ambulatory platforms. Migrations preserve historical patient records, clinical documentation, and billing history while ensuring data integrity across the transition.
- Schema mapping
- Reconciliation
- Go-live ops
- Bidirectional
- Clinical + demographic + financial data extraction from source EHR
- Terminology normalization to or from vendor-specific code sets
- Interface activation sequencing for coordinated go-live
- Parallel-run testing window with reconciliation reporting
- Post-migration monitoring + stabilization support
Allscripts-lineage managed services
Production interface and integration management for organizations running Veradigm or Altera products but lacking in-house healthcare integration engineering capacity. We monitor interface health, respond to alerts, resolve message-level failures, manage version upgrades on either vendor's release cadence, and provide on-call support against message-criticality SLAs. The managed-services model gives ambulatory practices and health systems a dedicated integration team without the cost of building one internally.
- 24x7 SLA
- Version upgrades
- Health reviews
- Fractional team
- 24x7 monitoring across Unity, FHIR, and HL7 v2 interfaces
- On-call coverage with message-criticality-tiered SLAs
- Version-upgrade coordination during Veradigm or Altera platform releases
- Quarterly health reviews + integration roadmap recommendations
- Provider-side fractional engineering for ongoing integration work
Ambulatory Workflows We've Built
Allscripts-lineage products live in specialty groups, faculty practices, FQHC networks, and hospital ambulatory operations. These are the kinds of integration projects we ship across Veradigm and Altera environments.
Unified care coordination across specialties
A 30-provider multi-specialty group running Altera TouchWorks needed coordinated care across cardiology, orthopedics, and primary care — three departments that historically operated as separate documentation silos. We built a SMART on FHIR coordination app embedded inside TouchWorks that surfaces cross-specialty referrals, shared problem lists, and pending consult notes. The integration uses Altera's Helios FHIR Platform for clinical data and Unity API for the scheduling and referral-routing flows. Result: referral leakage dropped because providers stopped having to ask 'has the patient been seen by cardiology?' and instead saw it directly in their TouchWorks chart.
Veradigm Connect marketplace app for Veradigm EHR customers
A digital health startup needed to distribute its chronic-condition management app to Veradigm EHR (formerly Professional EHR) customers through the Veradigm Connect marketplace. We handled Veradigm partner enrollment, built the Unity API integration for patient demographics and care plan writeback, developed the FHIR R4 read flows for clinical context, ran the company through the Veradigm certification gate, and supported the marketplace listing rollout. The startup went from zero Veradigm deployments to a published Veradigm Connect partner over the course of one engagement, with the technical certification artifacts to support distribution into the Veradigm-side provider network.
UDS automation + state HIE connectivity
A four-site Federally Qualified Health Center (FQHC) network running Veradigm EHR (rebranded Allscripts Professional EHR) needed automated UDS reporting for HRSA submission plus connectivity to the state Health Information Exchange. We built a FHIR R4 ETL pipeline that aggregates clinical, demographic, and visit data from each Veradigm EHR instance into a centralized data warehouse for UDS measure calculation. Simultaneously we configured outbound HL7 v2 ADT and ORU interfaces to the state HIE, enabling Federal-grant compliance and population-health data exchange with hospital systems. Manual chart abstraction time for UDS reporting collapsed from weeks per cycle to hours.
Multi-vendor interoperability bridge
A health system running Altera Sunrise for its hospital operations and Epic for an affiliated ambulatory group needed bidirectional data exchange between the two — Care Everywhere on the Epic side, FHIR R4 on the Sunrise side via the Helios FHIR Platform. We built the HL7 v2 ADT bridge between the two systems, configured the FHIR R4 patient-record query workflows, and managed the consent and policy work for cross-organization records exchange. Result: clinicians stopped logging into two EHRs to chase down patient histories; primary care notes and acute-care discharge summaries surface in both systems for the same patient encounter.
Veradigm EHR vs Altera TouchWorks vs Altera Sunrise
The Allscripts product lineage now sits with two separate vendors. Understanding which one owns each product determines the partner program, API surface, and roadmap dependencies for your integration.
| Feature | Veradigm EHR | Altera TouchWorks | Altera Sunrise |
|---|---|---|---|
| Vendor of record | Veradigm Inc. | Altera Digital Health (Harris) | Altera Digital Health (Harris) |
| Former name | Allscripts Professional EHR | Allscripts TouchWorks EHR | Allscripts Sunrise |
| Target market | Small to mid-size ambulatory practices | Large multi-specialty + faculty practice | Hospital + health-system ambulatory |
| Unity API surface | |||
| Native API alternative | — | — | Sunrise Web Services |
| FHIR R4 (US Core) | |||
| FHIR platform | Veradigm FHIR endpoints | Altera Helios FHIR Platform | Altera Helios FHIR Platform |
| HL7 v2 | |||
| Veradigm Connect eligible | |||
| Altera developer program | |||
| Typical interface engine | Mirth / Rhapsody | Mirth / Cloverleaf | Health-system standard |
Allscripts / Veradigm Integration Lifecycle
Every engagement follows a structured, five-phase approach — assessment through go-live and stabilization. Most projects take 14-22 weeks end-to-end depending on integration surface and scope.
Assessment & Discovery
We evaluate your Allscripts-lineage environment — Veradigm EHR (formerly Professional EHR) or Practice Fusion on the Veradigm side; TouchWorks, Sunrise, or Paragon on the Altera Digital Health side — and map clinical workflows, integration points, Unity API availability, FHIR R4 surface, and third-party dependencies. The 2022 Harris divestiture and 2023 Allscripts → Veradigm rename split products across two separate companies with independent partner programs and roadmaps. Step one of every engagement is mapping each product you run to its current vendor-of-record, because the wrong assumption ("Veradigm Connect distributes to TouchWorks") costs weeks once it hits the certification gate.
Integration Design
Detailed technical design covering Unity API endpoint selection (vendor-specific — Veradigm and Altera operate separate Unity surfaces), FHIR R4 resource scope, HL7 v2 interface specs, data mapping documents, and authentication flows (UnityToken, OAuth 2.0). For multi-site deployments we account for hosting differences — Veradigm has been migrating customers between on-prem and its Microsoft-Azure-backed Veradigm Cloud; Altera maintains its own hosted-services footprint for Sunrise and TouchWorks. The wrong hosting assumption can break integration patterns that worked in test.
Development & Build
Iterative development of integrations against whichever vendor owns the target product: Unity API consumers (Veradigm or Altera surface), FHIR R4 clients (Veradigm Patient Access API or Altera Helios FHIR Platform), HL7 v2 interfaces through Mirth Connect or your existing engine, custom middleware, and partner-program apps — Veradigm Connect for Veradigm-side ISVs or Altera's developer program for Altera-side ISVs. We build in vendor sandbox environments, validate against real ambulatory data structures, and instrument retry, error-queue, and audit-log behavior from day one rather than retrofitting it for go-live.
Testing & Validation
End-to-end testing across all integration touchpoints. Validation includes Unity API rate-limit behavior (both vendors enforce per-customer quotas that catch new teams off guard), HL7 v2 ack/nak handling against TouchWorks and Sunrise interface engines (Altera) or Veradigm EHR interfaces, FHIR conformance against US Core profiles, and parallel-data runs against production-equivalent volumes before any go-live activation. We validate not just that the integration works — but that it degrades gracefully when Unity returns a 500 or FHIR returns malformed data.
Go-Live & Stabilization
Production deployment with coordinated interface activation, real-time monitoring, and on-call support during the critical go-live period. We manage the cutover sequence, validate message flow in production, resolve data discrepancies, and provide stabilization support until all interfaces are running cleanly and ambulatory workflows are confirmed operational across your Veradigm or Altera environment.
Allscripts-Lineage Integration in Action
Real engagements spanning both vendors — Altera TouchWorks Unity API integrations, Altera Sunrise FHIR R4 work via Helios, Veradigm Connect marketplace builds, and HL7 v2 interface development.
Altera TouchWorks Specialty Coordination · Multi-Specialty Group
A 30-provider multi-specialty practice running Altera TouchWorks needed a custom care-coordination app for cross-specialty referrals and shared problem lists. We built a SMART on FHIR app using Altera's Helios FHIR Platform + Unity API, with HL7 v2 ADT/MDM feeds for clinical context.
scopes: "Patient + ServiceRequest"
specialties: 5
from: "primary",
to: "specialty"
})
Building an Allscripts-lineage integration — Veradigm EHR, Altera TouchWorks, Altera Sunrise, Unity API, FHIR R4, HL7 v2, or Veradigm Connect marketplace? Let's scope your project.
Talk to a Veradigm / Altera SpecialistCommon Questions
Both. In mid-2022, Allscripts Healthcare Solutions sold its Hospitals & Large Physician Practices business segment to Harris Computer (a subsidiary of Constellation Software). That divested segment became Altera Digital Health and took TouchWorks EHR, Sunrise, Paragon, dbMotion, and the Helios FHIR Platform with it. The remaining Allscripts entity — the small/mid-size ambulatory products plus the payer-side data and analytics businesses — renamed itself to Veradigm Inc. in January 2023. So today, products that were sold under the Allscripts brand for years now sit with two completely separate companies, each with its own API surface, partner program, and roadmap. Most customers still say "we use Allscripts" because the brand carried weight for two decades; the integration work begins by mapping each product you run to its current vendor-of-record.
Veradigm: Veradigm EHR (rebranded Allscripts Professional EHR), Practice Fusion, Allscripts Practice Management, Veradigm Connect Marketplace, plus the payer/life-sciences data and analytics businesses that drive most of Veradigm's revenue. Their Unity API surface covers Veradigm EHR and Practice Fusion. Altera Digital Health: TouchWorks EHR, Sunrise (acute care + the ambulatory modules used in hospital-employed clinics), Paragon (community-hospital EHR), dbMotion (HIE / population health), Helios FHIR Platform, EPSi (financial decision support). Altera operates its own Unity API surface, its own FHIR endpoints, and its own partner programs. Veradigm Connect does not distribute apps into Altera products. If a buyer says "we run Allscripts TouchWorks," that's an Altera engagement, not a Veradigm one — and getting that wrong at scoping costs weeks.
Yes — TouchWorks EHR is actively supported, but under Altera Digital Health, not Veradigm. Harris Computer's hold-and-maintain operating model means Altera's products are kept on a supported release cadence rather than being sunset. TouchWorks serves large multi-specialty groups, faculty practice plans, and health-system-owned ambulatory networks. Integration today uses Altera's Unity API surface for clinical/scheduling work, Altera's FHIR R4 endpoints (often via the Helios FHIR Platform) for patient access and SMART app launch, and HL7 v2 interfaces routed through Mirth Connect or the customer's existing integration engine. Saga IT works on TouchWorks integrations and also helps organizations evaluating a platform migration to Epic, athenahealth, or eClinicalWorks scope the data-migration and interface-cutover work.
Veradigm Connect is Veradigm's marketplace and partner program for ISVs distributing into the Veradigm-side ambulatory provider network — meaning Veradigm EHR (the rebranded Professional EHR) and Practice Fusion customers. Through Connect, partners get developer enrollment, sandbox environments, technical certification, and a marketplace listing. It's analogous to Epic's App Orchard or athenahealth's Marketplace. Important: Veradigm Connect does not apply to Altera products (TouchWorks, Sunrise, Paragon). ISVs targeting TouchWorks customers need to work through Altera's developer program separately. We handle Veradigm Connect enrollment, certification, and listing for Veradigm-side builds — and we handle Altera-side partner work as a separate engagement when the target product is on the Altera roadmap.
The entire Sunrise product line — acute care EHR plus the ambulatory modules that hospital-employed providers use inside a Sunrise deployment — went to Altera Digital Health in the 2022 divestiture. "Sunrise Ambulatory" is not a separate product that stayed with Veradigm; it's a workflow inside the Altera Sunrise platform. If you're scoping Sunrise integration, you're scoping an Altera engagement. Sunrise has had a publicly-announced AI partnership with Microsoft (Altera's investment in the platform continues post-divestiture), so the platform is not a maintenance-only product — but the contractual path, partner program, and technical surface are all Altera, not Veradigm.
End-to-end work for any integration that connects a Veradigm or Altera product to another system. That includes Unity API client development against either vendor's API surface, FHIR R4 app builds for Cures Act patient access, HL7 v2 interface configuration on Mirth Connect or your existing engine, Veradigm Connect partner-program enrollment and certification (Veradigm-side), Altera partner-program work (Altera-side), custom middleware, data migration from legacy EHRs into or out of these products, and ongoing managed services for production interface monitoring. We work as either a vendor-side partner (one integration end-to-end) or a provider-side partner (acting as the customer's integration engineering team across multiple vendors). Because we work both sides of the Allscripts split, we can also help organizations untangle which legacy contracts apply to which products before scoping integration.
Related Services
We Integrate With All Major EHRs
Keep reading
Related resources
Talk to a Veradigm / Altera Specialist
From Unity API integrations to Veradigm Connect partner enrollment and Altera Helios FHIR builds — let's scope your engagement in 30 minutes.
- 15 min conversation
- Healthcare IT engineers, not sales
- Reply within one business day
Book a 30-min call · or email us and we'll reply within one business day.