This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Endnotes"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "<div class="subSection"> <div class="header"> === Endnotes === </div> </div> # [[[source]]] SNOMED Clinical Terms and SNOMED CT are registered trademarks of the Internati...")
 
 
Line 24: Line 24:
 
|[[View Revision Marks]][[Hide Revision Marks]]
 
|[[View Revision Marks]][[Hide Revision Marks]]
 
|
 
|
|}  
+
|}
</div>
 
</div>
 

Latest revision as of 19:55, 18 July 2012

Endnotes

  1. [[[source]]] SNOMED Clinical Terms and SNOMED CT are registered trademarks of the International Healthcare Terminology Standards Development Organisation (IHTSDO). Prior to April 2007 the IP rights to SNOMED CT were owned by the College of American Pathologists (CAP) and for this reason some materials referenced by this document may still be badged with CAP Copyright. However, as far as the authors of this document are aware, ownership of all these materials has been transferred to the IHTSDO.
  2. [[[source]]] The Clinical Statement CMET is a proposed replacement for the Supporting Clinical Information CMET which is based on the Clinical Statement pattern.
  3. [[[source]]] This implementation guide does not recommend a particular model of meaning. See Normal Forms for more details.
  4. [[[source]]] The requirement for moodCode to be present may be met either by explicit inclusion or by a default specified in an HL7 model.
  5. [[[source]]] http://aurora.rg.iupui.edu/UCUM
  6. [[[source]]] Translation to from SNOMED CT to UCUM representations is supported by a mapping table developed by the UK NHS. It is anticipated that this will be maintained in future as part of SNOMED CT.
  7. [[[source]]] A third time attribute, Act.availabilityTime is related to the system availability of the information rather than the action itself.
  8. [[[source]]] These patterns assume the use of SNOMED CT. While other code systems (such as LOINC or ICD9) may be required or even preferable in some situations, these situations are outside the scope of this guide.
  9. [[[source]]] The Organizer class can be used to communicate batteries. Therefore measurement procedures representing batteries can be used.
  10. [[[source]]] The organizer may have contextual components (e.g. participants or act relationships) which propagate to nested observations.
  11. [[[source]]] SNOMED distributes an allergen subset, drawn from Substance and Product hierarchies.
  12. [[[source]]] Note that it may not be possible in this context to differentiate an allergic reaction from the condition of being allergic, since the data entry field only accepts substance and product values.
  13. [[[source]]] Note that the naming in SNOMED CT"s documentation/data has recently been updated - "context-dependent categories" in the data have been renamed "situation with explicit context". In this guide these concepts are referred to as [ <<243796009 | situation with explicit context ] or the more specific [ <<413350009 | finding with explicit context ] and [ <<129125009 | procedure with explicit context ].
View Revision MarksHide Revision Marks