VJL - Vähiandmete juhtimislaud
0.1.0 - draft Estonia flag

VJL - Vähiandmete juhtimislaud, published by TEHIK. 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/TEHIK-EE/ig-ee-vjl/ and changes regularly. See the Directory of published versions

Resource Profile: EEVJLClinicalTrialConsent - Mappings

Draft as of 2026-10-09

Mappings for the ee-vjl-clinical-trial-consent resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternFiveWs Pattern MappingHL7 V2 MappingRIM Mappingdoco
Consent
Event
infrastructure.information
CON
  • Entity
  • Role
  • or Act
Consent / id
Consent / meta
Consent / implicitRules
Consent / language
Consent / text
Act.text?
Consent / contained
N/A
Consent / extension
N/A
Consent / modifierExtension
N/A
Consent / identifier
Event.identifier
FiveWs.identifier
An implementation-specific requirement will be needed
Consent / status
Event.status
FiveWs.status
CON-11 (Consent Status – CNE using table HL70498)
Consent / category
Event.code
FiveWs.class
CON-2 (Consent Type - CWE using table HL70496)
Consent / category / id
n/a
Consent / category / extension
n/a
Consent / category / coding
  • C*E.1-8
  • C*E.10-22
  • union(.
  • ./translation)
Consent / category / text
C*E.9. But note many systems use C*E.2 for this
./originalText[mediaType/code="text/plain"]/data
Consent / subject
Event.subject
FiveWs.subject[x]
Consent / date
Event.occurrence[x]
FiveWs.recorded
CON-13 (Consent Decision Date/Time – DTM)
Consent / period
Consent / grantor
Consent / grantee
Consent / manager
FiveWs.witness
Consent / controller
Consent / sourceAttachment
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
Consent / sourceReference
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
Consent / regulatoryBasis
An implementation-specific requirement will be needed
Consent / policyBasis
Consent / policyText
Consent / verification
Consent / decision
Consent / provision

doco Documentation for this format