📄️ New
When a claim is created, an EHR generates a new message and sends it outbound. To create a claim, an application can similarly produce and post a New message inbound to the EHR.
📄️ Submission Batch
The SubmissionBatch message is used to send a payment request, typically from a healthcare provider to an insurer. It functions similarly to the Submission Event, but allows for multiple transactions to be sent in a batch for more efficient processing.
📄️ Claims Query
Using the given filter criteria, this query may be used to obtain claims. The QueryResponse event type specifies the format of the response.
📄️ Payment Batch
The PaymentBatch message is utilized to send a payment notification, typically from a payer to a healthcare provider, though it can also be used in other scenarios where funds are transferred between parties. This message is functionally similar to the Payment Event, but enables multiple transactions to be transmitted in a batch.
📄️ Claims QueryResponse
This is the format of the response you will get for a ClaimsQuery event.
📄️ Submission
The Submission message is employed to transmit a payment request, typically from a healthcare provider to an insurer. It is commonly transmitted as an EDI 837 form by healthcare providers.
📄️ Claim Update
When a claim is updated in an Electronic Health Record (EHR), an outbound Update message is generated and sent. Conversely, an application can generate an inbound Update message to the EHR in order to update a claim.
📄️ Payment
A Payment message is employed to transmit a payment notification, usually from a payer to a healthcare provider, although it may also be used in other scenarios where funds are transferred between parties.
📄️ Notes Query
The specified filter criteria can be utilized with this query to retrieve notes, and the format of the response adheres to the QueryResponse event type.
📄️ Notes QueryResponse
This is the format of the response you will receive for a Claims:NotesQuery.