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

Payment Notification

Overview

TBD

Workflow

1. Provider sends an Payment Notice Message to the nphies system.
2. nphies validates the message and if valid proceeds to Step 3 and return errors, otherwise proceeds to Step 2.
3. nphies stores the request message and returns an Acknowlegement Message indicating successful receipt of the PAyment Notice Message or errors to the provider.

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.

Message Structures

Payment Notice Message

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.

Nphies Bundle (.type = message )
  Nphies MessageHeader (.eventCoding = payment-notice)
  Nphies PaymentNotice 
  Nphies Organization (Provider)
  Nphies Organization (nphies)
  [any additional resources]

Acknowledgement Message

See Acknowledgement Message.

Guidance

TBD

Full Message Examples

Key Extensions

TBD

Error Handling

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.