HL7 Version 2 to FHIR
1.0.0 - STU 1

HL7 Version 2 to FHIR - Downloaded Version 1.0.0 See the Directory of published versions

## ConceptMap: Segment DG1 to EpisodeOfCare Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/segment-dg1-to-episodeofcare | Version: 1.0.0
Standards status: Informative | Computable Name: SegmentDG1ToEpisodeOfCare
Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment DG1 to the FHIR EpisodeOfCare Resource.

This ConceptMap represents the mapping from the HL7 V2 DG1 Segment to the FHIR EpisodeOfCare Resource. See also the FHIR Shorthand or the CSV Source.

HL7 v2 | Condition (IF True, args) | HL7 FHIR | Comments
--- | --- | --- | ---
Sort Order | Identifier | Name | Data Type | Cardinality - Min | Cardinality - Max | Computable ANTLR | Computable FHIRPath | Narrative | FHIR Attribute | Extension | Data Type | Cardinality - Min | Cardinality - Max | Data Type Mapping | Vocabulary Mapping (IS, ID, CE, CEN, CWE) | Assignment
1 | DG1-1 | Set ID | SI | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  | Doesn't warrant mapping
2 | DG1-2 | Diagnosis Coding Method | ID | 1 | 1 |  |  |  |  |  |  |  |  |  |  |  | Doesn't warrant mapping
3 | DG1-3 | Diagnosis Code | CWE | 1 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.code) |  | CodeableConcept | 0 | 1 | CWE[CodeableConcept] |  |  |
4 | DG1-4 | Diagnosis Description | ST | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.code.text) |  |  | 0 | 1 |  |  |  | Doesn't warrant mapping
5 | DG1-5 | Diagnosis Date/Time | DTM | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.onsetDateTime) |  | dateTime | 0 | 1 |  |  |  | Should confirm that these two concepts are equivalent. Condition.recordedDate is also available
6 | DG1-6 | Diagnosis Type | CWE | 1 | 1 |  |  |  | EpisodeOfCare.diagnosis.role |  | CodeableConcept | 0 | 1 | CWE[CodeableConcept] | DiagnosisType |  |
7 | DG1-7 | Major Diagnostic Category | CE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
8 | DG1-8 | Diagnostic Related Group | CE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
9 | DG1-9 | DRG Approval Indicator | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
10 | DG1-10 | DRG Grouper Review Code | IS | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
11 | DG1-11 | Outlier Type | CE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
12 | DG1-12 | Outlier Days | NM | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
13 | DG1-13 | Outlier Cost | CP | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
14 | DG1-14 | Grouper Version And Type | ST | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
15 | DG1-15 | Diagnosis Priority | NM | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.rank |  | positiveInt | 0 | 1 |  |  |  | Could contribute to Condition.category or be a new extension
16 | DG1-16 | Diagnosing Clinician | XCN | 0 | -1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.asserter(EpisodeOfCare.Practitioner) |  | Reference | 0 | 1 | XCN[Practitioner] |  |  | While DG1-16 can repeat, we are not aware of instances where this is used. Until such time, we will not yet establish an agreed to method to communicate the extra repeats in FHIR.
17 | DG1-17 | Diagnosis Classification | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
18 | DG1-18 | Confidential Indicator | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
19 | DG1-19 | Attestation Date/Time | DTM | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.extension.url) |  | uri | 1 | 1 |  |  | "http://hl7.org/fhir/StructureDefinition/condition-assertedDate" |
19 | DG1-19 | Attestation Date/Time | DTM | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.extension.valueDateTime) |  | dateTime | 1 | 1 |  |  |  | It is unclear whether to use recorded or asserted date. What is your opinion?
19 | DG1-19 | Attestation Date/Time | DTM | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.recordedDate) |  | dateTime | 0 | 1 |  |  |  | It is unclear whether to use recorded or asserted date. What is your opinion?
20 | DG1-20 | Diagnosis Identifier | EI | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.identifier) |  | Identifier | 0 | -1 | EI[Identifier-Extension] |  |  | We should confirm that this is truly a unique ID before it gets used as .id. It may need to be combined with a visit ID to make it fully unique.
21 | DG1-21 | Diagnosis Action Code | ID | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.verificationStatus.coding.code) |  | code | 0 | 1 |  |  | "entered-in-error" | Other values (A and U) don't map to anything
21 | DG1-21 | Diagnosis Action Code | ID | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.verificationStatus.coding.system) |  | uri | 0 | 1 |  |  | "http://terminology.hl7.org/CodeSystem/condition-ver-status" |
22 | DG1-22 | Parent Diagnosis | EI | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.extension.url) |  |  |  |  |  |  | "http://hl7.org/fhir/StructureDefinition/condition-dueTo" |
22 | DG1-22 | Parent Diagnosis | EI | 0 | 1 |  |  |  | EpisodeOfCare.diagnosis.condition(EpisodeOfCare.Condition.extension.valueReference(EpisodeOfCare.Condition) |  | Reference | 0 | 1 | EI[Condition] |  |  | Extensions for occurredFollowing and related also exist
23 | DG1-23 | DRG CCL Value Code | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
24 | DG1-24 | DRG Grouping Usage | ID | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
25 | DG1-25 | DRG Diagnosis Determination Status | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  |
26 | DG1-26 | Present On Admission (POA) Indicator | CWE | 0 | 1 |  |  |  |  |  |  |  |  |  |  |  | This could contribute to Condition.category, if that value set it extended to include multiple types of diagnoses

Mapping from (not specified) to (not specified)

Group 1 Mapping from `unspecified code system` to `unspecified code system`

Source Code | Relationship | Target Code | Comment
DG1-3 (Diagnosis Code) | is equivalent to | diagnosis.condition(Condition.code) |
DG1-4 (Diagnosis Description) | is equivalent to | diagnosis.condition(Condition.code.text) | Doesn't warrant mapping
DG1-5 (Diagnosis Date/Time) | is equivalent to | diagnosis.condition(Condition.onsetDateTime) | Should confirm that these two concepts are equivalent. Condition.recordedDate is also available
DG1-6 (Diagnosis Type) | is equivalent to | diagnosis.role |
DG1-15 (Diagnosis Priority) | is equivalent to | diagnosis.rank | Could contribute to Condition.category or be a new extension
DG1-16 (Diagnosing Clinician) | is equivalent to | diagnosis.condition(Condition.asserter(Practitioner) | While DG1-16 can repeat, we are not aware of instances where this is used. Until such time, we will not yet establish an agreed to method to communicate the extra repeats in FHIR.
DG1-19 (Attestation Date/Time) | is equivalent to | diagnosis.condition(Condition.extension[1].url) |
DG1-19 (Attestation Date/Time) | is equivalent to | diagnosis.condition(Condition.extension[1].valueDateTime) | It is unclear whether to use recorded or asserted date. What is your opinion?
DG1-19 (Attestation Date/Time) | is equivalent to | diagnosis.condition(Condition.recordedDate) | It is unclear whether to use recorded or asserted date. What is your opinion?
DG1-20 (Diagnosis Identifier) | is equivalent to | diagnosis.condition(Condition.identifier) | We should confirm that this is truly a unique ID before it gets used as .id. It may need to be combined with a visit ID to make it fully unique.
DG1-21 (Diagnosis Action Code) | is equivalent to | diagnosis.condition(Condition.verificationStatus.coding.code) | Other values (A and U) don't map to anything
DG1-21 (Diagnosis Action Code) | is equivalent to | diagnosis.condition(Condition.verificationStatus.coding.system) |
DG1-22 (Parent Diagnosis) | is equivalent to | diagnosis.condition(Condition.extension[2].url) |
DG1-22 (Parent Diagnosis) | is equivalent to | diagnosis.condition(Condition.extension[2].valueReference(Condition)) | Extensions for occurredFollowing and related also exist

### Notes: