Единая платформа цифрового здравоохранения Узбекистана
0.10.0 - draft Uzbekistan флаг

This page is part of the Uzbekistan Digital Health Platform (v0.10.0: Releases Draft) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

Профиль ресурса: UZ Core Consent ( Экспериментальный )

Официальный URL: https://dhp.uz/fhir/core/StructureDefinition/uz-core-consent Версия: 0.10.0
Active по состоянию на 2025-06-02 Вычисляемое имя: UZCoreConsent

Uzbekistan Core Consent profile, used to manage patient consent for data sharing and processing

UZ Core Consent содержит собственное решение пациента о том, могут ли его медицинские данные передаваться на Цифровой платформе здравоохранения. В Узбекистане применяется модель отказа (opt-out): если ресурс Consent для пациента отсутствует, обмен данными разрешён по умолчанию; пациент отказывается от обмена, регистрируя Consent, который его запрещает. Модель намеренно является бинарной: одно условие provision либо разрешает, либо запрещает доступ, и пациент самостоятельно задаёт решение в портале пациента. Платформа применяет это решение: если Consent запрещает доступ, запрос данных отклоняется с HTTP 403. Предусмотрены два исключения: законный доступ для лечащих специалистов и других уполномоченных законом сторон, а также экстренный доступ break-glass (регистрируемый в AuditEvent с экстренной целью использования данных). Consent связан с Patient.

Обязательные элементы и элементы Must Support

Приведённые ниже элементы должны либо всегда присутствовать (обязательные элементы), либо поддерживаться при наличии данных (Must Support). Не все из них обязательны, однако система должна заполнять каждый элемент Must Support, если соответствующие данные имеются, и обрабатывать его при получении. Это человекочитаемое описание; формальные представления ниже содержат точные кардинальности, типы и терминологические привязки.

Этот профиль не добавляет собственных обязательных кардинальностей. Единственный обязательный элемент унаследован от базового ресурса: status - состояние самой записи Consent, связанное с набором значений состояний согласия DHP.

  • subject - пациент, к данным которого применяется Consent;
  • grantor - сторона, предоставляющая решение (пациент);
  • period - начало и окончание периода, в течение которого применяется Consent;
  • regulatory basis - нормативное основание, определяющее закон или политику, на которых основано решение (обязательная привязка);
  • decision - permit или deny (обязательная привязка);
  • source - либо sourceAttachment с url и датой создания, либо sourceReference, содержащий исходный документ согласия;
  • provision, уточняющий решение, с указанием action и purpose (оба элемента имеют обязательные привязки).

Решение намеренно является бинарным: одно значение decision - permit или deny. Платформа использует его, чтобы разрешить или отклонить каждый запрос данных.

Пошаговое формирование JSON

Consent в основном формируется системой, когда пациент задаёт решение в портале, поэтому вручную требуется создавать немного данных. Ниже приведена полная запись: скопируйте её и адаптируйте; каждое показанное значение соответствует этому профилю. Полный экземпляр - пример Consent.

status - единственный строго обязательный элемент, однако Consent имеет смысл только тогда, когда указано, чьи данные он охватывает (subject), какое решение принято (decision - скалярный код permit или deny) и к чему применяется это решение (provision). Поскольку отсутствие Consent уже разрешает обмен данными, обычно отправляемая запись представляет собой отказ (opt-out): deny, где provision.action указывает, какое действие запрещается - в данном случае раскрытие данных. Каждый ресурс UZ Core также должен указывать профиль, которому он заявляет соответствие, в meta.profile:

{
  "resourceType": "Consent",
  "meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-consent"] },
  "status": "active",
  "subject": { "reference": "Patient/example-patient" },
  "decision": "deny",
  "provision": [
    {
      "action": [
        { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/consentaction", "code": "disclose" }] }
      ]
    }
  ]
}

status и decision используют обязательную привязку: значение должно входить в связанный набор значений, перечисленный ниже в представлении Snapshot. provision.action имеет тип CodeableConcept, поэтому его код размещается в массиве coding; subject имеет тип Reference, поэтому целевой ресурс указывается непосредственно в reference.

