FHIR Side
CodeableConcept, Coding, Code/String
Cardinality 1..1/1..*Cardinality 0..1/0..*
ExamplePreferredExtensibleRequiredExamplePreferredExtensibleRequired
v2 SideUser Table (no values)Project Approach: No mapping is provided unless common standardized values are known ofProject Approach: No mapping is provided unless common standardized values are known ofProject Approach: No mapping is provided unless common standardized values are known ofProject Approach: No mapping is provided unless common standardized values are known of
Implementation: If the transformation engine knows the receiving system supports a specific v2 VS then a custom mapping to the FHIR VS should be created and usedImplementation: If the transformation engine knows the receiving system supports a specific v2 VS then a custom mapping to the FHIR VS should be created and usedImplementation: If the transformation engine knows the receiving system supports a specific v2 VS then a custom mapping to the FHIR VS should be created and usedImplementation: If the transformation engine knows the receiving system supports a specific v2 VS then a custom mapping to the FHIR VS should be created and used
Default Behavior: The map should contain an "All Else" notation indicating that unmapped values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 table Default Behavior: The map should contain an "All Else" notation indicating that unmapped values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 table Default Behavior: The map should contain an "All Else" notation indicating that unmapped values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 table Default Behavior: The map should contain an "All Else" notation indicating that unmapped values should use the "orginal code" extension (pending FHIR-I input)
Example: Example: Example: Example:
User Table (suggested values)Project Approach: Unless we have reason to believe that the example FHIR VS is widely implemented, the vocabulary map will carry over the v2 code to the FHIR side and provide a CS uri representing the v2 tableProject Approach: If the preferred FHIR VS contains an appropriate concept, the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table.Project Approach: If the extensible FHIR VS contains an appropriate concept (even if the level of granularity is less granular than the v2 code), the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table.Project Approach: If the required FHIR VS contains an appropriate concept (even if the level of granularity is less granular than the v2 code), the v2 code is mapped to the FHIR VS entry.
Implementation: If the transformation engine knows the receiving system supports the example FHIR VS or alternative VS or knows the receiving system using an extended v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the receiving system supports an extended preferred or alternate FHIR VS or knows the sending system is using an extended or alternate v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the receiving system supports an extended FHIR VS or knows the sending system is using an extended or alternate v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the sending system supports an alternate v2 VS, then a custom mapping to the VS should be created and used
Default Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped values should use the "orginal code" extension (pending FHIR-I input)
Example: Hospital Service (PV1-10)Example: Example: Example:
HL7 Table (non-infrastructural)Project Approach: Unless we have reason to believe that the example VS is widely implemented, the vocabulary map will carry over the v2 code to the FHIR side and provide a CS uri representing the v2 table Project Approach: If the preferred FHIR VS contains an appropriate concept, the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table. Implementation: If the transformation engine knows the receiving system supports an extended or alternate v2 VS, then a custom mapping to the VS should be created and usedProject Approach: If the extensible FHIR VS contains an appropriate concept, the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table. Implementation: If the transformation engine knows the receiving system supports an extended v2 VS, then a custom mapping to the VS should be created and usedProject Approach: If the required FHIR VS contains an appropriate concept (even if the level of granularity is less granular than the v2 code), the v2 code is mapped to the FHIR VS entry. Implementation: If the transformation engine knows the receiving system supports an extended v2 VS, then a custom mapping to the required FHIR VS should be created and used
Implementation: If the transformation engine knows the receiving system supports the example FHIR VS or alternative VS or knows the receiving system using an extended v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the receiving system supports an extended preferred or alternate FHIR VS or knows the sending system is using an extended v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the receiving system supports an extended FHIR VS or knows the sending system is using an extended v2 VS, then a custom mapping to the VS should be created and usedImplementation: If the transformation engine knows the sending system supports an extended v2 VS, then a custom mapping to the VS should be created and used
Default Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped v2 values should either be mapped in a custom mapping or use the "orginal code" extension or the code should be carried over including the CS uri appropriate for the v2 tableDefault Behavior: The map should contain an "All Else" notation indicating that unmapped values should use the "orginal code" extension (pending FHIR-I input)
Example: Example: Example: Example:
HL7 Table (infrastructural)Project Approach: Unless we have reason to believe that the example VS is widely implemented, the vocabulary map will carry over the v2 code to the FHIR side and provide a CS uri representing the v2 tableProject Approach: If the preferred FHIR VS contains an appropriate concept, the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table.Project Approach: If the extensible FHIR VS contains an appropriate concept, the v2 code is mapped to the FHIR VS entry. If the FHIR VS does not contain an appropriate concept, the v2 value is carried over to the FHIR side with a CS uri appropriate to the v2 table.Project Approach: If the required FHIR VS contains an appropriate concept (even if the level of granularity is less granular than the v2 code), the v2 code is mapped to the FHIR VS entry
Implementation: Implementations should not extend or replace HL7 infrastructral tables, so no "default" mapping should be requiredImplementation: Implementations should not extend or replace HL7 infrastructral tables, so no "default" mapping should be requiredImplementation: Implementations should not extend or replace HL7 infrastructral tables, so no "default" mapping should be requiredImplementation: Implementations should not extend or replace HL7 infrastructral tables, so no "default" mapping should be required
Default Behavior: Implementations should not extend HL7 infrastructral tables, so no "default" mapping should be requiredDefault Behavior: Implementations should not extend HL7 infrastructral tables, so no "default" mapping should be requiredDefault Behavior: Implementations should not extend HL7 infrastructral tables, so no "default" mapping should be requiredDefault Behavior: Implementations should not extend HL7 infrastructral tables, so no "default" mapping should be required
Example: Example: Example: Example: