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

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

OperationDefinition: Relate a parent patient to a child confirmed by the civil registry

Официальный URL: https://dhp.uz/fhir/core/OperationDefinition/patient-relate Версия: 0.12.0
Draft по состоянию на 2026-10-19 Вычисляемое имя: PatientRelate

Relates a parent to a child. The parent is the Patient named in the URL; the child is named by PINFL. The kinship is confirmed against the child registry of the Ministry of Justice: the parent's PINFL must match the father or the mother of the child. The child Patient is then resolved by PINFL in the same way as Patient/$populate (and created if it does not exist yet), and a RelatedPerson is created on behalf of the parent, pointing to the child via RelatedPerson.patient and carrying the parent's identifier, name, gender, birthDate and address. The operation is invoked at instance level only (Patient/[id]/$relate) with POST and a Parameters body. The response is a Bundle, not Parameters.

Язык: ru

URL: [base]/Patient/[id]/$relate

Параметры

ИспользоватьНаименованиеСфера действияКардинальностьТипПривязкаДокументация
INchildIdentifier1..1Identifier

PINFL (NI) of the child. Identifier.value is mandatory and is always treated as a PINFL; Identifier.system is ignored. The value is checked for correctness: 14 digits, a gender digit of 1-6, a valid encoded date of birth and the 7-3-1 checksum. Passed as valueIdentifier.

INrelationship0..1code | Coding | CodeableConceptRelationship type (Example)

Relationship of the parent to the child, written to RelatedPerson.relationship of a new relation. When the parameter is absent, http://terminology.hl7.org/CodeSystem/v3-RoleCode#GUARD (guardian) is used. When supplied, the value is written as sent: valueCode gets the system http://terminology.hl7.org/CodeSystem/v3-RoleCode, valueCoding is written as a whole including a foreign system and display, valueCodeableConcept is written as a whole, including one carrying text only. An empty code is rejected with code value, and the default is not substituted for it.

INlink0..1boolean

When true, the parent Patient additionally gets a Patient.link entry with type seealso whose other points to the RelatedPerson. When false or absent, the parent Patient is not changed. If writing the parent Patient fails, the relation is still created and returned, and the closing OperationOutcome carries a warning with code forbidden. Passed as valueBoolean.

OUTreturn1..1Bundle

A collection Bundle with a fixed order of entries: (1) the created or reused RelatedPerson, (2) the child Patient, (3) the parent Patient, only when link is true and the write succeeded, (4) an OperationOutcome, always last. Resource entries carry fullUrl when the server's gateway URL is configured. On failure the Bundle contains only the OperationOutcome with severity error.

The operation always answers HTTP 200: success and failure are distinguished by the severity of the OperationOutcome that closes the returned Bundle, not by the HTTP status. On failure the Bundle contains that OperationOutcome only, with severity error and one of the codes not-found, deleted, structure, required, value, business-rule (the parent has no PINFL, kinship is not confirmed, or the child identifier resolved to the parent itself), invalid, transient or exception. The steps are ordered so that a refusal leaves no trace: kinship is checked before the child is resolved, so a request with unconfirmed kinship creates no Patient. The parent must carry an identifier in the PINFL system https://dhp.uz/fhir/core/sid/pid/uz/ni. The operation is idempotent per pair of parent PINFL and child Patient among RelatedPerson resources whose active is not false: an existing relation is returned as is and is never rewritten; if the requested relationship differs from the stored one, an informational issue reports both values. Kinship is re-checked on every call, including when an existing relation is reused. A new RelatedPerson is written with active: true. The relation by itself grants no access to the child's data.