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

Structure & planning Care Provision Domain

From HL7Wiki
Revision as of 13:46, 31 January 2012 by William Goossen (talk | contribs) (Created page with "The Care Provision materials consist of three levels of message constructs. All adhere to the Care Provision D-MIM specifications. This means that all constructs are directly der...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The Care Provision materials consist of three levels of message constructs. All adhere to the Care Provision D-MIM specifications. This means that all constructs are directly derivable via constraining from the D-MIM.

The first layer are the R-MIMs for messages. The messages include those for referral and acceptance (Referral Topic), Care Record (Care Record Topic) and Care Record Query (Query Topic).

The second layer consists of R-MIMs that are constraints on the Clinical Statement Pattern. These specify additional structures in the different messages. Examples of such level 2 structures include the Statement Collector, the Concern Tracker, the Care Plan structure, and others. All of these have, or will get a separate Topic under Care Provision. These structures are reusable in other HL7 domains that deploy the Clinical Statement.

The third layer consists of R-MIMs that are also constraints to the Clinical Statement, but are concrete clinical data elements. These structures can be general, such as the Assessment Scale Topic and the Vital Signs Topic. Alternatively, these can be concrete implementation specifications for clinical content. This level will normally not be specified in R-MIM format, but as specific Detailed Clinical Models and the clinical statement template representation for it.

Care Provision and Clinical Statement in particular can hold millions of variations of clinical data elements.