Difference between revisions of "Requirements-CMETs"

From HL7Wiki
Jump to navigation Jump to search
(New page: {{V3 Methodology Requirements}} Business names allow for one or more domain-specific and/or language-specific labels to be assigned to an element in additional to its formal HL7 English RI...)
 
Line 1: Line 1:
 
{{V3 Methodology Requirements}}
 
{{V3 Methodology Requirements}}
Business names allow for one or more domain-specific and/or language-specific labels to be assigned to an element in additional to its formal HL7 English RIM-speak name.  E.g. Even in English, the HL7 term "SubstanceAdministrationRequest" might be known as "Prescription", "Med Order" or "Script" depending on the jurisdiction and context.
 
  
To ensure interoperability, it's essential that the names of common elements not vary across languages and common business terms. However, being able to include a language-specific or common business term as a supplement aids in understanding.
+
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''  
 +
| Message type fragment that can be used by other message type fragments (static models). Expresses a common, useful, reuseable concepts expressed small model pieces (chunks)
 +
|-
 +
| ''Rationale''
 +
| Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
 +
|-
 +
| "Methodology"
 +
| HDF methodology, metadata
 +
|
 +
|-
 +
| ''MIF''
 +
|
 +
|-
 +
|}
  
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
| Business labels must identify the language and context (or contexts) they apply to
+
| Message type fragment that can be used by other message type fragments (static models). Expresses a common, useful, reuseable concepts expressed  small model pieces (chunks)
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
| In some cases multiple business names may be present on a particular element.  When publishing an artifact for a particular language group or business context, you want to use the labels most appropriate for that language or context.
+
| Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
 +
|-
 +
| "Methodology"
 +
| HDF methodology, metadata
 +
|
 
|-
 
|-
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-core-base.xsd/BusinessName/realmNamespace/value
 
* mif-core-base.xsd/BusinessName/@lang
 
 
|-
 
|-
| ''MIF Issue''  
+
|}
 +
 
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| May be referenced by both producing and other committees
 +
|-
 +
| ''Rationale''
 +
| Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
 +
|-
 +
| "Methodology"
 +
| HDF methodology, metadata
 
|
 
|
{{MIF Not Used}}
+
|-
mif-vocabulary-model.xsd/ConceptDomain: We don't presently maintain business names at the UV level, though at least one realm assigns them before publishing
+
| ''MIF''
 +
|
 +
|-
 
|}
 
|}

Revision as of 17:27, 17 February 2010

Requirement Message type fragment that can be used by other message type fragments (static models). Expresses a common, useful, reuseable concepts expressed small model pieces (chunks)
Rationale Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
"Methodology" HDF methodology, metadata
MIF
Requirement Message type fragment that can be used by other message type fragments (static models). Expresses a common, useful, reuseable concepts expressed small model pieces (chunks)
Rationale Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
"Methodology" HDF methodology, metadata
MIF
Requirement May be referenced by both producing and other committees
Rationale Promotes Re-use by modelers; Common model enables domain knowledge to be used. Uniformly represents a concept for use by all interested committees
"Methodology" HDF methodology, metadata
MIF