O‘zbekiston Raqamli sog‘liqni saqlash platformasi
0.10.0 - draft Uzbekistan bayroqcha

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

Resurss profili: UZ Core Consent ( Eksperimental )

Rasmiy URL: https://dhp.uz/fhir/core/StructureDefinition/uz-core-consent Versiya: 0.10.0
Active 2025-06-02 holatiga ko‘ra Kompyuterda qayta ishlanadigan nom: UZCoreConsent

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

UZ Core Consent bemorning tibbiy ma'lumotlarini DHP (Digital Health Platform - Raqamli sog'liqni saqlash platformasi) orqali almashish mumkinligi haqidagi o'z qarorini qayd etadi. O'zbekistonda rad etish modeli (opt-out) qo'llanadi: bemor uchun Consent resursi mavjud bo'lmasa, ma'lumot almashishga sukut bo'yicha ruxsat beriladi; bemor esa almashishni taqiqlovchi Consent ni qayd etish orqali undan voz kechadi. Model ataylab ikkilik shaklda tuzilgan: bitta provision ruxsat beradi yoki taqiqlaydi va bemor bu qarorni bemor portalida mustaqil belgilaydi. Platforma qarorni qo'llaydi: Consent kirishni taqiqlasa, ma'lumot so'rovi HTTP 403 bilan rad etiladi. Ikki istisno mavjud: davolovchi tibbiyot xodimlari va qonuniy vakolatga ega boshqa tomonlar uchun qonuniy kirish yo'li hamda favqulodda break-glass kirish yo'li (favqulodda ma'lumotlardan foydalanish maqsadi bilan AuditEvent da qayd etiladi). Consent Patient bilan bog'langan.

Majburiy va Must Support ma'lumot elementlari

Quyidagi elementlar har doim mavjud bo'lishi (majburiy) yoki ma'lumot mavjud bo'lganda qo'llab-quvvatlanishi (Must Support) kerak. Ularning barchasi majburiy emas, biroq tizim ma'lumot mavjud bo'lsa, har bir Must Support elementini to'ldirishi va uni qabul qilganda qayta ishlashi kerak. Bu inson o'qishi uchun mo'ljallangan qisqacha tavsif; quyidagi formal ko'rinishlar aniq karralilik, turlar va terminologik bog'lanishlarni beradi.

