loading...| Preferred Name | ObservationMethod | |
| Synonyms |
|
|
| Definitions |
<p>A code that provides additional detail about the means or technique used to ascertain the observation.</p><i>Examples:</i>Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.<i>Constraints:</i>In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.<p>If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code.</p><i>Discussion:</i>In all observations the method is already partially specified by simply knowing the kind of observation (observation definition, Act.code) and this implicit information about the method does not need to be specified in Observation.methodCode. Particularly, most LOINC codes are defined for specific methods as long as the method makes a practical difference in interpretation. For example, the difference between susceptibility studies using the "minimal inhibitory concentration" (MIC) or the "agar diffusion method" (Kirby-Baur) are specifically assigned to different LOINC codes. The methodCode therefore is only an additional qualifier to specify what may not be known already from the Act.code.<p>Also, some variances in methods may be tied to the particular device used. The methodCode should not be used to identify the specific device or test-kit material used in the observation. Such information about devices or test-kits should be associated with the observation as "device" participations.</p> <p>A code that provides additional detail about the means or technique used to ascertain the observation.</p><i>Examples:</i>Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.<i>OpenIssue:</i>Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved. <p>A code that provides additional detail about the means or technique used to ascertain the observation.</p><i>Examples:</i>Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.<i>Constraints:</i>In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.<p>If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code.</p> |
|
| ID |
http://purl.bioontology.org/ontology/HL7/C1553848 |
|
| Context binding of | ||
| cui |
C1553848 |
|
| definition |
A code that provides additional detail about the means or technique used to ascertain the observation. Examples:Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.Constraints:In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code. Discussion:In all observations the method is already partially specified by simply knowing the kind of observation (observation definition, Act.code) and this implicit information about the method does not need to be specified in Observation.methodCode. Particularly, most LOINC codes are defined for specific methods as long as the method makes a practical difference in interpretation. For example, the difference between susceptibility studies using the "minimal inhibitory concentration" (MIC) or the "agar diffusion method" (Kirby-Baur) are specifically assigned to different LOINC codes. The methodCode therefore is only an additional qualifier to specify what may not be known already from the Act.code.Also, some variances in methods may be tied to the particular device used. The methodCode should not be used to identify the specific device or test-kit material used in the observation. Such information about devices or test-kits should be associated with the observation as "device" participations. A code that provides additional detail about the means or technique used to ascertain the observation. Examples:Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.OpenIssue:Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved.A code that provides additional detail about the means or technique used to ascertain the observation. Examples:Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.Constraints:In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code. |
|
| Has context binding | ||
| Has supported concept property |
http://purl.bioontology.org/ontology/HL7/C1553880 |
|
| Has supported concept relationship | ||
| HL7 code status |
active |
|
| HL7 history item |
UPDATE: Migrated to the UTG maintenance environment and publishing tooling. UPDATE: Migrated to the UTG maintenance environment and publishing tooling. |
|
| HL7 internal Id |
19929 |
|
| HL7 OID |
2.16.840.1.113883.5.84 |
|
| HL7 release date |
2019-03-20 |
|
| HL7 version date |
2014-03-26 |
|
| HL7AI |
true |
|
| HL7CC |
true |
|
| HL7MI |
true |
|
| HL7PL |
true |
|
| HL7SCS |
2.16.840.1.113883.5.84 |
|
| HL7SL |
en |
|
| HL7VC | ||
| notation |
C1553848 |
|
| prefLabel |
ObservationMethod |
|
| tui |
T170 |
|
| subClassOf |
| Delete | Mapping To | Ontology | Source |
|---|---|---|---|
| http://rdf.geospecies.org/ont/geospecies#ObservationMethod | GEOSPECIES | LOOM |