Page History
...
Implementations of clinical messaging typically constrain the range of values that can be applied to particular fields several reasons for this are listed in the following table.
| Caption label | ||||
|---|---|---|---|---|
| ||||
Reasons for constraining the content of fields in clinical messages |
| Reason | Example |
|---|---|
| To ensure that the information encoded is meaningful as a value for the specified field. | A field that is intended to describe the nature of investigation may contain a code that means "Serum glucose measurement" but should not contain a code that means "Hypoglycemia." |
| To ensure that receiving application is able to process the message. | A locally added code value may be valid in a particular application but should not be used if the receiving application needs to retrieve, process or analyze the coded part of the message. |
| To ensure adequate detail and specificity. | A field used to report an operative procedure could contain a code for "Abdominal procedure." However, this would not be adequate to meet the business purpose served by a message. |
| To avoid unnecessary detail or diversity. | A biochemical investigation could be reported using a code that represents various detailed aspects of the method used to perform the investigation. Such details may be unnecessary to a clinician and may complicate the analysis, charting and graphing of a series of results reported at different levels of detail. |
...
Overview
Content Tools
Apps