Payment Notice

$10 / year

Payment Notice resource provides the status of the payment for goods and services rendered, and the request and response resource references.


The Payment Notice 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 payers to advise the provider or regulatory bodies of the state of a payment (check in the mail/Electronic Funds Transfer (EFT) sent, payment cashed, payment canceled). Employers or Insurance Exchanges may use this to advise payers of premium payment. 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 payers that premium payments have been issued and settled.

Additional information regarding electronic payment notice content and usage may be found at:

– Financial Resource Status Lifecycle: how status is used in the financial resources.
– Batches: how eClaims may handle batches of eligibility, claims, payments and responses.

The Payment Notice resource is used to indicate that a payment has occurred or is about to occur. The resource is used commonly when tracking of payment occurrences is required for regulatory or business purposes, such as ensuring that payment of claim adjudications occurs within a specific timeframe. The Payment Notice is not used to report adjudicated amounts or to reconcile adjudicated amounts against actual payment.

The Claim Response 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 Payment Reconciliation resource serves to correlate payment amounts to the adjudicated claim amounts appearing on one or more Claim Responses.

Date Created


Last Modified




Update Frequency


Temporal Coverage


Spatial Coverage

United States


John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements


Source Citation



FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Payment Notice Resource, Electronic Health Records Exchange Through FHIR

Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
RequiredThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
ConstThe value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.string-
Concept NameComputer Ready NameTypeDollar RefDescriptionItemsRequiredConst
PaymentNoticeresourceTypeThis is a PaymentNotice resourcePaymentNotice
PaymentNoticeid#/definitions/idThe logical id of the resource as used in the URL for the resource. Once assigned this value never changes.
PaymentNoticemeta#/definitions/MetaThe 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.
PaymentNoticeimplicitRules#/definitions/uriA 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.
PaymentNotice_implicitRules#/definitions/ElementExtensions for implicitRules
PaymentNoticelanguage#/definitions/codeThe base language in which the resource is written.
PaymentNotice_language#/definitions/ElementExtensions for language
PaymentNoticetext#/definitions/NarrativeA 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.
PaymentNoticecontainedarrayThese 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.{'$ref': '#/definitions/ResourceList'}
PaymentNoticeextensionarrayMay 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.{'$ref': '#/definitions/Extension'}
Related Data Packages