Healthcare Financial Services IG Edition 1 - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This use case enables Healthcare Providers (HCPs) to notify nphies that a submitted Payment Reconciliation has been received and the corresponding payment has been processed by the HIC. The Payment Notice serves as a confirmation message from the HCP acknowledging receipt of the payment. The service also supports linking the notice to an existing Payment Reconciliation for traceability, reconciliation and regulatory purposes.
This is a REAL TIME use case. In addition to returning the aknowledgement, nphies will provide the Meta Tag: queued-messages should any messages remain in the queue.
The key resources for the message are provided below and all require nphies-profiled resources as provided in the Artifacts. Note: the MessageHeader resource must be the first .entry in the bundle and any other resources may follow in any order.
Providers SHALL submit a PaymentNotice message to nphies only after receiving the actual payment in their bank account regarding a Payment Reconciliation. This supports accurate tracking of payments made by insurers and supports identify missing payments.
See also: Information Guides.
Example | Description |
---|---|
Example #1 | Full message for Payment Notice. |
Example #1 Acknowledgement | An Acknowledgement response indicating message was received and understood or was with errors. |
None to report.
If nphies detects errors in the request message such that the request cannot be processed then the response message will contain an OperationOutcome resource rather than a business-level Poll Response resource. Otherwise if nphies detects errors within the request it will return a Poll Response with errors (Task.output.type = 'error') and an extension indicating where the error occurred.
Like all other response messages the provider receives from nphies, if there are other messages queued at nphies which have not been delivered to the provider then this will be reflected in the presence of a MessageHeader.meta.tag.