Difference between revisions of "2.16.840.1.113883.3.1937.777.13.10.56"
(Automatic ADBot page (9936d5ec43dae00380705459058aa61863e73a53)) |
(Automatic ADBot page (9936d5ec43dae00380705459058aa61863e73a53)) |
||
| Line 5: | Line 5: | ||
=Template ''IPSEntryProblemStatusObservation''= | =Template ''IPSEntryProblemStatusObservation''= | ||
| − | <p>(CCD) Any problem or allergy observation may reference a problem status observation. This structure is included in the target observation using the <entryRelationship> element defined in the CDA Schema. The clinical status observation records information about the current status of the problem or allergy, for example, whether it is active, in remission, | + | <p> |
| − | + | (CCD) Any problem or allergy observation may reference a problem status observation. This structure is included in the target observation using the <entryRelationship> element defined in the CDA Schema. The clinical status observation records information about the current status of the problem or allergy, for example, whether it is active, in remission, resolved, et | |
| − | + | cetera. The example below shows the recording of clinical status of a condition or allergy, and is used as the context for the following sections. | |
| − | + | This CCD models a problem status observation as a separate observation from the problem, allergy or medication observation. While this model is different from work presently underway by various organizations (i.e., SNOMED, HL7, TermInfo), it is not wholly incompatible with that work. In that work, qualifiers may be used to identify problem status in the coded condition | |
| + | observation, and a separate clinical status observation is no longer necessary. The use of qualifiers in the problem observation is not precluded by this specification or by CCD. However, to support semantic interoperability between EMR systems using different vocabularies, this specification does require that problem status information also be provided in a separate | ||
| + | observation. This ensures that all EMR systems have equal access to the information, regardless of the vocabularies they support. | ||
| + | </p> | ||
==Actual version== | ==Actual version== | ||
{{:{{BASEPAGENAME}}/dynamic}} | {{:{{BASEPAGENAME}}/dynamic}} | ||
| Line 14: | Line 17: | ||
==List of all versions of this template== | ==List of all versions of this template== | ||
*[[2.16.840.1.113883.3.1937.777.13.10.56/static-2017-05-02T183645|2017-05-02 18:36:45 (Cancelled)]] | *[[2.16.840.1.113883.3.1937.777.13.10.56/static-2017-05-02T183645|2017-05-02 18:36:45 (Cancelled)]] | ||
| − | <!-- | + | <!--b9088df8fc0677e7d2467d255606bd900600829b--> |
Latest revision as of 05:11, 13 June 2024
| Comments on this page |
|---|
Template IPSEntryProblemStatusObservation
(CCD) Any problem or allergy observation may reference a problem status observation. This structure is included in the target observation using the <entryRelationship> element defined in the CDA Schema. The clinical status observation records information about the current status of the problem or allergy, for example, whether it is active, in remission, resolved, et cetera. The example below shows the recording of clinical status of a condition or allergy, and is used as the context for the following sections. This CCD models a problem status observation as a separate observation from the problem, allergy or medication observation. While this model is different from work presently underway by various organizations (i.e., SNOMED, HL7, TermInfo), it is not wholly incompatible with that work. In that work, qualifiers may be used to identify problem status in the coded condition observation, and a separate clinical status observation is no longer necessary. The use of qualifiers in the problem observation is not precluded by this specification or by CCD. However, to support semantic interoperability between EMR systems using different vocabularies, this specification does require that problem status information also be provided in a separate observation. This ensures that all EMR systems have equal access to the information, regardless of the vocabularies they support.
Actual version
Keine Versionen mit Status draft, active, review oder pending.
