Nictiz FHIR NL STU3 Zib2017 - Local Development build (v1.3.15) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Resource Profile: nl-core-practitionerrole - Mappings

Active as of 2024-04-09

Mappings for the nl-core-practitionerrole resource profile.

Mappings for HCIM HealthProfessional-v1.2.1(2015EN) (https://zibs.nl/wiki/HealthProfessional-v1.2.1(2015EN))

nl-core-practitionerrole
PractitionerRole
organization	NL-CM:17.1.6	HealthcareProvider
specialty	NL-CM:17.1.4	Specialty
telecom	NL-CM:17.1.8	TelephoneE-mail

Mappings for HCIM HealthProfessional-v3.0(2016EN) (https://zibs.nl/wiki/HealthProfessional-v3.0(2016EN))

nl-core-practitionerrole
PractitionerRole
organization	NL-CM:17.1.6	HealthcareProvider
specialty	NL-CM:17.1.4	Specialty
telecom	NL-CM:17.1.8	TelephoneE-mail

Mappings for HCIM HealthProfessional-v3.2(2017EN) (https://zibs.nl/wiki/HealthProfessional-v3.2(2017EN))

nl-core-practitionerrole
PractitionerRole
organization	NL-CM:17.1.6	HealthcareProvider
specialty	NL-CM:17.1.4	Specialty
telecom	NL-CM:17.1.8	ContactInformation

Mappings for HCIM Patient-v2.0.1(2015EN) (https://zibs.nl/wiki/Patient-v2.0.1(2015EN))

ContactInformation has become an independent information model as of release 2017 of the HCIMs.

nl-core-practitionerrole
PractitionerRole
telecom	NL-CM:0.1.5	ContactInformation

Mappings for HCIM Patient-v3.0(2016EN) (https://zibs.nl/wiki/Patient-v3.0(2016EN))

ContactInformation has become an independent information model as of release 2017 of the HCIMs.

nl-core-practitionerrole
PractitionerRole
telecom	NL-CM:0.1.5	ContactInformation

Mappings for HCIM ContactInformation-v1.0(2017EN) (https://zibs.nl/wiki/ContactInformation-v1.0(2017EN))

ContactInformation has become an independent information model as of release 2017 of the HCIMs.

nl-core-practitionerrole
PractitionerRole
telecom	NL-CM:20.6.1	ContactInformation

Mappings for HCIM BasicElements-v1.0(2017EN) (https://zibs.nl/wiki/BasicElements-v1.0(2017EN))

nl-core-practitionerrole
PractitionerRole
identifier	NL-CM:0.0.6	IdentificationNumber

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

nl-core-practitionerrole
PractitionerRole	PRD (as one example)
identifier	PRD-7 (or XCN.1)
active	STF-7
period	PRD-8/9 / PRA-5.4
code	PRD-1 / STF-18 / PRA-3 / PRT-4 / ROL-3 / ORC-12 / OBR-16 / PV1-7 / PV1-8 / PV1-9 / PV1-17
specialty	PRA-5
coding	C*E.1-8, C*E.10-22
coding (SpecialtyUZI)	C*E.1-8, C*E.10-22
coding (SpecialtyAGB)	C*E.1-8, C*E.10-22
text	C*E.9. But note many systems use C*E.2 for this
healthcareService	EDU-2 / AFF-3
telecom	XTN

Mappings for RIM Mapping (http://hl7.org/v3)

nl-core-practitionerrole
PractitionerRole	Entity. Role, or Act, Role
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	.id
active	.statusCode
period	.performance[@typeCode <= 'PPRF'].ActDefinitionOrEvent.effectiveTime
practitioner	.player
organization	.scoper
code	.code
specialty	.player.HealthCareProvider[@classCode = 'PROV'].code
id	n/a
extension	n/a
coding	union(., ./translation)
coding (SpecialtyUZI)	union(., ./translation)
coding (SpecialtyAGB)	union(., ./translation)
text	./originalText[mediaType/code="text/plain"]/data
location	.performance.ActDefinitionOrEvent.ServiceDeliveryLocation[@classCode = 'SDLOC']
healthcareService	.player.QualifiedEntity[@classCode = 'QUAL'].code
telecom	n/a, TEL
availableTime	.effectiveTime
id	n/a
extension	n/a
modifierExtension	N/A
daysOfWeek	.effectiveTime
allDay	.effectiveTime
availableStartTime	.effectiveTime
availableEndTime	.effectiveTime
notAvailable	.effectiveTime
id	n/a
extension	n/a
modifierExtension	N/A
description	n/a
during	.effectiveTime
availabilityExceptions	.effectiveTime
endpoint	n/a

Mappings for ServD (http://www.omg.org/spec/ServD/1.0/)

nl-core-practitionerrole
PractitionerRole	ServiceSiteProvider
identifier	./Identifiers
period	(ServD maps Practitioners and Organizations via another entity, so this concept is not available)
code	(ServD maps Practitioners and Organizations via another entity, so this concept is not available)
specialty	./Specialty
location	(ServD maps Practitioners and Organizations via another entity, so this concept is not available)<br/> However these are accessed via the Site.ServiceSite.ServiceSiteProvider record. (The Site has the location)
telecom	ContactPoint

Mappings for W5 Mapping (http://hl7.org/fhir/w5)

nl-core-practitionerrole
PractitionerRole	administrative.individual
identifier	id
active	status
period	when.done
location	where