PCD RTM 2008-12-03 WebEx: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
ToddCooper (talk | contribs)
1,843 edits
m Converted from rough notes...
ToddCooper (talk | contribs)
1,843 edits
m Finalized formatting
Line 79: Line 79:
:* The order/priority should be based on what clinicians want to see on their charts!  
:* 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")
:* 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,  
:* Steven reiterated the need to focus on the '''''clinical purpose''''' for which the data is being collected.  For example,  
Line 86: Line 86:
::: 3. Forensics ("black box")
::: 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.)?
:* 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?
                ??? Is there a way of indicating the intended "purpose" of the parameter, e.g., by including "setting" / "monitor"
::- (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.
                          at the start of the term so that the goal can be quickly determined?
::- Also, episodic / "spot" measurements vs. continuous trend streams should also be captured along with the intended usage.
                Re. index formulae - this can be specified / formalized in the vent OR in an external information system.  Should
::- 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.
                          accommodate both.
        (Paul)
                Could combine Observation & Settings under the same set of yellow columns ... as a TYPE of data
                Could add discriminator re. the use of the parameter
                For indicies - maybe a reference to the liturature


        (Dain) Airway pressure - where measured?
:* Question: Airway pressure measurement site - how is this captured?
                (Paul) indicate measurement site information
::- (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 /
::- (Dain) Is this the role of the device or the CIS?  (sometimes in machine / sometimes by clinician / sometimes by clinician entered into device...)
                                  sometimes by clinician entered into device...)
::- (Ken) measurement method also important (optional attribution ... but should be available)
                (Ken) measurement method also important (optional attribution ... but should be available)
::- (Jan) adding a methodological column would be very helpful (transductive <Functional> statistical)
                (Jan) adding a methodological column would be very helpful (transductive <Functional> statistical)


        Rosetta (Paul)
:* This usage characterization should be captured in the Rosetta.  Paul) Add another column "RefID 2" as a working space
                Add another column "RefID 2" as a working space
                (Jan) take the key terms from the rosetta to identify what we should target as a first order priority


        Steve - What are clinicians actually recording on charts today? We should factor in workflow as a key factor
:* Question: How to document & derive terminology from clinical workflow?
                toward prioritization of what is supported.
::- (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
        <thc> How to capture & factor in workflow w.r.t. terminology
                Jan:  Terminology vs. information model
                Todd:  Heuristics re. when this clinical context information is folded into the term vs. in the info model?
 
        ["stat" - ??? <don't have a clue what Jan meant> ]
 
        episodic / "spot" measurements vs. continuous trends - should also capture this class of numeric data (episodic & continuous)
 
        Why differentiate between episodic & continuous?  Paul:  the information is handled / communicated differently ... IOW
                data handling / management


'''Decisions/Issues:'''
'''Decisions/Issues:'''


'''Action(s):'''
'''Action(s):'''
:* (Paul) Add another column "RefID 2" to provide for the HL7-mangled-RefID's (as a WIP space).


|-
|-
Line 139: Line 122:
:::- Observation & Setting same YELLOW color  
:::- Observation & Setting same YELLOW color  
:::- Support "measurement site" (pre/post coordination)
:::- Support "measurement site" (pre/post coordination)
:::- Add a "clinical" column
:::- Add a "clinical" column (what do clinicians need, intended usage of the term, etc.)
:* Update RTM tables with "RefID 2" column + "measurement site" column
:* Update RTM tables with "RefID 2" column + "measurement site" column


Revision as of 18:31, 16 December 2008

(Vent TG Main Page)

Meeting Purpose

IHE PCD Rosetta Terminology Mapping (RTM) Ventilator Task Group regular discussion meeting. See the Proposed Agenda below for specific topics.

WebEx Information

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.

Proposed Agenda

(No advance agenda published)

Attachments / Materials

(no attachments)


Minutes

Participants

Chair/Host: Todd Cooper
Steven Dain, Robert Flanders, Brad Lunde, Ken Marks, John Rhoads, Paul Schluter, Jan Wittenber


Discussion

Item Topic Discussion
1 Introductions & Agenda Review
- Chair 		Status/Discussion:
  • (No advance agenda published)

Decisions/Issues:

Action(s):

2 Approval of Minutes
- Chair 		Status/Discussion:

Decisions/Issues:

Action(s):

3 Vent Term Model Review
- Jan Wittenber 		Status/Discussion:

Decisions/Issues:

Action(s):

4 General Term Development Discussion
- Group 		Status/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

Decisions/Issues:

Action(s):

  • (Paul) Add another column "RefID 2" to provide for the HL7-mangled-RefID's (as a WIP space).
5 Planning Discussion
- Group 		Status/Discussion:
  • There was a general discussion regarding the group's strategy for going forward.

Decisions/Issues:

  • 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

Action(s):

6 Next Meeting
- Chair 		Status/Discussion:

Decisions/Issues:

  • Next meeting 2008.12.17

Action(s):

Next Meeting

2008-12-17 Vent WebEx Session


(Reviewed & approved by PCD RTM Vent TG <tbd>)">


PCD Home

Retrieved from "http://wiki.ihe.net/index.php?title=PCD_RTM_2008-12-03_WebEx&oldid=27773"