Digital Health Platform
​0.1.0 - Uzbekistan флаг

Digital Health Platform, опубликовано Uzinfocom LLC. Это руководство не является санкционированной публикацией; это непрерывная сборка для версии 0.1.0, созданной FHIR (HL7® FHIR® Standard) CI Build. Эта версия основана на нынешнем содержании https://github.com/uzinfocom-org/digital-health-ig/ и регулярно изменяется. Смотрите каталог опубликованных версий

Профиль ресурса: Uzbekistan DHP Consent - Отображения

Active по состоянию на 2025-06-02

Отображения для dhp-consent профиль ресурса.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

НаименованиеWorkflow PatternFiveWs Pattern MappingHL7 V2 MappingRIM Mappingdoco
.. Consent
Event
infrastructure.information
CON
  • Entity
  • Role
  • or Act
... id
... meta
... implicitRules
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... identifier
Event.identifier
FiveWs.identifier
An implementation-specific requirement will be needed
... status
Event.status
FiveWs.status
CON-11 (Consent Status – CNE using table HL70498)
... category
Event.code
FiveWs.class
CON-2 (Consent Type - CWE using table HL70496)
... subject
Event.subject
FiveWs.subject[x]
... date
Event.occurrence[x]
FiveWs.recorded
CON-13 (Consent Decision Date/Time – DTM)
... period
.... id
n/a
.... extension
n/a
.... start
DR.1
./low
.... end
DR.2
./high
... grantor
... grantee
... manager
FiveWs.witness
... controller
... sourceAttachment
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
.... id
n/a
.... extension
n/a
.... contentType
ED.2+ED.3/RP.2+RP.3. Note conversion may be needed if old style values are being used
  • ./mediaType
  • ./charset
.... language
./language
.... data
ED.5
./data
.... url
RP.1+RP.2 - if they refer to a URL (see v2.6)
./reference/literal
.... size
N/A (needs data type R3 proposal)
.... hash
:ED/integrityCheckAlgorithm="SHA-1"]
.... title
./title/data
.... creation
N/A (needs data type R3 proposal)
.... height
  • .outboundRelationship[typeCode="COMP].target[classCode="OBS"
  • moodCode="EVN"
  • code="<CODE>"].value
.... width
  • .outboundRelationship[typeCode="COMP].target[classCode="OBS"
  • moodCode="EVN"
  • code="<CODE>"].value
.... frames
  • .outboundRelationship[typeCode="COMP].target[classCode="OBS"
  • moodCode="EVN"
  • code="<CODE>"].value
.... duration
  • .outboundRelationship[typeCode="COMP].target[classCode="OBS"
  • moodCode="EVN"
  • code="<CODE>"].value
.... pages
... sourceReference
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
... regulatoryBasis
An implementation-specific requirement will be needed
... policyBasis
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... reference
.... url
... policyText
... verification
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... verified
.... verificationType
.... verifiedBy
.... verifiedWith
.... verificationDate
... decision
... provision
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... period
  • CON-14&15 (Consent Effective Date Time
  • Consent End DateTime)
.... actor
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... role
..... reference
.... action
.... securityLabel
.... purpose
.... documentType
.... resourceType
.... code
.... dataPeriod
.... data
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... meaning
..... reference
.... expression
.... provision

doco Документация для этого формата