Claims Submission (beta)

Oystehr’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.

Mockup of a web page labeled "Billing Dashboard"

Claims Service 

You can leverage our claims service to automate data configuration to any biller to eliminate manual tasks in the billing process. 

How it works: 

The Oystehr Claims Service provides a robust API for users to seamlessly submit insurance claims. This service streamlines the process by wrapping key claims APIs and automatically generating FHIR resources to represent claims while accommodating different customer requirements within the EHR system.

What our Claims Service does: 

This service serves as a bridge within Oystehr, facilitating the submission of insurance claims. It allows users to:

  • Submit Professional Claims through seamless integration with a standardized claims API.
  • Create FHIR resources representing various components of a claim, such as patient, beneficiary, provider, etc., ensuring adherence to healthcare standards.
  • Enable a choice-based approach for users, allowing them to input data directly into a single Claim resource or reference existing FHIR resources when appropriate. This flexibility allows for efficient data handling and seamless resubmission of claims for the same patient without re-entering redundant information.

How you benefit:

By using Oystehr’s claims service, you can experience: 

  • Streamlined claim submission process - eliminates the need to manually handle the intricacies of various APIs and the creation of FHIR resources, saving time and effort
  • Adherence to healthcare standards: Ensures compliance with FHIR data models, enhancing interoperability and data consistency
  • Customizability and reusability: Allows users to efficiently manage claims by referencing existing FHIR resources, reducing redundancy and facilitating subsequent claims for the same patient. 
back to product page

Read more about other solutions

ONC compliance, HIPAA, and Soc 2 Type 1 badge

Compliance and Standards

Get FHIR, USCDI, ONC, X12 and HIPAA from the start. Health-tech software is highly regulated. Multiple organizations govern complicated, overlapping standards. Legislative and statutory mandates change regularly. Payers, states, and exchanges have their own requirements. Oystehr does the heavy lifting to ensure your application maintains compliance in a shifting landscape.

Read More
Mockup of a web page labeled "FHIR R4/R5"

Interoperability

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.

Read More
FHIR R4 and R5

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.

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