ToC+-+Use+Case+Assumptions

include component="page" wikiName="siframework" page="TOC Header" **Please reference the Final Use Case page to view the Use Case Assumptions incorporation within the full Use Case.** **//Note: The Use Case Assumptions Section is now section 5.0 instead of 6.0 due to the deletion of the separate User Story section.//**

**5.0 Use Case Assumptions**

The transferring or referring provider or provider organization has an EHR system capable of producing a structured summary document using C32/CCD and/or CCR standards and properly coded data elements; and can be exchanged to another EHR system or PHR system.
 * The EHR system is capable of ensuring that content of the Summary Record (as exchanged) maintains its fidelity to source, as well as assured identity, provenance, completeness, audit/traceability, full context, along with permissions and qualifications
 * Established network and policy infrastructure to enable consistent, appropriate, and accurate information exchange across clinician systems, data repositories and locator services. This includes, but is not limited to:
 * Methods to identify and authenticate users;
 * Methods to identify and determine providers of care;
 * Methods to enforce data access authorization policies;
 * Security and privacy policies, procedures and practices are commonly implemented to support acceptable levels of patient privacy and security; i.e. HIPAA, HITECH and EHR certification criteria.
 * The Patient has and uses a PHR.
 * The transmission of data may occur via Health Information Exchanges as data may be transmitted to multiple HIEs and providers.

//Appendix C provides more details on Privacy and Security assumptions.//

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