DSTU2 QA Preview

This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

1.25.4.1.1124 v3 Code System hl7Realm

This code system (http://hl7.org/fhir/v3/hl7Realm) is defined as part of HL7 v3.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-hl7Realm
Name:v3 Code System hl7Realm
Definition: Description: Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm. For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters. Open Issue: The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code. Open Issue: In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length.
OID:2.16.840.1.113883.1.11.20355 (for OID based terminology systems)
System URL:http://hl7.org/fhir/v3/hl7Realm
System OID:2.16.840.1.113883.5.1124
Source ResourceXML / JSON

This value set is not currently used

1.25.4.1.1124.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/v3/hl7Realm, which defines the following codes:

LvlCodeDisplayDefinition
1BindingRealms binding realmsDescription: Concepts that can be used as Binding Realms when creating Binding Statements. These codes are permitted to appear in the InfrastructureRoot.realmCode attribute.
2  AffiliateRealms Affiliate RealmsDescription: Realm codes for official HL7 organizational bodies. This includes both the HL7 International organization as well as all recognized international affiliates (past and present). These groups have the ability to bind vocabulary and develop artifacts. As well, they have the ability to have "ownership" over other binding realms and namespace realms via the owningAffiliate property of those other realm codes.
3    AR ArgentinaDescription: Realm code for use of Argentina
3    AT AustriaDescription: Realm code for use of Austria
3    AU AustraliaDescription: Realm code for use of Australia
3    BR BrazilDescription: Realm code for use of Brazil
3    CA CanadaDescription: Realm code for use of Canada
3    CH SwitzerlandDescription: Realm code for use of Switzerland
3    CL ChileDescription: Realm code for use of Chile
3    CN ChinaDescription: Realm code for use of China
3    CO ColumbiaDescription: Realm code for use of Localized Version
3    CZ Czech RepublicDescription: Realm code for use of Czech Republic
3    DE GermanyDescription: Realm code for use of Germany
3    DK DenmarkDescription: Realm code for use of Denmark
3    ES SpainDescription: Realm code for use of Spain
3    FI FinlandDescription: Realm code for use of Finland
3    FR FranceDescription: Realm code for use of France
3    GR GreeceDescription: Realm code for use of Greece
3    HR CroatiaDescription: Realm code for use of Croatia
3    IE IrelandDescription: Realm code for use of Ireland
3    IN IndiaDescription: Realm code for use of India
3    IT ItalyDescription: Realm code for use of Italy
3    JP JapanDescription: Realm code for use of Japan
3    KR KoreaDescription: Realm code for use of Korea
3    LT LithuaniaDescription: Realm code for use of Lithuania
3    MX MexicoDescription: Realm code for use of Mexico
3    NL The NetherlandsDescription: Realm code for use of The Netherlands
3    NZ New ZealandDescription: Realm code for use of New Zealand
3    RO RomaniaDescription: Realm code for use of Romania
3    RU Russian FederationDescription: Realm code for use of Russian Federation
3    SE SwedenDescription: Realm code for use of Sweden
3    SG SingaporeDescription: Realm code for use of Localized Version
3    SOA Southern AfricaDescription: Realm code for use of Southern Africa
3    TR TurkeyDescription: Realm code for use of Turkey
3    TW TaiwanDescription: Realm code for use of Taiwan
3    UK United KingdomDescription: Realm code for use of United Kingdom
3    US United States of AmericaDescription: Realm code for use of United States of America
3    UV UniversalDescription: Realm code for use of Universal realm or context, used in every instance
3    UY UruguayDescription: Realm code for use of Uruguay
2  C1 Unclassified RealmDescription: Realm code for use of Unclassified Realm
2  GB Great BritainDescription: Realm code for use of Great Britain
2  R1 Representative RealmDescription: Realm code for use of Representative Realm
2  X1 Example RealmDescription: Realm code for use of Example Realm
1NamespaceRealms namespace realmsDescription: Codes that can be used in the "realm" portion of HL7 v3 artifact identifiers.
2  ZZ Localized VersionDescription: An artifact created for local use only. This realm namespace has no owning affiliate. Its use is uncontrolled, i.e. anyone can create artifacts using this realm namespace. Because of this, there is a significant likelihood of artifact identifier collisions. Implementers are encouraged to register their artifacts under an affiliate owned and controlled namespace to avoid such collision problems where possible.