ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-06-23

include component="page" wikiName="siframework" page="TOC Header"

ToC Architecture Implementation RQ WG Meeting Minutes

 * Date:** 06-23-2011
 * Time:** 2:00-3:00pm
 * Dial-in:**1-408-600-3600 | **Passcode**: 667 669 756
 * Meeting Agenda: Click here for the agenda!**

Attendance
Robin Barnes, Susan Campbell, Tom Caruso, Steven Cason, Bob DeAnna, Lester Keepper, Cynthia Levy, Arien Malec, Mayuri Patel, Chitra Raghu, Dave Shevlin, David Tao Andriy Selivonenko, Lin Wan, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 06-23-2011 || Review the revised RI Architecture Scope and participate in the consensus process through the RI Architecture Scope Consensus Page. Only committed members can participate in the consensus process. If you are not a committed member, please see S&I Initiative, Overview, Phases and Outputs to become a committed member. || All || Open ||  ||
 * 2 || 06-23-2011 || Review the RI Architecture Overview and provide comments through the discussion tabs. || All || Open ||  ||
 * 3 || 06-23-201 || A ToC Glossary of Terms has been created. Please review and add additional comments. || All || Open ||  ||

Agenda Items

 * 1) Outcomes of F2F Meeting
 * 2) Consensus on RI Architecture Scope
 * 3) Review RI Architecture Overview
 * 4) Next Steps

Meeting Notes
F2F Outcomes Reviewed TOC Scope and goals –re-identified/rewrote RI Arch Scope statement.

Reference Implementation Goals (edits made in real-time)
 * RI Arch Scope** (reviewed by Mayuri Patel)
 * Create valid TOC documents as outputs, as defined in the TOC S&I Implementation Guide, using the Clinical Information Model (CIM) objects as inputs. Provide code which supports the ability of the source to "create a ToC Information Package" e.g., as required for Discharge or Consults.
 * Create an object-oriented implementation of the TOC CIM. Provide well-defined, straightforward API to CIM data elements for use by client applications in processing instances of TOC documents.
 * Create valid CIM objects as outputs using TOC documents as inputs. Provide code that supports the ability to "decipher and validate the ToC Information Package" for incorporation of the information by a consumer.
 * Validate TOC output documents against the TOC S&I Implementation Guide. These tools will validate that a ToC Information Package is complete and correct. These tools can validate ToC documents that are created either by the RI or any other method (e.g., ToC documents produced by vendors through their own code). These tools may be similar to tools currently provided by NIST, but will fully support any new constraints from the ToC initiative (including the CDA consolidation when it is approved), and will be offered to NIST to incorporate into their toolkit for validators.

Reference Implementation Assumptions (reviewed by Mayuri Patel) In-Scope (edits made in real-time)
 * The RI focuses on clinical content, consistent with the scope and charter of the ToC Initiative.
 * RI provides tools as aids, not as "standards." RI tools do not supersede or replace balloted standards or implementation guides (e.g., CDA is a standard, but any APIs provided by RI services are optional aids to produce standardized outputs, not to become standards in themselves).
 * The data elements identified by the ToC Use Case Care Planning WG, and supported by the ToC CIM, are within scope.

Out-of-Scope (edits made in real-time)
 * In the TOC Use Case Care Planning WG, the workflow, processes and governance associated with care planning, as well as care planning data elements, not currently supported by the TOC CIM, are out of scope.
 * Transport, Security, Privacy, Addressing, Audit, and Patient Identification are out of scope for the ToC RI. These are all essential components from an overall system perspective. However, this ToC initiative is about content, not about transport or other infrastructure. The RI will not produce code to transport, encrypt, or otherwise "secure" the payloads from a sender to a receiver. Other projects (Direct Project, Nationwide Health Information Network Exchange and CONNECT, etc.) have produced RI open source code for transport, encryption, and other infrastructure. (include links to their source libraries). Some standards -- e.g., access control, audit log, authentication, integrity, encryption of data in rest and in transit, have already been specified by ONC in its Final Rule for EHR Standards and Certification. Other ONC S&I Framework Initiatives, such as Provider Directory and Certificate Interoperability, address gaps in standards and implementation guidance that have not been previously specified in regulations and/or standards.

Next Meeting

 * Date:** 06-30-2011
 * Time:** 2:00-3:00pm
 * Dial-in:** 1-408-600-3600 **Passcode:** 665 317 27

Reference Materials

 * 1) ToC RI Arch Overview
 * 2) ToC RI Arch Workflow
 * 3) ToC RI Architecture Overview Consensus Page
 * 4) ToC RI Architecture Scope
 * 5) ToC RI Architecture Scope Consensus Page

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"