1. ToC Pilots Sample configuration S&I Framework October 11, 2011

2. Actors Involved A pilot may involve the following participants from the healthcare ecosystem: Provider (Hospital or Clinic) EHR vendor [Optional] HISP or System Integrator EHR or PHR vendors and Provider or Patient or Caregiver etc. 10/11/20112

3. Minimum Configuration Pilot system configurations to meet minimum requirements, ToC Clinical Information sender, an EHR system. ToC Clinical Information receiver, an EHR or a PHR system. A transport system being used in Production environments. A security system being used in Production environments. A means to capture and log Generated/Received messages Generated/Received acknowledgements Each pilot participant can include system configurations in addition to the requirements listed above. 10/11/20113

4. Sample Pilot Provider EHR or PHR Vendor specific adapter ToC Reference Library API EHR or PHR Vendor Transport, Security & Other HISP or System Integrator EHR ToC Reference Library API Vendor specific adapter EHR Vendor Provider or Patient or Caregiver etc. 410/11/2011

5. System Functions 10/11/20115 EHR Vendor (as sender)HISP or System IntegratorEHR or PHR Vendor (as receiver) Configure EHR Create approach to capturing transmitted and received messages Configure EHR or PHR Integrate with ToC RI APIFacilitate Communication/ Collaboration between sender and receiver vendors Integrate with ToC RI API Integrate appropriate adapterIntegrationIntegrate appropriate adapter Create MessagesCreate Transport MechanismReceive Messages Publish MessageCreate Security MechanismParse, store message contents

6. Questions What ToC information packets will be used? Is ToC RI being used for transformation/validation? What are the Transport/Security options? How will the patient matching be resolved? 10/11/20116