Более полная запись - здесь показано предоставление доступа, например когда пациент повторно разрешает обмен или ограничивает Consent конкретной целью и периодом - также содержит сведения о стороне, предоставившей решение (grantor, пациент), периоде действия (period), законе, на котором оно основано (regulatoryBasis), и provision, уточняющем решение для конкретных action и purpose. grantor представляет собой список Reference, а regulatoryBasis, provision.action и provision.purpose являются кодированными элементами; каждое значение выбирается из связанного набора значений:

{
  "resourceType": "Consent",
  "meta": { "profile": ["https://dhp.uz/fhir/core/StructureDefinition/uz-core-consent"] },
  "status": "active",
  "subject": { "reference": "Patient/example-patient" },
  "grantor": [
    { "reference": "Patient/example-patient" }
  ],
  "period": {
    "start": "2025-02-15T14:02:52+05:00",
    "end": "2026-02-15T14:02:52+05:00"
  },
  "regulatoryBasis": [
    {
      "coding": [
        { "system": "https://terminology.dhp.uz/fhir/core/CodeSystem/consent-policy-cs", "code": "uz-LRU-547" }
      ]
    }
  ],
  "decision": "permit",
  "provision": [
    {
      "action": [
        { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/consentaction", "code": "disclose" }] }
      ],
      "purpose": [
        { "system": "http://terminology.hl7.org/CodeSystem/v3-ActReason", "code": "RECORDMGT" }
      ],
      "period": {
        "start": "2025-02-15T14:02:52+05:00",
        "end": "2026-02-15T14:02:52+05:00"
      }
    }
  ]
}

Обратите внимание: provision.purpose имеет непосредственно тип Coding и не помещается в массив coding, тогда как regulatoryBasis и provision.action имеют тип CodeableConcept и содержат массив coding. Эта запись предоставляет доступ; отказ opt-out имеет такую же структуру, но в decision указывается deny, после чего платформа отклоняет каждый запрос данных с HTTP 403. Правила выбора кодированных значений приведены в разделах Отсутствующие и скрытые данные и Терминология.

​Примеры вызовов API и образец полезной нагрузки приведены в разделе Быстрый старт в нижней части страницы.

Использование:

You can also check for usages in the FHIR IG Statistics

Формальные представления содержимого профиля

Описание профилей, дифференциалов, снимков и их представлений.

НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contained 0..* Resource Contained, inline Resources
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
Constraints: ext-1
... subject SΣ 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... period SΣ 0..1 Period Effective period for this Consent
.... start SΣC 0..1 dateTime Starting time with inclusive boundary
.... end SΣC 0..1 dateTime End time with inclusive boundary, if not ongoing
... grantor SΣ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is granting rights according to the policy and rules
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... url SΣ 0..1 url Uri where the data can be found
Пример General: http://www.acme.com/logo-small.png
.... creation SΣ 0..1 dateTime Date attachment was first created
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... decision ?!SΣ 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision SΣ 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... action Σ 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... purpose Σ 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)

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

Привязки к терминологии

Путь Статус Использование ValueSet Версия Источник
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG

Ограничения

Id Градация Путь(и) Описание Выражение

НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... status S 1..1 code draft | active | inactive | not-done | entered-in-error | unknown
Привязка: ConsentStateCodesVS (0.10.0) (required)
... subject S 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... period S 0..1 Period Effective period for this Consent
.... start S 0..1 dateTime Starting time with inclusive boundary
.... end S 0..1 dateTime End time with inclusive boundary, if not ongoing
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... url S 0..1 url Uri where the data can be found
.... creation S 0..1 dateTime Date attachment was first created
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... decision S 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision S 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... action 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... purpose 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)

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

Терминологические привязки (дифференциал)

