CDA Mapping
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABIJKLMNO
1
Element
Cardinality
FHIR Specification MappingBase Card.
Profile Card.
TypeNotesCDA on FHIR call decisionsAdded to Profile
2
ClinicalDocument0..1Bundle.type1..11..1code (fixed to document)y
3
typeId1..1n/a.
4
classCode1..1n/a.
5
moodCode1..1n/a.
6
id1..1Bundle.id1..11..1uriII representation in URI. Use hl7ii. So example: urn:hl7ii:2.16.840.1.113883.19.5.99999.1:TT988

Note: The "mapping" here is illustrative only; if a transformation of one representation to another is performed, then the id is generally NOT the same id; the provenance is traced through the related document/parentDocument etc in the CDA header
Agreed this is where it should go, but this is not something we can actually profile since it is not in a resource. Does this mean we need an implementation guide in addition to a profile? y
7
code1..1Composition.type1..11..1CodeableConceptoky
8
title0..1Composition.title0..10..1stringoky
9
effectiveTime1..1Composition.date1..11..1dateTimeoky
10
confidentialityCode1..1Composition.confidentiality1..11..1CodingTODO: change to 0..1, but expand type? (Coding < CE)?y
11
languageCode0..1Resource.lang0..10..1codeoky
12
setId0..1Composition.identifier0..10..1Identifier
ok, but need to document clearly that this is NOT the equivalient of ClincalDocument/id.
y
13
versionNumber0..1Extension to Composition0..10..1Integerok, tentativelyTODO
14
copyTime0..1n/adeprecatedAgree for now not needed. .
15
recordTarget1..*Composition.subject1..11..*PatientStrictly this is not a correct match (subject not record target, but that's how it's used anyway)
In FHIR, you could handle the case of HAI and QRDA denominator reports by making the subject a group. In CDA, we had to null the record target then create a separate subject participant.
y
16
typeCode1..1n/a.
17
contextControlCode1..1n/a.
18
patientRole1..1n/a.
19
classCode1..1n/a.
20
id1..*Patient.identifier0..*1..*Identifieroky
21
addr0..*Patient.address0..*0..*Addressoky
22
telecom0..*Patient.telecom0..*0..*Contactoky
23
patient0..1n/a.
24
classCode1..1n/a.
25
determinerCode1..1n/a.
26
id0..1n/adeprecated
Still needs to map to Patient.identifier, because C32 used this even though deprecated in CDA.
y
27
name0..*Patient.name0..*0..*HumanNameoky
28
administrativeGenderCode0..1Patient.gender0..10..1CodeableConceptdomain ok oky
29
birthTime0..1Patient.birthDate0..10..1dateTimeoky
30
maritalStatusCode0..1Patient.maritalStatus0..10..1CodeableConceptdomain ok oky
31
religiousAffiliationCode0..1Extension to Patient 0..10..1CodeableConceptExtension defined in US profileoky
32
raceCode0..1Extension to Patient 0..*0..*CodeableConceptAlready defined in US profileoky
33
ethnicGroupCode0..1Extension to Patient 0..*0..*CodeableConceptAlready defined in US profileoky
34
guardian0..*Patient.contact0..*0..*oky
35
classCode1..1Patient.contact.relationship1..11..1CodeableConcepthttp://hl7.org/fhir/patient-contact-relationship::guardianoky
36
id0..*Extension to Patient.contact0..*0..*IdentifierTODO: create task to bring this back (serves dual purpose…)
ok, but may become a core addition to Patient.contact vs. an extension to Patient.contact.
y
37
code0..1Patient.contact.relationship0..10..1CodeableConceptAdditional codeoky
38
addr0..*Patient.contact.address0..10..*AddressTodo: define an extensionoky
39
telecom0..*Patient.contact.telecom0..*0..*Contactoky
40
guardianChoice1..1n/a.
41
guardianPerson1..1n/a.
42
classCode1..1n/a.
43
determinerCode1..1n/a.
44
name0..*Patient.contact.name0..10..*HumanNameTodo: define an extensionoky
45
guardianOrganization1..1Patient.contact.organization0..11..1ReferenceSee below for mappingoky
46
birthplace0..1Extension to Patient 0..10..1Extension
Referrence to Location- TODO: Add extension to intl profile
Vital statistics use this. Seems appropriate as an extension vs. core.
y
47
classCode1..1n/a.
48
place1..1n/a.
49
classCode1..1n/a.
50
determinerCode1..1n/a.
51
name0..1Location.name0..10..1Stringoky
52
addr0..1Location.address0..10..1Addressoky
53
languageCommunication0..*n/a.
54
languageCode0..1Patient.communication0..*0..*CodeableConceptok. Discussed that this is required in US, but not appropriate for all international needs.y
55
modeCode0..1Extension to Patient.communication0..10..1CodeableConceptTODO: Add extension to intl profileoky
56
proficiencyLevelCode0..1Extension to Patient.communication0..10..1CodeableConceptTODO: Add extension to intl profileoky
57
preferenceInd0..1Extension to Patient.communication0..10..1booleanTODO: Add extension to intl profileoky
58
providerOrganization0..1Patient.managingOrganization0..10..1Referenceoky
59
classCode1..1n/a.
60
determinerCode1..1n/a.
61
id0..*Organization.identifier0..*0..*Identifieroky
62
name0..*Organization.name0..10..*HumanNameTodo: define an extensionoky
63
telecom0..*Organization.telecom0..*0..*Contactoky
64
addr0..*Organization.address0..*0..*Addressoky
65
standardIndustryClassCode0..1Organization.type0..10..1CodeableConceptoky
66
asOrganizationPartOf0..1n/a.
67
classCode1..1n/a.
68
id0..*See notes0..*0..*Identifier
Put this in Organization.id (because of role/entity id legacy)
y
69
code0..1Extension to Organization.partOf0..10..1CodeableConceptoky
70
statusCode0..1Extension to Organization.partOf0..10..1codeoky
71
effectiveTime0..1Extension to Organization.partOf0..10..1Periodoky
72
wholeOrganization0..1Extension to Organization0..10..1Referencethis is an extensionoky
73
author1..*Composition.author1..*1..*
Practitioner/Device/Patient/RelatedPerson
May be Patient or related Person depending on the author.role
(Rick)
74
typeCode1..1n/a
75
functionCode0..1Extension to Composition.author0..10..1CodeableConceptok
76
contextControlCode1..1n/a
77
time1..1Extension to Composition author1..1
ok, Grahame will see if this should be moved to core in the future.
78
assignedAuthor1..1Practitioner / Patient / Device / RelatedPerson1..1ok
79
classCode1..1n/a
80
id1..*Practitioner.id / Device.id0..*1..*ok
81
code0..1Practitioner.role / Device.type0..* / 1..10..1CodeableConceptDevice Type is requiredok
82
addr0..*Practitioner.address / Device.location->address0..10..*ok
83
telecom0..*Practitioner.telecom / Device.contact0..*0..*ok
84
assignedAuthorChoice0..1n/a
85
assignedPerson1..1Practitioner / Patient / RelatedPerson1..1see belowok
86
assignedAuthoringDevice1..1Device1..1ok
87
classCode1..1n/a
88
determinerCode1..1n/a
89
code0..1Device.type1..10..1CodeableConceptAnd also mapped aboveok with caveats on required device.type
90
manufacturerModelName0..1Device.model0..10..1stringok
91
softwareName0..1Extension to Device0..10..1string?
92
asMaintainedEntity0..*Extension to Device0..*0..*Extensionok
93
classCode1..1n/a
94
effectiveTime0..1Extension to Device extension0..10..1Periodok
95
maintainingPerson1..1Extension to Device extension1..11..1Referenceok
96
representedOrganization0..1Practitioner.organization / Device.owner0..10..1Referenceok
97
dataEnterer0..1Provenance Resource 0..10..1backwards ReferenceTo a Practitioner
98
typeCode1..1n/a
99
contextControlCode1..1n/a
100
time0..1Provenance.period0..1
Loading...