R4 Ballot #1 (Mixed Normative/Trial use) Current Build
This page was published as part of FHIR v3.3.0: R4 Ballot #1 : Mixed Normative/Trial use (First Normative ballot). It has been superceded by R4 . For a full list of available versions, see the Directory of published versions .

13.8 Resource PaymentNotice - Content

Financial Management Work Group Maturity Level : 2   Trial Use Security 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 payors payers to advise the Provider provider or regulatory bodies of the state of a payment (cheque (check in the mail/EFT sent, payment cashed, payment cancelled). canceled). Employers or Insurance Exchanges may use this to advise payors payers of premium payment.

Payors and /or 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 payors 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.

No resources refer to this resource directly.

This resource implements the Event pattern.

Structure

Name Flags Card. Type Description & Constraints doco
. . PaymentNotice TU DomainResource PaymentNotice request
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier 0..* Identifier Business Identifier for the payment noctice
. . . status ?! Σ 0..1 1..1 code active | cancelled | draft | entered-in-error
Financial Resource Status Codes ( Required )
. . . request 0..1 Reference ( Any ) Request reference
. . . response 0..1 Reference ( Any ) Response reference
. . . statusDate created Σ 0..1 1..1 date dateTime Payment or clearing Creation date
. . created . provider 0..1 dateTime Reference ( Practitioner | PractitionerRole | Organization ) Creation date Responsible practitioner
. . . target payment Σ 0..1 1..1 Reference ( Organization PaymentReconciliation ) Insurer Payment reference
... paymentDate 0..1 date Payment or Regulatory body clearing date
. . . provider payee 0..1 Reference ( Practitioner | PractitionerRole | Organization ) Responsible practitioner Party being paid
... recipient Σ 1..1 Reference ( Organization ) Party being notified
... amount Σ 1..1 Money Monetary amount of the payment
. . . paymentStatus 0..1 CodeableConcept Whether payment has been sent Issued or cleared Status of the payment
Payment Status Codes ( Example )

doco Documentation for this format

UML Diagram ( Legend )

PaymentNotice ( DomainResource ) The notice business A unique identifier assigned to this payment notice identifier : Identifier [0..*] The status of the resource instance (this element modifies the meaning of other elements) status : code [0..1] [1..1] « A code specifying the state of the resource instance. (Strength=Required) Financial Resource Status FinancialResourceStatusCodes ! » Reference of resource for which payment is being made request : Reference [0..1] « Any » Reference of response to resource for which payment is being made response : Reference [0..1] « Any » The date when the above payment action occurrred this resource was created statusDate created : date dateTime [0..1] [1..1] The date when this resource was created practitioner who is responsible for the services rendered to the patient created provider : dateTime Reference [0..1] « Practitioner | PractitionerRole | Organization » The Insurer who A reference to the payment which is target of the request subject of this notice target payment : Reference [0..1] [1..1] « Organization PaymentReconciliation » The practitioner date when the above payment action occurred paymentDate : date [0..1] The party who will receive or has received payment that is responsible for the services rendered to the patient subject of this notification provider payee : Reference [0..1] « Practitioner | PractitionerRole | Organization » The party who is notified of the payment status, typically paid: payment sent, cleared: status recipient : Reference [1..1] « Organization » The amount sent to the payee amount : Money [1..1] A code indicating whether payment received has been sent or cleared paymentStatus : CodeableConcept [0..1] « The payment conveyance status codes codes. (Strength=Example) Payment Status PaymentStatusCodes ?? »

XML Template

<PaymentNotice xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <

 <identifier><!-- 0..* Identifier Business Identifier for the payment noctice --></identifier>
 <status value="[code]"/><!-- 1..1 active | cancelled | draft | entered-in-error -->

 <request><!-- 0..1 Reference(Any) Request reference --></request>
 <response><!-- 0..1 Reference(Any) Response reference --></response>
 <
 <
 <</target>
 <</provider>
 <</paymentStatus>

 <created value="[dateTime]"/><!-- 1..1 Creation date -->
 <provider><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Responsible practitioner --></provider>
 <payment><!-- 1..1 Reference(PaymentReconciliation) Payment reference --></payment>
 <paymentDate value="[date]"/><!-- 0..1 Payment or clearing date -->
 <payee><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Party being paid --></payee>
 <recipient><!-- 1..1 Reference(Organization) Party being notified --></recipient>
 <amount><!-- 1..1 Money Monetary amount of the payment --></amount>
 <paymentStatus><!-- 0..1 CodeableConcept Issued or cleared Status of the payment --></paymentStatus>

