universal domain common observation 20080808
TRANSCRIPT
- 1. An Seong Hyun06/05/09
2.
- 1. About Storyboard, Application Role, Trigger Event
- 2. Chapter 3.Common Observation Topic
- Storyboards Application Roles Trigger Events Refined Message Information Models(RMIM) Hierarchical Message Descriptions(HMD) Interactions
- 3. Chapter 4. CMETs Defined by this Domain
06/05/09 3.
- Storyboard
- - Story
- - .
- - .
- - application role Interaction Diagram
- -
06/05/09 4.
- Application Role
- - a set of communication responsibilities
- - describe system components or sub-components that send and/or receiveinteractions.
- ( HL7 Interaction ,application role sending Application role receiving
- .interaction sending receiving Application role .)
- Trigger Event
- system component
- name, Artifact ID, description, Type .
06/05/09 5.
- covers all interactions related to recording simple measured clinical
- observations
-
- Recording clinical and coded observations for a patient ( )
-
- Retrieving clinical and coded observations recorded against a patient( )
- Basic Observation :height, weight, blood-pressure, temperature
- LAB Observation : using the Appropriate messages
- Coded observations : APGAR score, symptom, blood type, smoker
06/05/09 6.
- 3.1.1Heart Murmur Assessment(POOB_ST100001UV)
- -collected during a heart murmur assessment.
- Precondition
- Dr. Patricia Primary is doing a cardiac assessment on Patient Everyman. Mr. Everyman has come to emergency room
- following a syncopal episode and chest pain while running to catch his bus.The information regarding the syncopal
- episode and chest pain were entered in the EDIS (emergency department information system).
- Activities
- On examination Mr. E has a harsh grade III mid-systolic murmur best appreciated lateral to the left costal margin towards
- the laterally displaced PMI. There is a faint diastolic murmur intermittently heard over the right 2nd ICS at the right sternal
- border. The systolic murmur diminishes with Valsalva and squatting.Upon standing the murmur becomes
- pronounced. Mr. Everyman's assessment findings are entered in the EDIS, and an Echocardiogram( )is
- ordered.
- Post-condition
- Mr. Everyman's assessment findings and an Echocardiogram order are now present in the EDIS.
06/05/09 7.
- 3.2.1 Observation Entry System(POOB_AR000001UV)
- Description :Structured Name: Common Observation Event Placer
- This is a system that iscapable of recording informationabout simple common observations such as height, weight, blood-pressure.
- 3.2.2 Observation Querying System(POOB_AR000003UV)
- Description: Structured Name: Common Observation Event Information Solicitor
- This is a system thatretrieves information a bout about simple common observations such as height, weight, blood-pressure.
- 3.2.3 Observation EHR Repository(POOB_AR000002UV)
- Description : Structured Name: Common Observation Event Manager
- This is a system thatstores and exposes measurement informationabout simple common observations such as height, weight, blood-pressure.
06/05/09 8.
- 3.3.1 Request to record clinical observation(POOB_TE000001UV)
- Description:Structured Name: Common Observation Event Complete Request
- Type:User request
- A user attempts to record a clinical observation in a subject's record.
- 3.3.2 Decision not to record clinical observation(POOB_TE000002UV)
- Description :Structured Name: Common Observation Event Complete Rejection
- Type:Interaction based
- A request to record a clinical observation in a subject's record has been refused.
- 3.3.3 Observation recorded in subject record(POOB_TE000003UV)
- Description :Structured Name : Common Observation Event Complete
- Type :State-transition based
- A clinical observation has been recorded in a subject's record.
- 3.3.4 Subject clinical observation info. Requested(POOB_TE000007UV)
- Description :Structured Name : Common Observation Event Query
- Type : User request
- A user or system requires information about clinical observations for a subject.
- 3.3.5 Request for subject. observation info. Received(POOB_TE000008UV)
- Description :Structured Name : Common Observation Event Query Response
- Type :Interaction based
- An application responds to a request for information about clinical observations for a subject.
06/05/09 9.
- 3.4.1 Common Observation (POOB_RM410000UV)
- Focal Act(EventChoice)
- ResultGroup : the grouping and reporting of multiple observations in one message.
- - CommonObservationEvent : a single point-in-time observation
- Observation. methodCode
- :code that provides additional detail about the means or technique used to ascertain the observation.
- Examples :Blood pressure measurement method
- arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position
- Contraints :Method Act.code methodCode
- . methodCode , .
06/05/09 10.
- Observation .value
- :Information that is assigned or determined by the observation action.
- The appropriate data type of the Observation.value varies with the kind of Observation
-
- Quantitative measurement - numeric values
-
- Titer( )- use two integer numbers ex) 1: 64, 1:128
-
- Index values - use a PQ with a dimensionless unit (e.g., 1 or %).
-
- Ranges - ex)