Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Abstract categoryConcrete
Category
DescriptionProposed CIMI Modelling pattern
Lab result categoriesLab Analyte

Common features:

  • logically atomic panel items 
  • all items have the same specific context structure
while logically atomic, due to the need of specific context items, a container like a CLUSTER or higher is required; the key datum is an ELEMENT containing a DATA_VALUE.

It may be possible to model every single Lab analyte using a single ELEMENT archetype with LOINC coding- Stan doesn't do this however.
 Lab Panel

Common features:

  • one or more atomic panel items; situation context is same for all items in panel
ENTRY with slot for Lab Analyte CLUSTERs. One Lab panel archetype should be usable for most lab panels. Possibly a couple of other variants for special structures.
 Lab ReportReport containing one or more panel result(s); carries audit + attestation, and other
specific context like order ids, lab comments etc
COMPOSITION containing one or more Lab Panels, plus top-level situation context
    
QuestionnairesQuestionnaire item

Common features:

  • logically atomic question / answer pair, probably with other meta-data
  • 'values' represented structurally cannot typically be treated as having the same clinical meaning as similarly/same named data points in normal clinical Entries - they are instead usually classifiers.
CLUSTER containing ELEMENTs that model the natural language form of the question (via terms), the meaning of the question, and the possible result values.
 Questionnaire group / listSet of Questionnaire items making up the logical questionnaire (equivalent to a 'panel' for questionnaires)ENTRY containing one or more Questionnaire Item CLUSTERs
 Questionnaire formThe full thing, filled out, attested, committed to EHR; carries audit + attestationCOMPOSITION containing (usually?) one Questionnaire group
    
General clinical
information
structures
Clinical entry structure

Common features:

  • 'molecular' information structure that is different for each content type,
  • and usually has the same situation context for all items in a given recording
  • may include linking to previously existing Entries, e.g. BMI linking to existing height and weight
  • may include derived fields e.g. BMI, Apgar total etc
ENTRY containing free structure of CLUSTERs and ELEMENTs, making up the overall datum + specific context structure
 Clinical situation recordingcommitted report, document, or other artefact containing one or more Clinical
entry structures, potentially with added heading structure; carries audit + attestation
COMPOSITION containing one or more ENTRYs
OrdersOrder item

Common features:

  • complex timing / condition item(s)
  • possibly conditional branched structures (since orders are about the future)
  • description of the intervention / drug
ENTRY
 Order setA set of order items + other meta-data (TBC) 
 PrescriptionArguably a special kind of grouping of order items 
Actions TBC 
etc   

...