Ushbu profil o'ziga xos majburiy karralilik qo'shmaydi. Yagona majburiy element bazaviy resursdan meros olingan status bo'lib, u Consent yozuvining o'z holatini bildiradi va DHP rozilik holatlari qiymatlar to'plamiga bog'langan.

  • subject - Consent qo'llanadigan bemor;
  • grantor - qarorni beruvchi tomon (bemor);
  • period - Consent amal qiladigan davrning boshlanish va tugash vaqti;
  • regulatory basis - qaror asosidagi qonun yoki siyosatni belgilovchi normativ-huquqiy asos (majburiy bog'lanish);
  • decision - permit yoki deny (majburiy bog'lanish);
  • source - sourceAttachment (uning url va yaratilgan sanasi bilan) yoki asosiy rozilik hujjatini saqlovchi sourceReference;
  • qarorni aniqlashtiruvchi provision, uning action va purpose elementlari bilan (ikkalasi ham majburiy bog'lanishga ega).

Qaror ataylab ikkilik shaklda tuzilgan: bitta decision qiymati - permit yoki deny. Platforma har bir ma'lumot so'roviga ruxsat berish yoki uni rad etish uchun shu qiymatdan foydalanadi.

JSON-ni bosqichma-bosqich shakllantirish

Bemor portalda qarorni belgilaganda Consent asosan tizim tomonidan shakllantiriladi, shuning uchun uni qo'lda yaratish uchun ko'p ish talab etilmaydi. Quyidagi misol to'liq yozuvni ko'rsatadi: uni nusxalang va moslashtiring; ko'rsatilgan har bir qiymat ushbu profilga mos keladi. To'liq instansiya - Consent misoli.

status - yagona qat'iy majburiy element. Biroq Consent faqat qaysi ma'lumotlarga nisbatan qo'llanishi (subject), qanday qaror qabul qilingani (decision - permit yoki deny skalyar kodi) va qaror nimaga qo'llanishi (provision) ko'rsatilgandagina mazmunli bo'ladi. Consent mavjud bo'lmasligi ma'lumot almashishga allaqachon ruxsat bergani sababli, odatda yuboriladigan yozuv opt-out hisoblanadi: deny qiymati, bunda provision.action qaysi amal taqiqlanganini - bu yerda ma'lumotni oshkor qilishni - ko'rsatadi. Har bir UZ Core resursi o'zi mos kelishini bildiradigan profilni meta.profile da ko'rsatishi kerak:

{
  "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 va decision majburiy bog'lanishdan foydalanadi: qiymat quyidagi Snapshot ko'rinishida ko'rsatilgan bog'langan qiymatlar to'plamidan olinishi kerak. provision.action CodeableConcept turiga ega, shuning uchun uning kodi coding massivida joylashadi; subject oddiy Reference bo'lgani sababli, maqsad resurs bevosita reference ostida ko'rsatiladi.

To'liqroq yozuv - bu yerda bemor qayta rozilik bildirganda yoki Consent ni muayyan maqsad va davr bilan cheklaganda bo'lgani kabi kirishga ruxsat berish ko'rsatilgan - qarorni kim berganini (grantor, bemor), uning amal qilish muddatini (period), u asoslanadigan qonunni (regulatoryBasis) va qarorni muayyan action hamda purpose bilan cheklovchi provision ni ham qayd etadi. grantor Reference ro'yxati bo'lib, regulatoryBasis, provision.action va provision.purpose kodlangan elementlardir; har bir qiymat bog'langan qiymatlar to'plamidan olinadi:

{
  "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"
      }
    }
  ]
}

E'tibor bering: provision.purpose bevosita Coding turiga ega va coding massiviga o'ralmaydi, regulatoryBasis hamda provision.action esa CodeableConcept turiga ega bo'lib, coding massivini saqlaydi. Ushbu yozuv kirishga ruxsat beradi; opt-out xuddi shu tuzilishga ega, faqat decision qiymati deny etib belgilanadi, shundan so'ng platforma har bir ma'lumot so'rovini HTTP 403 bilan rad etadi. Kodlangan qiymatlarni tanlash qoidalari Yetishmayotgan va yashirilgan ma'lumotlar hamda Terminologiya bo'limlarida keltirilgan.

​API chaqiruvlari misollari va namunaviy foydali yuklama sahifaning pastki qismidagi Tezkor boshlash bo'limida keltirilgan.

Usages:

You can also check for usages in the FHIR IG Statistics

Profil mazmunining rasmiy ko‘rinishlari

Profillar, differentsiyalar, snapshotlar va ularning tasvirlari ta’rifi.

NameFlagsCard.TypeDescription & Constraints    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
Example 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
Binding: ConsentPolicyVS (0.10.0) (required)
... decision ?!SΣ 0..1 code deny | permit
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... purpose Σ 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG

Constraints

Id Grade Path(s) Description Expression

NameFlagsCard.TypeDescription & Constraints    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
Binding: 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
Binding: ConsentPolicyVS (0.10.0) (required)
... decision S 0..1 code deny | permit
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... purpose 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG
NameFlagsCard.TypeDescription & Constraints    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
Binding: ConsentStateCodesVS (0.10.0) (required)
... category Σ 0..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: 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
Slice: Unordered, Open by 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
Slice: Unordered, Open by value:url
Constraints: ext-1
.... contentType ΣC 0..1 code Mime type of the content, with charset etc.
Binding: MimeTypes (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
Example General: text/plain; charset=UTF-8, image/png
.... language Σ 0..1 code Human language of the content (BCP-47)
Binding: AllLanguages (required): IETF language tag for a human language.
Additional BindingsPurpose
CommonLanguages Starter

Example General: en-AU
.... data C 0..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Example 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
Example 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
Binding: 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
Binding: 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
Binding: 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
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Binding: SecurityLabelExamples (example): Example Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)
.... documentType Σ 0..* Coding e.g. Resource Type, Profile, CDA, etc
Binding: ConsentContentClass (preferred): The document type a consent provision covers.
.... resourceType Σ 0..* Coding e.g. Resource Type, Profile, etc
Binding: ResourceType (extensible): The resource types a consent provision covers.
.... code Σ 0..* CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the content
Binding: 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
Binding: 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..* See provision (Consent) Nested Exception Provisions

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.language Base required All Languages 📍5.0.0 FHIR Std.
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.category Base example Consent Category Codes 📍5.0.0 FHIR Std.
Consent.sourceAttachment.​contentType Base required Mime Types 📍5.0.0 FHIR Std.
Consent.sourceAttachment.​language Base required All Languages 📍5.0.0 FHIR Std.
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.verification.​verificationType Base example Consent Vefication Codes 📍5.0.0 FHIR Std.
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.actor.​role Base extensible Participation Role Type 📍5.0.0 FHIR Std.
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.securityLabel Base example Example set of Security Labels 📍5.0.0 FHIR Std.
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG
Consent.provision.documentType Base preferred Consent Content Class 📍5.0.0 FHIR Std.
Consent.provision.resourceType Base extensible Resource Types 📍5.0.0 FHIR Std.
Consent.provision.code Base example Consent Content Codes 📍5.0.0 FHIR Std.
Consent.provision.data.​meaning Base required Consent Data Meaning 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Summary

Must-Support: 13 elements

Asosiy elementlar ko'rinishi

NameFlagsCard.TypeDescription & Constraints    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
Example 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
Binding: ConsentPolicyVS (0.10.0) (required)
... decision ?!SΣ 0..1 code deny | permit
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... purpose Σ 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG

Constraints

Id Grade Path(s) Description Expression

Differensial ko‘rinish

NameFlagsCard.TypeDescription & Constraints    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
Binding: 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
Binding: ConsentPolicyVS (0.10.0) (required)
... decision S 0..1 code deny | permit
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... purpose 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG

Snapshot ko‘rinishiView

NameFlagsCard.TypeDescription & Constraints    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
Binding: ConsentStateCodesVS (0.10.0) (required)
... category Σ 0..* CodeableConcept Classification of the consent statement - for indexing/retrieval
Binding: 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
Slice: Unordered, Open by 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
Slice: Unordered, Open by value:url
Constraints: ext-1
.... contentType ΣC 0..1 code Mime type of the content, with charset etc.
Binding: MimeTypes (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
Example General: text/plain; charset=UTF-8, image/png
.... language Σ 0..1 code Human language of the content (BCP-47)
Binding: AllLanguages (required): IETF language tag for a human language.
Additional BindingsPurpose
CommonLanguages Starter

Example General: en-AU
.... data C 0..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Example 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
Example 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
Binding: 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
Binding: 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
Binding: 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
Binding: 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
Binding: ConsentActionVS (0.10.0) (required)
.... securityLabel Σ 0..* Coding Security Labels that define affected resources
Binding: SecurityLabelExamples (example): Example Security Labels from the Healthcare Privacy and Security Classification System.
.... purpose Σ 0..* Coding Context of activities covered by this provision
Binding: ConsentPurposeOfUseVS (0.10.0) (required)
.... documentType Σ 0..* Coding e.g. Resource Type, Profile, CDA, etc
Binding: ConsentContentClass (preferred): The document type a consent provision covers.
.... resourceType Σ 0..* Coding e.g. Resource Type, Profile, etc
Binding: ResourceType (extensible): The resource types a consent provision covers.
.... code Σ 0..* CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the content
Binding: 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
Binding: 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..* See provision (Consent) Nested Exception Provisions

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Consent.language Base required All Languages 📍5.0.0 FHIR Std.
Consent.status Base required Consent State Codes 📍0.10.0 This IG
Consent.category Base example Consent Category Codes 📍5.0.0 FHIR Std.
Consent.sourceAttachment.​contentType Base required Mime Types 📍5.0.0 FHIR Std.
Consent.sourceAttachment.​language Base required All Languages 📍5.0.0 FHIR Std.
Consent.regulatoryBasis Base required Consent policies 📍0.10.0 This IG
Consent.verification.​verificationType Base example Consent Vefication Codes 📍5.0.0 FHIR Std.
Consent.decision Base required Consent provision type 📍0.10.0 This IG
Consent.provision.actor.​role Base extensible Participation Role Type 📍5.0.0 FHIR Std.
Consent.provision.action Base required Possible consent actions 📍0.10.0 This IG
Consent.provision.securityLabel Base example Example set of Security Labels 📍5.0.0 FHIR Std.
Consent.provision.purpose Base required Consent purpose of use 📍0.10.0 This IG
Consent.provision.documentType Base preferred Consent Content Class 📍5.0.0 FHIR Std.
Consent.provision.resourceType Base extensible Resource Types 📍5.0.0 FHIR Std.
Consent.provision.code Base example Consent Content Codes 📍5.0.0 FHIR Std.
Consent.provision.data.​meaning Base required Consent Data Meaning 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Summary

Must-Support: 13 elements

 

Profilning boshqa ko‘rinishlari: CSV, Excel, Schematron

Tezkor boshlash

Ushbu profil uchun keng tarqalgan API amallari. So'rovlar JWT kirish tokenini talab qiladi - Xavfsizlik va autentifikatsiya bo'limiga qarang. [base] - FHIR-serverning bazaviy URL manzili; | kod tizimini qiymatdan ajratadi va %7C ko'rinishida URL-kodlanishi kerak.

Server identifikatori bo'yicha olish

GET [base]/Consent/[id]

Bemorning rozilik bo'yicha qarorlarini qidirish

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

Yaratish - bemorning ma'lumot almashishni rad etishini qayd etish; Consent mavjud bo'lmasa, almashishga sukut bo'yicha ruxsat beriladi

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

Yangilash - masalan, bemor almashishni rad etsa yoki qayta ruxsat bersa: to'liq resursni yangi decision qiymati bilan yuboring:

PUT [base]/Consent/[id]
If-Match: W/"3"   # oxirgi o'qishdagi ETag; resurs shu vaqtdan beri o'zgargan bo'lsa, 412

Consent odatda bemor tomonidan portalda belgilanadi. Consent kirishni taqiqlasa, ma'lumot so'rovlari HTTP 403 bilan rad etiladi; mijoz tizimlari bu natijani to'g'ri qayta ishlashi kerak.

Qo'llab-quvvatlanadigan qidiruv parametrlarining to'liq ro'yxati CapabilityStatement da keltirilgan.

Bog'liq bo'limlar