Uzbekistan Digital Health Platform
0.3.0 - ci-build
Uzbekistan Digital Health Platform, published by Ministry of Health of the Republic of Uzbekistan. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/uzinfocom-org/digital-health-ig/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| DHPCapabilityStatement |
DHP platform capability statement, describing the supported resources, profiles, and searchparameters |
These define forms used by systems conforming to this implementation guide to capture or expose data to end users.
| Опросник удовлетворённости пациента |
Опросник для оценки удовлетворённости пациента качеством обслуживания (для Patient Portal) |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| UZ Core AuditEvent |
Uzbekistan Core AuditEvent profile, used to track user and application activity |
| UZ Core Clinical Condition |
Uzbekistan Core Clinical Condition profile, used for documenting a patient's clinical symptoms, conditions, and their characteristics |
| UZ Core Condition |
Uzbekistan Core Condition profile, used for documenting general, non-clinical symptoms, conditions, and their characteristics. Generally, this means ICD-10 codes are not applicable for such conditions |
| UZ Core Consent |
Uzbekistan Core Consent profile, used to manage patient consent for data sharing and processing |
| UZ Core Encounter |
Uzbekistan Core Encounter profile, used to represent clinical encounters |
| UZ Core EpisodeOfCare |
Uzbekistan Core profile for EpisodeOfCare, representing a patient's period of long-term care such as pregnancy care or chronic disease management. |
| UZ Core Goal |
Uzbekistan Core Goal profile, used for a patient, group or organization care. For example: weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. |
| UZ Core HealthcareService |
Uzbekistan Core HealthcareService profile, used to define healthcare services available |
| UZ Core Location |
Uzbekistan Core Location profile, used to define locations of healthcare services |
| UZ Core Observation |
Uzbekistan Core Observation profile, used to represent clinical and laboratory observations |
| UZ Core Organization |
Uzbekistan Core Organization profile, used to define healthcare organizations and sub-units |
| UZ Core Patient |
Uzbekistan Core Patient profile, used to represent patients administrative information |
| UZ Core Practitioner |
Uzbekistan Core Practitioner profile, used to define healthcare practitioners |
| UZ Core PractitionerRole |
Uzbekistan Core PractitionerRole profile, used to define roles of practitioners |
| UZ Core Provenance |
Uzbekistan Core Provenance profile, used to digitally sign documents via myID |
| UZ Core Questionnaire |
Uzbekistan Core Questionnaire profile for multilingual structured data capture forms |
| UZ Core QuestionnaireResponse |
Uzbekistan Core QuestionnaireResponse profile for capturing responses with digital signature support |
| UZ Core RelatedPerson |
Uzbekistan Core RelatedPerson profile, used to represent persons related to the patient |
| UZ Core Socioeconomic Observation |
Uzbekistan Core socioeconomic observation profile, used to represent patients' benefits, education, profession, and social status. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Diagnosis type |
Extension to differentiate the diagnosis type, which is different from the condition type / category |
| Differentiation of the administrative gender 'other' |
Extension for more precise differentiation of the administrative gender 'other', aligned with German base profiles representation of the same concept. |
| Managing organization attachment date |
Date when the patient was attached to the managing organization. In Uzbekistan, patients can only change their managing organization once a year. |
These define sets of codes used by systems conforming to this implementation guide.
| Audit event action |
Defines audit event action that is being recorded in Uzbek and Russian |
| Audit event outcome |
Defines the outcome of the event that is being recorded in Uzbek and Russian |
| Audit event role type |
Defines how the participant participated in Uzbek and Russian |
| Audit event subtype |
Defines the subtype of event that is being recorded in Uzbek and Russian |
| Audit event type |
Defines the type of event that is being recorded in Uzbek and Russian |
| Cancer-related services |
Defines the actual cancer-related services in Uzbek and Russian |
| Categories of cancer-related services |
Defines categories of cancer-related services in Uzbek and Russian |
| Consent State Codes |
Defines the consent state codes in Uzbek and Russian |
| Consent policies |
Determines the regulatory basis for consent |
| Consent provision type |
Determines the type of consent |
| Consent purpose of use |
Defines the purposes of use for consent |
| Defines a nationality of a person as used in Uzbekistan |
Nationality |
| Defines the possible positions and professions |
State classification of positions of employees and worker professions (KODP-2020) |
| Diagnosis Type |
Diagnosis types in Uzbekistan |
| Differentiation of the administrative gender 'other' |
Defines the differentiation of the administrative gender 'other' in Uzbek and Russian |
| Disability levels |
Disability levels in Uzbekistan |
| Education levels |
Education levels in Uzbekistan |
| Encounter admission translations |
Encounter readmission codes with English and Russian translations |
| Encounter admit source translations |
Encounter admit source codes with English and Russian translations |
| Encounter class translations |
Encounter Class codes with English and Russian translations |
| Encounter discharge disposition translations |
Encounter discharge disposition codes with English and Russian translations |
| Encounter participant type translations |
Encounter participant type codes with English and Russian translations |
| Encounter priority translations |
Encounter priority codes with English and Russian translations |
| Encounter status translations |
Encounter status codes with English and Russian translations |
| Encounter subject status translations |
Encounter subject status codes with English and Russian translations |
| Encounter type translations |
Defines encounter type codes with English and Russian translations |
| EpisodeOfCare reason use value set |
Allowed reason use for EpisodeOfCare in Uzbekistan's health information exchange. |
| EpisodeOfCare status value set |
Allowed codes for EpisodeOfCare status in Uzbekistan's health information exchange. |
| EpisodeOfCare type value set |
Allowed codes for EpisodeOfCare types in Uzbekistan's health information exchange. |
| Foreign Driver's License System Value Set |
Allowed system URIs for foreign (non-Uzbekistan) driver's license identifiers. Used in the UZ Core Patient profile for the driversLicenseForeign slice. |
| Foreign Passport System Value Set |
Allowed system URIs for foreign (non-Uzbekistan) passport identifiers. Used in the UZ Core Patient profile for the passportForeign slice. |
| Goal Achievement VS |
Value Set for Goal Achievement translations |
| Goal Category VS |
Value Set for Goal Category translations |
| Goal Description VS |
Value Set for Goal Description |
| Goal Lifecycle Status VS |
Value Set for Goal Lifecycle Status translations |
| Goal Priority VS |
Value Set for Goal Priority translations |
| Goal Start Event VS |
Value Set for Goal Start Event |
| ISO 3166 part 1 2-letter codes |
Defines Uzbek and Russian translations for ISO 3166 part 1 2-letter codes |
| ISO 3166 part 1 2-letter codes, sans Uzbekistan |
Defines Uzbek and Russian translations for ISO 3166 part 1 2-letter codes, sans Uzbekistan, for international addresses |
| Identifier domain |
Description of the identifier systems acceptable for entity (patient, practitioner, organization) identification. This is modelled after the Estonian Identifier Domain with the exception that country codes are ISO 3166 two letter codes for consistency within UZ Core. |
| License, certificate, degree |
Defines the type of license, certificate, degree in Uzbek and Russian |
| Location Kinds |
Defines the kind of Location in Uzbek and Russian |
| Location status |
Defines type of Location |
| Location types |
Location types defined by the Ministry of Health of the Republic of Uzbekistan |
| Mahallas translations |
Mahallas names with English and Russian translations |
| Marital status translations |
Encounter reason use codes with Uzbek and Russian translations |
| Marital status translations |
Defines marital status codes in Uzbek and Russian |
| Nomenclature group |
High-level classification of healthcare institutions by functional category (e.g., hospitals, outpatient clinics, emergency services). This is a broad grouping defined by the Ministry of Health; for detailed institution types, see OrganizationalStructureVS. |
| Object role |
Defines object's role in Uzbek and Russian |
| Observation category |
Observation category in Uzbekistan |
| Observation normal value |
Observation normal value in Uzbekistan |
| Observation status |
Observation status in Uzbekistan |
| Organization Identifier Domain Value Set |
Allowed codes for organization identification domains (national tax numbers, registration numbers, etc) in Uzbekistan's health information exchange. Used in the UZ Core Organization profile. |
| Organizational service group |
Classifies healthcare organizations by their service delivery capabilities (e.g., outpatient only, inpatient only, outpatient + inpatient, day hospital). Defined by the Ministry of Health. |
| Organizational specialization |
Determines the specialization of a medical organization |
| Organizational structure |
Detailed classification of healthcare institution types (e.g., specialized centers, clinical hospitals, dispensaries). This is a granular categorization defined by the Ministry of Health; for high-level functional groupings, see NomenclatureGroupVS. |
| Organizational subordination group |
Defines the subordination group of the medical organization |
| Organizational subordination institution |
Defines the type of medical organizations without forming a legal entity |
| Patient Identifier Domain Value Set |
Allowed codes for patient identification domains (international passport numbers, drivers licenses) in Uzbekistan's health information exchange. Used in the UZ Core Patient profile. |
| Possible consent actions |
Determines the actions that can be taken with consent |
| Practitioner Identifier Domain Value Set |
Allowed codes for practitioner identification domains (national unique identifiers, etc) in Uzbekistan's health information exchange. Used in the UZ Core Practitioner profile. |
| Practitioner roles |
Defines the roles of medical practitioners |
| Profession specializations |
Defines the specializations of medical professions |
| Provenance Activity Types |
Defines the provenance activity types. |
| Provenance Entity Role |
Defines the provenance entity role. |
| Provenance Participation Role Type |
Defines how the participant participated in Uzbek and Russian |
| Purpose of use |
Defines agent's the purpose of use in Uzbek and Russian |
| Reference range meaning |
Reference range meaning in Uzbekistan |
| Relationship type |
Relationship types in Uzbekistan |
| Security label |
Defines security label in Uzbek and Russian |
| Security role type |
Defines the role of the participant that is being recorded in Uzbek and Russian |
| Signature Type |
Defines the possible Provenance signature types. |
| Social status |
Social status types in Uzbekistan |
| Socioeconomic Observation Codes |
Codes for socioeconomic observations including benefits, education, profession, and social status |
| Telecom use |
Telecom use types in Uzbekistan |
| Triggered by type |
Triggered by types in Uzbekistan |
| Types of Condition severities |
Types of Condition severities in Uzbekistan |
| Types of address registration |
Defines type of address registration in Uzbek and Russian |
| Types of benefits |
Types of benefits in Uzbekistan |
| Types of clinical status |
Types of clinical status in Uzbekistan |
| Types of participation role |
Types of participation role in Uzbekistan |
| Types of possible addresses |
Defines the types of addresses with translations in Uzbek and Russian |
| Types of possible contact points |
Defines the contact point |
| Types of possible identifier uses |
Defines the |
| Types of possible identifiers |
Defines identifier |
| Types of possible name uses |
Defines the different uses of a name in Uzbek and Russian |
| Types of verification status |
Types of verification status in Uzbekistan |
| Types of verification status |
Types of verification status in Uzbekistan |
| UZCore Data Absent Reason |
Defines the reasons why a value is missing in an observation within the Uzbekistan Core Implementation |
| UZCore observation interpretation |
Codes representing the clinical meaning of an observation result in the Uzbekistan Core. |
| Uzbekistan MVD's international country codes |
Uzbekistan MVD's international country codes with English and Russian translations |
| Uzbekistan MVD's international country codes (excluding Uzbekistan) |
Uzbekistan MVD's international country codes excluding Uzbekistan for international address use |
| Uzbekistan Regions and Locations |
List of regions and locations in Uzbekistan |
| Uzbekistan states and Locations |
List of states and locations in Uzbekistan |
These define new code systems used by systems conforming to this implementation guide.
| Act code translations |
Act code supplement with translations in Uzbek and Russian |
| Act reason translations |
Act reason supplement with translations in Uzbek and Russian |
| Address registration translations |
Types of address registration supplement with translations in Uzbek and Russian |
| Address type translations |
Address type supplement with Uzbek and Russian translations |
| Admit source from home |
Admit source home code for Admit Source ValueSet with English and Russian translations |
| All FHIR Types |
One of the types defined as part of this version of FHIR with Uzbek and Russian translations. |
| Audit event action translations |
Audit event action supplement with translations in Uzbek and Russian |
| Audit event outcome translations |
Audit event outcome supplement with translations in Uzbek and Russian |
| Cancer Types |
List of cancer types defined by the Ministry of Health of the Republic of Uzbekistan |
| Clinical status translations |
Clinical status supplement with translations in Uzbek and Russian |
| Confidentiality translations |
Confidentiality supplement with translations in Uzbek and Russian |
| Consent State Codes translations |
Consent State Codes supplement with translations in Uzbek and Russian |
| Consent policies |
Defines the regulatory basis for consent |
| Consent provision type translations |
Consent provision type supplement with translations in Uzbek and Russian |
| Countries digital MVD translations |
Countries digital MVD codes with translations in Russian and English |
| DICOM Controlled Terminology Definitions |
DICOM Controlled Terminology Definitions supplement with translations in Uzbek and Russian |
| Data absent reason |
Data absent reason supplement with translations in Uzbek and Russian |
| Defines the possible location types |
Defines the possible location types in Uzbek and Russian |
| Defines the possible positions and professions |
State classification of positions of employees and worker professions based on CBPEPW-2020 using the 14.05.2025 update |
| Diagnosis Types |
Diagnosis types in Uzbekistan |
| Differentiation of the administrative gender 'other' |
Differentiation of the administrative gender 'other' in Uzbek and Russian |
| Disability levels |
Disability levels in Uzbekistan |
| Education levels |
Education levels in Uzbekistan |
| Encounter Type translations |
Encounter type codes with English and Russian translations |
| Encounter admission translations |
Encounter readmission codes with English and Russian translations |
| Encounter admit source translations |
Encounter admit source codes with English and Russian translations |
| Encounter discharge disposition from died |
Encounter discharge disposition home codes with English and Russian translations |
| Encounter discharge disposition translations |
Encounter discharge disposition codes with English and Russian translations |
| Encounter priority home translations |
Encounter priority home codes with English and Russian translations |
| Encounter priority translations |
Encounter priority codes with English and Russian translations |
| Encounter reason use translations |
Encounter reason use codes with English and Russian translations |
| Encounter status translations |
Encounter status codes with English and Russian translations |
| Encounter subject status translations |
Encounter subject status codes with English and Russian translations |
| EpisodeOfCare reason use |
Episode of care reason use in Uzbekistan |
| EpisodeOfCare status translations |
EpisodeOfCare status supplement with translation in Uzbek and Russian. |
| EpisodeOfCare types |
Episode of care types in Uzbekistan |
| Goal Achievement CS |
Code System for Goal Achievement translations in Uzbek and Russian |
| Goal Category CS |
Code System for Goal Category translations in Uzbek and Russian |
| Goal Lifecycle Status CS |
Code System for Goal Lifecycle Status translations in Uzbek and Russian |
| Goal Priority CS |
Code System for Goal Priority translations in Uzbek and Russian |
| HTTP interaction translations |
HTTP interaction supplement with translations in Uzbek and Russian |
| ISO 3166-1 two-letter translations |
ISO 3166-1 2-letter supplement with Uzbek and Russian translations |
| Identifier domain |
Description of the identifier systems acceptable for entity (patient, practitioner, organization) identification. See identifiers page for guidance and examples on using this codesystem. This is modelled after the Estonian Identifier Domain with the exception that country codes are ISO 3166 two letter codes for consistency within UZ Core. |
| License, certificate, degree translations |
License, certificate, degree supplement with translations in Uzbek and Russian |
| Location Kinds |
Defines the kind of Location in Uzbek and Russian |
| Location status translations |
Location status supplement with translations in Uzbek and Russian |
| Mahalla Codes and Names |
Mahalla codes and names with translations in Russian and English |
| Marital status translations |
Marital status supplement with Uzbek and Russian translations |
| Nationality |
Defines a nationality of a person as used in Uzbekistan |
| Nomenclature group |
High-level classification of healthcare institutions by functional category (e.g., hospitals, outpatient clinics, emergency services). This is a broad grouping defined by the Ministry of Health; for detailed institution types, see OrganizationalStructureCS. |
| Null Flavor translations |
Null Flavor supplement with Uzbek and Russian translations |
| Observation category translations |
Observation category with translations in Uzbek and Russian |
| Observation interpretation |
Observation interpretation supplement with translations in Uzbek and Russian |
| Observation normal value translations |
Translation of observation's normal value concept into Uzbek and Russian |
| Observation status translations |
Observation status with translations in Uzbek and Russian |
| Organizational Structure |
Detailed classification of healthcare institution types (e.g., specialized centers, clinical hospitals, dispensaries). This is a granular categorization defined by the Ministry of Health; for high-level functional groupings, see NomenclatureGroupCS. |
| Organizational service group |
Classifies healthcare organizations by their service delivery capabilities (e.g., outpatient only, inpatient only, outpatient + inpatient, day hospital). Defined by the Ministry of Health. |
| Organizational specialization |
Determines the specialization of a medical organization |
| Organizational subordination group |
Defines the subordination group of the medical organization |
| Organizational subordination institution |
Defines the type of medical organizations without forming a legal entity |
| Participant type translations |
Participant type supplement with translations in Uzbek and Russian |
| Participation type translations |
Participation type supplement with translations in Uzbek and Russian |
| Possible consent actions translations |
Possible consent actions supplement with translations in Uzbek and Russian |
| Possible identifier uses translations |
Types of possible identifier uses supplement with translations in Uzbek and Russian |
| Possible identifiers translations |
Types of possible identifiers supplement with translations in Uzbek and Russian |
| Possible name uses translations |
Types of possible name uses supplement with translations in Uzbek and Russian |
| Profession specializations |
Defines the specializations of medical professions |
| Provenance Activity Types translations |
Provenance Activity Types supplement with translations in Uzbek and Russian |
| Provenance Entity Role translations |
Provenance Entity Role supplement with translations in Uzbek and Russian |
| Provenance Participation Role Type translations |
Provenance Participation Role Type supplement with translations in Uzbek and Russian |
| Reference range meaning translations |
Meaning of reference range, supplemented with translations in Uzbek and Russian |
| Relationship type |
Relationship types in Uzbekistan |
| Role class |
Provides localized definitions of role class codes in Uzbek and Russian. |
| Role code |
Specifies role codes used to define the function or position of a person or organization, with translations in Uzbek and Russian. |
| Sample security structural roles |
Sample security structural roles with translations in Uzbek and Russian, used in DHP as actual codes |
| Secondary Contact Role Definitions |
Provides additional contact role codes with translations in Uzbek and Russian for use in specific contexts or implementations. |
| Security role type translations |
Security role type supplement with translations in Uzbek and Russian |
| Signature Type |
Defines the possible Provenance signature types. |
| Social status |
Social status types in Uzbekistan |
| Telecom use |
Telecom use type supplement with translation in Uzbek and Russian |
| Triggered by type translations |
Triggered by type words with translations in Uzbek and Russian |
| Types of benefits |
Types of benefits in Uzbekistan |
| Types of possible contact points translations |
Types of possible contact points supplement with translations in Uzbek and Russian |
| Uzbekistan Regions and Locations |
List of regions and locations in Uzbekistan |
| Uzbekistan states and Locations |
List of states and locations in Uzbekistan |
| Verification status types |
Verification status supplement with translations in Uzbek and Russian |
| Verification status types |
Verification status in Uzbekistan |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| episodeofcare-identifier |
Identifier system used for EpisodeOfCare resources within the Uzbekistan DHP context. |
| location-unit |
Naming system for unique identifiers assigned to location units such as branches, wards, and beds within healthcare facilities in the Uzbekistan Digital Health Platform |
| patient-id-uzb-birth-certificate |
Birth certificate identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-drivers-license |
Driver's license identifiers assigned by the Uzbekistan Ministry of Internal Affairs |
| patient-id-uzb-health-card |
Health card number identifiers assigned by the Uzbekistan Ministry of Health |
| patient-id-uzb-military-id |
Military ID number identifiers assigned by the Uzbekistan Ministry of Defense |
| patient-id-uzb-national-id |
National unique identifiers (PINFL) assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-passport-diplomatic |
Diplomatic passport identifiers assigned by the Uzbekistan Ministry of Foreign Affairs |
| patient-id-uzb-passport-international |
International passport identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-passport-local |
Local (internal) passport identifiers assigned by the Uzbekistan Personalization Agency |
| patient-id-uzb-penitentiary-number |
Penitentiary institution number identifiers assigned by the Uzbekistan correctional system |
| patient-id-uzb-provider-assigned |
Provider-assigned patient identifiers issued by healthcare organizations for unknown patients |
| patient-id-uzb-temp-medical-record |
Temporary medical record numbers assigned by healthcare organizations |
| patient-id-uzb-unknown-patient |
Unknown patient codes generated by healthcare providers (fallback when organization ID unavailable) |
| uzb-hrm-argos |
Healthcare provider identifiers assigned by the Uzbekistan Human Resource Management (HRM) system |
| uzb-hrm-argos-practitioner |
Healthcare professional identifiers assigned by the Uzbekistan Human Resource Management (HRM) system |
| uzb-soliq |
Tax identification numbers and other identifiers assigned by the Uzbekistan Tax Authority (Soliq) |
These define transformations to convert between codes by systems conforming with this implementation guide.
| Countries Digital MVD to ISO 3166-1 Alpha-2 Mapping |
ConceptMap for translating Uzbekistan MVD numeric codes to ISO 3166-1 alpha-2 (2-letter) country codes. |
| ISO 3166-1 Alpha-3 to Alpha-2 Country Code Mapping |
ConceptMap for translating ISO 3166-1 alpha-3 (3-letter) country codes to alpha-2 (2-letter) country codes. For consistency, UZ Core uses 2-letter codes; this ConceptMap is provided to assist 3rd party systems in performing the translation. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example Encounter |
Example of an psychiatric encounter |
| Example Goal |
An example goal instance for a patient aiming to manage benign essential hypertension. |
| Example Uz Core Condition - Cancer |
Example instance of a cancer diagnosis documented during a patient encounter |
| Example Uz Core Condition - Disability Group I |
Example instance of a disability condition with Group I classification |
| Example Uz Core Condition - Headache |
Example instance of a headache condition documented during a patient encounter |
| Example Uz Core Condition - Pregnancy |
Example instance of a pregnancy condition documented during a patient encounter |
| Example for EpisodeOfCare |
Test example of an episode of care for the UZCoreEpisodeOfCare profile. |
| Example of EpisodeOfCare |
Example EpisodeOfCare for pregnancy management and related treatment services |
| blood-pressure-example |
Example of a blood pressure vital sign observation with systolic and diastolic components |
| bmi-example |
Example of a body mass index (BMI) vital sign observation |
| body-height-example |
Example of a body height vital sign observation |
| body-temperature-example |
Example of a body temperature vital sign observation |
| body-weight-example |
Example of a body weight vital sign observation |
| example-auditevent-condition-lookup |
Example of an audit event where a pracititioner looked up the patient's condition |
| example-auditevent-login |
Example of an audit event where a user logs in |
| example-consent |
Example of a consent |
| example-david |
Example of a patient named David |
| example-david-benefits |
Example benefits observation for David |
| example-david-education |
Example education observation for David |
| example-david-profession |
Example profession observation for David |
| example-david-social-status |
Example social status observation for David |
| example-emma |
Example of a foreign patient named Emma |
| example-healthcareservice |
Example of a healthcare service |
| example-location |
Example of psychiatric hospital |
| example-location-1 |
Example of an organization location |
| example-location-2 |
Example of a branch location |
| example-organization |
Example of a hospital organization |
| example-patient |
Example of a patient |
| example-pdf-document |
Example of a PDF document signed with myID |
| example-practitioner |
Example of a practitioner |
| example-practitioner-gender-other |
Example of a practitioner with a gender extension |
| example-practitionerrole |
Example of a practitioner's role |
| example-provenance |
Example of a provenance event |
| example-related-person |
Example of a related person |
| example-salim |
Example of a patient named Salim |
| example-salim-benefits |
Example benefits observation for Salim |
| example-salim-education |
Example education status for Salim |
| example-salim-profession |
Example profession observation for Salim |
| example-salim-social-status |
Example social status observation for Salim |
| head-circumference-example |
Example of a head circumference vital sign observation |
| heart-rate-example |
Example of a heart rate vital sign observation |
| oxygen-saturation-example |
Example of an oxygen saturation vital sign observation with interpretation and reference range |
| respiratory-rate-example |
Example of a respiratory rate vital sign observation |
| tashkent-diseases-hospital |
Example of a hospital organization |
| Пример ответа на опросник удовлетворённости |
Пример заполненного опросника удовлетворённости пациента |