xCaliber healthCare Data Mesh

Record Payment

Source Object: Record Payment

Overview and Usage: The "Record Payment" source object is essential for recording and managing payment details related to healthcare services. This source object contains information about payments received for appointments or services. Here's a breakdown of the key components:

  • Appointment ID: The unique identifier for the appointment to which the payment is related.
  • Card Number Last 4: The last 4 digits of the credit card number used for the payment.
  • Check Number: The number associated with the payment check.
  • Claim Payment: The amount of the payment applied to the insurance claim.
  • Copay Amount: The amount paid as a copayment by the patient.
  • Department ID: The unique identifier for the department associated with the payment.
  • Other Amount: Any other miscellaneous payment amount.
  • Payment Method: The method of payment used, such as credit card, check, cash, etc.
  • Post Date: The date on which the payment was posted or recorded.
  • Today's Service: Indicates whether the payment is related to the services provided on the same day.
  • Patient ID: The unique identifier for the patient making the payment.

The "Record Payment" source object helps healthcare organizations efficiently manage financial transactions related to patient appointments and services, ensuring accurate payment records and reconciliation.

Mapping Table

Data FieldExample ValueSource Data Field DescriptionSource Field Data TypeSource Data Field CardinalityMapped FHIR++ ResourceMapped FHIR Data FieldAugmented MappingAssociated Coding SystemAssociated FHIR Data Field ExtensionMapping Context
appointmentid-The ID of the appointment where the copay should be applied.integer0..1PaymentNoticeextension.valueStringappointment-idTop Level
cardnumberlast4-The last 4 digits of the credit card number. This is required if the payment method is a credit card.string0..1PaymentNoticeextension.valueStringcard-number-last4Top Level
checknumber-The check number. This is required if the payment is made by check.string0..1PaymentNoticeextension.valueStringcheck-numberTop Level
claimpayment-A JSON representation of claim ID and payment combinations. For example, '[ { "1":"1.00"}, { "2":"5.00"} ].' This indicates a payment of $1 for claim ID #1 and a payment of $5 for claim ID #2.array0..1PaymentNoticeextension.valueStringclaim-paymentTop Level
copayamount-The amount associated with a particular appointment for a copay.string0..1PaymentNoticeamount.valueTop Level
departmentid-The ID of the department where the payment or contract is being collected.integer0..1PaymentNoticecontextTop Level
otheramount-The amount being collected that is not associated with individual appointment. This money goes into the "unapplied" bucket. In the future, these payments will be able to be broken down by individual claim level. Co-pay amounts should be in "copayamount".string0..1PaymentNoticeextension.valueStringother-amountTop Level
paymentmethod-Valid values include CASH or CHECK or anything as a result of /configuration/validnonccpcreditcardmethods. Note that practices using Credit Card Plus (CCP) should typically NOT be using this call and should instead use the collectpayment endpoints to charge the card. In addition, all payments recorded via this method are subject to the same policies as any other money collected by athenahealth.string0..1PaymentNoticeextension.valueStringpayment-methodTop Level
postdate-The date the payment was made. Defaulted to today.string0..1PaymentNoticeextension.valueDatepost-dateTop Level
todayservice-Apply the other amount value to today's service.string0..1PaymentNoticeextension.valueStringtoday-serviceTop Level
patientId--string0..1PaymentNoticecontextTop Level