FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

13.8 Resource PaymentNotice - Content

Financial Management icon Work GroupMaturity Level: 4 Trial UseSecurity Category: Patient Compartments: Practitioner

This resource provides the status of the payment for goods and services rendered, and the request and response resource references.

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 regarding electronic payment notice content and usage may be found at:

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.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. PaymentNotice TUDomainResourcePaymentNotice request

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier 0..*IdentifierBusiness Identifier for the payment notice

... status ?!Σ1..1codeactive | cancelled | draft | entered-in-error
Binding: Financial Resource Status Codes (Required)
... request 0..1Reference(Any)Request reference
... created Σ1..1dateTimeCreation date
... reporter 0..1Reference(Practitioner | PractitionerRole | Organization)Responsible practitioner
... payment Σ0..1Reference(PaymentReconciliation)Payment reference
... paymentDate 0..1datePayment or clearing date
... payee 0..1Reference(Practitioner | PractitionerRole | Organization)Party being paid
... recipient Σ1..1Reference(Organization)Party being notified
... amount Σ1..1MoneyMonetary amount of the payment
... paymentStatus 0..1CodeableConceptIssued or cleared Status of the payment
Binding: Payment Status Codes (Example)

doco Documentation for this format icon

See the Extensions for this resource

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:PaymentNotice;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Business Identifier for the payment notice
  fhir:status [ code ] ; # 1..1 active | cancelled | draft | entered-in-error
  fhir:request [ Reference(Any) ] ; # 0..1 Request reference
  fhir:response [ Reference(Any) ] ; # 0..1 Response reference
  fhir:created [ dateTime ] ; # 1..1 Creation date
  fhir:reporter [ Reference(Organization|Practitioner|PractitionerRole) ] ; # 0..1 Responsible practitioner
  fhir:payment [ Reference(PaymentReconciliation) ] ; # 0..1 Payment reference
  fhir:paymentDate [ date ] ; # 0..1 Payment or clearing date
  fhir:payee [ Reference(Organization|Practitioner|PractitionerRole) ] ; # 0..1 Party being paid
  fhir:recipient [ Reference(Organization) ] ; # 1..1 Party being notified
  fhir:amount [ Money ] ; # 1..1 Monetary amount of the payment
  fhir:paymentStatus [ CodeableConcept ] ; # 0..1 Issued or cleared Status of the payment
]

Changes from both R4 and R4B

PaymentNotice
PaymentNotice.reporter
  • Added Element
PaymentNotice.payment
  • Min Cardinality changed from 1 to 0
PaymentNotice.provider
  • Deleted

See the Full Difference for further information

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON.

See R4 <--> R5 Conversion Maps (status = See Conversions Summary.)

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. PaymentNotice TUDomainResourcePaymentNotice request

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier 0..*IdentifierBusiness Identifier for the payment notice

... status ?!Σ1..1codeactive | cancelled | draft | entered-in-error
Binding: Financial Resource Status Codes (Required)
... request 0..1Reference(Any)Request reference
... created Σ1..1dateTimeCreation date
... reporter 0..1Reference(Practitioner | PractitionerRole | Organization)Responsible practitioner
... payment Σ0..1Reference(PaymentReconciliation)Payment reference
... paymentDate 0..1datePayment or clearing date
... payee 0..1Reference(Practitioner | PractitionerRole | Organization)Party being paid
... recipient Σ1..1Reference(Organization)Party being notified
... amount Σ1..1MoneyMonetary amount of the payment
... paymentStatus 0..1CodeableConceptIssued or cleared Status of the payment
Binding: Payment Status Codes (Example)

doco Documentation for this format icon

See the Extensions for this resource

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:PaymentNotice;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Business Identifier for the payment notice
  fhir:status [ code ] ; # 1..1 active | cancelled | draft | entered-in-error
  fhir:request [ Reference(Any) ] ; # 0..1 Request reference
  fhir:response [ Reference(Any) ] ; # 0..1 Response reference
  fhir:created [ dateTime ] ; # 1..1 Creation date
  fhir:reporter [ Reference(Organization|Practitioner|PractitionerRole) ] ; # 0..1 Responsible practitioner
  fhir:payment [ Reference(PaymentReconciliation) ] ; # 0..1 Payment reference
  fhir:paymentDate [ date ] ; # 0..1 Payment or clearing date
  fhir:payee [ Reference(Organization|Practitioner|PractitionerRole) ] ; # 0..1 Party being paid
  fhir:recipient [ Reference(Organization) ] ; # 1..1 Party being notified
  fhir:amount [ Money ] ; # 1..1 Monetary amount of the payment
  fhir:paymentStatus [ CodeableConcept ] ; # 0..1 Issued or cleared Status of the payment
]

Changes from both R4 and R4B

PaymentNotice
PaymentNotice.reporter
  • Added Element
PaymentNotice.payment
  • Min Cardinality changed from 1 to 0
PaymentNotice.provider
  • Deleted

See the Full Difference for further information

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON.

See R4 <--> R5 Conversion Maps (status = See Conversions Summary.)

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

PathValueSetTypeDocumentation
PaymentNotice.status FinancialResourceStatusCodes Required

This value set includes Status codes.

PaymentNotice.paymentStatus PaymentStatusCodes Example

This value set includes a sample set of Payment Status codes.



Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionExpressionIn Common
createddateCreation date for the noticePaymentNotice.created
identifiertokenThe business identifier of the noticePaymentNotice.identifier
payment-statustokenThe type of payment noticePaymentNotice.paymentStatus
reporterreferenceThe reference to the reporterPaymentNotice.reporter
(Practitioner, Organization, PractitionerRole)
requestreferenceThe ClaimPaymentNotice.request
(Any)
responsereferenceThe ClaimResponsePaymentNotice.response
(Any)
statustokenThe status of the payment noticePaymentNotice.status