Oystehr is an API-first solution. You can invoke Oystehr APIs entirely a la carte. There is no data silo, no obligation to use any particular front-end. You can use our open-source EHR or not. You can maintain your own database or not. You can build an application entirely on Oystehr’s hosted infrastructure or interact strictly with the APIs you need statelessly. You can create inbound Zambdas (serverless hosted functions) that accept invocations from external systems, and you can create outbound Zambas that listen for Oystehr events and push data to external systems. You will not experience the restrictions on external integrations that monolithic EHRs impose.
We offer single sign-on capabilities, allowing you to streamline access to your systems.
We prioritize interoperability by leveraging modern healthcare language standards such as FHIR R4, R5, and SMART on FHIR*.
FHIR is the growing standard for modeling and exchanging healthcare data electronically. Many EHRs, payer systems, and other healthcare products either already support or are adding support for sending and receiving data following the FHIR standard.
FHIR has resources like Patients, Practitioners, Schedules, and Encounters. These resources store health information.
The standard was created to give disparate healthcare systems with proprietary data models a common language for communicating healthcare data to improve interoperability. Existing players have to maintain their proprietary data models as well as a mapping to and from FHIR to facilitate interoperability. With Oystehr, you use FHIR as your data model from the start, removing the entire cost center of mapping into and out of FHIR.
Oystehr is built on top of FHIR, meaning medical resources are stored in FHIR. This comes with many benefits:
Check out our docs for more information.
* SMART on FHIR Coming Q1 2024
Like all Oystehr services, you are welcome to use your own payment processor, but Oystehr provides a payment processing solution powered by Stripe that allows you, without any additional account creation or integration effort, to immediately process payments from patients. We aggregate all payment activity through our service to leverage better processing rates with volume, which we directly pass on to Oystehr users. Like all Oystehr services, the payment processing API integrates automatically with our FHIR datastore to facilitate tracking and association of co-pays, claims submission, billing services, and other RCM activities.
Read MoreOystehr’s claims submission service allows you to directly submit claims to any payer. You don’t need to contract for or configure a clearinghouse or otherwise arrange for external accounts and access to process submissions, Oystehr handles all of that under the hood.
Read MoreOystehr’s insurance validation service allows you to directly submit patient insurance information for real-time validation from payers.
Read MoreOur 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.
Chief Medical Information Officer at PM Pediatric Care