Interopion's Commitment to Standards
Interopion is fiercely committed to the health IT standards and we've designed that into interopiO at its core. All of interopiO's data APIs are implementations of FHIR and are designed by there very nature to not create vendor lock-in. By using interopiO, you are committing to the FHIR standard and not to proprietary interopiO APIs.
Supported Versions of FHIR
interopiO currently provides FHIR servers for the following versions of FHIR:
interopiO FHIR based Cloud CDR
Subscribers of interopiO can provision a cloud hosted FHIR CDR based on any of the major released versions of FHIR in a few clicks using interopiO's FHIR based Cloud CDR. Using interopiO's Gateway data routing capabilities, subscribers can route some data to their interopiO CDR and other data to external sources.
interopiO is an Integration Engine
Many EHR/EMR (or any clinical data source) provide some FHIR capabilities. Others provide proprietary APIs. Some offer only legacy integration approaches (such as HL7 v2 messaging or CDA document exchange). Most offer a combination of all three integration approaches. Further, each implement these integration approaches in unique ways. Even EHRs that claim to support specific FHIR® resources and operations on those resources actually do so in nuanced and unique ways. Using the combination of interopiO's Data Adapters, Gateways, and HL7 ingestion capabilities, Subscribers can using interopiO as a unified, faithful implementation of the FHIR specification and push the complexities introduced by all of the unique and proprietary approaches to data integration each EHR introduces.
interopiO can convert between different versions of FHIR, proprietary APIs and FHIR, HL7 messaging and FHIR, and much more.
Transform Any Data Source Into a FHIR Server
Using interopiO's Data Adapters library and SDK, subscribers of interopiO can transform any data source into a FHIR® Server fully capable of any of the types of operations and resources relevant to that data source.