Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-26601

Rename PaymentReconciliation and expand scope to include Patient Payments

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Financial Mgmt
    • PaymentReconciliation
    • Hide

      2) Alter the descriptive and supporting text and examples to support the expanded scope.

      3) Need to add the following elements:

      .type - 1..1 CodeableConcept for the type of transaction (payment, adjustment, etc.) extensible

      .originatedFrom (or onBehalfOf) - 0..1 CodeableConcept for the nature of the source (patient, insurance) (extensible)

      .reason (kind?) - 0..1 CodeableConcept for the type of workflow from which this payment arose (kiosk, Online Bill payment, periodic payment, deposit on account, ...)

      .enterer - 0..1 Reference(Practitioner | PractitionerRole | Organization)

      .location - 0..1 reference(Location) - where the payment was collected

      .method - 0..1 CodeableConcept the method of payment (check, credit card etc.) not required for adjustments just actual funds movements (extensible)

      .cardBrand 0..1 string

      .accountNumber 0..1 string

      .expirationDate 0..1 date (YYYY-MM)

      .processor 0..1 string - name of the card processor, etf processor, bank for checks

      .referenceNumber 0..1 string check number, eft reference, car processor reference

      .authorization 0..1 string authorization number

      .tenderedAmount 0..1 Money for cash tendered

      .returnedAmount 0..1 Money cash returned as change

      under .allocation (formerly .detail)

      .allocation.target 1..1 Reference(Claim | Account | Invoice | ChargeItem | Statement |Encounter|Contract) the particular 'thing' being paid/adjusted/advanced against

      .allocation.targetItem 0..1 string | Identifier identifies the line item being paid (may be partial)

      .allocation.encounter 0..1 Reference(Encounter) may be completed by the receiver, used for search

      .allocation.account 0..1 Reference(Account) may be completed by the receiver, used for search

      4) Rename the following fields

      .paymentDate to date

      .paymentAmount to amount

      .detail to allocation

       

      5) Change the cardinality:

      .allocation.type from 1..1 to 0..1 given that patient payments do not require

      .allocation.request - is superseded by target for payor payments

      .allocation.response change Reference(Any) to Reference(ClaimResponse)

       

      6) Changes to Search parameters

      Change request to target to reflect field name change

      Add a search to .allocation.encounter

      Add a search to .allocation.account

      Show
      2) Alter the descriptive and supporting text and examples to support the expanded scope. 3) Need to add the following elements: .type - 1..1 CodeableConcept for the type of transaction (payment, adjustment, etc.) extensible .originatedFrom (or onBehalfOf) - 0..1 CodeableConcept for the nature of the source (patient, insurance) (extensible) .reason (kind?) - 0..1 CodeableConcept for the type of workflow from which this payment arose (kiosk, Online Bill payment, periodic payment, deposit on account, ...) .enterer - 0..1 Reference(Practitioner | PractitionerRole | Organization) .location - 0..1 reference(Location) - where the payment was collected .method - 0..1 CodeableConcept the method of payment (check, credit card etc.) not required for adjustments just actual funds movements (extensible) .cardBrand 0..1 string .accountNumber 0..1 string .expirationDate 0..1 date (YYYY-MM) .processor 0..1 string - name of the card processor, etf processor, bank for checks .referenceNumber 0..1 string check number, eft reference, car processor reference .authorization 0..1 string authorization number .tenderedAmount 0..1 Money for cash tendered .returnedAmount 0..1 Money cash returned as change under .allocation (formerly .detail) .allocation.target 1..1 Reference(Claim | Account | Invoice | ChargeItem | Statement |Encounter|Contract) the particular 'thing' being paid/adjusted/advanced against .allocation.targetItem 0..1 string | Identifier identifies the line item being paid (may be partial) .allocation.encounter 0..1 Reference(Encounter) may be completed by the receiver, used for search .allocation.account 0..1 Reference(Account) may be completed by the receiver, used for search 4) Rename the following fields .paymentDate to date .paymentAmount to amount .detail to allocation   5) Change the cardinality: .allocation.type from 1..1 to 0..1 given that patient payments do not require .allocation.request - is superseded by target for payor payments .allocation.response change Reference(Any) to Reference(ClaimResponse)   6) Changes to Search parameters Change request to target to reflect field name change Add a search to .allocation.encounter Add a search to .allocation.account
    • Alex Beckner/Celine Lefebvre : 7-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Want to apply a suite of changes to PaymentReconciliation to support payments made on behalf of patients (collected directly from the patient or via a third part payment collector):

      1) After review it was determined NOT to change the name of the resource, see Jira ticket FHIR-

      2) Alter the descriptive and supporting text and examples to support the expanded scope.

      3) Need to add the following elements:

      .type - 1..1 CodeableConcept for the type of transaction (payment, adjustment, etc.)

      .originatedFrom (or onBehalfOf) - 0..1 CodeableConcept for the nature of the source (patient, insurance)

      .reason (kind?) - 0..1 CodeableConcept for the type of workflow from which this payment arose (kiosk, Online Bill payment, periodic payment, deposit on account, ...)

      .enterer - 0..1 Reference(Practitioner | PractitionerRole | Organization)

      .location - 0..1 reference(Location) - where the payment was collected

      .paymentMethod - 0..1 CodeableConcept the method of payment (check, credit card, EFT etc) not required for adjustments just actual funds movements

      .cardBrand 0..1 string

      .accountNumber 0..1 string

      .expirationDate 0..1 date (YYYY-MM)

      .processor 0..1 string - name of the card processor, EFT processor, bank for checks

      .referenceNumber 0..1 string check number, EFT reference, car processor reference

      .authorization 0..1 string authorization number

      .tenderedAmount 0..1 Money for cash tendered

      .returnedAmount 0..1 Money cash returned as change

      under .allocation (formerly .detail)

      .allocation.target 1..1 Reference(Claim | Account | Invoice | ChargeItem | Statement |Encounter|Contract) the particular 'thing' being paid/adjusted/advanced against

      .allocation.targetItem 0..1 string | Identifier identifies the line item being paid (may be partial)

      .allocation.encounter 0..1 Reference(Encounter) may be completed by the receiver, used for search

      .allocation.account 0..1 Reference(Account) may be completed by the receiver, used for search

      4) Rename the following fields

      .paymentDate to date

      .paymentAmount to amount

      .detail to allocation

       

      5) Change the cardinality:

      .allocation.type from 1..1 to 0..1 given that patient payments do not require

      .allocation.request - is superseded by target for payor payments, therefore this field is removed

      .allocation.response change Reference(Any) to Reference(ClaimResponse)

       

      6) Changes to Search parameters

      Change request to target to reflect field name change

      Add a search to .allocation.encounter

      Add a search to .allocation.account

       

       

      Attachments

        Activity

          People

            pknapp Paul Knapp
            pknapp Paul Knapp
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: