IP Review

This publication includes IP covered under the following statements.

Copyright © 2021 Australian Digital Health Agency - All rights reserved. Except for the material identified below, this content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ .[This resource also includes material from the ‘Australian Immunisation Register Vaccine Code Formats’ last updated: 22 February 2021 © Commonwealth of Australia, represented by Services Australia https://www.servicesaustralia.gov.au/organisations/health-professionals/services/medicare/australian-immunisation-register-health-professionals/resources/air-vaccine-code-formats . Licensed under https://creativecommons.org/licenses/by/3.0/au) .All copies of this resource must include this copyright statement and all information contained in this statement.
Show Usage
- Australian Immunisation Register Vaccine : AIRVaccineTranslationsCS , UZCoreImmunization , UZCoreImmunizationRecommendation , UZCoreVaccinationActivityDefinition and VaccineCodeVS
HL7 Inc.
Show Usage
HL7 International.
Show Usage
- Financial Resource Status Codes : FMStatusVS , UZCoreClaim and UZCoreClaimResponse
- Financial Resource Status Codes : FMStatusCS
These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright Â© 2011 by the National Electrical Manufacturers Association.
Show Usage
- DICOM Controlled Terminology Definitions : AuditEvent/example-auditevent-condition-lookup , AuditEvent/example-auditevent-login ... Show 6 more
- DICOM Controlled Terminology Definitions : DicomDCMCS
This is an example set.
Show Usage
- Sample Codes for Security Structural Role : AuditEvent/example-auditevent-condition-lookup , AuditEvent/example-auditevent-login , SecurityRoleTypeVS and UZCoreAuditEvent
- Sample Codes for Security Structural Role : SampleSecurityStructuralRolesCS
This material contains content from LOINC . LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license . LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
Show Usage
- LOINC: Bundle/example-transaction-bundle , Composition/example-medical-composition ... Show 25 more
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org .
Show Usage
- SNOMED Clinical Terms® (SNOMED CT®): ActionParticipantRoleCS , ActionParticipantRoleVS ... Show 71 more
This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
Show Usage
WHO Collaborating Centre for Drug Statistics Methodology, Oslo, Norway. Use of all or parts of the material requires reference to the WHO Collaborating Centre for Drug Statistics Methodology. Copying and distribution for commercial purposes is not allowed. Changing or manipulating the material is not allowed.
Show Usage
- ATC classification system : ATCClassificationCS , Medication/example-amoxicillin ... Show 6 more

hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )

CHR ensures standardized clinical record management in accordance with the international HL7 FHIR® specification, providing full compatibility with the Master Data Management (MDM) and Metadata and Security Management (MSM) components, as well as with external medical information systems (MIS, LIS, RIS, and others). ( src )

CHR klinik yozuvlarni HL7 FHIR® xalqaro spetsifikatsiyasiga muvofiq standartlashtirilgan tarzda yuritishni ta'minlaydi hamda Asosiy ma'lumotlarni boshqarish (MDM), Metama'lumotlar va xavfsizlikni boshqarish (MSM) komponentlari, shuningdek tashqi tibbiy axborot tizimlari (MIS, LIS, RMIS va boshqalar) bilan to'liq interoperabellikni ta'minlaydi. ( src )

CHR обеспечивает стандартизированное ведение клинических записей в соответствии с международной спецификацией HL7 FHIR®, обеспечивая полную совместимость с подсистемами Master Data Management (MDM), Metadata and Security Management (MSM), а также внешними медицинскими информационными системами (МИС, ЛИС, РМИС и т.д.). ( src )

Confidentiality code total order hierarchy: Restricted (R) is less protective than V, and subsumes all other protection levels (i.e., N, M, L, and U). ( src )

Copyright © 2021 Australian Digital Health Agency - All rights reserved. Except for the material identified below, this content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.[This resource also includes material from the ‘Australian Immunisation Register Vaccine Code Formats’ last updated: 22 February 2021 © Commonwealth of Australia, represented by Services Australia https://www.servicesaustralia.gov.au/organisations/health-professionals/services/medicare/australian-immunisation-register-health-professionals/resources/air-vaccine-code-formats. Licensed under https://creativecommons.org/licenses/by/3.0/au).All copies of this resource must include this copyright statement and all information contained in this statement. Show Usage * Australian Immunisation Register Vaccine: AIRVaccineTranslationsCS, UZCoreImmunization, UZCoreImmunizationRecommendation, UZCoreVaccinationActivityDefinition and VaccineCodeVS ( src )

Privacy metadata indicating the level of protection required to safeguard potentially stigmatizing information, which if disclosed without authorization, would present a high risk of harm to an individual's reputation and sense of privacy.*Usage Note:* The level of protection afforded restricted confidential information is dictated by specially protective organizational or jurisdictional privacy policies, including at an authorized individual's request, intended to engender patient trust in providers of sensitive services.Privacy policies mandating additional levels of protection by restricting information access preempt less protective privacy policies when the information is used in the delivery and management of healthcare. May be pre-empted by jurisdictional law (e.g., for public health reporting or emergency treatment).Confidentiality code total order hierarchy: Restricted (R) is less protective than *V*, and subsumes all other protection levels (i.e., *N, M, L, and U*).**Examples:** Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual (e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer). ( src )

The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element. ( src )

The short copyright declaration (e.g. (c) '2015+ xyz organization' should be sent in the copyrightLabel element. ( src )

These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright Â© 2011 by the National Electrical Manufacturers Association. Show Usage * DICOM Controlled Terminology Definitions: AuditEvent/example-auditevent-condition-lookup, AuditEvent/example-auditevent-login... Show 6 more, AuditEventSubTypeVS, AuditEventTypeVS, AuditParticipationRoleTypeVS, ConditionParticipationRoleTypeVS, UZCoreAuditEvent and UZCoreCondition * DICOM Controlled Terminology Definitions: DicomDCMCS ( src )

This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. Show Usage * LOINC: Bundle/example-transaction-bundle, Composition/example-medical-composition... Show 25 more, GroupCharacteristicKindCS, GroupCharacteristicKindVS, Immunization/immunization-example-001, ImmunizationRecommendation/example-uz-core-immunization-recommendation, Observation/blood-pressure-example, Observation/bmi-example, Observation/body-height-example, Observation/body-temperature-example, Observation/body-weight-example, Observation/head-circumference-example, Observation/heart-rate-example, Observation/observation-reaction-example, Observation/oxygen-saturation-example, Observation/respiratory-rate-example, ObservationCodesVS, RecommendationDateCriterionCS, RecommendationDateCriterionVS, ServiceRequestCodesVS, Type 2 diabetes screening target group, UZCoreGroup, UZCoreHealthcareService, UZCoreImmunizationRecommendation, UZCoreLaboratoryObservationDefinition, UZCoreObservation and UZCoreServiceRequest ( src )

This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html Show Usage * Adjudication Value Codes: ClaimResponse/example-claim-response, ClaimResponseCategoryVS and UZCoreClaimResponse * Adjudication Value Codes: ClaimResponseCategoryCS * Admit source: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterAdmitSourceVS and UZCoreEncounter * Admit source: EncounterAdmitSourceCS * AdverseEventSeriousness: AdverseEvent/example-averted-medication-error, AdverseEvent/example-fatal-anaphylaxis, AdverseEventSeriousnessVS and UZCoreAdverseEvent * AdverseEventSeriousness: AdverseEventSeriousnessCS * AllergyIntolerance Clinical Status Codes: AllergyClinicalStatusVS, AllergyIntolerance/example-grass-pollen-allergy and UZCoreAllergyIntolerance * AllergyIntolerance Clinical Status Codes: AllergyClinicalStatusCS * AllergyIntolerance Verification Status: AllergyIntolerance/example-grass-pollen-allergy, AllergyVerificationStatusVS and UZCoreAllergyIntolerance * AllergyIntolerance Verification Status: AllergyVerificationStatusCS * Claim Type Codes: Claim/example-claim, ClaimResponse/example-claim-response, ClaimTypeVS, UZCoreClaim and UZCoreClaimResponse * Claim Type Codes: ClaimTypeCS * Condition Clinical Status Codes: ClinicalStatusVS, Condition/condition-tuberculosis-risk-example... Show 6 more, Condition/example-anaphylaxis, Condition/example-cancer, Condition/example-disability, Condition/example-headache, Condition/example-pregnancy and UZCoreCondition * Condition Clinical Status Codes: ClinicalStatusCS * ConditionVerificationStatus: Condition/condition-tuberculosis-risk-example, Condition/example-anaphylaxis... Show 6 more, Condition/example-cancer, Condition/example-disability, Condition/example-headache, Condition/example-pregnancy, ConditionVerificationStatusVS and UZCoreCondition * ConditionVerificationStatus: ConditionVerificationStatusCS * Consent Action Codes: Consent/example-consent, ConsentActionVS and UZCoreConsent * Consent Action Codes: ConsentActionCS * DataAbsentReason: DataAbsentReasonVS and UZCoreObservation * DataAbsentReason: DataAbsentReasonCS * Diagnosis Role: Bundle/example-transaction-bundle, EpisodeOfCare/UZCoreEpisodeOfCare-Example and EpisodeOfCare/UZCoreEpisodeOfCare-Example02 * Discharge disposition: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterDischargeDispositionVS and UZCoreEncounter * Discharge disposition: EncounterDischargeDispositionCS * Security Role Type: AuditEvent/example-auditevent-condition-lookup, AuditEvent/example-auditevent-login... Show 4 more, AuditParticipationRoleTypeVS, ConditionParticipationRoleTypeVS, UZCoreAuditEvent and UZCoreCondition * Security Role Type: ExtraSecurityRoleTypeCS * Goal achievement status: Goal/example-goal, GoalAchievementVS and UZCoreGoal * Goal achievement status: GoalAchievementCS * Goal category: Goal/example-goal, GoalCategoryVS and UZCoreGoal * Goal category: GoalCategoryCS * Goal priority: Goal/example-goal, GoalPriorityVS and UZCoreGoal * Goal priority: GoalPriorityCS * Immunization Funding Source: FundingSourceVS, Immunization/immunization-example-001 and UZCoreImmunization * Immunization Funding Source: FundingSourceCS * Immunization Origin Codes: Immunization/immunization-example-001, ImmunizationOriginVS and UZCoreImmunization * Immunization Origin Codes: ImmunizationOriginCS * Immunization Program Eligibility: Immunization/immunization-example-001 * Immunization Recommendation Status Codes: ImmunizationRecommendation/example-uz-core-immunization-recommendation, ImmunizationRecommendation/immunization-recommendation-example, RecommendationforecastStatusVS and UZCoreImmunizationRecommendation * Immunization Recommendation Status Codes: RecommendationforecastStatusCS * Immunization Subpotent Reason: SubpotentReasonVS and UZCoreImmunization * Immunization Subpotent Reason: SubpotentReasonCS * List Empty Reasons: CompositionListEmptyReasonVS and UZCoreComposition * List Empty Reasons: CompositionListEmptyReasonCS * List Order Codes: Composition/example-medical-composition, CompositionListOrderVS and UZCoreComposition * List Order Codes: CompositionListOrderCS * AuditEventEntityRole: AuditEvent/example-auditevent-condition-lookup, ObjectRoleVS and UZCoreAuditEvent * Observation Category Codes: Bundle/example-transaction-bundle, HemoglobinMassPerVolumeInBlood... Show 13 more, Observation/blood-pressure-example, Observation/bmi-example, Observation/body-height-example, Observation/body-temperature-example, Observation/body-weight-example, Observation/cbc-panel-example, Observation/head-circumference-example, Observation/heart-rate-example, Observation/oxygen-saturation-example, Observation/respiratory-rate-example, ObservationCategoryVS, UZCoreLaboratoryObservationDefinition and UZCoreObservation * Observation Category Codes: ObservationCategoryCS * Participant type: EncounterParticipantTypeVS and UZCoreEncounter * Participant type: ParticipantTypeCS * Provenance participant type: Condition/example-cancer, Condition/example-disability... Show 7 more, Condition/example-headache, Condition/example-pregnancy, ConditionParticipationRoleTypeVS, Provenance/example-provenance, ProvenanceParticipationRoleTypeVS, UZCoreCondition and UZCoreProvenance * Provenance participant type: ProvenanceParticipationRoleTypeCS * Observation Reference Range Meaning Codes: HemoglobinMassPerVolumeInBlood, ReferenceRangeMeaningVS, UZCoreLaboratoryObservationDefinition and UZCoreObservation * Observation Reference Range Meaning Codes: ReferenceRangeMeaningCS * Audit Event Source Type: AuditEvent/example-auditevent-condition-lookup and AuditEvent/example-auditevent-login * UsageContextType: ExampleImmunizationPlanDefinition, HemoglobinMassPerVolumeInBlood, UZCoreImmunizationPlanDefinition and UZCoreLaboratoryObservationDefinition * diagnosticServiceSectionId: DiagnosticReport/example-external-lab-report-coded, DiagnosticReport/example-external-lab-report-text-only, DiagnosticReport/uz-core-diagnostic-report-example, DiagnosticReportServiceCategoryVS and UZCoreDiagnosticReport * diagnosticServiceSectionId: DiagnosticReportServiceCategoryCS * re-admissionIndicator: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterReAdmissionVS and UZCoreEncounter * re-admissionIndicator: EncounterReAdmissionCS * contactRole2: Patient/example-david, Patient/example-emma, Patient/example-salim, RelationshipTypeVS and UZCoreRelatedPerson * contactRole2: ContactRole2CS * identifierType: IdentifierDomainCS, IdentifierTypeVS... Show 37 more, Patient/example-david, Patient/example-emma, Patient/example-nodira, Patient/example-salim, Practitioner/example-practitioner, Practitioner/example-practitioner-gender-other, RelatedPerson/example-related-person, Respublika onkologiya markazi, Toshkent viloyati yuqumli kasalliklar shifoxonasi, UZCoreMedication, UZCoreOrganization, UZCorePatient, UZCorePractitioner, UZCorePractitionerRole, UZCoreRelatedPerson, UzDhpEpisodeOfCareIdentifier, UzDhpLocationUnitSystem, UzbekistanBirthCertificateSystem, UzbekistanDriversLicenseSystem, UzbekistanHealthCardNumberSystem, UzbekistanHrmArgosPractitionerSystem, UzbekistanHrmArgosSystem, UzbekistanMedicalInformationSystem, UzbekistanMilitaryIdNumberSystem, UzbekistanMohOrganizationSystem, UzbekistanNationalUniqueIdSystem, UzbekistanPassportDiplomaticSystem, UzbekistanPassportInternationalSystem, UzbekistanPassportLocalSystem, UzbekistanPenitentiaryInstitutionNumberSystem, UzbekistanPensionNumberSystem, UzbekistanProviderAssignedIdentifierSystem, UzbekistanShifSystem, UzbekistanSoliqSystem, UzbekistanTempMedicalRecordSystem, UzbekistanUnknownPatientCodeSystem and Xonobod shahar tibbiyot birlashmasi * identifierType: IdentifierTypeCS * degreeLicenseCertificate: LicenseCertificateVS, Practitioner/example-practitioner and UZCorePractitioner * degreeLicenseCertificate: LicenseCertificateCS * providerRole: Immunization/immunization-example-001 * specimenType: Specimen/example-specimen-blood-cbc, Specimen/specimen-example-blood, SpecimenTypesVS and UZCoreSpecimen * specimenType: SpecimenTypesCS * relevantClincialInformation: RelevantClinicalInformationVS, Specimen/example-specimen-blood-cbc, Specimen/specimen-example-blood and UZCoreSpecimen * relevantClincialInformation: RelevantClinicalInformationCS * ActCode: AuditEvent/example-auditevent-condition-lookup, Bundle/example-transaction-bundle... Show 5 more, Encounter/example-encounter, EncounterClassVS, SecurityLabelVS, UZCoreAuditEvent and UZCoreEncounter * ActCode: ActCodeCS * ActPriority: Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterPriorityVS and UZCoreEncounter * ActPriority: EncounterPriorityCS * ActReason: AuditEvent/example-auditevent-condition-lookup, AuditEvent/example-auditevent-login... Show 9 more, AuditPurposeOfUseVS, Consent/example-consent, ConsentPurposeOfUseVS, Immunization/immunization-example-001, ImmunizationStatusReasonVS, SecurityLabelVS, UZCoreAuditEvent, UZCoreConsent and UZCoreImmunization * ActReason: ActReasonCS * ActSite: Immunization/immunization-example-001, ImmunizationSiteVS and UZCoreImmunization * ActSite: ImmunizationSiteCS * Confidentiality: SecurityLabelVS and UZCoreAuditEvent * Confidentiality: ConfidentialityCS * DocumentCompletion: Provenance/example-provenance, ProvenanceActivityTypesVS and UZCoreProvenance * DocumentCompletion: ProvenanceActivityTypesCS * MaritalStatus: MaritalStatusVS, Patient/example-david, Patient/example-emma, Patient/example-salim and UZCorePatient * MaritalStatus: MaritalStatusCS * NullFlavor: MaritalStatusVS and UZCorePatient * NullFlavor: NullFlavorCS * ObservationInterpretation: Observation/oxygen-saturation-example, ObservationInterpretationVS and UZCoreObservation * ObservationInterpretation: ObservationInterpretationCS * ParticipationType: AdverseEvent/example-averted-medication-error, AdverseEvent/example-fatal-anaphylaxis... Show 8 more, Bundle/example-transaction-bundle, Encounter/example-encounter, EncounterParticipantTypeVS, RelatedPerson/example-related-person, RelationshipTypeVS, UZCoreAdverseEvent, UZCoreEncounter and UZCoreRelatedPerson * ParticipationType: ParticipationTypeCS * RoleClass: PositionAndProfessionVS, RelationshipTypeVS, UZCorePractitionerRole and UZCoreRelatedPerson * RoleClass: DMEDROleClassCS and RoleClassCS * RoleCode: LocationTypesVS, PositionAndProfessionVS... Show 5 more, RelationshipTypeVS, Respublika onkologiya markazi, UZCoreLocation, UZCorePractitionerRole and UZCoreRelatedPerson * RoleCode: RoleCodeCS ( src )

Uzbekistan Digital Health Platform - Local Development build (v0.7.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions ( src )

Uzbekistan Digital Health Platform - Локальная сборка (v0.7.0), построенная FHIR (HL7® FHIR® Стандартные инструменты сборки. Смотрите каталог опубликованных версий ( src )

aceturas (R) ( src )

acistras (R) ( src )

acoxilum (R) ( src )

amsonas (R) ( src )

anisatilum (R) ( src )

axetilum (R) ( src )

besilas (R) ( src )

bezomilum (R) ( src )

buciclas (R) ( src )

bunapsilas (R) ( src )

butepras (R) ( src )

camsilas (R) ( src )

carbesilas (R) ( src )

ciclotas (R) ( src )

cilexetilum (R) ( src )

cipionas (R) ( src )

closilas (R) ( src )

crobefas (R) ( src )

cromacas (R) ( src )

cromesilas (R) ( src )

daropas (R) ( src )

deanil (R) ( src )

decil (R) ( src )

dibudinas (R) ( src )

dibunas (R) ( src )

digolilum (R) ( src )

diolaminum (R) ( src )

docosilum (R) ( src )

dofosfatum (R) ( src )

edaminum (R) ( src )

edisilas (R) ( src )

embonas (R) ( src )

enantas (R) ( src )

epolaminum (R) ( src )

erbuminum (R) ( src )

esilas (R) ( src )

estolas (R) ( src )

etabonas (R) ( src )

farnesilum (R) ( src )

fendizoas (R) ( src )

fostedatum (R) ( src )

gluceptas (R) ( src )

hibenzas (R) ( src )

hyclas (R) ( src )

isetionas (R) ( src )

lauril (R) ( src )

laurilsulfas (R) ( src )

megallas (R) ( src )

mesilas (R) ( src )

metembonas (R) ( src )

metilsulfas (R) ( src )

mofetilum (R) ( src )

napadisilas (R) ( src )

napsilas (R) ( src )

octilum (R) ( src )

olaminum (R) ( src )

oxogluras (R) ( src )

pentexilum (R) ( src )

pivalas (R) ( src )

pivoxetilum (R) ( src )

pivoxil (R) ( src )

proxetilum (R) ( src )

soproxilum (R) ( src )

steaglas (R) ( src )

tebutas (R) ( src )

tenoas (R) ( src )

teoclas (R) ( src )

teprosilas (R) ( src )

tetraxetanum (R) ( src )

tofesilas (R) ( src )

tosilas (R) ( src )

triclofenas (R) ( src )

triflutas (R) ( src )

trolaminum (R) ( src )

troxundas (R) ( src )

xinafoas (R) ( src )

External References

Internal Images

../assets/images/uzb.svg

tree-filter.png

validator-fhir-org-1-options.png

validator-fhir-org-2-enter-resource.png

validator-fhir-org-3-results.png

Unattributed Code Systems

Copyright Fragment

Copyright and Registered Trademark Uses

External References

Internal Images