DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

7.10 Resource PaymentReconciliation - Content

Financial Management Work GroupMaturity Level: 0Compartments: Not linked to any defined compartments

This resource provides payment details and claim references supporting a bulk payment.

7.10.1 Scope and Usage

The PaymentReconciliation resource 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. These are the payment reconciliation details which align to the individual payment amounts indicated on discrete ClaimResponses.

Bulk payments need to provide a means to associate the amounts paid again specific Claims, and other financial exchanges and adjustments, to the bulk payment itself in order to reconcile provider accounts receivable.

Todo

7.10.2 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. PaymentReconciliation ΣDomainResourcePaymentReconciliation resource
... identifier Σ0..*IdentifierBusiness Identifier
... request Σ0..1Reference(ProcessRequest)Claim reference
... outcome Σ0..1codecomplete | error
RemittanceOutcome (Required)
... disposition Σ0..1stringDisposition Message
... ruleset Σ0..1CodingResource version
Ruleset Codes (Example)
... originalRuleset Σ0..1CodingOriginal version
Ruleset Codes (Example)
... created Σ0..1dateTimeCreation date
... period Σ0..1PeriodPeriod covered
... organization Σ0..1Reference(Organization)Insurer
... requestProvider Σ0..1Reference(Practitioner)Responsible practitioner
... requestOrganization Σ0..1Reference(Organization)Responsible organization
... detail Σ0..*BackboneElementDetails
.... type Σ1..1CodingType code
Payment Type Codes (Example)
.... request Σ0..1Reference(Any)Claim
.... responce Σ0..1Reference(Any)Claim Response
.... submitter Σ0..1Reference(Organization)Submitter
.... payee Σ0..1Reference(Organization)Payee
.... date Σ0..1dateInvoice date
.... amount Σ0..1MoneyDetail amount
... form Σ0..1CodingPrinted Form Identifier
Form Codes (Required)
... total Σ1..1MoneyTotal amount of Payment
... note Σ0..*BackboneElementNote text
.... type Σ0..1Codingdisplay | print | printoper
NoteType (Required)
.... text Σ0..1stringNotes text

doco Documentation for this format

UML Diagram

PaymentReconciliation (DomainResource)The Response business identifieridentifier : Identifier [0..*]Original request resource referencerequest : Reference [0..1] « ProcessRequest »Transaction status: error, completeoutcome : code [0..1] « The outcome of the processing. (Strength=Required)RemittanceOutcome! »A description of the status of the adjudicationdisposition : string [0..1]The version of the style of resource contents. This should be mapped to the allowable profiles for this and supporting resourcesruleset : Coding [0..1] « The static and dynamic model to which contents conform, which may be business version or standard/version. (Strength=Example)Ruleset ?? »The style (standard) and version of the original material which was converted into this resourceoriginalRuleset : Coding [0..1] « The static and dynamic model to which contents conform, which may be business version or standard/version. (Strength=Example)Ruleset ?? »The date when the enclosed suite of services were performed or completedcreated : dateTime [0..1]The period of time for which payments have been gathered into this bulk payment for settlementperiod : Period [0..1]The Insurer who produced this adjudicated responseorganization : Reference [0..1] « Organization »The practitioner who is responsible for the services rendered to the patientrequestProvider : Reference [0..1] « Practitioner »The organization which is responsible for the services rendered to the patientrequestOrganization : Reference [0..1] « Organization »The form to be used for printing the contentform : Coding [0..1] « The forms codes. (Strength=Required)Form ! »Total payment amounttotal : Quantity(Money) [1..1]DetailsCode to indicate the nature of the payment, adjustment, funds advance, etctype : Coding [1..1] « The reason for the amount: payment, adjustment, advance. (Strength=Example)Payment Type ?? »The claim or financial resourcerequest : Reference [0..1] « Any »The claim response resourceresponce : Reference [0..1] « Any »The Organization which submitted the invoice or financial transactionsubmitter : Reference [0..1] « Organization »The organization which is receiving the paymentpayee : Reference [0..1] « Organization »The date of the invoice or financial resourcedate : date [0..1]Amount paid for this detailamount : Quantity(Money) [0..1]NotesThe note purpose: Print/Displaytype : Coding [0..1] « The presentation types of notes. (Strength=Required)NoteType! »The note texttext : string [0..1]List of individual settlement amounts and the corresponding transactiondetail[0..*]Suite of notesnote[0..*]

