Response to Regulatory Questions (RTQ)
0.1.0 - ci-build

Response to Regulatory Questions (RTQ), published by HL7 International. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/rtq-ig/ and changes regularly. See the Directory of published versions

Resource Profile: RegulatoryQuestionnaireResponse - Mappings

Active as of 2025-11-15

Mappings for the RegulatoryQuestionnaireResponse resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternFiveWs Pattern MappingRIM Mappingdoco
.. QuestionnaireResponse
Event
infrastructure.information
  • Entity
  • Role
  • or Act
  • Observation[moodCode=EVN]
... id
... meta
.... id
n/a
.... extension
n/a
.... versionId
.... lastUpdated
.... source
.... profile
.... security
.... tag
... implicitRules
... text
Act.text?
.... id
n/a
.... extension
n/a
.... status
N/A
.... div
N/A
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... Slices for identifier
Event.identifier
FiveWs.identifier
.id
.... identifier:qa-request
Event.identifier
FiveWs.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
.... identifier:procedure-number
Event.identifier
FiveWs.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
... basedOn
Event.basedOn
.outboundRelationship[typeCode=FLFS].target
... partOf
Event.partOf
.inboundRelationship[typeCode=COMP].source[moodCode=EVN]
... questionnaire
  • ./outboundRelationship[typeCode=INST]/target[classCode=OBS
  • moodCode=DEFN]
... status
Event.status
FiveWs.status
.statusCode (also whether there's a revisionControlAct - and possibly mood to distinguish "in-progress" from "published)
... subject
Event.subject
FiveWs.subject[x]
.participation[typeCode=SBJ].role
... encounter
Event.encounter
FiveWs.context
  • .inboundRelationship(typeCode=COMP].source[classCode<=PCPR
  • moodCode=EVN]
... authored
Event.recorded
FiveWs.recorded
.participation[typeCode=AUT].time
... author
Event.performer.actor
FiveWs.author
.participation[typeCode=AUT].role
... source
FiveWs.source
.participation[typeCode=INF].role
... item
  • .outboundRelationship[typeCode=COMP].target[classCode=OBS
  • moodCode=EVN]
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... linkId
  • .outboundRelationship[typeCode=DEFN].target[classCode=OBS
  • moodCode=DEFN].id
.... definition
  • .outboundRelationship[typeCode=DEFN].target[classCode=OBS
  • moodCode=DEFN].code
.... text
.text
..... id
..... Slices for extension
...... extension:richText
..... value
.... answer
.value[type=LIST_ANY]
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... value[x]
.item
...... value[x]All Types
....... id
n/a
....... Slices for extension
........ extension:richText
..... item
  • .outboundRelationship[typeCode=COMP].target[classCode=OBS
  • moodCode=EVN]
.... item
  • .outboundRelationship[typeCode=COMP].target[classCode=OBS
  • moodCode=EVN]

doco Documentation for this format