This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
.
Page
versions:
R4B
R4
R3
Extension-translation.xml
Example
PaymentReconciliation/ER2500
(XML)
Raw
XML
(
canonical
form
+
also
see
XML
Format
Specification
)
Jump
past
Narrative
Translation
General
Payment
Reconciliation
Example
(id
=
"ER2500")
unique id for the element within a resource (for internal references). This may be any
string value that does not contain spaces.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
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.
unique id for the element within a resource (for internal references). This may be any
string value that does not contain spaces.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
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.
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.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
unique id for the element within a resource (for internal references). This may be any
string value that does not contain spaces.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
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.
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.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
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.
Value of extension - may be a resource or one of a constrained set of the data types (see
Extensibility in the spec for list).
<?xml version="1.0" encoding="UTF-8"?>
<PaymentReconciliation xmlns="http://hl7.org/fhir"> <id value="ER2500"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">A human-readable rendering of the PaymentReconciliation</div> </text> <identifier> <system value="http://www.BenefitsInc.com/fhir/enrollmentresponse"/> <value value="781234"/> </identifier> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/payment-type"/> <code value="payment"/> </coding> </type> <status value="active"/> <period> <start value="2014-08-16"/> <end value="2014-08-31"/> </period> <created value="2014-08-16"/> <paymentIssuer> <reference value="Organization/2"/> </paymentIssuer> <request> <reference value="http://www.BenefitsInc.com/fhir/eligibility/225476332402"/> </request> <requestor> <reference value="Organization/1"/> </requestor> <outcome value="complete"/> <disposition value="2014 August mid-month settlement."/> <date value="2014-08-01"/> <amount> <value value="7000.00"/> <currency value="USD"/> </amount> <paymentIdentifier> <system value="http://www.BenefitsInc.com/payment/2018"/> <value value="10-12345"/> </paymentIdentifier> <allocation> <identifier> <system value="http://www.BenefitsInc.com/payment/2018/detail"/> <value value="10-12345-001"/> </identifier> <target> <identifier> <system value="http://happyvalleyclinic.com/claim"/> <value value="AB12345"/> </identifier> </target> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/payment-type"/> <code value="payment"/> </coding> </type> <submitter> <reference value="Organization/1"/> </submitter> <response> <identifier> <system value="http://www.BenefitsInc.com/fhir/claimresponse"/> <value value="CR20140815-AB12345"/> </identifier> </response> <date value="2014-08-16"/> <payee> <reference value="Organization/1"/> </payee> <amount> <value value="3500.00"/> <currency value="USD"/> </amount> </allocation> <allocation> <identifier> <system value="http://www.BenefitsInc.com/payment/2018/detail"/> <value value="10-12345-002"/> </identifier> <target> <reference value="http://www.BenefitsInc.com/fhir/oralhealthclaim/225476332699"/> </target> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/payment-type"/> <code value="payment"/> </coding> </type> <date value="2014-08-12"/> <amount> <value value="4000.00"/> <currency value="USD"/> </amount> </allocation> <allocation> <identifier> <system value="http://www.BenefitsInc.com/payment/2018/detail"/> <value value="10-12345-003"/> </identifier> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/payment-type"/> <code value="advance"/> </coding> </type> <date value="2014-08-16"/> <amount> <value value="-1500.00"/> <currency value="USD"/> </amount> </allocation> <formCode> <coding> <system value="http://ncforms.org/formid"/> <code value="PAYREC/2016/01B"/> </coding> </formCode> <processNote> <type value="display"/> <text value="Due to the year end holiday the cutoff for submissions for December will be the
28th."/>
</processNote>
</
StructureDefinition
PaymentReconciliation
>
Usage
note:
every
effort
has
been
made
to
ensure
that
the
examples
are
correct
and
useful,
but
they
are
not
a
normative
part
of
the
specification.