Путь Статус Использование ValueSet Версия Источник
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG
НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
Constraints: ext-1
... identifier Σ 0..* Identifier Identifier for this record (external references)
... status ?!SΣ 1..1 code draft | active | inactive | not-done | entered-in-error | unknown
Привязка: ConsentStateCodesVS (0.10.0) (required)
... category Σ 0..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Привязка: ConsentCategoryCodes (example): A classification of the type of consents found in a consent statement.
... subject SΣ 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... date Σ 0..1 date Fully executed date of the consent
... period SΣ 0..1 Period Effective period for this Consent
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Разрез: Не упорядочено, Открыто от value:url
Constraints: ext-1
.... start SΣC 0..1 dateTime Starting time with inclusive boundary
.... end SΣC 0..1 dateTime End time with inclusive boundary, if not ongoing
... grantor SΣ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is granting rights according to the policy and rules
... grantee Σ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is agreeing to the policy and rules
... manager 0..* Reference(HealthcareService | Organization | Patient | Practitioner) Consent workflow management
... controller 0..* Reference(HealthcareService | Organization | Patient | Practitioner) Consent Enforcer
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Разрез: Не упорядочено, Открыто от value:url
Constraints: ext-1
.... contentType ΣC 0..1 code Mime type of the content, with charset etc.
Привязка: MimeTypes (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
Пример General: text/plain; charset=UTF-8, image/png
.... language Σ 0..1 code Human language of the content (BCP-47)
Привязка: AllLanguages (required): IETF language tag for a human language.
Дополнительные привязкиЦель
CommonLanguages Старт

Пример General: en-AU
.... data C 0..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Пример General: http://www.acme.com/logo-small.png
.... size Σ 0..1 integer64 Number of bytes of content (if url provided)
.... hash Σ 0..1 base64Binary Hash of the data (sha-1, base64ed)
.... title Σ 0..1 string Label to display in place of the data
Пример General: Official Corporate Logo
.... creation SΣ 0..1 dateTime Date attachment was first created
.... height 0..1 positiveInt Height of the image in pixels (photo/video)
.... width 0..1 positiveInt Width of the image in pixels (photo/video)
.... frames 0..1 positiveInt Number of frames if > 1 (photo)
.... duration 0..1 decimal Length in seconds (audio / video)
.... pages 0..1 positiveInt Number of printed pages
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... policyBasis 0..1 BackboneElement Computable version of the backing policy
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... reference 0..1 Reference(Resource) Reference backing policy resource
.... url 0..1 url URL to a computable backing policy
... policyText 0..* Reference(DocumentReference) Human Readable Policy
... verification Σ 0..* BackboneElement Consent Verified by patient or family
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... verified Σ 1..1 boolean Has been verified
.... verificationType 0..1 CodeableConcept Business case of verification
Привязка: ConsentVerificationCodes (example): Types of Verification/Validation.
.... verifiedBy 0..1 Reference(Organization | Practitioner | PractitionerRole) Person conducting verification
.... verifiedWith 0..1 Reference(Patient | RelatedPerson) Person who verified
.... verificationDate 0..* dateTime When consent verified
... decision ?!SΣ 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision SΣ 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... period Σ 0..1 Period Timeframe for this provision
.... actor 0..* BackboneElement Who|what controlled by this provision (or group, by role)
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
..... role 0..1 CodeableConcept How the actor is involved
Привязка: ParticipationRoleType (extensible): How an actor is involved in the consent considerations.
..... reference 0..1 Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Resource for the actor (or group, by role)
.... action Σ 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Привязка: SecurityLabelExamples (example): Example Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)
.... documentType Σ 0..* Coding e.g. Resource Type, Profile, CDA, etc
Привязка: ConsentContentClass (preferred): The document type a consent provision covers.
.... resourceType Σ 0..* Coding e.g. Resource Type, Profile, etc
Привязка: ResourceType (extensible): The resource types a consent provision covers.
.... code Σ 0..* CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the content
Привязка: ConsentContentCodes (example): If this code is found in an instance, then the exception applies.
.... dataPeriod Σ 0..1 Period Timeframe for data controlled by this provision
.... data Σ 0..* BackboneElement Data controlled by this provision
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
..... meaning Σ 1..1 code instance | related | dependents | authoredby
Привязка: ConsentDataMeaning (required): How a resource reference is interpreted when testing consent restrictions.
..... reference Σ 1..1 Reference(Resource) The actual data reference
.... expression 0..1 Expression A computable expression of the consent
.... provision 0..* Смотреть provision (Consent) Nested Exception Provisions

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

