FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-EpisodeOfCare-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/ConceptMap-R5-EpisodeOfCare-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-EpisodeOfCare-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:04:45.1859381-05:00 |
| Name | R5EpisodeOfCareElementMapToR4 |
| Title | Cross-version mapping for FHIR R5 EpisodeOfCare to FHIR R4 EpisodeOfCare |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 EpisodeOfCare to FHIR R4. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-EpisodeOfCare.diagnosis.condition | Cross-version Extension for R5.EpisodeOfCare.diagnosis.condition for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-EpisodeOfCare.reason | Cross-version Extension for R5.EpisodeOfCare.reason for use in FHIR R4 |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-EpisodeOfCare-element-map-to-R4
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/EpisodeOfCare|5.0.0 to EpisodeOfCareversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| EpisodeOfCare.meta (meta) | is equivalent to | EpisodeOfCare.meta | Element `EpisodeOfCare.meta` is mapped to FHIR R4 element `EpisodeOfCare.meta` as `Equivalent`. |
| EpisodeOfCare.implicitRules (implicitRules) | is equivalent to | EpisodeOfCare.implicitRules | Element `EpisodeOfCare.implicitRules` is mapped to FHIR R4 element `EpisodeOfCare.implicitRules` as `Equivalent`. 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 its narrative along with other profiles, value sets, etc. |
| EpisodeOfCare.language (language) | is equivalent to | EpisodeOfCare.language | Element `EpisodeOfCare.language` is mapped to FHIR R4 element `EpisodeOfCare.language` as `Equivalent`. 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). |
| EpisodeOfCare.text (text) | is equivalent to | EpisodeOfCare.text | Element `EpisodeOfCare.text` is mapped to FHIR R4 element `EpisodeOfCare.text` as `Equivalent`. Contained resources do not have a 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. |
| EpisodeOfCare.contained (contained) | is equivalent to | EpisodeOfCare.contained | Element `EpisodeOfCare.contained` is mapped to FHIR R4 element `EpisodeOfCare.contained` as `Equivalent`. 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. |
| EpisodeOfCare.identifier (identifier) | is equivalent to | EpisodeOfCare.identifier | Element `EpisodeOfCare.identifier` is mapped to FHIR R4 element `EpisodeOfCare.identifier` as `Equivalent`. |
| EpisodeOfCare.status (status) | is equivalent to | EpisodeOfCare.status | Element `EpisodeOfCare.status` is mapped to FHIR R4 element `EpisodeOfCare.status` as `Equivalent`. This element is labeled as a modifier because the status contains codes that mark the episode as not currently valid. |
| EpisodeOfCare.statusHistory (statusHistory) | maps to wider concept | EpisodeOfCare.statusHistory | Element `EpisodeOfCare.statusHistory` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory` as `Equivalent`. |
| EpisodeOfCare.statusHistory.status (status) | is equivalent to | EpisodeOfCare.statusHistory.status | Element `EpisodeOfCare.statusHistory.status` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory.status` as `Equivalent`. |
| EpisodeOfCare.statusHistory.period (period) | is equivalent to | EpisodeOfCare.statusHistory.period | Element `EpisodeOfCare.statusHistory.period` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory.period` as `Equivalent`. |
| EpisodeOfCare.type (type) | is equivalent to | EpisodeOfCare.type | Element `EpisodeOfCare.type` is mapped to FHIR R4 element `EpisodeOfCare.type` as `Equivalent`. The type can be very important in processing as this could be used in determining if the EpisodeOfCare is relevant to specific government reporting, or other types of classifications. |
| EpisodeOfCare.diagnosis (diagnosis) | maps to wider concept | EpisodeOfCare.diagnosis | Element `EpisodeOfCare.diagnosis` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis` as `Equivalent`. The diagnosis communicates what medical conditions were actually addressed during the episode of care. If a diagnosis was provided as a reason, and was treated during the episode of care, it may be listed in both EpisodeOfCare.reason and EpisodeOfCare.diagnosis. Diagnoses related to billing can be documented on the Account resources which supports ranking for the purpose of reimbursement. |
| EpisodeOfCare.diagnosis.condition (condition) | maps to wider concept | EpisodeOfCare.diagnosis.condition | Element `EpisodeOfCare.diagnosis.condition` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.condition` as `SourceIsBroaderThanTarget`. The mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types: CodeableReference. The mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types based on type expansion: concept. |
| EpisodeOfCare.diagnosis.use (use) | is equivalent to | EpisodeOfCare.diagnosis.role | Element `EpisodeOfCare.diagnosis.use` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.role` as `Equivalent`. |
| EpisodeOfCare.patient (patient) | is equivalent to | EpisodeOfCare.patient | Element `EpisodeOfCare.patient` is mapped to FHIR R4 element `EpisodeOfCare.patient` as `Equivalent`. |
| EpisodeOfCare.managingOrganization (managingOrganization) | is equivalent to | EpisodeOfCare.managingOrganization | Element `EpisodeOfCare.managingOrganization` is mapped to FHIR R4 element `EpisodeOfCare.managingOrganization` as `Equivalent`. If multiple organizations are involved in care delivery, the care teams from those organizations would be represented in EpisodeOfCare.team, while the primary organization managing the care would be listed in EpisodeOfCare.managingOrganization. Other organizations may have their own EpisodeOfCare for tracking their activities. |
| EpisodeOfCare.period (period) | is equivalent to | EpisodeOfCare.period | Element `EpisodeOfCare.period` is mapped to FHIR R4 element `EpisodeOfCare.period` as `Equivalent`. |
| EpisodeOfCare.referralRequest (referralRequest) | is equivalent to | EpisodeOfCare.referralRequest | Element `EpisodeOfCare.referralRequest` is mapped to FHIR R4 element `EpisodeOfCare.referralRequest` as `Equivalent`. |
| EpisodeOfCare.careManager (careManager) | is equivalent to | EpisodeOfCare.careManager | Element `EpisodeOfCare.careManager` is mapped to FHIR R4 element `EpisodeOfCare.careManager` as `Equivalent`. |
| EpisodeOfCare.careTeam (careTeam) | is equivalent to | EpisodeOfCare.team | Element `EpisodeOfCare.careTeam` is mapped to FHIR R4 element `EpisodeOfCare.team` as `Equivalent`. |
| EpisodeOfCare.account (account) | is equivalent to | EpisodeOfCare.account | Element `EpisodeOfCare.account` is mapped to FHIR R4 element `EpisodeOfCare.account` as `Equivalent`. The billing system may choose to allocate billable items associated with the EpisodeOfCare to different referenced Accounts based on internal business rules. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/EpisodeOfCare|5.0.0 to R5: The list of medical reasons that are expected to be addressed during the episode of care (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EpisodeOfCare.reason (reason) | maps to wider concept | Extension (R5: The list of medical reasons that are expected to be addressed during the episode of care (new)) | Element `EpisodeOfCare.reason` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`. Element `EpisodeOfCare.reason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The reason communicates what medical problem the patient has that should be addressed during the episode of care. This reason could be patient reported complaint, a clinical indication that was determined in a previous encounter or episode of care, or some planned care such as an immunization recommendation. In the case where you have a primary reason, but are expecting to also address other problems, you can list the primary reason with a use code of 'Chief Complaint', while the other problems being addressed would have a use code of 'Reason for Visit'. Examples: * pregnancy would use HealthcareService or a coding as the reason * patient home monitoring could use Condition as the reason |
| EpisodeOfCare.reason.use (use) | maps to wider concept | Extension.extension:use (R5: What the reason value should be used for/as (new)) | Element `EpisodeOfCare.reason.use` is part of an existing definition because parent element `EpisodeOfCare.reason` requires a cross-version extension. Element `EpisodeOfCare.reason.use` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`. Element `EpisodeOfCare.reason.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| EpisodeOfCare.reason.value (value) | maps to wider concept | Extension.extension:value (R5: Medical reason to be addressed (new)) | Element `EpisodeOfCare.reason.value` is part of an existing definition because parent element `EpisodeOfCare.reason` requires a cross-version extension. Element `EpisodeOfCare.reason.value` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`. Element `EpisodeOfCare.reason.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/EpisodeOfCare|5.0.0 to R5: The medical condition that was addressed during the episode of care additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EpisodeOfCare.diagnosis.condition (condition) | is equivalent to | Extension (R5: The medical condition that was addressed during the episode of care additional types) | Element `EpisodeOfCare.diagnosis.condition` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.condition` as `SourceIsBroaderThanTarget`. The mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types: CodeableReference. The mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types based on type expansion: concept. |
{
"resourceType": "ConceptMap",
"id": "R5-EpisodeOfCare-element-map-to-R4",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-EpisodeOfCare-element-map-to-R4",
"version": "0.1.0",
"name": "R5EpisodeOfCareElementMapToR4",
"title": "Cross-version mapping for FHIR R5 EpisodeOfCare to FHIR R4 EpisodeOfCare",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:04:45.1859381-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 EpisodeOfCare to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/EpisodeOfCare",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/EpisodeOfCare",
"targetVersion": "4.0.1",
"element": [
{
"code": "EpisodeOfCare.meta",
"display": "meta",
"target": [
{
"code": "EpisodeOfCare.meta",
"display": "EpisodeOfCare.meta",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.meta` is mapped to FHIR R4 element `EpisodeOfCare.meta` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "EpisodeOfCare.implicitRules",
"display": "EpisodeOfCare.implicitRules",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.implicitRules` is mapped to FHIR R4 element `EpisodeOfCare.implicitRules` as `Equivalent`.\nAsserting 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 its narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "EpisodeOfCare.language",
"display": "language",
"target": [
{
"code": "EpisodeOfCare.language",
"display": "EpisodeOfCare.language",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.language` is mapped to FHIR R4 element `EpisodeOfCare.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code": "EpisodeOfCare.text",
"display": "text",
"target": [
{
"code": "EpisodeOfCare.text",
"display": "EpisodeOfCare.text",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.text` is mapped to FHIR R4 element `EpisodeOfCare.text` as `Equivalent`.\nContained resources do not have a 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."
}
]
},
{
"code": "EpisodeOfCare.contained",
"display": "contained",
"target": [
{
"code": "EpisodeOfCare.contained",
"display": "EpisodeOfCare.contained",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.contained` is mapped to FHIR R4 element `EpisodeOfCare.contained` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "EpisodeOfCare.identifier",
"display": "identifier",
"target": [
{
"code": "EpisodeOfCare.identifier",
"display": "EpisodeOfCare.identifier",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.identifier` is mapped to FHIR R4 element `EpisodeOfCare.identifier` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.status",
"display": "status",
"target": [
{
"code": "EpisodeOfCare.status",
"display": "EpisodeOfCare.status",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.status` is mapped to FHIR R4 element `EpisodeOfCare.status` as `Equivalent`.\nThis element is labeled as a modifier because the status contains codes that mark the episode as not currently valid."
}
]
},
{
"code": "EpisodeOfCare.statusHistory",
"display": "statusHistory",
"target": [
{
"code": "EpisodeOfCare.statusHistory",
"display": "EpisodeOfCare.statusHistory",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.statusHistory` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.statusHistory.status",
"display": "status",
"target": [
{
"code": "EpisodeOfCare.statusHistory.status",
"display": "EpisodeOfCare.statusHistory.status",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.statusHistory.status` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory.status` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.statusHistory.period",
"display": "period",
"target": [
{
"code": "EpisodeOfCare.statusHistory.period",
"display": "EpisodeOfCare.statusHistory.period",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.statusHistory.period` is mapped to FHIR R4 element `EpisodeOfCare.statusHistory.period` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.type",
"display": "type",
"target": [
{
"code": "EpisodeOfCare.type",
"display": "EpisodeOfCare.type",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.type` is mapped to FHIR R4 element `EpisodeOfCare.type` as `Equivalent`.\nThe type can be very important in processing as this could be used in determining if the EpisodeOfCare is relevant to specific government reporting, or other types of classifications."
}
]
},
{
"code": "EpisodeOfCare.diagnosis",
"display": "diagnosis",
"target": [
{
"code": "EpisodeOfCare.diagnosis",
"display": "EpisodeOfCare.diagnosis",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.diagnosis` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis` as `Equivalent`.\nThe diagnosis communicates what medical conditions were actually addressed during the episode of care. If a diagnosis was provided as a reason, and was treated during the episode of care, it may be listed in both EpisodeOfCare.reason and EpisodeOfCare.diagnosis.\r\rDiagnoses related to billing can be documented on the Account resources which supports ranking for the purpose of reimbursement."
}
]
},
{
"code": "EpisodeOfCare.diagnosis.condition",
"display": "condition",
"target": [
{
"code": "EpisodeOfCare.diagnosis.condition",
"display": "EpisodeOfCare.diagnosis.condition",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.diagnosis.condition` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.condition` as `SourceIsBroaderThanTarget`.\nThe mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types: CodeableReference.\nThe mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types based on type expansion: concept."
}
]
},
{
"code": "EpisodeOfCare.diagnosis.use",
"display": "use",
"target": [
{
"code": "EpisodeOfCare.diagnosis.role",
"display": "EpisodeOfCare.diagnosis.role",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.diagnosis.use` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.role` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.patient",
"display": "patient",
"target": [
{
"code": "EpisodeOfCare.patient",
"display": "EpisodeOfCare.patient",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.patient` is mapped to FHIR R4 element `EpisodeOfCare.patient` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.managingOrganization",
"display": "managingOrganization",
"target": [
{
"code": "EpisodeOfCare.managingOrganization",
"display": "EpisodeOfCare.managingOrganization",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.managingOrganization` is mapped to FHIR R4 element `EpisodeOfCare.managingOrganization` as `Equivalent`.\nIf multiple organizations are involved in care delivery, the care teams from those organizations would be represented in EpisodeOfCare.team, while the primary organization managing the care would be listed in EpisodeOfCare.managingOrganization. Other organizations may have their own EpisodeOfCare for tracking their activities."
}
]
},
{
"code": "EpisodeOfCare.period",
"display": "period",
"target": [
{
"code": "EpisodeOfCare.period",
"display": "EpisodeOfCare.period",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.period` is mapped to FHIR R4 element `EpisodeOfCare.period` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.referralRequest",
"display": "referralRequest",
"target": [
{
"code": "EpisodeOfCare.referralRequest",
"display": "EpisodeOfCare.referralRequest",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.referralRequest` is mapped to FHIR R4 element `EpisodeOfCare.referralRequest` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.careManager",
"display": "careManager",
"target": [
{
"code": "EpisodeOfCare.careManager",
"display": "EpisodeOfCare.careManager",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.careManager` is mapped to FHIR R4 element `EpisodeOfCare.careManager` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.careTeam",
"display": "careTeam",
"target": [
{
"code": "EpisodeOfCare.team",
"display": "EpisodeOfCare.team",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.careTeam` is mapped to FHIR R4 element `EpisodeOfCare.team` as `Equivalent`."
}
]
},
{
"code": "EpisodeOfCare.account",
"display": "account",
"target": [
{
"code": "EpisodeOfCare.account",
"display": "EpisodeOfCare.account",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.account` is mapped to FHIR R4 element `EpisodeOfCare.account` as `Equivalent`.\nThe billing system may choose to allocate billable items associated with the EpisodeOfCare to different referenced Accounts based on internal business rules."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/EpisodeOfCare",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-EpisodeOfCare.reason",
"targetVersion": "0.1.0",
"element": [
{
"code": "EpisodeOfCare.reason",
"display": "reason",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.reason` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`.\nElement `EpisodeOfCare.reason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe reason communicates what medical problem the patient has that should be addressed during the episode of care. This reason could be patient reported complaint, a clinical indication that was determined in a previous encounter or episode of care, or some planned care such as an immunization recommendation. In the case where you have a primary reason, but are expecting to also address other problems, you can list the primary reason with a use code of 'Chief Complaint', while the other problems being addressed would have a use code of 'Reason for Visit'.\r\rExamples:\r * pregnancy would use HealthcareService or a coding as the reason\r * patient home monitoring could use Condition as the reason"
}
]
},
{
"code": "EpisodeOfCare.reason.use",
"display": "use",
"target": [
{
"code": "Extension.extension:use",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.reason.use` is part of an existing definition because parent element `EpisodeOfCare.reason` requires a cross-version extension.\nElement `EpisodeOfCare.reason.use` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`.\nElement `EpisodeOfCare.reason.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "EpisodeOfCare.reason.value",
"display": "value",
"target": [
{
"code": "Extension.extension:value",
"equivalence": "wider",
"comment": "Element `EpisodeOfCare.reason.value` is part of an existing definition because parent element `EpisodeOfCare.reason` requires a cross-version extension.\nElement `EpisodeOfCare.reason.value` has a context of EpisodeOfCare based on following the parent source element upwards and mapping to `EpisodeOfCare`.\nElement `EpisodeOfCare.reason.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/EpisodeOfCare",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-EpisodeOfCare.diagnosis.condition",
"targetVersion": "0.1.0",
"element": [
{
"code": "EpisodeOfCare.diagnosis.condition",
"display": "condition",
"target": [
{
"code": "Extension",
"equivalence": "equivalent",
"comment": "Element `EpisodeOfCare.diagnosis.condition` is mapped to FHIR R4 element `EpisodeOfCare.diagnosis.condition` as `SourceIsBroaderThanTarget`.\nThe mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types: CodeableReference.\nThe mappings for `EpisodeOfCare.diagnosis.condition` do not cover the following types based on type expansion: concept."
}
]
}
]
}
]
}