ISO13582-part2: Unterschied zwischen den Versionen

Aus Hl7wiki
Wechseln zu: Navigation, Suche
(→‎HL7 Viewpoint)
(→‎category)
 
(7 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 1: Zeile 1:
−
=List of Codes and Enumerations=
+
=Information model=
  
−
==CountryCodes==
+
In order to exchange OID and their metadata between different registries and applications the following additional data items beyond the OID itself need to be taken under consideration (see also
 +
<ref>[http://www.itu.int/rec/T-REC-X.680/en Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1: 2008, Information Technology – Abstract Syntax Notation One (ASN.1), Specification of Basic Notation, 1997]</ref>
 +
<ref>[http://www.itu.int/rec/T-REC-X.667/en Recommendation ITU-T X.667 | ISO/IEC 9834-8: Information technology – Open Systems Interconnection – Procedures for the operation of OSI Registration Authorities: Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 object identifier components]</ref>):
 +
* descriptions
 +
* status information
 +
* categorization
 +
* time information
 +
* comments
 +
* versions
 +
* links
 +
* relationships to other OIDs and external sources
 +
* registering and responsible organizations
 +
* associated persons.
  
−
ISO 3166-1 alpha two letter country codes are used<ref>[http://www.iso.org/iso/english_country_names_and_code_elements ISO 3166-1-alpha-2 country codes]</ref><ref>ISO 3166 - Codes for the representation of names of countries - The International Organization for Standardization, 3rd edition.</ref>. This list states the country names as given in ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code elements.
+
An information model with all classes, attributes and their properties aiming on a common understanding of the requirements of an OID registry has been created (Figure 1).
  
−
==LanguageCodes==
+
[[Datei:Oidmodel.jpg|700px|OID Registry Model (Draft)]]
  
−
Reflects the Human Language. Language is specified conformant to RFC 3066 (Tags for the Identification of Languages). The format is
+
==XML exchange format==
−
ss[-CC]
+
Data exchange can be facilitated by a standardized representation of the complete set of information as an XML structure together with the associated checks of underlying constraints and business rules. This XML structure for importing and exporting OID amongst different registries and other healthcare applications is aiming on the availability of reliable information about OIDs.
−
where '''ss''' is the language code drawn from ISO-639-1<ref>[http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-2 Codes for the Representation of Names of Languages]</ref>, and '''CC''' is the country code, conformant to ISO-3166 alpha-2.
 
  
−
Example:
+
The following sections summarise and explain classes and their attributes.
−
<syntaxhighlight lang="text">
+
 
−
en-US
+
==Registry==
−
</syntaxhighlight>
+
This is the basic information about the OID-Registry hosting the OIDs.
 +
 
 +
[[Datei:Oid-registry.jpg | 300px]]
  
−
==OIDcategory==
+
===Attributes===
−
This enumeration reflects the category of the OID (node, leaf) and possible sub categories.
 
  
 
{|class="hl7table"
 
{|class="hl7table"
−
! Level !! Code !! Description
+
! Attribute !! Description !! DT !! Card !! Conf || Length
−
|-
 
−
| 0 || N || node
 
 
|-
 
|-
−
| 1 || NRA || registration authority (RA)
+
| validTime || validity time interval || IVL_TS || 1..* || mandatory || -
 
|-
 
|-
−
| 1 || NMN || structure for the management of OIDs (it is not good practice but we know that some of these nodes in some registries also identify objects, which should not be)
+
| scopedOIDs || List of scoped root OIDs || ST.OID || 0..* || optional || 64
 
|-
 
|-
−
| 0 || L || leaf
+
| name || Official name of the OID registry || ST || 1..1 || mandatory || 64
 
|-
 
|-
−
| 1 || LIO || an instance of an object
+
| description || Description of the OID registry, possible in multiple languages || ED || 0..* || optional || -
 
|-
 
|-
−
| 1 || LNS || a namespace identifier
 
 
|}
 
|}
  
−
==OIDstatusCodes==
+
====validTime====
−
This code reflects the status of the OID. Valid values are:
 
  
 +
This is the validity time interval, i.e. the begin (and end) time when this registry is/was responsible for registering OIDs. This can be a list of intervals.
 +
{{ConstraintBox|rg-vt:
 +
A ''validTime'' element shall be present and of datatype IVL_TS with at least the low child element populated.
 +
}}
 +
 +
====scopedOIDs====
 +
 +
List of scoped root OIDs, i.e. the OIDs for which this OID registry is responsible for registration.
 +
{{ConstraintBox|rg-so:
 +
If the OID registry is responsible for issuing/registering a root OID, this OID should be listed in ''scopedOIDs''.
 +
}}
 +
 +
====name====
 +
 +
Official name of the OID registry
 +
 +
====description====
 +
 +
A description of the OID registry, possible in multiple languages
 +
{{ConstraintBox|rg-ds:
 +
If at least one ''description'' element is present one of the description's language code shall be English (“en”, “en-US” etc.).
 +
}}
 +
 +
===Associations===
 
{|class="hl7table"
 
{|class="hl7table"
−
! Level !! Code !! Description
+
! Association !! Description !! Class !! Card !! Conf
 
|-
 
|-
−
| 0 || pending || OID assignment pending
+
| person || Contact person(s) || [[#Person|Person]] || 1..* || mandatory
 
|-
 
|-
−
| 0 || complete || assignment complete
+
| hostingOrganization || Hosting organization || [[#Organization|Organization]] || 1..* || mandatory
 
|-
 
|-
−
| 0 || retired || OID retired/withdrawn
+
| oid || List of OIDs || [[#Oid|Oid]] || 0..* || required
 
|-
 
|-
−
| 0 || unknown || status of the OID unknown
 
 
|}
 
|}
  
−
==ReferenceType==
+
===Example===
−
The type of reference covers the following values:
+
<syntaxhighlight lang="xml">
 +
<registry>
 +
 
 +
    <validTime>
 +
        <low value="20100501"/>
 +
    </validTime>
 +
 
 +
    <scopedOID value="1.2.3.4.5"/>
 +
 
 +
    <name value="The best OID registry ever"/>
 +
    <description language="en-US" value="This is a test OID registry, although the best"/>
 +
 
 +
    <person> ... </person>
 +
    <hostingOrganization> ... </hostingOrganization>
 +
 
 +
    <oid> ... </oid>
 +
 
 +
</registry>
 +
</syntaxhighlight>
 +
 
 +
==Oid==
 +
This class contains the registered OID and the associated meta data.
 +
 
 +
[[Datei:Oid-OID.jpg | 300px]]
 +
 
 +
===Attributes===
  
 
{|class="hl7table"
 
{|class="hl7table"
−
! Level !! Code !! Description
+
! Attribute !! Description !! DT !! Card !! Conf || Length
 
|-
 
|-
−
| 0 || RPLC || replaced by OID
+
| dotNotation || registered OID, dot notation || ST.OID || 1..1 || mandatory || 64
 
|-
 
|-
−
| 0 || PREF || preferred OID
+
| asn1Notation || ASN.1 notation || ST.ASN1 || 0..1 || optional || 128
 
|-
 
|-
−
| 0 || LINK || link access (to code and value set tables)
+
| iriNotation || IRI notation || ST.IRI || 0..1 || optional || 128
 
|-
 
|-
−
| 0 || IDSD || identification scheme documentation
+
| symbolicName || symbolic name || ST.SYMB || 0..1 || optional || 128
−
|}
 
−
 
 
−
==RoleCodes==
 
−
This covers the kind of role of an authority. Valid values are:
 
−
 
 
−
{|class="hl7table"
 
−
! Level !! Code !! Description
 
 
|-
 
|-
−
| 0 || PRI || primary
+
| category || OID category || CS || 1..1 || required || -
 
|-
 
|-
−
| 0 || SEC || secondary
+
| status || OID status || CS || 1..1 || mandatory || -
 
|-
 
|-
−
| 0 || OBO || on behalf of
+
| creationDate || date of creation || TS || 0..1 || optional || -
 
|-
 
|-
−
| 0 || CON || contact person
+
| realm || countries || CS || 0..* || optional || -
−
|}
 
−
 
 
−
==RoleStatus==
 
−
This covers the status of role:
 
−
 
 
−
{|class="hl7table"
 
−
! Level !! Code !! Description
 
 
|-
 
|-
−
| 0 || active || active
+
| description || textual description || ED || 1..* || mandatory || -
 
|-
 
|-
−
| 0 || terminated || terminated
 
 
|}
 
|}
  
−
=Data types=
+
====dotNotation====
−
 
 
−
A subset of the ISO 21090 data types<ref>ISO/FDIS 21090:2010 Health Informatics - Harmonized data types for information
 
−
interchange</ref> is used for the XML representation of data. In some cases additional flavors or constraints are defined.
 
  
−
The following section gives examples and describes the restrictions / constraints on the generic specification.
+
The OID in dot notation of SNMP or ASN.1/XER.
  
−
==Address AD==
 
 
Example:
 
Example:
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
−
<addr use="HP">
+
2.16.528
−
<part type="STR" value="Windsteiner Weg"/>
 
−
<part type="BNR" value="54a"/>
 
−
<part type="CNT" code="DEU" codeSystem=" 1.0.3166.1.2" value="D"/>
 
−
<part type="ZIP" value="14165"/>
 
−
<part type="CTY" value="Berlin"/>
 
−
</addr>
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
==Coded Simple Value CS==
+
====asn1Notation====
−
A coded attribute with a simple value. The attribute is always bound to a specific code system mentioned in the section about [[#List of code systems and Enumerations|lists of code systems and enumerations]] .
+
 
 +
The OID in ASN.1 notation with (optional) identifiers and numbers.
  
−
Example:
+
Examples:
−
<syntaxhighlight lang="xml">
+
<syntaxhighlight lang="text">
−
<statusCode code="active"/>
+
{joint-iso-itu-t(2) country(16) nl(528)}
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
==Encapsulated Data ED==
+
<syntaxhighlight lang="text">
−
In this specification this is either plain text (media type "text/plain") and HTML (media type "text/html") only. A language code is required.
+
{itu-t(0) recommendation(0) a(1)}
−
{{ConstraintBox|ed-lc:
+
</syntaxhighlight>
−
An element of data type ED SHALL have a language code represented in ''@language''.
+
{{NoteBox|
 +
Note that the surrounding curly brackets can be omitted.
 
}}
 
}}
−
{{ConstraintBox|ed-mt:
+
{{NoteBox|
−
An element of data type ED SHALL have a ''@mediaType'' of "text/plain" or "text/html".
+
Note that this information is not necessarily entered by a human, this item maybe populated algorithmically.
 
}}
 
}}
  
−
Examples:
+
====iriNotation====
−
<syntaxhighlight lang="xml">
 
−
<text value="this is plain text" language="en-US" mediaType="text/plain"/>
 
  
−
<text value="dieses ist normaler Text" language="de-DE" mediaType="text/plain"/>
+
The OID in Internationalized Resource Identifier<ref>http://www.oid-info.com/faq.htm#iri</ref> (IRI) notation.
−
</syntaxhighlight>
 
  
−
==Entity Name for a person EN.PN==
 
 
Example:
 
Example:
−
<syntaxhighlight lang="xml">
+
<syntaxhighlight lang="text">
−
<name use="OR C">
+
oid:/Country/528
−
<part type="GIV" value="Selby"/>
 
−
<part type="FAM" qualifier="SP" value="Butt"/>
 
−
<part type="FAM" value="Hadrian"/>
 
−
</name>
 
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
{{NoteBox|
 +
Note that this information is not necessarily entered by a human, this item maybe populated algorithmically.
 +
}}
  
−
==Entity Name for an organization EN.ON==
+
====symbolicName / Secondary Arc Identifier ====
−
Example:
 
−
<syntaxhighlight lang="xml">
 
−
<name use="LS">
 
−
  <part value="Healthy Hospital"/>
 
−
  <part qualifier="SFX">LLC</part>
 
−
</name>
 
−
</syntaxhighlight>
 
  
−
==Interval of time stamp IVL_TS==
+
A symbolic short name, unique among the siblings of the arc of the OID.
−
Example:
 
−
<syntaxhighlight lang="xml">
 
−
<validTime>
 
−
  <low value="20101201"/>
 
−
  <high value="20101224"/>
 
−
</validTime>
 
−
</syntaxhighlight>
 
  
−
==String ST==
+
The ISO rules on Secondary Arc Identifiers, as laid out in Rec. ITU-T | ISO/IEC 9834-1 ''Procedures for Registration Authorities'', section 6.2.2, apply:
−
A character string, with possible translations.
+
* identifiers of an arc are required to commence with a lowercase letter, and to contain only letters, digits, and hyphens.
 +
* the last characters shall not be a hyphen
 +
* there shall be no two consecutive hyphens in the name
  
−
Example:
+
Example
−
<syntaxhighlight lang="xml">
+
<syntaxhighlight lang="text">
−
<name value="I am a name"/>
+
nl
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
==String ST.NT==
+
====category====
−
A character string, with no translations allowed.
 
  
−
==Object Identifier (dot notation) ST.OID==
+
The type/category of the OID; enumeration, values see value set [[#OIDcategories|OIDcategories]].
−
This is actually a character string without translation (ST.NT) with a certain pattern. The pattern can be found in the Schema for XML representation (see Annex C).
 
  
−
Example:
+
There are actually two main types of OIDs: ''leafs'' (id of an object), and ''nodes'' representing an ontological branch.
−
<syntaxhighlight lang="xml">
 
−
<oid value="1.2.3.4.5.0.6.7.8.9"/>
 
−
</syntaxhighlight>
 
  
−
==Object Identifier (asn1 notation) ST.ASN1==
+
The types of ''node'' OID may be
−
This is actually a character string without translation (ST.NT) with a certain pattern. The pattern can be found in the Schema for XML representation (see Annex C).
+
* a registration authority (RA) or
 +
* a structure for the management of OIDs.
  
−
==Object Identifier (iri notation) ST.IRI==
+
The proposal for sub categories of ''leaf'' OIDs are
−
This is actually a character string without translation (ST.NT) with a certain pattern. The pattern can be found in the Schema for XML representation (see Annex C).
+
* identifiers of an instance of an object (for example a person)
 +
* namespace identifiers (for example code systems, value sets)
 +
{{NoteBox|
 +
In addition there are properties of OIDs that can reflect other business needs.
 +
These can be
 +
* tags (simple text)
 +
* other categorizations of the OID, coded or as text
 +
* "sub-types" of the OID
 +
For further information see ''[[#AdditionalProperty|AdditionalProperty]]''.
 +
}}
  
−
==Symbolic name ST.SYMB==
+
====status====
−
This is actually a character string without translation (ST.NT) with a certain pattern. The pattern can be found in the Schema for XML representation (see Annex C).
 
  
−
==Telecommunication TEL==
+
Status of the OID. This is an enumeration, for values see value set [[#OIDstatusCodes|OIDstatusCodes]]
−
Example:
 
−
<syntaxhighlight lang="xml">
 
−
<telecom value="tel:+491234567890" use="H WP" capabilities="voice fax"/>
 
−
</syntaxhighlight>
 
  
−
==Locatable Resource TEL.URL==
+
====creationDate====
−
This points to a locatable resource, e.g. an internet address (see also: <ref>IETF RFC 1738 - Uniform Resource Locators (URL)</ref><ref>IETF RFC 2396 - Uniform Resource Identifiers (URI): Generic Syntax</ref>).
 
  
−
Example:
+
The creationDate is used to describe when the OID was first registered. It is not the date when the OID description is submitted to the OID repository.
−
<syntaxhighlight lang="xml">
+
The creationDate, once set, never changes.
−
<ref value="http://x.y.org"/>
 
−
</syntaxhighlight>
 
  
−
==Time stamp TS==
+
====realm====
−
Example:
 
−
<syntaxhighlight lang="xml">
 
−
<applicationDate value="20101205"/>
 
−
</syntaxhighlight>
 
  
−
= Annex A (informative) =
+
In some cases OIDs may apply to a specific county/realm only, e.g. the namespace identifiers for the US Social Security Number (SSN) or the Dutch Citizen Service Number (BSN) or the codes system representing ICD-10 International Classification of Diseases 10th Revision for the use in Germany only (ICD10gm). This can be indicated by ''realm'' which is either the code of country or "UV" for universal. For values see code system [[#CountryCodes| CountryCodes]].
−
This informative annex includes a specification of those parts of the OID tree that are known to be used for national and for international e-health applications. A description of possible of sub trees reflecting OID types is given.
 
  
−
==OID types==
+
====description====
−
In many OID registries the type of an OID is used to improve for example the administrative process around assigning new OIDs or improve search capabilities of registry users etc.. The OID type has nothing to do with ISO standards, or any intrinsic meaning or form of the OID itself, it is only a convenience for the users of an OID registry.
 
  
−
In order to store OID types along with OID metadata described in this technical standard, class AdditionalProperty is used. It seemed from international experience with OID registries that this can be a recommendation only. OID types vary from registry to registry.
+
This element contains a free text description of the OID ("what is the OID?"). The text typically contains an explanation but also can contain:
 +
* explicit versioning aspects
 +
* licensing information
 +
* Intellectual Property rights information
 +
* trademarks.
  
−
Therefore OID types may be used as additional properties; if OID type is used it is recommended that  AdditionalProperty.attribute should be “OIDType” and AdditionalProperty.value shall be an enumeration or code string representing the OID type.
+
This element is repeatable for each language.  
  
−
==HL7 Viewpoint==
+
The datatype [[#ED|ED]] allows for a thumbnail child element. A thumbnail may be populated describing a short description of the OID (sometimes referred to as ''identifier name'').
−
HL7 International has created a type ontology for the OIDs in the HL7 registry to make it easier for the user community to search for OIDs they may be looking for.
 
  
−
The following types have been defined for use in the HL7 OID Registry [7]:
+
Example:
 +
<syntaxhighlight lang="xml">
 +
<description language="en-US" value="this is plain text as a long description">
 +
  <thumbnail value="short text"/>
 +
</description>
 +
</syntaxhighlight>
  
−
{|class="wikitable"
+
{{NoteBox|
−
! Arc !! Type !! Description
+
Note that data type [[#ED|ED]] also reflects the aspect of language of the description (language code).
 +
}}
 +
 
 +
{{ConstraintBox|oi-ds:
 +
There SHALL be one description instance with language code English (“en”, “en-US” etc.).
 +
}}
 +
 
 +
===Associations===
 +
{|class="hl7table"
 +
! Association !! Description !! Class !! Card !! Conf
 
|-
 
|-
−
|.1 ||HL7 registered internal objects (other than organizational bodies) ||Type 1 OIDs are used for certain internal administrative functions, and to identify released and published Standards. This includes Version 3 International Releases, Normative Editions, V2.x Standards releases, CDA releases, etc.  This is almost never used at this time.
+
| registrationAuthority || Registration Authority || [[#RegistrationAuthority|RegistrationAuthority]] || 1..1 || required
 
|-
 
|-
−
|.2 ||HL7 organizational bodies and groups ||Type 2 OIDs are only used to identify an HL7 Group, such as a Working Group, or an International Council Member of HL7, such as HL7 Australia. These are created only when a new organizational body is recognized by HL7 International Headquarters.
+
| responsibleAuthority || Responsible Authority || [[#ResponsibleAuthority | ResponsibleAuthority]] || 1..* || required
 
|-
 
|-
−
|.3 ||External (not HL7) group functioning as a Registration Authority ||Type 3 OIDs are used for organizations that wish to create their own trees of OIDs for their use. If you will be assigning OIDs yourself under the OID that you are applying for, then you should select Type 3.  This effectively delegates Registration Authority to your organization for all OIDs under this new Type 3 OID.  No one else anywhere will create OIDs under your new root.  Every OID created ‘under’ this new root will be considered by HL7 to be an ‘external’ OID, since you will have created it external to the HL7 OID Registry OID assignment software.  These may be requested or registered by anyone.
+
| submittingAuthority || Submitting Authority || [[#SubmittingAuthority | SubmittingAuthority]] || 0..1 || optional
−
 
 
−
Note that a Type 3 OID identifies an organizational entity, not a particular piece of hardware machinery.  It does not have to be a corporation, it could be as small as a single development group building interface software for an NHIN Connect project, for instance.  Type 3 OIDs should not be used to identify objects in addition to the organizational entity responsible for creating new OIDs under it.
 
 
|-
 
|-
−
|.4 ||Registered externally maintained identifier systems and namespaces ||Type 4 OIDs are used for namespaces for identifiers that are public, and used widely, such as health card numbers, ID numbers assigned by jurisdictional authorities, etc.   This is also used for any namespaces you may manage with your own defined OIDs under your own root, such as Medical Record Numbers or Accession Numbers, for example.  This type of OID is typically used in the root of the version 3 datatype Instance Identifier.
+
| additionalProperty || Additional Properties || [[#AdditionalProperty | AdditionalProperty]] || 0..* || optional
 
|-
 
|-
−
|.5 ||HL7 Internal Code Systems ||Type 5 OIDs are used only for HL7 created and maintained Coding Systems, that have been approved through the HL7 V3 Harmonization process.   This type is assigned only by the group that applies decisions from the harmonization processes to the HL7 databases.  These OIDs are typically used in the codSystem property of an HL7 Version 3 coded datatype.
+
| historyAnnotation || History Annotations || [[#HistoryAnnotation | HistoryAnnotation]] || 0..* || optional
 
|-
 
|-
−
|.6 ||Registered external coding systems ||Type 6 is assigned to those OIDs that identify a Coding System or terminology that is created, published, and maintained by any organization outside of HL7.   At this time, only an HL7 cochair or OID administrator can assign Type 6 to any OID.  This type of OID is typically used in the codeSystem property of an HL7 Version 3 coded datatype.
+
| reference || References || [[#Reference | Reference]] || 0..* || optional
 
|-
 
|-
−
|.7 ||HL7 published document artifacts ||Type 7 OIDs are used solely for HL7 published artifacts (not releases of Standards), and are assigned only by members of the HL7 publishing group.  This includes tutorial slides, implementation guides, databases, published RIM graphic billboards, Wiki pages, etc.
+
|}
 +
 
 +
==RegistrationAuthority==
 +
 
 +
[[Datei:Oid-RegistrationAuthority.jpg | 600px]]
 +
 
 +
This class represents the Registration Authority (RA).
 +
 
 +
===Attributes===
 +
 
 +
{|class="hl7table"
 +
! Attribute !! Description !! DT !! Card !! Conf || Length
 
|-
 
|-
−
|.8 ||(deprecated) ||Type 8 is currently not used.
+
| code || RA role code || CS || 1..1 || mandatory || -
 
|-
 
|-
−
|.9 ||HL7 Registered conformance profiles ||Type 9 is used to indicate HL7 Conformance Profiles, published in the HL7 Profile Registry.
+
|}
 +
 
 +
====code====
 +
The code holds information about the role type of the RA. Valid codes are listed in [[#RoleCodes|RoleCodes]].
 +
 
 +
===Associations===
 +
{|class="hl7table"
 +
! Association !! Description !! Class !! Card !! Conf
 
|-
 
|-
−
|.10 ||HL7 Registered Templates ||Type 10 OIDs identify published Templates. These are created and registered by the Templates Workgroup, or by HL7 Workgroups that define and publish templates as part of their balloted standards.
+
| scopingOrganization || Scoping organization || [[#Organization|Organization]] || 1..1 || mandatory
 
|-
 
|-
−
|.11 ||HL7 defined and registered Value Sets ||Type 11 OIDs identify Value Sets that have been created and published by HL7, and have been approved through the HL7 Harmonization processes only. These are used in HL7 Version 3 Model Binding and Context Binding mechanisms, and can only be assigned by members of the group that applies the HL7 Harmonization process approvals to the HL7 databases.
+
| person || Contact person(s) || [[#Person|Person]] || 0..1 || optional
 
|-
 
|-
−
|.12 ||HL7 Version 2.x tables ||Type 12 indicates that an OID identifies explicitly an HL7 Version 2.x Table, as published in the HL7 Version 2 series of standards.  These exist to help facilitate development of translation capabilities between Version 2.x and Version 3/CDA interfaces.
+
|}
 +
 
 +
==ResponsibleAuthority==
 +
This is a class representing the (managing) authority that is responsible for the object that is identified by the OID (not for the OID itself).
 +
 
 +
[[Datei:Oid-ResponsibleAuthority.jpg | 600px]]
 +
 
 +
===Attributes===
 +
 
 +
{|class="hl7table"
 +
! Attribute !! Description !! DT !! Card !! Conf || Length
 
|-
 
|-
−
|.13 ||Externally authored and curated Value Sets ||Type 13 OIDs identify Value Sets that have been created, published, and are maintained by organizations outside of HL7.   They may be registered by anyone, and are generally used in Hl7 Version 3 Model Binding and Context Binding mechanisms.
+
| code || role code || CS || 1..1 || mandatory || -
 
|-
 
|-
−
|.14 ||Assignment Ontology node ||Type 14 OIDs may be used by any Registration Authority to indicate a structural ‘branch’ in the tree that they create under their own root, where the node is not any particular type of OID, the types will be below this node.   Normally any node that is not a leaf is a registration authority, but some find that adding levels in the structure of the OIDs they create as Registration Authorities make the administration of the tree a bit easier.  Each of the nodes in the HL7 tree that is the root of each of the Types is actually a Type 14 OID.
+
| statusCode || status code || CS || 1..1 || mandatory || -
 
|-
 
|-
−
|.15 ||Small code sets externally defined ||Type 15 OIDs are used to identify small code lists or sets that are defined and maintained by organizations outside of HL7.   Where Value Sets are built upon underlying coding systems, short code lists are often ad-hoc values that are used in various applications, that are not components of a particular terminology or coding system. This type of OID may be used in the codeSystem property of a version 3 coded datatype.
+
| validTime || validity time || IVL_TS || 1..* || mandatory || -
 +
|-
 +
|}
 +
 
 +
====code====
 +
The code holds information about the role type of the ResponsibleAuthority. Valid codes are listed in [[#RoleCodes|RoleCodes]].
 +
 
 +
====statusCode====
 +
The statusCode holds information about the status of the ResponsibleAuthority. Valid codes are listed in [[#RoleStatus|RoleStatus]].
 +
 
 +
====validTime====
 +
This is an interval of time, representing the period when the ResponsibleAuthority is/was responsible for the object that is identified by the OID. If the ResponsibleAuthority is still responsible, only ''validTime.low'' is populated.
 +
 
 +
===Associations===
 +
{|class="hl7table"
 +
! Association !! Description !! Class !! Card !! Conf
 
|-
 
|-
−
|.17 ||Non-specified type ||Type 17 OIDs are for any other type of object that does not fall into one of the other Type categories.  
+
| scopingOrganization || Scoping organization || [[#Organization|Organization]] || 1..1 || mandatory
 
|-
 
|-
−
|.18 ||HL7 Version 2.8 Coding Systems ||Type 18 OIDs are specifically for those coding systems that are defined as such in the HL7 Version 2.8 standard.  These may only be created by HL7 cochairs.
+
| person || Contact person(s) || [[#Person|Person]] || 0..1 || optional
 
|-
 
|-
−
|.19 ||HL7 Examples ||Type 19 OIDs are used for published examples; it is a truly meaningless identifier, as it is not to be used for any actual entities.  This is the only kind of OID that may not be a unique identifier, i.e. it may refer to more than one object if it appears in different publications or slides.  Type 19 OIDs are used '''ONLY''' in published examples in documents and slide presentations, and should '''NEVER''' appear in any implementation or any HL7 model instance.
 
 
|}
 
|}
  
−
==Recommendations for OID types==
+
==SubmittingAuthority==
−
From a policy perspective it is common practice in several healthcare related OID registries
+
This is a class representing the submitting authority that originally asked for a new OID.
−
<ref>http://www.dimdi.de/dynamic/de/ehealth/oid/verzeichnis.html OID registry Germany</ref>
 
−
<ref>http://oid.refdata.ch/ OID registry Switzerland</ref>
 
−
<ref>https://www.gesundheit.gv.at/OID_Frontend/ OID registry Austria</ref>
 
−
to distinguish at least between the following types of OIDs:
 
  
−
{|class="wikitable"
+
[[Datei:Oid-SubmittingAuthority.jpg | 600px]]
−
! Arc !! Type
+
 
 +
(Please note: to avoid redundancy, the classes ''Organization'' and ''Peron'' are shown with attributes here, at all other places only a "shadow" class of these two classes is shown)
 +
 
 +
===Attributes===
 +
{|class="hl7table"
 +
! Attribute !! Description !! DT !! Card !! Conf || Length
 
|-
 
|-
−
|.3 || organizational bodies and groups
+
| code || role code || CS || 1..1 || mandatory || -
 
|-
 
|-
−
|.4 || identifier systems and namespaces
+
| applicationDate || date of application || TS || 0..1 || optional || -
 
|-
 
|-
−
|.5 || code systems
+
|}
 +
 
 +
====code====
 +
The code holds information about the role type of the submitting authority. Valid codes are listed in [[#RoleCodes|RoleCodes]].
 +
 
 +
====applicationDate====
 +
 
 +
Date of application (submission or certified submission) of the requested OID.
 +
 
 +
===Associations===
 +
{|class="hl7table"
 +
! Association !! Description !! Class !! Card !! Conf
 
|-
 
|-
−
|.7 || document artifacts
+
| scopingOrganization || Scoping organization || [[#Organization|Organization]] || 1..1 || mandatory
 
|-
 
|-
−
|.9 || conformance profiles
+
| person || Contact person(s) || [[#Person|Person]] || 1..1 || mandatory
 
|-
 
|-
−
|.10 || templates
+
|}
−
|-
+
 
−
|.11 || value sets
+
==HistoryAnnotation==
 +
This class reflects historical annotations of the OID and records the changes of any data over time.
 +
 
 +
[[Datei:Oid-HistoryAnnotation.jpg | 300px]]
 +
 
 +
===Attributes===
 +
{|class="hl7table"
 +
! Attribute !! Description !! Datatype !! Cardinality !! Conformance || Recommended Length
 
|-
 
|-
−
|.19 || examples
+
| annotationDate || date annotation was created || TS || 0..1 || required || -
 
|-
 
|-
−
|.99 || experimental
+
| text || annotation || ED || 1..1 || mandatory || -
 
|-
 
|-
 
|}
 
|}
 +
{{NoteBox|
 +
Note that data type ED also reflects the aspect of language of the description (language code).
 +
}}
  
−
= Annex B (informative)  =
+
==Reference==
−
Informative Annex B specifies the list of use cases of an OID registry/repository and an Object Identifier Resolution System (ORS) for e-health related OIDs based on RESTful Web Services.
 
  
−
==Use Cases==
+
[[Datei:Oid-Reference.jpg | 300px]]
−
A list of OID Registry Use Cases has been defined in order to drive metadata model requirements, and functional requirements for Registry interoperability.
 
  
−
===U1: OID Creation where the registry owner is the RA===
+
This class provides a link to
−
* Creation of a new OID in the standard ontological structure
+
* other data sources, code tables, value sets, descriptions etc; typically this is a URL and always points to an object with different semantics than the OID itself.
−
* Creation of a new OID in a sub-structure
+
* other OIDs (within or outside this OID registry) in order to be able to express that an OID has been superseded/replaced or that there is a preferred OID.
  
−
===U2: OID Registration===
+
===Attributes===
−
* Registration where the registry owner created the OID
+
{|class="hl7table"
−
* Registration of an OID created elsewhere
+
! Attribute !! Description !! DT !! Card !! Conf || Length
 +
|-
 +
| ref || reference URI || URI || 1..1 || mandatory || -
 +
|-
 +
| type || type of reference || CS || 1..1 || mandatory || -
 +
|-
 +
| lastVisitedDate || date URI last visited || TS || 0..1 || optional || -
 +
|-
 +
|}
  
−
===U3: OID Withdrawal/Replacement===
+
====ref====
−
* Withdraw an OID created in error with no replacement
+
The referenced URI.
−
* Withdraw an OID created in error with specified replacement
 
−
* Withdraw an OID registered in error with no replacement
 
−
* Withdraw an OID registered in error with specified replacement
 
−
* Withdraw an OID that is found to be a duplicate, with original specified
 
  
−
===U4: OID Metadata Update/Editing===
+
====type====
−
* Permissions model
+
The nature of the reference is coded in the ''type'' attribute, for vocabulary see [[#ReferenceType|ReferenceType]].
−
* Distributed effort model
 
−
* Proxies for Editors
 
  
−
===U5: OID Information Publication===
+
====lastVisitedDate====
−
* Web presence
+
Specifies the date the UIR was last visited.
−
* Internet-accessible API (Web service presence)
 
−
* Full registry output to machine-readable form
 
−
* Full registry output to human-readable form
 
−
* Partial registry output to machine-readable form
 
−
* Partial registry output to human-readable form
 
  
−
===U6: OID Information Request===
+
==AdditionalProperty==
−
* Search for the OID of an object
 
−
* Search for the object identified by an OID
 
−
* Search for a list of kinds of OIDs
 
−
* Search for a list of OID based on various sub-criteria, with and without wildcards
 
−
** Those registered by a particular entity
 
−
** Those associated with a type of information object
 
−
** Those associated with implementation guides
 
−
** Those registered during some time period
 
−
** etc.
 
  
−
== RESTful Web Servcies for an Object Identifier Resolution System ==
+
[[Datei:Oid-AdditionalProperty.jpg | 300px]]
  
−
'''Representational state transfer''' ('''REST''') is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term ''representational state transfer'' was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation.
+
This class reflects additional properties of an OID that might be used to fit business rules that cannot (or should not) be standardized. This includes:
 +
* additional categories
 +
* additional status information
 +
* tags, simple text
 +
* coded properties
  
−
A RESTful web service is implemented using HTTP and the principles of REST. It is a collection of resources, with four defined aspects:
+
It is made of  
−
* the base URI for the web service, such as <syntaxhighlight lang="xml">http://oid.server.org/</syntaxhighlight>
+
* attribute, describing the type of the additional property
−
* the Internet media type of the data supported by the web service, in this case either XML or HTML only.
+
* value, the value of the additional property.
−
* the set of operations supported by the web service using HTTP methods, in this case GET only.
 
  
−
This part of annex B recommends a simple mechanism to be provided in order to retrieve lists of OIDs from a registry, details of a particular OID or an extract of the entire OID registry. Various formats should be supported like HTML and the original XML format.
+
{|class="hl7table"
−
 
+
! Attribute !! Description !! DT !! Card !! Conf || Length
−
The suggested calls should be implemented as RESTful Web Services and their parameters are stated as follows.
+
|-
−
 
+
| attribute || Additional property type || ST.NT || 1..1 || mandatory || -
−
===REST ressource specification ===
 
−
{|class="wikitable"
 
−
! Resource
 
−
! Description GET
 
−
! Parameters
 
 
|-
 
|-
−
| '''OIDIndex'''
+
| value || Additional property value || ST.NT || 1..1 || mandatory || -
−
| retrieves an index of all OIDs in the OID registry in HTML format
 
−
|  
 
−
id (optional): an OID
 
−
 
 
−
language (optional): language
 
−
 
 
−
format (default, fixed): html
 
 
|-
 
|-
−
|
+
|}
−
| colspan=2 |
 
−
<syntaxhighlight lang="email">http://oid.server.org/OIDIndex</syntaxhighlight>
 
  
−
gets an HTML table of all OIDs in the registry with links to the details for each OID
+
==Person==
 +
A class to hold the properties of a person.
  
−
<syntaxhighlight lang="email">http://oid.server.org/OIDIndex?id=1.0.3166.1.2.2</syntaxhighlight>
+
[[Datei:Oid-Person.jpg | 300px]]
  
−
gets an HTML table of OID 1.0.3166.1.2.2 with links to the details for this OID
+
===Attributes===
−
 
+
{|class="hl7table"
−
<syntaxhighlight lang="email">http://oid.server.org/OIDIndex?id=1.0.3166.1.2.2&language=de-DE</syntaxhighlight>
+
! Attribute !! Description !! DT !! Card !! Conf || Length
−
 
+
|-
−
gets an HTML table of OID 1.0.3166.1.2.2 with links to the details for this OID in the German language
+
| name || person's name || EN.PN || 1..* || mandatory || -
 
|-
 
|-
 +
| addr || person's address || AD || 0..* || optional || -
 
|-
 
|-
−
| '''RetrieveOID'''
+
| telecom || person's telecommunication contact || TEL || 0..* || optional || -
−
| retrieves a particular OID in the OID registry
 
−
|
 
−
id (required): an OID
 
−
 
 
−
format (optional): html or xml
 
−
 
 
−
language (optional): language
 
 
|-
 
|-
−
|
+
|}
−
| colspan=2 |
 
−
<syntaxhighlight lang="email">http://oid.server.org/RetrieveOID?id=1.0.3166.1.2.2&format=html</syntaxhighlight>
 
  
−
gets details of OID 1.0.3166.1.2.2 in HTML format
+
==Organization==
 +
A class to hold the properties of an organization.
  
−
<syntaxhighlight lang="email">http://oid.server.org/RetrieveOID?id=1.0.3166.1.2.2&format=html&language=de-DE</syntaxhighlight>
+
[[Datei:Oid-Organization.jpg | 300px]]
  
−
gets details of OID 1.0.3166.1.2.2 in HTML format in the German language
+
===Attributes===
−
 
+
{|class="hl7table"
−
<syntaxhighlight lang="email">http://oid.server.org/RetrieveOID?id=1.0.3166.1.2.2&format=xml</syntaxhighlight>
+
! Attribute !! Description !! DT !! Card !! Conf || Length
−
 
+
|-
−
gets details of OID 1.0.3166.1.2.2 in XML format
+
| id || id (OID) of the organization || ST.OID || 0..* || optional || -
 +
|-
 +
| name || name of the organization || EN.ON || 1..* || mandatory || -
 
|-
 
|-
−
| '''GetOIDRegistry'''
+
| addr || address of the organization || AD || 0..* || optional || -
−
| gets the entire content of the OID registry in XML format
 
−
|
 
−
format (default, fixed): xml
 
 
|-
 
|-
−
|
+
| telecom || telecommunication contact of the organization || TEL || 0..* || optional || -
−
| colspan=2 |
 
−
<syntaxhighlight lang="email">http://oid.server.org/GetOIDRegistry</syntaxhighlight>
 
−
 
 
−
gets the entire content of the OID registry in XML format
 
 
|-
 
|-
 
|}
 
|}
−
 
−
= Annex C (informative): W3C schema for the XML representation=
 
−
Informative Annex C references a W3C schema for the XML representation.
 

Aktuelle Version vom 3. März 2012, 17:13 Uhr

Information model

In order to exchange OID and their metadata between different registries and applications the following additional data items beyond the OID itself need to be taken under consideration (see also [1] [2]):

  • descriptions
  • status information
  • categorization
  • time information
  • comments
  • versions
  • links
  • relationships to other OIDs and external sources
  • registering and responsible organizations
  • associated persons.

An information model with all classes, attributes and their properties aiming on a common understanding of the requirements of an OID registry has been created (Figure 1).

OID Registry Model (Draft)

XML exchange format

Data exchange can be facilitated by a standardized representation of the complete set of information as an XML structure together with the associated checks of underlying constraints and business rules. This XML structure for importing and exporting OID amongst different registries and other healthcare applications is aiming on the availability of reliable information about OIDs.

The following sections summarise and explain classes and their attributes.

Registry

This is the basic information about the OID-Registry hosting the OIDs.

Oid-registry.jpg

Attributes

Attribute Description DT Card Conf Length
validTime validity time interval IVL_TS 1..* mandatory -
scopedOIDs List of scoped root OIDs ST.OID 0..* optional 64
name Official name of the OID registry ST 1..1 mandatory 64
description Description of the OID registry, possible in multiple languages ED 0..* optional -

validTime

This is the validity time interval, i.e. the begin (and end) time when this registry is/was responsible for registering OIDs. This can be a list of intervals.

Conformance.svg rg-vt: A validTime element shall be present and of datatype IVL_TS with at least the low child element populated.

scopedOIDs

List of scoped root OIDs, i.e. the OIDs for which this OID registry is responsible for registration.

Conformance.svg rg-so: If the OID registry is responsible for issuing/registering a root OID, this OID should be listed in scopedOIDs.

name

Official name of the OID registry

description

A description of the OID registry, possible in multiple languages

Conformance.svg rg-ds: If at least one description element is present one of the description's language code shall be English (“en”, “en-US” etc.).

Associations

Association Description Class Card Conf
person Contact person(s) Person 1..* mandatory
hostingOrganization Hosting organization Organization 1..* mandatory
oid List of OIDs Oid 0..* required

Example

<registry>

    <validTime>
        <low value="20100501"/>
    </validTime>

    <scopedOID value="1.2.3.4.5"/>

    <name value="The best OID registry ever"/>
    <description language="en-US" value="This is a test OID registry, although the best"/>

    <person> ... </person>
    <hostingOrganization> ... </hostingOrganization>

    <oid> ... </oid>

</registry>

Oid

This class contains the registered OID and the associated meta data.

Oid-OID.jpg

Attributes

Attribute Description DT Card Conf Length
dotNotation registered OID, dot notation ST.OID 1..1 mandatory 64
asn1Notation ASN.1 notation ST.ASN1 0..1 optional 128
iriNotation IRI notation ST.IRI 0..1 optional 128
symbolicName symbolic name ST.SYMB 0..1 optional 128
category OID category CS 1..1 required -
status OID status CS 1..1 mandatory -
creationDate date of creation TS 0..1 optional -
realm countries CS 0..* optional -
description textual description ED 1..* mandatory -

dotNotation

The OID in dot notation of SNMP or ASN.1/XER.

Example: 

2.16.528

asn1Notation

The OID in ASN.1 notation with (optional) identifiers and numbers.

Examples: 

{joint-iso-itu-t(2) country(16) nl(528)}

{itu-t(0) recommendation(0) a(1)}
Information icon.svg Note that the surrounding curly brackets can be omitted.
Information icon.svg Note that this information is not necessarily entered by a human, this item maybe populated algorithmically.

iriNotation

The OID in Internationalized Resource Identifier[3] (IRI) notation.

Example: 

oid:/Country/528
Information icon.svg Note that this information is not necessarily entered by a human, this item maybe populated algorithmically.

symbolicName / Secondary Arc Identifier

A symbolic short name, unique among the siblings of the arc of the OID.

The ISO rules on Secondary Arc Identifiers, as laid out in Rec. ITU-T | ISO/IEC 9834-1 Procedures for Registration Authorities, section 6.2.2, apply:

  • identifiers of an arc are required to commence with a lowercase letter, and to contain only letters, digits, and hyphens.
  • the last characters shall not be a hyphen
  • there shall be no two consecutive hyphens in the name

Example 

nl

category

The type/category of the OID; enumeration, values see value set OIDcategories.

There are actually two main types of OIDs: leafs (id of an object), and nodes representing an ontological branch.

The types of node OID may be

  • a registration authority (RA) or
  • a structure for the management of OIDs.

The proposal for sub categories of leaf OIDs are

  • identifiers of an instance of an object (for example a person)
  • namespace identifiers (for example code systems, value sets)
Information icon.svg In addition there are properties of OIDs that can reflect other business needs.

These can be

  • tags (simple text)
  • other categorizations of the OID, coded or as text
  • "sub-types" of the OID
For further information see AdditionalProperty.

status

Status of the OID. This is an enumeration, for values see value set OIDstatusCodes

creationDate

The creationDate is used to describe when the OID was first registered. It is not the date when the OID description is submitted to the OID repository. The creationDate, once set, never changes.

realm

In some cases OIDs may apply to a specific county/realm only, e.g. the namespace identifiers for the US Social Security Number (SSN) or the Dutch Citizen Service Number (BSN) or the codes system representing ICD-10 International Classification of Diseases 10th Revision for the use in Germany only (ICD10gm). This can be indicated by realm which is either the code of country or "UV" for universal. For values see code system CountryCodes.

description

This element contains a free text description of the OID ("what is the OID?"). The text typically contains an explanation but also can contain:

  • explicit versioning aspects
  • licensing information
  • Intellectual Property rights information
  • trademarks.

This element is repeatable for each language.

The datatype ED allows for a thumbnail child element. A thumbnail may be populated describing a short description of the OID (sometimes referred to as identifier name).

Example: 

<description language="en-US" value="this is plain text as a long description">
   <thumbnail value="short text"/>
</description>
Information icon.svg Note that data type ED also reflects the aspect of language of the description (language code).
Conformance.svg oi-ds: There SHALL be one description instance with language code English (“en”, “en-US” etc.).

Associations

Association Description Class Card Conf
registrationAuthority Registration Authority RegistrationAuthority 1..1 required
responsibleAuthority Responsible Authority ResponsibleAuthority 1..* required
submittingAuthority Submitting Authority SubmittingAuthority 0..1 optional
additionalProperty Additional Properties AdditionalProperty 0..* optional
historyAnnotation History Annotations HistoryAnnotation 0..* optional
reference References Reference 0..* optional

RegistrationAuthority

Oid-RegistrationAuthority.jpg

This class represents the Registration Authority (RA).

Attributes

Attribute Description DT Card Conf Length
code RA role code CS 1..1 mandatory -

code

The code holds information about the role type of the RA. Valid codes are listed in RoleCodes.

Associations

Association Description Class Card Conf
scopingOrganization Scoping organization Organization 1..1 mandatory
person Contact person(s) Person 0..1 optional

ResponsibleAuthority

This is a class representing the (managing) authority that is responsible for the object that is identified by the OID (not for the OID itself).

Oid-ResponsibleAuthority.jpg

Attributes

Attribute Description DT Card Conf Length
code role code CS 1..1 mandatory -
statusCode status code CS 1..1 mandatory -
validTime validity time IVL_TS 1..* mandatory -

code

The code holds information about the role type of the ResponsibleAuthority. Valid codes are listed in RoleCodes.

statusCode

The statusCode holds information about the status of the ResponsibleAuthority. Valid codes are listed in RoleStatus.

validTime

This is an interval of time, representing the period when the ResponsibleAuthority is/was responsible for the object that is identified by the OID. If the ResponsibleAuthority is still responsible, only validTime.low is populated.

Associations

Association Description Class Card Conf
scopingOrganization Scoping organization Organization 1..1 mandatory
person Contact person(s) Person 0..1 optional

SubmittingAuthority

This is a class representing the submitting authority that originally asked for a new OID.

Oid-SubmittingAuthority.jpg

(Please note: to avoid redundancy, the classes Organization and Peron are shown with attributes here, at all other places only a "shadow" class of these two classes is shown)

Attributes

Attribute Description DT Card Conf Length
code role code CS 1..1 mandatory -
applicationDate date of application TS 0..1 optional -

code

The code holds information about the role type of the submitting authority. Valid codes are listed in RoleCodes.

applicationDate

Date of application (submission or certified submission) of the requested OID.

Associations

Association Description Class Card Conf
scopingOrganization Scoping organization Organization 1..1 mandatory
person Contact person(s) Person 1..1 mandatory

HistoryAnnotation

This class reflects historical annotations of the OID and records the changes of any data over time.

Oid-HistoryAnnotation.jpg

Attributes

Attribute Description Datatype Cardinality Conformance Recommended Length
annotationDate date annotation was created TS 0..1 required -
text annotation ED 1..1 mandatory -
Information icon.svg Note that data type ED also reflects the aspect of language of the description (language code).

Reference

Oid-Reference.jpg

This class provides a link to

  • other data sources, code tables, value sets, descriptions etc; typically this is a URL and always points to an object with different semantics than the OID itself.
  • other OIDs (within or outside this OID registry) in order to be able to express that an OID has been superseded/replaced or that there is a preferred OID.

Attributes

Attribute Description DT Card Conf Length
ref reference URI URI 1..1 mandatory -
type type of reference CS 1..1 mandatory -
lastVisitedDate date URI last visited TS 0..1 optional -

ref

The referenced URI.

type

The nature of the reference is coded in the type attribute, for vocabulary see ReferenceType.

lastVisitedDate

Specifies the date the UIR was last visited.

AdditionalProperty

Oid-AdditionalProperty.jpg

This class reflects additional properties of an OID that might be used to fit business rules that cannot (or should not) be standardized. This includes:

  • additional categories
  • additional status information
  • tags, simple text
  • coded properties

It is made of

  • attribute, describing the type of the additional property
  • value, the value of the additional property.
Attribute Description DT Card Conf Length
attribute Additional property type ST.NT 1..1 mandatory -
value Additional property value ST.NT 1..1 mandatory -

Person

A class to hold the properties of a person.

Oid-Person.jpg

Attributes

Attribute Description DT Card Conf Length
name person's name EN.PN 1..* mandatory -
addr person's address AD 0..* optional -
telecom person's telecommunication contact TEL 0..* optional -

Organization

A class to hold the properties of an organization.

Oid-Organization.jpg

Attributes

Attribute Description DT Card Conf Length
id id (OID) of the organization ST.OID 0..* optional -
name name of the organization EN.ON 1..* mandatory -
addr address of the organization AD 0..* optional -
telecom telecommunication contact of the organization TEL 0..* optional -
  1. ↑ Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1: 2008, Information Technology – Abstract Syntax Notation One (ASN.1), Specification of Basic Notation, 1997
  2. ↑ Recommendation ITU-T X.667 | ISO/IEC 9834-8: Information technology – Open Systems Interconnection – Procedures for the operation of OSI Registration Authorities: Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 object identifier components
  3. ↑ http://www.oid-info.com/faq.htm#iri
Abgerufen von „https://wiki.hl7.de/index.php?title=ISO13582-part2&oldid=3757“