Koppeltaal 2.0 Implementation Guide - Local Development build (v0.9.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON

Resource Profile: KT2_Device - Mappings

Draft as of 2023-02-07

Mappings for the KT2Device resource profile.

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

KT2_Device
Device	Entity. Role, or Act, Device
text	Act.text?
contained	N/A
modifierExtension	N/A
identifier	.id
id	n/a
extension	n/a
use	Role.code or implied by context
type	Role.code or implied by context
system	II.root or Role.id.root
value	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period	Role.effectiveTime or implied by context
assigner	II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
status	.statusCode
deviceName
id	n/a
extension	n/a
modifierExtension	N/A
type	.playedRole[typeCode=MANU].code
owner	.playedRole[typeCode=OWN].scoper

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

KT2_Device
Device
identifier	FiveWs.identifier
status	FiveWs.status
deviceName
type	FiveWs.what[x]
owner	FiveWs.source

Mappings for UDI Mapping (http://fda.gov/UDI)

KT2_Device
Device
identifier	The serial number which is a component of the production identifier (PI), a conditional, variable portion of a UDI. The identifier.type code should be set to “SNO”(Serial Number) and the system left empty.