Release 4 Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32 ) in it's permanent home (it will always be available at this URL). ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Consent-example.xml

13.9.24 Resource PaymentReconciliation - Maturity Dependency View

Community Based Collaborative Care Financial Management icon Work Group Maturity Level : N/A 2   Trial Use Standards Status : Informative Compartments : Patient Practitioner

Raw XML Dependency Graph for PaymentReconciliation FMM level 2

Jump past Narrative </ Consent
Name Card. Type Dependency Analysis
.. PaymentReconciliation DomainResource
... identifier 0..* Identifier
... type 1..1 CodeableConcept
... status 1..1 code
... kind 0..1 CodeableConcept
... period 0..1 Period
... created 1..1 dateTime
... enterer 0..1 Reference ( canonical form Practitioner + also see XML Format Specification | PractitionerRole | Organization )
. . . issuerType General Consent Example (id 0..1 CodeableConcept
... paymentIssuer 0..1 Reference ( Organization | Patient | Person | RelatedPerson )
... request 0..1 Reference ( Task )
... requestor 0..1 Reference ( Practitioner | PractitionerRole | Organization )
... outcome 0..1 code
... disposition 0..1 string
... date 1..1 date
... location 0..1 Reference ( Location )
... method 0..1 CodeableConcept Binding Error: Unable to resolve vs 'http://terminology.hl7.org/ValueSet/v2-0570' to check dependencies
... cardBrand 0..1 string
... accountNumber 0..1 string
... expirationDate 0..1 date
... processor 0..1 string
... referenceNumber 0..1 string
... authorization 0..1 string
... tenderedAmount 0..1 Money
... returnedAmount 0..1 Money
... amount 1..1 Money
... paymentIdentifier 0..1 Identifier
... allocation 0..* BackboneElement
.... identifier 0..1 Identifier
.... predecessor 0..1 Identifier
.... target 0..1 Reference ( Claim | Account | Invoice | ChargeItem | Encounter | Contract ) Type Warning: (Invoice = "consent-example-basic") <?xml version="1.0" encoding="UTF-8"?> Authorize Normal access for Treatment Patient &quot;P. van de Heuvel&quot; wishes to have all of the PHI collected at the Good Health Psychiatric Hospital available for normal treatment use. FMM0-Trial Use vs. Element = FMM2-Trial Use)
Type Warning: (ChargeItem = FMM0-Trial Use vs. Element = FMM2-Trial Use)
Type Warning: (Contract = FMM1-Trial Use vs. Element = FMM2-Trial Use)
. . . . targetItem[x] > 0..1
..... targetItemString string
. . . . . targetItemIdentifier Identifier
..... targetItemPositiveInt positiveInt
.... encounter 0..1 Reference ( Encounter )
.... account 0..1 Reference ( Account )
.... type 0..1 CodeableConcept
.... submitter 0..1 Reference ( Practitioner | PractitionerRole | Organization )
.... response 0..1 Reference ( ClaimResponse )
.... date 0..1 date
.... responsible 0..1 Reference ( PractitionerRole )
.... payee 0..1 Reference ( Practitioner | PractitionerRole | Organization )
.... amount 0..1 Money
... formCode 0..1 CodeableConcept
... processNote 0..* BackboneElement
.... type 0..1 code
.... text 0..1 string
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.