FHIR Integration Services
FHIR integration services for healthtech startups and digital health vendors: FHIR APIs, data mapping and validation between your product and clinical systems. We built the FHIR side of PENallergy✔ and AIDA.
What our FHIR integration work covers
FHIR gives you a standard way to read and write patient data. Making it work with real hospital data is the part that takes engineering.
FHIR APIs
Reading and writing FHIR R4 resources from EHRs, with the narrowest access your workflow needs. PENallergy✔ reads and writes AllergyIntolerance.
Data mapping
Your product's data model mapped to FHIR resources, with the mapping documented and versioned, not hidden in code.
Validation and error handling
Checks on structure, profiles, codes and business rules, with failed records kept visible so someone can fix them.
Profiles and implementation guides
US Core as the usual U.S. baseline, plus the implementation guides your use case and payers require.
Authorization
SMART on FHIR for apps with a user, backend services for system-to-system jobs.
Less work per hospital
Standard APIs mean less custom interface work behind each new customer. That is why AIDA was built on FHIR.
HL7 v2 interfaces and FHIR, side by side
Many hospitals still send admissions, orders and results as HL7 v2 messages, while newer data comes through FHIR APIs. Your product may need both for years.
- Receive HL7 v2Parse and route the messages hospitals already send.
- Normalize to FHIRTurn them into the same FHIR resources your product reads from the APIs.
- One model for your productYour team works with one data model, whatever the hospital sends.
How a FHIR integration project goes
- DiscoveryWhich data, which systems, which profiles, and what happens when data is wrong.
- Data model and mappingYour model mapped to FHIR, documented and versioned.
- Build and validateAPIs, connectors and validation, tested against EHR sandboxes.
- Connect each systemConfiguration and go-live with each customer's IT team.
- Monitor in productionFailed messages visible, fixed and re-sent by the same engineers.
Selected FHIR integration projects
A few examples from our case studies. Each product belongs to our client; we designed, built and support it. All case studies
Read more on FHIR integration
FHIR integration: questions
What product and engineering teams ask us before the first call.
What does a FHIR integration project include?
Discovery, a data model mapped to FHIR, the APIs and connectors, validation and error handling, go-live with each customer's systems, and support in production.
Do we need FHIR or HL7 v2?
Often both. Many hospitals still send admissions, orders and results as HL7 v2, while newer data and apps use FHIR APIs. We normalize both into one model for your product.
How do we choose a FHIR vendor?
Ask to see FHIR integrations running in production, not demos, and ask how the team handles bad data. We wrote down the questions we would ask any team in our article on choosing a FHIR development partner.
Who owns the integration?
You do. The code lives in your repository from the start, and you see working software in regular demos.
Need patient data to move in a standard format?
Book 30 minutes with Michael Nikitin, our CEO. Bring the systems you need to connect.