Привязки к терминологии

Путь Статус Использование ValueSet Версия Источник
Consent.language Base required All Languages 📍5.0.0 Стандарт FHIR
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.category Base example Consent Category Codes 📍5.0.0 Стандарт FHIR
Consent.sourceAttachment.​contentType Base required Mime Types 📍5.0.0 Стандарт FHIR
Consent.sourceAttachment.​language Base required All Languages 📍5.0.0 Стандарт FHIR
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.verification.​verificationType Base example Consent Vefication Codes 📍5.0.0 Стандарт FHIR
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.actor.​role Base extensible Participation Role Type 📍5.0.0 Стандарт FHIR
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.securityLabel Base example Example set of Security Labels 📍5.0.0 Стандарт FHIR
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG
Consent.provision.documentType Base preferred Consent Content Class 📍5.0.0 Стандарт FHIR
Consent.provision.resourceType Base extensible Resource Types 📍5.0.0 Стандарт FHIR
Consent.provision.code Base example Consent Content Codes 📍5.0.0 Стандарт FHIR
Consent.provision.data.​meaning Base required Consent Data Meaning 📍5.0.0 Стандарт FHIR

Ограничения

Id Градация Путь(и) Описание Выражение

Summary

Обязательная поддержка: 13 элементs

Просмотр ключевых элементов

НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contained 0..* Resource Contained, inline Resources
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
Constraints: ext-1
... subject SΣ 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... period SΣ 0..1 Period Effective period for this Consent
.... start SΣC 0..1 dateTime Starting time with inclusive boundary
.... end SΣC 0..1 dateTime End time with inclusive boundary, if not ongoing
... grantor SΣ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is granting rights according to the policy and rules
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... url SΣ 0..1 url Uri where the data can be found
Пример General: http://www.acme.com/logo-small.png
.... creation SΣ 0..1 dateTime Date attachment was first created
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... decision ?!SΣ 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision SΣ 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... action Σ 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... purpose Σ 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)

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

Привязки к терминологии

Путь Статус Использование ValueSet Версия Источник
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG

Ограничения

Id Градация Путь(и) Описание Выражение

Дифференциальный вид

НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... status S 1..1 code draft | active | inactive | not-done | entered-in-error | unknown
Привязка: ConsentStateCodesVS (0.10.0) (required)
... subject S 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... period S 0..1 Period Effective period for this Consent
.... start S 0..1 dateTime Starting time with inclusive boundary
.... end S 0..1 dateTime End time with inclusive boundary, if not ongoing
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... url S 0..1 url Uri where the data can be found
.... creation S 0..1 dateTime Date attachment was first created
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... decision S 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision S 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... action 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... purpose 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)

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

Терминологические привязки (дифференциал)

Путь Статус Использование ValueSet Версия Источник
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG

Обзор моментальных снимковView