</PaymentNotice>

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:
  fhir:

  fhir:PaymentNotice.identifier [ Identifier ], ... ; # 0..* Business Identifier for the payment noctice
  fhir:PaymentNotice.status [ code ]; # 1..1 active | cancelled | draft | entered-in-error

  fhir:PaymentNotice.request [ Reference(Any) ]; # 0..1 Request reference
  fhir:PaymentNotice.response [ Reference(Any) ]; # 0..1 Response reference
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:PaymentNotice.created [ dateTime ]; # 1..1 Creation date
  fhir:PaymentNotice.provider [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Responsible practitioner
  fhir:PaymentNotice.payment [ Reference(PaymentReconciliation) ]; # 1..1 Payment reference
  fhir:PaymentNotice.paymentDate [ date ]; # 0..1 Payment or clearing date
  fhir:PaymentNotice.payee [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Party being paid
  fhir:PaymentNotice.recipient [ Reference(Organization) ]; # 1..1 Party being notified
  fhir:PaymentNotice.amount [ Money ]; # 1..1 Monetary amount of the payment
  fhir:PaymentNotice.paymentStatus [ CodeableConcept ]; # 0..1 Issued or cleared Status of the payment

]

Changes since R3

PaymentNotice
PaymentNotice.provider PaymentNotice.status
  • Type changed Change value set from Reference(Practitioner) http://hl7.org/fhir/ValueSet/fm-status|4.0.0 to Reference(Practitioner|PractitionerRole|Organization) PaymentNotice.organization deleted http://hl7.org/fhir/ValueSet/fm-status|4.1.0

See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. 1 fail round-trip testing and 1 r3 resources are invalid (0 errors). )

Structure

Name Flags Card. Type Description & Constraints doco
. . PaymentNotice TU DomainResource PaymentNotice request
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier 0..* Identifier Business Identifier for the payment noctice
. . . status ?! Σ 0..1 1..1 code active | cancelled | draft | entered-in-error
Financial Resource Status Codes ( Required )
. . . request 0..1 Reference ( Any ) Request reference
. . . response 0..1 Reference ( Any ) Response reference
. . . statusDate created Σ 0..1 1..1 date dateTime Payment or clearing Creation date
. . created . provider 0..1 dateTime Reference ( Practitioner | PractitionerRole | Organization ) Creation date Responsible practitioner
. . . target payment Σ 0..1 1..1 Reference ( Organization PaymentReconciliation ) Insurer Payment reference
... paymentDate 0..1 date Payment or Regulatory body clearing date
. . . provider payee 0..1 Reference ( Practitioner | PractitionerRole | Organization ) Responsible practitioner Party being paid
... recipient Σ 1..1 Reference ( Organization ) Party being notified
... amount Σ 1..1 Money Monetary amount of the payment
. . . paymentStatus 0..1 CodeableConcept Whether payment has been sent Issued or cleared Status of the payment
Payment Status Codes ( Example )

doco Documentation for this format

UML Diagram ( Legend )

