Difference between revisions of "Naming Conventions"
Jump to navigation
Jump to search
(Created page with " Excerpt and paraphrase from HL7 Governance and Operations Manual (GOM) 12.02.02 01 Constructing Other HL7 Ballot and Protocol Specification Names and HL7 Essential Requireme...") |
|||
| Line 4: | Line 4: | ||
The full document name shall begin with an organizational identifier followed by family name, product type and release number with a subfamily name, product type and release number, if applicable, then the product name and release number followed by the realm designation, if applicable, and the ballot type and number. In the case of a reaffirmation ballot the term “Reaffirmation of” shall precede the family name. | The full document name shall begin with an organizational identifier followed by family name, product type and release number with a subfamily name, product type and release number, if applicable, then the product name and release number followed by the realm designation, if applicable, and the ballot type and number. In the case of a reaffirmation ballot the term “Reaffirmation of” shall precede the family name. | ||
| − | The naming construct is described below using a notation of {required} or [optional] with literals expressed in | + | The naming construct is described below using a notation of {required} or [optional] with literals expressed in <b><i>bold italics </b></i>. |
{|width=100% cellspacing=0 cellpadding=2 border="1" | {|width=100% cellspacing=0 cellpadding=2 border="1" | ||
| − | |- | + | |- |
| − | | colspan=2 valign="middle" |Ballot Document Name and Information | + | | colspan=2 valign="middle" |<b>Ballot Document Name and Information |
|- | |- | ||
| − | | | + | |colspan=1|Structure |
| + | |Comments</b> | ||
|- | |- | ||
|{Organization Identifier}||Organization Identifier shall be: | |{Organization Identifier}||Organization Identifier shall be: | ||
| − | |||
*HL7 indicating a Health Level Seven International document | *HL7 indicating a Health Level Seven International document | ||
| − | *HL7/Other [such as NCPDP] indicating an HL7 document published in conjunction with another organization | + | *HL7/Other [such as NCPDP] indicating an HL7 document published in conjunction with another organization |
|- | |- | ||
| − | | | + | |<b><i>[Reaffirmation of] </b></i>||""| |
|- | |- | ||
| − | | {||One or more of the following 3 line items required | | + | | {||One or more of the following 3 line items required |
| − | [Family Name] [Product Type] [<b><i>Release</ | + | |- |
| + | | [Family Name] [Product Type] [<b><i>Release</b></i> [Release Number]] : | ||
| + | |The standard family names are | ||
*Version 2.x (V2.x); | *Version 2.x (V2.x); | ||
*Version 3 (V3) [note: V3 itself does not have a release number, although each of its products typically will]; | *Version 3 (V3) [note: V3 itself does not have a release number, although each of its products typically will]; | ||
| Line 30: | Line 32: | ||
*Fast Healthcare Interoperability Resources (FHIR® is the preferred designation); | *Fast Healthcare Interoperability Resources (FHIR® is the preferred designation); | ||
*where a document includes reference to two or more family names it may be identified as a Cross Paradigm Specification. | *where a document includes reference to two or more family names it may be identified as a Cross Paradigm Specification. | ||
| − | + | <br/> | |
| − | |||
Product types are defined as | Product types are defined as | ||
*Specification or Standard; | *Specification or Standard; | ||
| Line 43: | Line 44: | ||
The TSC may, at their discretion, declare additional product types. | The TSC may, at their discretion, declare additional product types. | ||
|- | |- | ||
| − | | [Sub-family Name] [Product Type] [<b><i>Release</i></b> [Release Number]] ;| | + | |align="right"| [Sub-family Name] [Product Type] [<b><i>Release</i></b> [Release Number]] ; |
| + | |align="left"|Subfamily names are specific to a given family and are not further defined in this document. | ||
|- | |- | ||
| − | | [Product Name], [<b><i>Release </ | + | |align="right"|[Product Name], [<b><i>Release</b></i> [Release Number]]||""| |
|- | |- | ||
| } ||""| | | } ||""| | ||
Revision as of 23:05, 26 January 2016
Excerpt and paraphrase from HL7 Governance and Operations Manual (GOM) 12.02.02 01 Constructing Other HL7 Ballot and Protocol Specification Names and HL7 Essential Requirements (HL7 ER)
The full document name shall begin with an organizational identifier followed by family name, product type and release number with a subfamily name, product type and release number, if applicable, then the product name and release number followed by the realm designation, if applicable, and the ballot type and number. In the case of a reaffirmation ballot the term “Reaffirmation of” shall precede the family name.
The naming construct is described below using a notation of {required} or [optional] with literals expressed in bold italics .
| Ballot Document Name and Information | |
| Structure | Comments |
| {Organization Identifier} | Organization Identifier shall be:
|
| [Reaffirmation of] | |
| { | One or more of the following 3 line items required |
| [Family Name] [Product Type] [Release [Release Number]] : | The standard family names are
The TSC may, at their discretion, declare additional product types. |
| [Sub-family Name] [Product Type] [Release [Release Number]] ; | Subfamily names are specific to a given family and are not further defined in this document. |
| [Product Name], [Release [Release Number]] | |
| } | |
| [ - Realm Designation] | HL7 Version 3 Standard > Vocabulary > HL7 Value Sets > HL7 Realm |
