Difference between revisions of "PCD RTM 2008-08-27 WebEx"
ToddCooper (talk | contribs) m (Initial Version) |
m (→Next Meeting) |
||
(One intermediate revision by one other user not shown) | |||
Line 57: | Line 57: | ||
| '''RTM UoM Update''' <br>- Schluter | | '''RTM UoM Update''' <br>- Schluter | ||
| '''Status/Discussion:''' | | '''Status/Discussion:''' | ||
+ | Paul provided an update on his work with the RTM Units of Measurement (UOM) table, esp. folding in proposed terms and gaps. | ||
+ | |||
'''Decisions/Issues:''' | '''Decisions/Issues:''' | ||
− | + | The table should be provided to participants in this WebEx, but not sent to the entire group until the next major release in the next week or so. | |
'''Action(s):''' | '''Action(s):''' | ||
+ | :* (Paul) send out updated UoM table to group participants. | ||
|- | |- | ||
| align="center" | 3 | | align="center" | 3 | ||
| '''RTM REF_ID Groups - Update''' <br>- Schluter | | '''RTM REF_ID Groups - Update''' <br>- Schluter | ||
| '''Status/Discussion:''' | | '''Status/Discussion:''' | ||
+ | :* Paul reviewed a report that he generated from his current Rosetta tables indicating all the GROUP ID's that are associated with a single REF_ID. (file: "RefID.Group.Units.2d.table.sortbyGroup.doc") This type of report will form the basis of further analysis of group assignments, esp. to collapse multiple group associations to a single ID where there is no valid use case context to warrent the assignments. | ||
+ | :* Todd mentioned that a future activity would be to define the constraints associated with a given GROUP-REF_ID pairing. For example, sourced from a specific medical device (or other containment) or clinical application. Paul mentioned a use case where a clinician might want to say, "I want to review all the cardiology related parameters." | ||
'''Decisions/Issues:''' | '''Decisions/Issues:''' | ||
Line 70: | Line 75: | ||
'''Action(s):''' | '''Action(s):''' | ||
+ | :* (Paul) send out the sample report to the WebEx participants. | ||
|- | |- | ||
| align="center" | 4 | | align="center" | 4 | ||
| '''RTM Testing Update''' <br>- Garguilo | | '''RTM Testing Update''' <br>- Garguilo | ||
| '''Status/Discussion:''' | | '''Status/Discussion:''' | ||
+ | :* John G. led a general discussion relating to how RTM would be tested '''this''' year vs. future cycles. | ||
+ | :* John mentioned the need for ICS Generator profiles (e.g., pump or vent) + an HL7 v2.x message profile, that can be used for test tool configuration this year. Todd indicated that he should have a pump and vent ICS for review in the next week or sooner. | ||
'''Decisions/Issues:''' | '''Decisions/Issues:''' | ||
− | |||
'''Action(s):''' | '''Action(s):''' | ||
+ | :* (Paul) send out the latest "RTM validation notes" to the group for review. | ||
|- | |- | ||
| align="center" | 5 | | align="center" | 5 | ||
| '''NIST Terminology Modeling Update''' <br>- Garguilo | | '''NIST Terminology Modeling Update''' <br>- Garguilo | ||
| '''Status/Discussion:''' | | '''Status/Discussion:''' | ||
+ | There was a general discussion (very brief) of the UML modeling work that has been undertaken at NIST to support tool & testing development. A key issue is to ensure that those who look at the model realize that only a small part of it is relevant to those who are looking for specific terms, but that the rest of it is needed for tooling and to formally capture the relationships between semantics. | ||
'''Decisions/Issues:''' | '''Decisions/Issues:''' | ||
'''Action(s):''' | '''Action(s):''' | ||
+ | :* (Todd) Create a "term model" section for the RTM wiki page and add references to the historical X73 terminology models as well as recent work done at NIST for the RTM. | ||
+ | :* (Garguilo / Martinez) Provide a detailed review of the model + tooling activities at the upcoming Vancouver meeting. | ||
|} | |} | ||
Line 98: | Line 109: | ||
[[Patient Care Device | PCD Home]] | [[Patient Care Device | PCD Home]] | ||
− | [[Category:PCD Meeting]] | + | [[Category:PCD Meeting Archive]] |
Latest revision as of 12:47, 24 January 2009
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, August 27, 2008
Time: 12:00 pm, Eastern Daylight Time (GMT -04: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
- 1 Review agenda
- 2 Review update / issues for RTM Units of Measurement
- 3 Reviewed term group analysis (initial work-in-progress)
- 4 RTM Testing Issues
- 5 NIST Terminology Modeling Update
- 6 New Issues
Attachments / Materials
<add any attachments here>'
Minutes
Participants
- Chair/Host: Paul Schluter (GE)
- Todd Cooper (Breakthrough Solutions Foundry), Bikram Day (Capsule), Robert Flanders (GE), Manny Furst (Improvement Technologies), John Garguilo (NIST), Neil Henry (Capsule), Sandra Martinez (NIST)
Discussion
Item Topic Discussion 1 Introductions & Agenda Review
- ChairStatus/Discussion: Decisions/Issues: Agenda approved without modification.
Action(s):
2 RTM UoM Update
- SchluterStatus/Discussion: Paul provided an update on his work with the RTM Units of Measurement (UOM) table, esp. folding in proposed terms and gaps.
Decisions/Issues: The table should be provided to participants in this WebEx, but not sent to the entire group until the next major release in the next week or so.
Action(s):
- (Paul) send out updated UoM table to group participants.
3 RTM REF_ID Groups - Update
- SchluterStatus/Discussion: - Paul reviewed a report that he generated from his current Rosetta tables indicating all the GROUP ID's that are associated with a single REF_ID. (file: "RefID.Group.Units.2d.table.sortbyGroup.doc") This type of report will form the basis of further analysis of group assignments, esp. to collapse multiple group associations to a single ID where there is no valid use case context to warrent the assignments.
- Todd mentioned that a future activity would be to define the constraints associated with a given GROUP-REF_ID pairing. For example, sourced from a specific medical device (or other containment) or clinical application. Paul mentioned a use case where a clinician might want to say, "I want to review all the cardiology related parameters."
Decisions/Issues:
Action(s):- (Paul) send out the sample report to the WebEx participants.
4 RTM Testing Update
- GarguiloStatus/Discussion: - John G. led a general discussion relating to how RTM would be tested this year vs. future cycles.
- John mentioned the need for ICS Generator profiles (e.g., pump or vent) + an HL7 v2.x message profile, that can be used for test tool configuration this year. Todd indicated that he should have a pump and vent ICS for review in the next week or sooner.
Decisions/Issues:
Action(s):
- (Paul) send out the latest "RTM validation notes" to the group for review.
5 NIST Terminology Modeling Update
- GarguiloStatus/Discussion: There was a general discussion (very brief) of the UML modeling work that has been undertaken at NIST to support tool & testing development. A key issue is to ensure that those who look at the model realize that only a small part of it is relevant to those who are looking for specific terms, but that the rest of it is needed for tooling and to formally capture the relationships between semantics.
Decisions/Issues:
Action(s):
- (Todd) Create a "term model" section for the RTM wiki page and add references to the historical X73 terminology models as well as recent work done at NIST for the RTM.
- (Garguilo / Martinez) Provide a detailed review of the model + tooling activities at the upcoming Vancouver meeting.
Next Meeting
<Add review line here when minutes are approved; e.g., "(Reviewed & approved by PCD RTM Vent TG 2008-04-16)">