Segment ROL to RelatedPerson Map - HL7 Version 2 to FHIR v1.0.0

HL7 Version 2 to FHIR
1.0.0 - STU 1 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 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/ConceptMap/segment-rol-to-relatedperson				Version: 1.0.0
Active as of 2025-04-30				Computable Name: SegmentROLToRelatedPerson
Copyright/Legal: Copyright (c) 2025, 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 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	Comments
1	ROL-1	Role Instance ID	EI	0	1				Identifier		Identifier	0	-1	EI[Identifier-Extension]
2	ROL-2	Action Code	ID	1	1			if mapped to a restful service to progress the message.
3	ROL-3	Role-ROL	CWE	1	1				RelatedPerson.relationship		CodeableConcept	0	-1	CWE[CodeableConcept]	ProviderRole
4	ROL-4	Role Person	XCN	1	-1				RelatedPerson.$this					XCN[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.
5	ROL-5	Role Begin Date/Time	DTM	0	1				RelatedPerson.period.start		dateTime	0	1
6	ROL-6	Role End Date/Time	DTM	0	1				RelatedPerson.period.end		dateTime	0	1
7	ROL-7	Role Duration	CWE	0	1					extension?-duration	code	0	1	CWE[code]
8	ROL-8	Role Action Reason	CWE	0	1
9	ROL-9	Provider Type	CWE	0	-1					extension?-providerType	CodeableConcept	0	-1	CWE[CodeableConcept]
10	ROL-10	Organization Unit Type	CWE	0	1					extension?-organizationType	CodeableConcept	0	1	CWE[CodeableConcept]
11	ROL-11	Office/Home Address/Birthplace	XAD	0	-1				Address		Address	0	-1	XAD[Address]
12	ROL-12	Phone	XTN	0	-1				RelatedPerson.telecom		ContactPoint	0	-1	XTN[ContactPoint]
13	ROL-13	Person's Location	PL	0	1					extension?-location(Location)	Reference(RelatedPerson.Location)	0	1	PL[Location]
14	ROL-14	Organization	XON	0	1					extension?-organization(Organization)	Reference(RelatedPerson.Organization)	0	1	XON[Organization]

Generated Narrative: ConceptMap segment-rol-to-relatedperson

Mapping from (not specified) to (not specified)

Group 1 Mapping from unspecified code system to unspecified code system

Source Code

Relationship

Target Code

Comment

ROL-1 (Role Instance ID)

is equivalent to

identifier

ROL-3 (Role-ROL)

is equivalent to

relationship

ROL-4 (Role Person)

is equivalent to

$this

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.

ROL-5 (Role Begin Date/Time)

is equivalent to

period.start

ROL-6 (Role End Date/Time)

is equivalent to

period.end

ROL-11 (Office/Home Address/Birthplace)

is equivalent to

address

ROL-12 (Phone)

is equivalent to

telecom