Syndech builds and operates the exchange layer between care organizations, state systems, and EHRs: FHIR R4 APIs, HL7 v2.x interfaces, and C-CDA document exchange, secured with SMART on FHIR, OAuth 2.0, and OIDC. Our first product, EVV Bridge, automates EVV transmission for home care agencies.
Pick the interface that matches the system on the other end. Every path lands in the same validated, audited pipeline.
RESTful exchange of resources such as Patient, Encounter, Practitioner, and Observation, with Bulk FHIR for population-scale export.
Message-based integration with systems that speak HL7 v2 over MLLP or HTTPS.
Structured clinical documents for transitions of care and referrals.
What each standard is, and how Syndech uses it.
HL7's current REST-and-JSON standard for exchanging healthcare resources.
How we use itSyndech exposes and consumes FHIR R4 endpoints for patient, encounter, and observation data, and designs new integrations FHIR-first.
R4 · REST · JSONThe FHIR Bulk Data Access specification for exporting large populations as NDJSON.
How we use itSupports $export-style bulk pulls where a partner needs a full population rather than record-by-record queries.
$export · NDJSONUS Core is the FHIR profile set that implements the USCDI data classes required of certified US health IT.
How we use itSyndech maps to US Core profiles when exchanging with certified EHRs so the data classes line up on both sides.
USCDI profilesAn authorization framework layering OAuth 2.0 and OpenID Connect over FHIR with scoped access.
How we use itSyndech's APIs use OAuth 2.0 and OIDC with SMART scopes, so partners authorize access the same way they do with an EHR.
OAuth 2.0 · OIDC · scopesThe long-standing message standard most hospital and agency systems still speak.
How we use itSyndech supports ADT, ORM, and ORU message flows over MLLP or HTTPS with mapping and ACK handling built in.
ADT · ORM · ORUHL7's XML document standard for clinical summaries and transitions of care.
How we use itSyndech generates and parses C-CDA documents for referrals and care summaries and validates them against the schema.
XML · CCD · Referral NoteSyndech designs its exchange services to align with these frameworks' data and trust requirements, so connecting through a participating partner is a configuration step rather than a rebuild.
An interoperability framework connecting health data networks under a common trust agreement.
A nationwide network for patient identity and record location across vendors.
The largest public–private health information network in the US, spanning federal agencies and HIEs.
ONC's Trusted Exchange Framework and Common Agreement, connecting Qualified Health Information Networks.
Syndech is not a member, implementer, or QHIN of these networks. We build to their published data and trust requirements.
Every request is authenticated with scoped tokens, every record is logged, and every transmission is encrypted end to end. Your team keeps ownership of its data; Syndech operates the exchange.
EVV Bridge runs on this exchange layer, purpose-built for home care agencies that need visit data delivered to state aggregators.
EVV Bridge ingests visit data, validates it against state-specific rules, normalizes it to the aggregator's format, and transmits it in near real-time to state aggregators, starting with Sandata and HHAeXchange.
Describe the systems on each side and the data that needs to move. An engineer replies within 24 hours.