НаименованиеФлагиКарта.ТипОписание и ограничения    Filter: Filtersdoco
.. Consent 0..* Consent(5.0.0) A healthcare consumer's or third party's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored
Constraints: ext-1
... identifier Σ 0..* Identifier Identifier for this record (external references)
... status ?!SΣ 1..1 code draft | active | inactive | not-done | entered-in-error | unknown
Привязка: ConsentStateCodesVS (0.10.0) (required)
... category Σ 0..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Привязка: ConsentCategoryCodes (example): A classification of the type of consents found in a consent statement.
... subject SΣ 0..1 Reference(Patient | Practitioner | Group) Who the consent applies to
... date Σ 0..1 date Fully executed date of the consent
... period SΣ 0..1 Period Effective period for this Consent
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Разрез: Не упорядочено, Открыто от value:url
Constraints: ext-1
.... start SΣC 0..1 dateTime Starting time with inclusive boundary
.... end SΣC 0..1 dateTime End time with inclusive boundary, if not ongoing
... grantor SΣ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is granting rights according to the policy and rules
... grantee Σ 0..* Reference(CareTeam | HealthcareService | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Who is agreeing to the policy and rules
... manager 0..* Reference(HealthcareService | Organization | Patient | Practitioner) Consent workflow management
... controller 0..* Reference(HealthcareService | Organization | Patient | Practitioner) Consent Enforcer
... sourceAttachment S 0..* Attachment Source from which this consent is taken
.... id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Разрез: Не упорядочено, Открыто от value:url
Constraints: ext-1
.... contentType ΣC 0..1 code Mime type of the content, with charset etc.
Привязка: MimeTypes (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
Пример General: text/plain; charset=UTF-8, image/png
.... language Σ 0..1 code Human language of the content (BCP-47)
Привязка: AllLanguages (required): IETF language tag for a human language.
Дополнительные привязкиЦель
CommonLanguages Старт

Пример General: en-AU
.... data C 0..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Пример General: http://www.acme.com/logo-small.png
.... size Σ 0..1 integer64 Number of bytes of content (if url provided)
.... hash Σ 0..1 base64Binary Hash of the data (sha-1, base64ed)
.... title Σ 0..1 string Label to display in place of the data
Пример General: Official Corporate Logo
.... creation SΣ 0..1 dateTime Date attachment was first created
.... height 0..1 positiveInt Height of the image in pixels (photo/video)
.... width 0..1 positiveInt Width of the image in pixels (photo/video)
.... frames 0..1 positiveInt Number of frames if > 1 (photo)
.... duration 0..1 decimal Length in seconds (audio / video)
.... pages 0..1 positiveInt Number of printed pages
... sourceReference S 0..* Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Source from which this consent is taken
... regulatoryBasis S 0..* CodeableConcept Regulations establishing base Consent
Привязка: ConsentPolicyVS (0.10.0) (required)
... policyBasis 0..1 BackboneElement Computable version of the backing policy
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... reference 0..1 Reference(Resource) Reference backing policy resource
.... url 0..1 url URL to a computable backing policy
... policyText 0..* Reference(DocumentReference) Human Readable Policy
... verification Σ 0..* BackboneElement Consent Verified by patient or family
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... verified Σ 1..1 boolean Has been verified
.... verificationType 0..1 CodeableConcept Business case of verification
Привязка: ConsentVerificationCodes (example): Types of Verification/Validation.
.... verifiedBy 0..1 Reference(Organization | Practitioner | PractitionerRole) Person conducting verification
.... verifiedWith 0..1 Reference(Patient | RelatedPerson) Person who verified
.... verificationDate 0..* dateTime When consent verified
... decision ?!SΣ 0..1 code deny | permit
Привязка: ConsentProvisionTypeVS (0.10.0) (required)
... provision SΣ 0..* BackboneElement Constraints to the base Consent.policyRule/Consent.policy
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... period Σ 0..1 Period Timeframe for this provision
.... actor 0..* BackboneElement Who|what controlled by this provision (or group, by role)
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
..... role 0..1 CodeableConcept How the actor is involved
Привязка: ParticipationRoleType (extensible): How an actor is involved in the consent considerations.
..... reference 0..1 Reference(Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole) Resource for the actor (or group, by role)
.... action Σ 0..* CodeableConcept Actions controlled by this provision
Привязка: ConsentActionVS (0.10.0) (required)
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Привязка: SecurityLabelExamples (example): Example Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this provision
Привязка: ConsentPurposeOfUseVS (0.10.0) (required)
.... documentType Σ 0..* Coding e.g. Resource Type, Profile, CDA, etc
Привязка: ConsentContentClass (preferred): The document type a consent provision covers.
.... resourceType Σ 0..* Coding e.g. Resource Type, Profile, etc
Привязка: ResourceType (extensible): The resource types a consent provision covers.
.... code Σ 0..* CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the content
Привязка: ConsentContentCodes (example): If this code is found in an instance, then the exception applies.
.... dataPeriod Σ 0..1 Period Timeframe for data controlled by this provision
.... data Σ 0..* BackboneElement Data controlled by this provision
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Constraints: ext-1
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
Constraints: ext-1
..... meaning Σ 1..1 code instance | related | dependents | authoredby
Привязка: ConsentDataMeaning (required): How a resource reference is interpreted when testing consent restrictions.
..... reference Σ 1..1 Reference(Resource) The actual data reference
.... expression 0..1 Expression A computable expression of the consent
.... provision 0..* Смотреть provision (Consent) Nested Exception Provisions

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

Привязки к терминологии

Путь Статус Использование ValueSet Версия Источник
Consent.language Base required All Languages 📍5.0.0 Стандарт FHIR
Consent.status Base required Consent State Codes 📍0.10.0 этот IG
Consent.category Base example Consent Category Codes 📍5.0.0 Стандарт FHIR
Consent.sourceAttachment.​contentType Base required Mime Types 📍5.0.0 Стандарт FHIR
Consent.sourceAttachment.​language Base required All Languages 📍5.0.0 Стандарт FHIR
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 этот IG
Consent.verification.​verificationType Base example Consent Vefication Codes 📍5.0.0 Стандарт FHIR
Consent.decision Base required Consent provision type 📍0.10.0 этот IG
Consent.provision.actor.​role Base extensible Participation Role Type 📍5.0.0 Стандарт FHIR
Consent.provision.action Base required Possible consent actions 📍0.10.0 этот IG
Consent.provision.securityLabel Base example Example set of Security Labels 📍5.0.0 Стандарт FHIR
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 этот IG
Consent.provision.documentType Base preferred Consent Content Class 📍5.0.0 Стандарт FHIR
Consent.provision.resourceType Base extensible Resource Types 📍5.0.0 Стандарт FHIR
Consent.provision.code Base example Consent Content Codes 📍5.0.0 Стандарт FHIR
Consent.provision.data.​meaning Base required Consent Data Meaning 📍5.0.0 Стандарт FHIR

Ограничения

Id Градация Путь(и) Описание Выражение

Summary

Обязательная поддержка: 13 элементs

 

Другие представления профиля: CSV, Excel, Schematron

Быстрый старт

Распространённые операции API для этого профиля. Для запросов требуется токен доступа JWT - см. раздел Безопасность и аутентификация. [base] - это базовый URL FHIR-сервера; | отделяет систему кодирования от значения и должен быть URL-кодирован как %7C.

Получение по идентификатору сервера

GET [base]/Consent/[id]

Поиск решений пациента о согласии

GET [base]/Consent?patient=Patient/[id]
GET [base]/Consent?patient=Patient/[id]&status=active
GET [base]/Consent?patient=Patient/[id]&category=http://terminology.hl7.org/CodeSystem/consentcategorycodes%7Cinfa
GET [base]/Consent?patient=Patient/[id]&period=ge2025-01-01
GET [base]/Consent?patient=Patient/[id]&date=ge2025-01-01

Создание - регистрация отказа пациента от обмена данными; при отсутствии Consent обмен разрешён по умолчанию

POST [base]/Consent
{
  "resourceType": "Consent",
  "meta": { "profile": [ "https://dhp.uz/fhir/core/StructureDefinition/uz-core-consent" ] },
  "status": "active",
  "subject": { "reference": "Patient/[id]" },
  "decision": "deny",
  ...
}

Обновление - например, если пациент отказывается от обмена или повторно предоставляет разрешение: отправьте полный ресурс с новым decision:

PUT [base]/Consent/[id]
If-Match: W/"3"   # ETag из последнего чтения; 412, если ресурс с тех пор изменился

Consent обычно задаётся пациентом в портале. Если Consent запрещает доступ, запросы данных отклоняются с HTTP 403; клиентские системы должны корректно обрабатывать такой результат.

Полный перечень поддерживаемых параметров поиска приведён в CapabilityStatement.

Связанные разделы