FHIR R4/R5 APIs

Oystehr offers a comprehensive read/write FHIR API and hosted storage for both R4 and R5. It’s almost table-stakes, but because so few EHR vendors actually offer full, unrestricted FHIR access, it’s important. FHIR is the native data model of Oystehr, not a bolt-on afterthought. We support multiple versions of FHIR and an upgrade path as new versions are released. However, we view Oystehr as “more than just a FHIR store.” Offering direct FHIR access is critical for interoperability and implementing many workflows, but the real power of Oystehr’s FHIR API is that it is directly integrated with all our other service offerings. So, if you want to do an insurance validation, claims submission, order a diagnostic test, initiate a video telemed call, or support SMS or text chat, you can do so directly from Oystehr APIs and appropriate FHIR records are created.

FHIR R4 and R5
back to product page

Read more about other solutions

Mockup of a web page labeled "Zambda"

Custom Endpoints

Zambdas offers a powerful tool for tailoring your application without needing your own server. With Zambdas, you create custom API endpoints using your own custom code. Zambdas are hosted within your own segregated, provisioned environment within the Oystehr. This environment has direct access to Oystehr events and data, allowing you to create robust integrations and applications with server-side logic.

Read More
Mockup of a virtual call with a doctor

Telehealth

Configure HIPAA-compliant, customizable video workflows using Oystehr's telehealth service. Oystehr seamlessly provisions multi-party video access for you, no external account setup required, and associates it with appropriate FHIR resources.

Read More
Image of device with chat messages

Patient Messaging & Engagement

Like Oystehr’s video service, the messaging and engagement service offers comprehensive provisioned support for one way messaging and multi-party threaded two-way communications without requiring external account setup, configuration, or integration. Sending an SMS to patients is a single line API call, and complex, multi-party threaded communications with routing and promotion are also directly supported within the API.

Read More

Learn why healthcare orgs trust Oystehr as their health tech dev platform

Meet with our engineers
Quotation icon

Our new behavioral health intake application, built on Oystehr, allowed us to build a solution that is customized for our use including scheduling, insurance validation, and direct integration with our eClinicalWorks EHR.

Mordechai Raskas
Mordechai Raskas

Chief Medical Information Officer at PM Pediatric Care