Sep 18, 2018: OMG Field Guide Working Group
1. Need for Modeling the Use and Change of Information in the Context of Clinical Workflow Information is a key resource for clinical care and capturing its usage gives a more complete picture of clinical workflows
- Clinical care depends on availability of information resources
- Need to know information flow- where information needed by tasks comes from, where it goes if it gets changed
- Information models can tell us the what-when-where for just-in-time HIT requirements
- Important aspect of interoperability
- Workflow is an effective heuristic to elicit knowledge about information use
2. Special Needs for Modeling Clinical Information
- Information systems are carried out not only by computers but also by the activities of clinical personnel who use and change information in either cognitive activities or events that take place the physical world
- Information flow about a patient is not the same as the flow of care of that patient. They often follow parallel flows.
- An information model must reflect the context-sensitive roles for when information is the object of work verses when it is a resource needed by other activities
3. Best Modeling Practice
- Use workflow as heuristic to elicit information usage. Much easier for subject matter experts to recognize information requirements in context of workflow model then to just try to remember them.
- Capture the what-where-when
- Granularity of information model is decision-actionable
- Give references to authoritative sources for structured data the comprises the information
- Granularity of workflow should expose use and change of information
- Need examples
4. Relate Back to Rest of Field Guide
- Data objects
- Data sources
- Data dictionary
- Work flow activities
- . . .
Issues to incorporate to expand Best Information Modeling Practice
- Authoritative sources and citations
- An accurate information model must include the contents of a variety of media types that serve as information resources
- Mapping Information Modeling Back to Rest of the Guide
- Data Sources of all media are key types of information resources needed by workflow activities
- Data Objects, such as diagnoses, treatment plans, etc., get created as cognitive clinical work and can be either tangible or abstract
- Need Examples
Robert-4 layers of modeling (information or data)
- Requirement level: e.g., age, gender,
- Using the modeling tool: beginning structure of information
- More formal: platform independent, industry accepted, more structure, semantic binding, (controlled vocabulary?)
- Platform dependent model: information model for the enterprise- consuming side (where is lab data, where is radiology data)
Joanne- 2 questions
- Data vs information
- Architectural, layered approach- case, processes, decisions, information, data
Robert-
- Process knowledge
- Decision knowledge
- Situational knowledge
- 4th leg of a table bound by semantics
Robert-
We are trying to model concepts
What is right level of granularity?
BPMN, DMN, CMN
Joanne-
Table top is supported by case, processes, decisions, information
Robert-
Producer, consumer, . . viewpoints for each type of stakeholder (IEEE 471?)
another part of the table?
Sean-
MITRE Simple on top of sharable core
Generate FHIR profiles
Mark Kramer (sp?)
Robert-
We should make an explicit decision- is “Information modeling” a coverage gap
- all agreed
Steve-
Currently have “data dictionary”
Situational model
Used by other 3 pillars
Common to other models
Need 4th section to pull that out
Keith-
Practice guidance
Workflow model granularity should expose use/change of situational data Meeting Discussion Notes 9-18-2018
Progress update at OMG tech agenda (Robert)