PCD TC 2011-03-23 Webex
Patient Care Device Domain
PC Regularly Scheduled Meeting
Topic: PCD Planning and Technical Committees Joint Meeting
- Regularly Scheduled Meeting Time
Date: Wednesday, March 23, 2011
Time: 11:00 am, Eastern Time (New York)
Duration: 60 Minutes
- 1. Agenda Approval
- 2. Review Discussion Summaries: Technical Committee March 9 PCD TC 2011-03-09 Webex
- 3. NIST Tool Update
- 4. Technical Framework Final Text windup
- PCD OIDS - see PCD_OID_Management
- 5. Other Development Updates
- ADQ meets Thursday for the first time Thurs. 2 pm EDT
- 6. F2F Agenda Items?
- 7. Action Item Review
- 8. Next and Recent Meetings
- 9. Additional Business
- 10. Next Meetings
Action Items from Previous Meetings
Significant changes, other than dates, will be in bold.
- Chair: John Garguilo and John Rhoads
- Participants: Jon Blasingame, Julien Deshayes, John Donnelly, Al Engelbert, Robert Flanders, John Garguilo, Khalil Maalouf, Sandra Martinez, Steve Merritt, Monroe Pattillo, John Rhoads, Jeff Rinda, Paul Schluter, Rob Snelick, Scott Zaffrin, Khalid Zubaidi, Manny Furst
Discussion Summaries do not require formal approval, while minutes of meetings where votes are taken do. Participants are encouraged to review and bring up significant issues with discussion summaries of previous meetings. Votes will be taken to approve meetings where votes took place; these may be email ballots.
Item Topic Discussion 1 Introductions & Agenda Review
- Agenda approved
2 Discussion Summary or Approval of Minutes
- Discussion Summary of previous meeting was accepted
3 Agenda Items
- As Noted
3. NIST Tool Update:
- - John Garguilo, (NIST), described the move to “Isolated System Testing” in which transactions are evaluated within a scenario (test case) as contrasted with “instance Testing” which IHI-PCD uses to date: in which one instance of transaction (HL7 message) is validated. Isolated System Testing will be available as we move through IHE-PCD cycle 6 (2011-12) and will include “Instance Testing”, again which is the current level of testing available to IHE-PCD members (and whomever wishes to use the web site). The update permits testing Use Cases from the perspective of a multi-transactional scenario - as contrasted to single transactions. Additionally, Isolated System Testing will include protocol conformance and functional behavior conformance (features and operational behavior corresponding to specifications). Using the test interface, Users will register with the test system and be able to select particular roles or actors (refered to as the “system under test ([SUT])” to serve as they communicate and test against the test system. Once registered users communicate by using specific configuration information (including a specified IP address and port). User accounts are role-based such that each user (e.g., vendor) can see what test they’ve execute and a status of the results. Additionally the test system can be viewed and used by the test manager to get a dashboard of all testing which has occurred to date and render the status. The slide presentation is available at ftp://email@example.com/Patient_Care_Devices/Tools/NIST-Tools/Presentations_Tool_updates/NIST Test Tool Demo 3_23_11_NISTv1 0.pptx.
- - Julien Deshayes, also from NIST, demonstrated the tool with a DOR to DOC test case involving the DEC messages (ORU and ACK). Julien showed that the test system can both initiate or receive messages which are correct or incorrect (i.e., with errors as defined by the specifications – HL7, IHE-PCD TF and Supplements, hRTN, and test case specific) to evaluate to a level the behavior of an SUT.The updated test service provides similar reports to those previously available but enables a more comprehensive report which progresses through a defined scenario (or test case) showing validation on each transaction sent or received (from the test system’s perspective). John Garguilo noted that Isolated testing is valuable in the pre-Connectathon period and can potentially be used as a test partner in the Connectathon if there the number of actual systems is less than three - thus enhancing Connectathon testing.
- - John noted that the system will track each vendor’s experience and has an “administrator’s” dashboard that provides an overview of all participating vendors, which tests have been executed, how many, and the pass/fail status. This will be valuable in tracking progress in Pre-Connectathon (and Connectathon) testing.
4. Technical Framework:
- - PCD OIDS: John Rhoads described the PCD OID structure and the Wiki page he established. These OIDS will be used in MSH-21 to provide unique PCD Profile Message Identifiers. These OIDs will include identification of Supplements, and as Profiles are released a version level can be added for unique identification to that level. John Garguilo noted that the NIST test tool can check the OID as well, adding not only to level of rigor, but enabling a clear distinction of which Integration Profile (including version) is being referenced by the vendor in their messages.
- - Robert will send John Rhoads a note about MSH-15; this was an issue at the Connectathon.
5. Other Development Updates: ADQ will meet for the first time tomorrow.
6. F2F Agenda:
- - A Wiki page has been established to provide a place to organize the May meeting. Members are asked to add topics for consideration in the agenda. Jon Blasingame will contact Christel when she returns from vacation to explore outreach to clinicians.
Other Agenda Items: Deferred
The next meetings are:
TC April 6, 2011 PCD TC 2011-04-06 Webex
PC March 16, 2011 PCD PC 2011-03-30 Webex