PaymentNotice
This resource provides the status of the payment for goods and services rendered, and the request and response resource references.
- Schema
- Usage
- Relationships
Elements
Name | Required | Type | Description |
---|---|---|---|
identifier | Identifier[] | Business Identifier for the payment noctice DetailsA unique identifier assigned to this payment notice. | |
status | ✓ | code | active | cancelled | draft | entered-in-error DetailsThe status of the resource instance. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
request | Reference<Resource> | Request reference DetailsReference of resource for which payment is being made. | |
response | Reference<Resource> | Response reference DetailsReference of response to resource for which payment is being made. | |
created | ✓ | dateTime | Creation date DetailsThe date when this resource was created. |
provider | Reference< Practitioner | PractitionerRole | Organization > | Responsible practitioner DetailsThe practitioner who is responsible for the services rendered to the patient. | |
payment | ✓ | Reference<PaymentReconciliation> | Payment reference DetailsA reference to the payment which is the subject of this notice. |
paymentDate | date | Payment or clearing date DetailsThe date when the above payment action occurred. | |
payee | Reference< Practitioner | PractitionerRole | Organization > | Party being paid DetailsThe party who will receive or has received payment that is the subject of this notification. | |
recipient | ✓ | Reference<Organization> | Party being notified DetailsThe party who is notified of the payment status. |
amount | ✓ | Money | Monetary amount of the payment DetailsThe amount sent to the payee. |
paymentStatus | CodeableConcept | Issued or cleared Status of the payment DetailsA code indicating whether payment has been sent or cleared. Typically paid: payment sent, cleared: payment received. |
Search Parameters
Name | Type | Description | Expression |
---|---|---|---|
created | date | Creation date fro the notice | PaymentNotice.created |
identifier | token | The business identifier of the notice | PaymentNotice.identifier |
payment-status | token | The type of payment notice | PaymentNotice.paymentStatus |
provider | reference | The reference to the provider | PaymentNotice.provider |
request | reference | The Claim | PaymentNotice.request |
response | reference | The ClaimResponse | PaymentNotice.response |
status | token | The status of the payment notice | PaymentNotice.status |
Inherited Elements
Name | Required | Type | Description |
---|---|---|---|
id | string | Logical id of this artifact DetailsThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | |
meta | Meta | Metadata about the resource DetailsThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |
implicitRules | uri | A set of rules under which this content was created DetailsA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. | |
language | code | Language of the resource content DetailsThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | |
text | Narrative | Text summary of the resource, for human interpretation DetailsA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | |
contained | Resource[] | Contained, inline Resources DetailsThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. | |
extension | Extension[] | Additional content defined by implementations DetailsMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
modifierExtension | Extension[] | Extensions that cannot be ignored DetailsMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
The PaymentNotice resource indicates the resource for which the payment has been indicated and reports the current status information of that payment. The payment notice may be used by providers and payers to advise the provider or regulatory bodies of the state of a payment (check in the mail/EFT sent, payment cashed, payment canceled). Employers or Insurance Exchanges may use this to advise payers of premium payment.
Payers and/or providers may have the need to advise providers and/or regulators of the status of claim settlement and payment completion. This same resource may be used by employers and insurance exchanges to advise payers that premium payments have been issued and settled.
The PaymentNotice resource is a "event" resource from a FHIR workflow perspective - see Workflow Event.
Additional Information
Additional information regarding electronic payment notice content and usage may be found at:
- Financial Resource Status Lifecycle: how .status is used in the financial resources.
- Batches: how eClaims may handle batches of eligibility, claims, payments and responses.
The PaymentNotice resource is used to indicate that a payment is, or is about to occur. The resource is used commonly when tracking of payment occurences is required for regulatory or business purposes, such as ensuring that payment of claim adjudications occurs within a specific timeframe. The PaymentNotice is not used to report adjudicated amounts (see ClaimResponse) or to reconcile adjudicated amounts against actual payment (see PaymentReconciliation)
The ClaimResponse resource is an insurer's adjudication and/or authorization of a set of healthcare-related goods and services for a patient against the patient's insurance coverages and does not indicate that payment has occured.
The PaymentReconciliation resource serves to correlate payment amounts to the adjudicated claim amounts appearing on one or more ClaimResponses.
The eClaim domain includes a number of related resources
PaymentNotice | An indication that a payment has occured, is about to occur, or has been cancelled. |
ClaimResponse | A payor's adjudication and/or authorization response to the suite of services provided in a Claim. Typically the ClaimResponse references the Claim but does not duplicate the clinical or financial information provided in the claim. |
PaymentReconciliation | Provides the bulk payment details associated with a payment by the payor for goods and services rendered by a provider to patients covered by insurance plans offered by that payor. |