XML Template

<PaymentReconciliation xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business Identifier --></identifier>
 <request><!-- 0..1 Reference(ProcessRequest) Claim reference --></request>
 <outcome value="[code]"/><!-- 0..1 complete | error -->
 <disposition value="[string]"/><!-- 0..1 Disposition Message -->
 <ruleset><!-- 0..1 Coding Resource version --></ruleset>
 <originalRuleset><!-- 0..1 Coding Original version --></originalRuleset>
 <created value="[dateTime]"/><!-- 0..1 Creation date -->
 <period><!-- 0..1 Period Period covered --></period>
 <organization><!-- 0..1 Reference(Organization) Insurer --></organization>
 <requestProvider><!-- 0..1 Reference(Practitioner) Responsible practitioner --></requestProvider>
 <requestOrganization><!-- 0..1 Reference(Organization) Responsible organization --></requestOrganization>
 <detail>  <!-- 0..* Details -->
  <type><!-- 1..1 Coding Type code --></type>
  <request><!-- 0..1 Reference(Any) Claim --></request>
  <responce><!-- 0..1 Reference(Any) Claim Response --></responce>
  <submitter><!-- 0..1 Reference(Organization) Submitter --></submitter>
  <payee><!-- 0..1 Reference(Organization) Payee --></payee>
  <date value="[date]"/><!-- 0..1 Invoice date -->
  <amount><!-- 0..1 Quantity(Money) Detail amount --></amount>
 </detail>
 <form><!-- 0..1 Coding Printed Form Identifier --></form>
 <total><!-- 1..1 Quantity(Money) Total amount of Payment --></total>
 <note>  <!-- 0..* Note text -->
  <type><!-- 0..1 Coding display | print | printoper --></type>
  <text value="[string]"/><!-- 0..1 Notes text -->
 </note>
</PaymentReconciliation>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. PaymentReconciliation ΣDomainResourcePaymentReconciliation resource
... identifier Σ0..*IdentifierBusiness Identifier
... request Σ0..1Reference(ProcessRequest)Claim reference
... outcome Σ0..1codecomplete | error
RemittanceOutcome (Required)
... disposition Σ0..1stringDisposition Message
... ruleset Σ0..1CodingResource version
Ruleset Codes (Example)
... originalRuleset Σ0..1CodingOriginal version
Ruleset Codes (Example)
... created Σ0..1dateTimeCreation date
... period Σ0..1PeriodPeriod covered
... organization Σ0..1Reference(Organization)Insurer
... requestProvider Σ0..1Reference(Practitioner)Responsible practitioner
... requestOrganization Σ0..1Reference(Organization)Responsible organization
... detail Σ0..*BackboneElementDetails
.... type Σ1..1CodingType code
Payment Type Codes (Example)
.... request Σ0..1Reference(Any)Claim
.... responce Σ0..1Reference(Any)Claim Response
.... submitter Σ0..1Reference(Organization)Submitter
.... payee Σ0..1Reference(Organization)Payee
.... date Σ0..1dateInvoice date
.... amount Σ0..1MoneyDetail amount
... form Σ0..1CodingPrinted Form Identifier
Form Codes (Required)
... total Σ1..1MoneyTotal amount of Payment
... note Σ0..*BackboneElementNote text
.... type Σ0..1Codingdisplay | print | printoper
NoteType (Required)
.... text Σ0..1stringNotes text

doco Documentation for this format

UML Diagram

