O‘zbekiston Raqamli sog‘liqni saqlash platformasi
0.10.0 - draft
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
| Rasmiy URL: https://dhp.uz/fhir/core/OperationDefinition/person-populate | Versiya: 0.10.0 | ||||
| Active 2026-08-13 holatiga ko‘ra | Kompyuterda qayta ishlanadigan nom: PersonPopulate | ||||
Creates a Person resource from an identity document, populating it with data from the state registries of natural persons. The operation takes the identifier as a system + code + value triple (with birthDate where needed), resolves it to a PINFL (NI), and retrieves the citizen's details by that PINFL. The operation is idempotent: if a Person with that PINFL already exists in the system it is returned without calling any external source and without creating a duplicate; otherwise a new Person resource is created with an assigned identifier and version. The operation is invoked at type level (Person/$populate) with POST and a Parameters body. The response is the Person resource itself, not Parameters.
Language: uz
URL: [base]/Person/$populate
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | system | 1..1 | uri | Identification system of the document (Identifier.system). Permitted values: | ||
| IN | code | 1..1 | code | Document type: | ||
| IN | value | 1..1 | string | Document value: the PINFL for | ||
| IN | birthDate | 0..1 | date | Date of birth in YYYY-MM-DD format. Mandatory when | ||
| OUT | return | 1..1 | Person | The Person resource that was created, or the one that already existed, populated with data from the state registries. |
The document codes NI (PINFL), PPN (passport / ID card) and BCT (birth certificate) are supported; the case of code does not matter. For NI the value is checked locally for correctness. For PPN the birthDate parameter is mandatory - the PINFL is resolved from the series and number together with the date of birth. For BCT the value is split into series and number, which resolve the PINFL. The system value must be one of the permitted identification systems; an unknown system or code results in an OperationOutcome with code invalid. The citizen's address is requested separately and is optional: if it is unavailable, the Person is still created, but without address details. If the citizen is not found in the external registries, or the data retrieved is invalid, no resource is created and an error is returned. Equivalent operations are defined for Practitioner and Organization.