PCD RTM 2008-12-03 WebEx
IHE PCD Rosetta Terminology Mapping (RTM) Ventilator Task Group regular discussion meeting. See the Proposed Agenda below for specific topics.
Topic: IHE PCD RTM Vent TG
Date: Wednesday, December 3, 2008
Time: 12:00 pm, Eastern Time (GMT -05:00, New York)
Duration: 120 Minutes
Note: Specific web & phone informaiton will be provided via e-mail to group members.
Contact Manny Furst for more information.
- (No advance agenda published)
Attachments / Materials
- (no attachments)
- Chair/Host: Todd Cooper
- Steven Dain, Robert Flanders, Brad Lunde, Ken Marks, John Rhoads, Paul Schluter, Jan Wittenber
Item Topic Discussion 1 Introductions & Agenda Review
- (No advance agenda published)
2 Approval of Minutes
- Discussion notes from 2008.11.12 meeting reviewed and approved
3 Vent Term Model Review
- Jan Wittenber
- Jan reviewed the Ventilator Nomenclature architecture model that was developed in discussions between him, Chip Furniss & Pete Goulding.
4 General Term Development Discussion
- Paul reiterated that the group should focus on (in priority order): reported monitored parameters, reported settings ("read only configs"), Waves, ..., Alarms, Control parameters . In other words, in order to make the problem set more tractable, the universe of possible parameters should be organized by application data type.
- The order/priority should be based on what clinicians want to see on their charts!
- NOTE: In the case of an "index", the underlying arithmetic expression or at least some of the key properties should be identified (e.g., "...per BSA"). This index formulae could be specified either in the device or an external information system. Both approaches should be supported.
- Steven reiterated the need to focus on the clinical purpose for which the data is being collected. For example,
- 1. For the HIS/Charting
- 2. Research purposes
- 3. Forensics ("black box")
- Question: Is there a way of indicating the intended "purpose" of the parameter (e.g., by including "setting", or "monitor" etc.)? Is there a method for indicating the intented "purpose" of the parameter (e.g., by including "setting" / "monitor" at the start of the term so that the goal can be quickly determined?
- - (Paul) Could combine Observation & Settings under the same set of yellow columns ... as a TYPE of data; Could also add a discriminator regarding the use of the parameter. For indicies - maybe a reference to the liturature where more complete documentation is available.
- - Also, episodic / "spot" measurements vs. continuous trend streams should also be captured along with the intended usage.
- - Question: Why differentiate between episodic & continuous? Paul: the information is handled / communicated differently ... in other words, there are varying data handling / management issues that need to be addressed.
- Question: Airway pressure measurement site - how is this captured?
- - (Paul) There are mechanisms to indicate measurement site information, both pre- & post-coordinated
- - (Dain) Is this the role of the device or the CIS? (sometimes in machine / sometimes by clinician / sometimes by clinician entered into device...)
- - (Ken) measurement method also important (optional attribution ... but should be available)
- - (Jan) adding a methodological column would be very helpful (transductive <Functional> statistical)
- This usage characterization should be captured in the Rosetta. Paul) Add another column "RefID 2" as a working space
- Question: How to document & derive terminology from clinical workflow?
- - (Jan) Terminology vs. information model
- - (Todd) We should capture heuristics regarding when this clinical context information is folded into the term vs. in the info model
- (Paul) Add another column "RefID 2" to provide for the HL7-mangled-RefID's (as a WIP space).
5 Planning Discussion
- There was a general discussion regarding the group's strategy for going forward.
- Complete core mindmap of semantic architecture
- Focus on numeric parameters (esp. what is charted...) first
- Update table:
- - Add functional discriminator column (e.g., energy per breath, indexed per BSA, body weight)
- - IOW 5th row discriminators ... next set of columns (min / max / ...)
- - Observation & Setting same YELLOW color
- - Support "measurement site" (pre/post coordination)
- - Add a "clinical" column (what do clinicians need, intended usage of the term, etc.)
- Update RTM tables with "RefID 2" column + "measurement site" column
6 Next Meeting
- Next meeting 2008.12.17
(Reviewed & approved by PCD RTM Vent TG 2008-12-17)