PaymentReconciliation (DomainResource)The Response business identifieridentifier : Identifier [0..*]Original request resource referencerequest : Reference [0..1] « ProcessRequest »Transaction status: error, completeoutcome : code [0..1] « The outcome of the processing. (Strength=Required)RemittanceOutcome! »A description of the status of the adjudicationdisposition : string [0..1]The version of the style of resource contents. This should be mapped to the allowable profiles for this and supporting resourcesruleset : Coding [0..1] « The static and dynamic model to which contents conform, which may be business version or standard/version. (Strength=Example)Ruleset ?? »The style (standard) and version of the original material which was converted into this resourceoriginalRuleset : Coding [0..1] « The static and dynamic model to which contents conform, which may be business version or standard/version. (Strength=Example)Ruleset ?? »The date when the enclosed suite of services were performed or completedcreated : dateTime [0..1]The period of time for which payments have been gathered into this bulk payment for settlementperiod : Period [0..1]The Insurer who produced this adjudicated responseorganization : Reference [0..1] « Organization »The practitioner who is responsible for the services rendered to the patientrequestProvider : Reference [0..1] « Practitioner »The organization which is responsible for the services rendered to the patientrequestOrganization : Reference [0..1] « Organization »The form to be used for printing the contentform : Coding [0..1] « The forms codes. (Strength=Required)Form ! »Total payment amounttotal : Quantity(Money) [1..1]DetailsCode to indicate the nature of the payment, adjustment, funds advance, etctype : Coding [1..1] « The reason for the amount: payment, adjustment, advance. (Strength=Example)Payment Type ?? »The claim or financial resourcerequest : Reference [0..1] « Any »The claim response resourceresponce : Reference [0..1] « Any »The Organization which submitted the invoice or financial transactionsubmitter : Reference [0..1] « Organization »The organization which is receiving the paymentpayee : Reference [0..1] « Organization »The date of the invoice or financial resourcedate : date [0..1]Amount paid for this detailamount : Quantity(Money) [0..1]NotesThe note purpose: Print/Displaytype : Coding [0..1] « The presentation types of notes. (Strength=Required)NoteType! »The note texttext : string [0..1]List of individual settlement amounts and the corresponding transactiondetail[0..*]Suite of notesnote[0..*]

XML Template

<PaymentReconciliation xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business Identifier --></identifier>
 <request><!-- 0..1 Reference(ProcessRequest) Claim reference --></request>
 <outcome value="[code]"/><!-- 0..1 complete | error -->
 <disposition value="[string]"/><!-- 0..1 Disposition Message -->
 <ruleset><!-- 0..1 Coding Resource version --></ruleset>
 <originalRuleset><!-- 0..1 Coding Original version --></originalRuleset>
 <created value="[dateTime]"/><!-- 0..1 Creation date -->
 <period><!-- 0..1 Period Period covered --></period>
 <organization><!-- 0..1 Reference(Organization) Insurer --></organization>
 <requestProvider><!-- 0..1 Reference(Practitioner) Responsible practitioner --></requestProvider>
 <requestOrganization><!-- 0..1 Reference(Organization) Responsible organization --></requestOrganization>
 <detail>  <!-- 0..* Details -->
  <type><!-- 1..1 Coding Type code --></type>
  <request><!-- 0..1 Reference(Any) Claim --></request>
  <responce><!-- 0..1 Reference(Any) Claim Response --></responce>
  <submitter><!-- 0..1 Reference(Organization) Submitter --></submitter>
  <payee><!-- 0..1 Reference(Organization) Payee --></payee>
  <date value="[date]"/><!-- 0..1 Invoice date -->
  <amount><!-- 0..1 Quantity(Money) Detail amount --></amount>
 </detail>
 <form><!-- 0..1 Coding Printed Form Identifier --></form>
 <total><!-- 1..1 Quantity(Money) Total amount of Payment --></total>
 <note>  <!-- 0..* Note text -->
  <type><!-- 0..1 Coding display | print | printoper --></type>
  <text value="[string]"/><!-- 0..1 Notes text -->
 </note>
</PaymentReconciliation>

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

7.10.2.1 Terminology Bindings

PathDefinitionTypeReference
PaymentReconciliation.outcome The outcome of the processing.RequiredRemittanceOutcome
PaymentReconciliation.ruleset
PaymentReconciliation.originalRuleset 		The static and dynamic model to which contents conform, which may be business version or standard/version.ExampleRuleset Codes
PaymentReconciliation.detail.type The reason for the amount: payment, adjustment, advance.ExamplePayment Type Codes
PaymentReconciliation.form The forms codes.RequiredForm Codes
PaymentReconciliation.note.type The presentation types of notes.RequiredNoteType

7.10.3 Search Parameters

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

NameTypeDescriptionPaths
identifiertokenThe business identifier of the Explanation of BenefitPaymentReconciliation.identifier