HL7 Version 2 to FHIR
1.0.0-ballot - ballot International flag

HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions

ConceptMap: Segment ROL to RelatedPerson Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/segment-rol-to-relatedperson Version: 1.0.0-ballot
Active as of 2024-10-30 Computable Name: SegmentROLToRelatedPerson

Copyright/Legal: Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment ROL to the FHIR RelatedPerson Resource.

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

HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierNameData TypeCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativeFHIR AttributeExtensionData TypeCardinality - MinCardinality - MaxData Type MappingVocabulary Mapping
(IS, ID, CE, CEN, CWE)
Assignment
1ROL-1Role Instance IDEI01RelatedPerson.identifierRelatedPerson.Identifier0-1EI[Identifier-Extension]
2ROL-2Action CodeID11if mapped to a restful service to progress the message.
3ROL-3Role-ROLCWE11RelatedPerson.relationshipRelatedPerson.CodeableConcept0-1CWE[CodeableConcept]ProviderRole
4ROL-4Role PersonXCN1-1RelatedPerson.$thisXCN[RelatedPerson]A given ROL segment should create a single RelatedPerson resource, with the name coming from ROL-4 via the Data Type Map provided here and other attributes (eg. address, phone number) from other ROL fields. Therefor, when performing $this, the data type map updates the RelatedPerson resource created from this ROL[RelatedPerson] map.
5ROL-5Role Begin Date/TimeDTM01RelatedPerson.period.startRelatedPerson.dateTime01
6ROL-6Role End Date/TimeDTM01RelatedPerson.period.endRelatedPerson.dateTime01
7ROL-7Role DurationCWE01extension?-durationRelatedPerson.code01CWE[code]
8ROL-8Role Action ReasonCWE01
9ROL-9Provider TypeCWE0-1extension?-providerTypeRelatedPerson.CodeableConcept0-1CWE[CodeableConcept]
10ROL-10Organization Unit TypeCWE01extension?-organizationTypeRelatedPerson.CodeableConcept01CWE[CodeableConcept]ParticipantOrganizationUnitType
11ROL-11Office/Home Address/BirthplaceXAD0-1RelatedPerson.addressRelatedPerson.Address0-1XAD[Address]
12ROL-12PhoneXTN0-1RelatedPerson.telecomRelatedPerson.ContactPoint0-1XTN[ContactPoint]
13ROL-13Person's LocationPL01extension?-location(Location)Reference(RelatedPerson.Location)01PL[Location]
14ROL-14OrganizationXON01extension?-organization(Organization)Reference(RelatedPerson.Organization)01XON[Organization]

Generated Narrative: ConceptMap segment-rol-to-relatedperson

Mapping from ROL to RelatedPerson


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
ROL-1 (Role Instance ID)is equivalent toidentifier
ROL-3 (Role-ROL)is equivalent torelationship
ROL-4 (Role Person)is equivalent to$thisA given ROL segment should create a single RelatedPerson resource, with the name coming from ROL-4 via the Data Type Map provided here and other attributes (eg. address, phone number) from other ROL fields. Therefor, when performing $this, the data type map updates the RelatedPerson resource created from this ROL[RelatedPerson] map.
ROL-5 (Role Begin Date/Time)is equivalent toperiod.start
ROL-6 (Role End Date/Time)is equivalent toperiod.end
ROL-11 (Office/Home Address/Birthplace)is equivalent toaddress
ROL-12 (Phone)is equivalent totelecom

Notes: