Skip to content

Payment Reconciliation Profile

Canonicalhttps://fhir.apps.health/StructureDefinition/nexus-core-paymentreconciliation
Statusdraft · 1.33.0
BasePaymentReconciliation (constraint)
SourceFSH · JSON

Defines the Nexus EMR FHIR profile for a payment or refund taken at the clinic against private and third-party invoices raised at the billing vendor. One reconciliation per money event: a payment split across several invoices is one reconciliation with one detail per invoice. Invoices are named by the billing vendor's invoice identifier. Amounts are always positive; the detail type says whether money came in or went back. A reversal sets status to cancelled with a reason and keeps the record.

Elements / Details

Every element this profile touches, with its full definition. Element names in the tables link here.

PaymentReconciliation

Short Nexus EMR payment or refund against billing-vendor invoices
Definition One payment or one refund taken at the clinic, allocated across one or more invoices raised at the billing vendor. The billing vendor cannot record payments, so this is the clinic's ledger of them; an invoice's balance is its total less the active payments allocated to it plus the active refunds allocated to it.
Comments R4 PaymentReconciliation was designed for an insurer remitting to a provider. This profile uses it the other way round -- money taken from a patient or a third party at the clinic -- because it is the R4 resource whose elements fit: a payment with a date, an amount, an issuer, a reference number and per-invoice allocations. R5 widened the resource to cover exactly this case, and the two R5 elements this profile needs (method, enterer) are carried as R5 cross-version extensions.
Cardinality 0..*
Invariants dom-2, dom-3, dom-4, dom-5, dom-6, nexus-payment-detail-names-invoice, nexus-payment-invoices-indexed, nexus-payment-detail-kind, nexus-payment-one-direction, nexus-payment-amounts-positive, nexus-payment-reversal-has-reason, nexus-payment-refund-has-reason

PaymentReconciliation.id

Short Logical id of this artifact
Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.meta

Short Metadata about the resource
Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
Cardinality 0..1
Type Meta
Invariants ele-1

PaymentReconciliation.implicitRules

Short A set of rules under which this content was created
Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Cardinality 0..1
Type uri
Modifier yes — This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
Invariants ele-1

PaymentReconciliation.language

Short Language of the resource content
Definition The base language in which the resource is written.
Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Cardinality 0..1
Type code
Binding languages (preferred)
Invariants ele-1

PaymentReconciliation.text

Short Text summary of the resource, for human interpretation
Definition A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Cardinality 0..1
Type Narrative
Invariants ele-1
Also called narrative, html, xhtml, display

PaymentReconciliation.contained

Short Contained, inline Resources
Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Cardinality 0..*
Type Resource
Also called inline resources, anonymous resources, contained resources

PaymentReconciliation.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 1..*
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.extension:method

Short How the money was paid: cash, debit, credit card, cheque, e-transfer, insurer EFT
Definition How the money changed hands. The R5 element PaymentReconciliation.method, carried as its published R4 cross-version extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 1..1
Type Extension(extension-PaymentReconciliation.method)
Must Support yes
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.extension:method.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.extension:method.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..0
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.extension:method.url

Short identifies the meaning of the extension
Definition Source of the definition for the extension code - a logical name or a URL.
Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Cardinality 1..1
Type http://hl7.org/fhirpath/System.String
Fixed value http://hl7.org/fhir/5.0/StructureDefinition/extension-PaymentReconciliation.method

PaymentReconciliation.extension:method.value[x]

Short Payment instrument
Definition The means of payment such as check, card cash, or electronic funds transfer.
Cardinality 0..1
Type CodeableConcept
Binding Payment Method Value Set (extensible)
Invariants ele-1

PaymentReconciliation.extension:enterer

Short Who keyed the payment
Definition The person who recorded the payment or refund in the clinic's system. The R5 element PaymentReconciliation.enterer, carried as its published R4 cross-version extension. Absent only when the signed-in user cannot be named.
Comments Not requestor: in R4 that element is the practitioner responsible for the services being paid for, which is a different person from whoever took the money.
Cardinality 0..1
Type Extension(extension-PaymentReconciliation.enterer)
Must Support yes
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.extension:enterer.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.extension:enterer.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..0
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.extension:enterer.url

Short identifies the meaning of the extension
Definition Source of the definition for the extension code - a logical name or a URL.
Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Cardinality 1..1
Type http://hl7.org/fhirpath/System.String
Fixed value http://hl7.org/fhir/5.0/StructureDefinition/extension-PaymentReconciliation.enterer

PaymentReconciliation.extension:enterer.value[x]

Short Who entered the payment
Definition Payment enterer if not the actual payment issuer.
Cardinality 0..1
Type Reference(Practitioner Profile | PractitionerRole Profile)
Invariants ele-1

PaymentReconciliation.extension:reason

Short Why it was reversed or refunded
Definition Why this reconciliation was reversed, or why the refund was given. Required on a cancelled reconciliation and on every refund.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..1
Type Extension(Payment Reason Extension)
Must Support yes
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.modifierExtension

Short Extensions that cannot be ignored
Definition May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Modifier yes — Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.identifier

Short The invoices this reconciliation touches, for search
Definition One entry per invoice the reconciliation allocates money to, under https://fhir.apps.health/NamingSystem/nexus-clinicaid-invoice-uuid, repeating the identifiers on detail.request. It is the index: every reconciliation touching an invoice is found by one token search on identifier, and a reader does not depend on a server supporting the :identifier modifier on detail.request.
Requirements Allows payment reconciliations to be distinguished and referenced.
Comments This repurposes the business identifier as an index rather than naming the reconciliation itself. Where a server advertises detail.request:identifier, that search is the better one, and the mirror may be retired in a later version.
Cardinality 1..*
Type Identifier
Must Support yes
Invariants ele-1

PaymentReconciliation.status

Short active | cancelled | draft | entered-in-error
Definition active counts toward a balance. cancelled is a reversal: the record stays, carrying its reason, and counts toward nothing. entered-in-error is a record that should never have existed and also counts toward nothing. The clinic does not write draft.
Requirements Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.
Comments This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Cardinality 1..1
Type code
Must Support yes
Modifier yes — This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Binding fm-status (required)
Invariants ele-1

PaymentReconciliation.period

Short Period covered
Definition The period of time for which payments have been gathered into this bulk payment for settlement.
Requirements Needed to allow receivers to monitor and reconcile payment issuer schedules.
Cardinality 0..1
Type Period
Invariants ele-1

PaymentReconciliation.created

Short When the payment was keyed
Definition The instant the payment or refund was recorded. Distinct from paymentDate, the day the money changed hands.
Requirements Need to record a timestamp for use by both the recipient and the issuer.
Cardinality 1..1
Type dateTime
Must Support yes
Invariants ele-1

PaymentReconciliation.paymentIssuer

Short Who paid
Definition The payer -- the patient, a family member, an employer or an insurer -- as the office named them. Usually a display only: a private payer is seldom a resource the clinic holds.
Requirements Need to identify the party resonsible for the payment and this resource.
Comments This party is also responsible for the reconciliation.
Cardinality 0..1
Type Reference(Organization)
Must Support yes
Invariants ele-1

PaymentReconciliation.request

Short Reference to requesting resource
Definition Original request resource reference.
Requirements Needed to allow the response to be linked to the request.
Cardinality 0..1
Type Reference(Task)
Invariants ele-1

PaymentReconciliation.requestor

Short Responsible practitioner
Definition The practitioner who is responsible for the services rendered to the patient.
Requirements Need to identify the party responsible for the request.
Comments Not used by this profile. In R4 this is the practitioner responsible for the services being paid for; who keyed the payment is the enterer extension.
Cardinality 0..1
Type Reference(Practitioner | PractitionerRole | Organization)
Invariants ele-1

PaymentReconciliation.outcome

Short queued | complete | error | partial
Definition The outcome of a request for a reconciliation.
Requirements To advise the requestor of an overall processing outcome.
Comments The resource may be used to indicate that: the request has been held (queued) for processing; that it has been processed and errors found (error); that no errors were found and that some of the adjudication has been undertaken (partial) or that all of the adjudication has been undertaken (complete).
Cardinality 0..1
Type code
Binding remittance-outcome (required)
Invariants ele-1

PaymentReconciliation.disposition

Short Disposition message
Definition A human readable description of the status of the request for the reconciliation.
Requirements Provided for user display.
Cardinality 0..1
Type string
Invariants ele-1

PaymentReconciliation.paymentDate

Short The day the money changed hands
Definition The day the payer paid, or the day the refund was given. This is the effective date: receipts, day-end totals and ageing read it, never created.
Requirements To advise the payee when payment can be expected.
Cardinality 1..1
Type date
Must Support yes
Invariants ele-1

PaymentReconciliation.paymentAmount

Short The whole amount, always positive
Definition The whole sum handed over or returned: equal to the sum of the detail amounts. Always positive -- a refund is told apart by its detail type, not by its sign.
Requirements Needed to provide the actual payment amount.
Cardinality 1..1
Type Money
Must Support yes
Invariants ele-1

PaymentReconciliation.paymentAmount.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.paymentAmount.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.paymentAmount.value

Short Numerical value (with implicit precision)
Definition Numerical value (with implicit precision).
Requirements The amount of the currency. The value includes an implicit precision in the presentation of the value.
Comments Monetary values have their own rules for handling precision (refer to standard accounting text books).
Cardinality 1..1
Type decimal
Invariants ele-1

PaymentReconciliation.paymentAmount.currency

Short ISO 4217 Currency Code
Definition ISO 4217 Currency Code.
Requirements A code indicating the currency, taken from ISO 4217.
Cardinality 1..1
Type code
Must Support yes
Binding currencies (required)
Invariants ele-1

PaymentReconciliation.paymentIdentifier

Short Cheque number, transaction or e-transfer reference
Definition The reference the payment instrument carried, when it carried one: a cheque number, a card terminal transaction number, an e-transfer reference.
Requirements Enable the receiver to reconcile when payment is received.
Comments For example: EFT number or check number.
Cardinality 0..1
Type Identifier
Must Support yes
Invariants ele-1

PaymentReconciliation.detail

Short One allocation per invoice
Definition Where the money lands: one entry per invoice, with the amount allocated to it. A payment split across invoices carries one entry for each.
Requirements Needed to show how the payment amount is distributed across the payables.
Cardinality 1..*
Type BackboneElement
Must Support yes
Invariants ele-1

PaymentReconciliation.detail.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.detail.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.detail.modifierExtension

Short Extensions that cannot be ignored even if unrecognized
Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Modifier yes — Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Invariants ele-1, ext-1
Also called extensions, user content, modifiers

PaymentReconciliation.detail.identifier

Short Business identifier of the payment detail
Definition Unique identifier for the current payment item for the referenced payable.
Requirements Needed for reconciliation of payments.
Cardinality 0..1
Type Identifier
Invariants ele-1

PaymentReconciliation.detail.predecessor

Short Business identifier of the prior payment detail
Definition Unique identifier for the prior payment item for the referenced payable.
Requirements Needed for reconciliation of payments.
Cardinality 0..1
Type Identifier
Invariants ele-1

PaymentReconciliation.detail.type

Short payment | refund
Definition Whether this allocation is money in (http://terminology.hl7.org/CodeSystem/payment-type#payment) or money back (https://fhir.apps.health/CodeSystem/nexus-payment-type#refund). Every detail in one reconciliation carries the same type.
Requirements Needed to provide context for the amount.
Comments For example: payment, adjustment, funds advance, etc.
Cardinality 1..1
Type CodeableConcept
Must Support yes
Binding payment-type (example)
Invariants ele-1

PaymentReconciliation.detail.request

Short The invoice, by its billing-vendor identifier
Definition The invoice this allocation settles, as a logical reference carrying the billing vendor's invoice identifier under https://fhir.apps.health/NamingSystem/nexus-clinicaid-invoice-uuid. The invoice itself is held by the vendor, not by this server.
Requirements Needed to provide a linkage to the original request.
Cardinality 1..1
Type Reference(Resource)
Must Support yes
Invariants ele-1

PaymentReconciliation.detail.submitter

Short Submitter of the request
Definition The party which submitted the claim or financial transaction.
Requirements Needed for audit and validation.
Cardinality 0..1
Type Reference(Practitioner | PractitionerRole | Organization)
Invariants ele-1

PaymentReconciliation.detail.response

Short Response committing to a payment
Definition A resource, such as a ClaimResponse, which contains a commitment to payment.
Requirements Needed to provide a linkage to the payment commitment.
Cardinality 0..1
Type Reference(Resource)
Invariants ele-1

PaymentReconciliation.detail.date

Short The day the money changed hands
Definition The date from the response resource containing a commitment to pay.
Requirements Needed for audit and validation.
Cardinality 0..1
Type date
Must Support yes
Invariants ele-1

PaymentReconciliation.detail.responsible

Short Contact for the response
Definition A reference to the individual who is responsible for inquiries regarding the response and its payment.
Requirements To provide contact information.
Cardinality 0..1
Type Reference(PractitionerRole)
Invariants ele-1

PaymentReconciliation.detail.payee

Short Recipient of the payment
Definition The party which is receiving the payment.
Requirements Needed for audit and validation.
Cardinality 0..1
Type Reference(Practitioner | PractitionerRole | Organization)
Invariants ele-1

PaymentReconciliation.detail.amount

Short The amount allocated to this invoice, always positive
Definition The monetary amount allocated from the total payment to the payable.
Requirements Needed to explain the distribution of the payment to the payables.
Cardinality 1..1
Type Money
Must Support yes
Invariants ele-1

PaymentReconciliation.formCode

Short Printed form identifier
Definition A code for the form to be used for printing the content.
Requirements Needed to specify the specific form used for producing output for this response.
Comments May be needed to identify specific jurisdictional forms.
Cardinality 0..1
Type CodeableConcept
Binding forms (example)
Invariants ele-1

PaymentReconciliation.processNote

Short The office's note on the payment
Definition Free text the office recorded with the payment. This element, not an extension, is the home for a note on this resource.
Requirements Provides the specific textual explanations associated with the processing.
Cardinality 0..*
Type BackboneElement
Must Support yes
Invariants ele-1

PaymentReconciliation.processNote.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

PaymentReconciliation.processNote.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

PaymentReconciliation.processNote.modifierExtension

Short Extensions that cannot be ignored even if unrecognized
Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..*
Type Extension
Modifier yes — Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Invariants ele-1, ext-1
Also called extensions, user content, modifiers

PaymentReconciliation.processNote.type

Short display | print | printoper
Definition The business purpose of the note text.
Requirements To convey the expectation for when the text is used.
Cardinality 0..1
Type code
Binding note-type (required)
Invariants ele-1

PaymentReconciliation.processNote.text

Short Note explanatory text
Definition The explanation or description associated with the processing.
Requirements Required to provide human readable explanation.
Cardinality 0..1
Type string
Invariants ele-1