PaymentNotice ( DomainResource ) The notice business A unique identifier assigned to this payment notice identifier : Identifier [0..*] The status of the resource instance (this element modifies the meaning of other elements) status : code [0..1] [1..1] « A code specifying the state of the resource instance. (Strength=Required) Financial Resource Status FinancialResourceStatusCodes ! » Reference of resource for which payment is being made request : Reference [0..1] « Any » Reference of response to resource for which payment is being made response : Reference [0..1] « Any » The date when the above payment action occurrred this resource was created statusDate created : date dateTime [0..1] [1..1] The date when this resource was created practitioner who is responsible for the services rendered to the patient created provider : dateTime Reference [0..1] « Practitioner | PractitionerRole | Organization » The Insurer who A reference to the payment which is target of the request subject of this notice target payment : Reference [0..1] [1..1] « Organization PaymentReconciliation » The practitioner date when the above payment action occurred paymentDate : date [0..1] The party who will receive or has received payment that is responsible for the services rendered to the patient subject of this notification provider payee : Reference [0..1] « Practitioner | PractitionerRole | Organization » The party who is notified of the payment status, typically paid: payment sent, cleared: status recipient : Reference [1..1] « Organization » The amount sent to the payee amount : Money [1..1] A code indicating whether payment received has been sent or cleared paymentStatus : CodeableConcept [0..1] « The payment conveyance status codes codes. (Strength=Example) Payment Status PaymentStatusCodes ?? »

XML Template

<PaymentNotice xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <

 <identifier><!-- 0..* Identifier Business Identifier for the payment noctice --></identifier>
 <status value="[code]"/><!-- 1..1 active | cancelled | draft | entered-in-error -->

 <request><!-- 0..1 Reference(Any) Request reference --></request>
 <response><!-- 0..1 Reference(Any) Response reference --></response>
 <
 <
 <</target>
 <</provider>
 <</paymentStatus>

 <created value="[dateTime]"/><!-- 1..1 Creation date -->
 <provider><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Responsible practitioner --></provider>
 <payment><!-- 1..1 Reference(PaymentReconciliation) Payment reference --></payment>
 <paymentDate value="[date]"/><!-- 0..1 Payment or clearing date -->
 <payee><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Party being paid --></payee>
 <recipient><!-- 1..1 Reference(Organization) Party being notified --></recipient>
 <amount><!-- 1..1 Money Monetary amount of the payment --></amount>
 <paymentStatus><!-- 0..1 CodeableConcept Issued or cleared Status of the payment --></paymentStatus>

</PaymentNotice>

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:
  fhir:

  fhir:PaymentNotice.identifier [ Identifier ], ... ; # 0..* Business Identifier for the payment noctice
  fhir:PaymentNotice.status [ code ]; # 1..1 active | cancelled | draft | entered-in-error

  fhir:PaymentNotice.request [ Reference(Any) ]; # 0..1 Request reference
  fhir:PaymentNotice.response [ Reference(Any) ]; # 0..1 Response reference
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:PaymentNotice.created [ dateTime ]; # 1..1 Creation date
  fhir:PaymentNotice.provider [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Responsible practitioner
  fhir:PaymentNotice.payment [ Reference(PaymentReconciliation) ]; # 1..1 Payment reference
  fhir:PaymentNotice.paymentDate [ date ]; # 0..1 Payment or clearing date
  fhir:PaymentNotice.payee [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Party being paid
  fhir:PaymentNotice.recipient [ Reference(Organization) ]; # 1..1 Party being notified
  fhir:PaymentNotice.amount [ Money ]; # 1..1 Monetary amount of the payment
  fhir:PaymentNotice.paymentStatus [ CodeableConcept ]; # 0..1 Issued or cleared Status of the payment

]

Changes since DSTU2 Release 3

PaymentNotice
PaymentNotice.provider PaymentNotice.status
  • Type changed Change value set from Reference(Practitioner) http://hl7.org/fhir/ValueSet/fm-status|4.0.0 to Reference(Practitioner|PractitionerRole|Organization) PaymentNotice.organization deleted http://hl7.org/fhir/ValueSet/fm-status|4.1.0

See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. 1 fail round-trip testing and 1 r3 resources are invalid (0 errors). )

 

Alternate See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis a

Path Definition Type Reference
PaymentNotice.status A code specifying the state of the resource instance. Required Financial Resource Status Codes FinancialResourceStatusCodes
PaymentNotice.paymentStatus The payment conveyance status codes codes. Example Payment Status Codes PaymentStatusCodes

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

statusdate date The date of the payment action PaymentNotice.statusDate
Name Type Description Expression In Common
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
( Practitioner , Organization , PractitionerRole )
request reference The Claim PaymentNotice.request
(Any)
response reference The ClaimResponse PaymentNotice.response
(Any)
status token The status of the payment notice PaymentNotice.status