Common use of Requested Action Clause in Contracts

Requested Action. Need input from all stakeholders on the content of the new Multipurpose Agreement (MPA). History of IHS Data Exchange • IHS as data aggregator for reporting purposes. • Bilateral relationship between IHS and tribes. • IHS as data broker. Healtheway eHealth Exchange Direct Trust • Multilateral relationship between IHS and tribes. • RPMS Network: – Master Patient Index (MPI) – provides a unique identifier for all patients registered across facilities that use the RPMS – Health Information Exchange (HIE [internal] / eHealth [external]) – allows providers at one facility to access patient health summary documents from another location (I/T/U)and provides a gateway to the external, national Healtheway eHealth Exchange to support the exchange of information with other public and private health care partners – Personal Health Record (PHR) – web-based portal that allows patients to access their personal health information – DIRECT Mail (DIRECT) – enables directed, secure exchange of personal health information between providers and between patients and their health care teams using the Direct secure email protocol • Ensure the privacy, integrity, security of personal health information (PHI) and personally identifiable information, such that the Indian health system can effectively and safely carry out its mission while ensuring our patients’ trust in us • Bind T/U sites to the requirements of HealtheWay’s DURSA for query-based exchange and DirectTrust for directed, secure email exchange • Ensure compliance with HIPAA, Privacy Act, FISMA, and other laws, which are incorporated in the proposed IHS policies and MPA • Avoid compromising our mutual trust vis-à-vis the RPMS Network, other tribes, our business associates, and other external exchange partners • Simplify the process by combining multiple agreements into one where possible (e.g. Business Associate Agreement, Interconnection Security Agreement, and End User Agreement); reducing the number of executed agreements from 900 to 300 • Enable equitable information sharing and a level playing field between tribes, honoring tribal sovereignty, while establishing a federated trust framework • Aligning processes with those of other HIEs, HISPs and federated exchanges at the national, state, or regional level • Maintaining integrity of the agreements through one, consistent master MPA and a single, consistent signing document (the Joinder Agreement) Articles I. Definitions

Requested Action. Need input from all stakeholders Views and comments on the content MPA due to CDR ▇▇▇▇ ▇▇▇▇▇, Chief Information Officer (CIO), IHS at this email address: ▇▇▇@▇▇▇.▇▇▇. History of the new Multipurpose Agreement (MPA). Indian Health System Data Exchange History of IHS Data Exchange • IHS as data aggregator for reporting purposes. Healtheway eHealth Exchange‌‌ Direct Trust • Bilateral relationship between IHS and tribes. • IHS as data broker. Healtheway eHealth Exchange Direct Trust • Multilateral relationship between IHS and tribes. • RPMS Network: – • Master Patient Index (MPI) – provides a unique identifier for all patients registered across facilities that use the RPMS – • Health Information Exchange (HIE [internal] / eHealth [external]) – allows providers at one facility to access patient health summary documents from another location (I/T/U)and provides a gateway to the external, national Healtheway eHealth Exchange to support the exchange of information with other public and private health care partners – • Personal Health Record (PHR) – web-based portal that allows patients to access their personal health information – • DIRECT Mail (DIRECT) – enables directed, secure exchange of personal health information between providers and between patients and their health care teams using the Direct secure email protocol • Ensure the privacy, integrity, security of personal health information (PHI) and personally identifiable information, such that the Indian health system can effectively and safely carry out its mission while ensuring our patients’ trust in us • Bind T/U sites to the requirements of HealtheWay’s DURSA for query-based exchange and DirectTrust for directed, secure email exchange • Ensure compliance with HIPAA, Privacy Act, FISMA, and other laws, which are incorporated in the proposed IHS policies and MPA • Avoid compromising our mutual trust vis-à-vis the RPMS Network, other tribes, our business associates, and other external exchange partners • Simplify the process by combining multiple agreements into one where possible (e.g. Business Associate Agreement, Interconnection Security Agreement, and End User Agreement); reducing the number of executed agreements from 900 to 300 • Enable equitable information sharing and a level playing field between tribes, honoring tribal sovereignty, while establishing a federated trust framework • Aligning processes with those of other HIEs, HISPs and federated exchanges at the national, state, or regional level • Maintaining integrity of the agreements through one, consistent master MPA and a single, consistent signing document (the Joinder Agreement) Articles I. Definitions)

Requested Action. Need input from all stakeholders Views and comments on the content of the new Multipurpose Agreement MPA due to CDR ▇▇▇▇ ▇▇▇▇▇, Chief Information Officer (MPACIO), IHS at this email address: ▇▇▇@▇▇▇.▇▇▇. History of IHS Data Exchange • IHS as data aggregator for reporting purposes. Direct Trust • Bilateral relationship between IHS and tribes. • IHS as data broker. Healtheway eHealth Exchange Direct Trust • Multilateral relationship between IHS and tribes. Scope of the RPMS Network • RPMS Network: – • Master Patient Index (MPI) – provides a unique identifier for all patients registered across facilities that use the RPMS – • Health Information Exchange (HIE [internal] / eHealth [external]) – allows providers at one facility to access patient health summary documents from another location (I/T/U)and provides a gateway to the external, national Healtheway eHealth Exchange to support the exchange of information with other public and private health care partners – • Personal Health Record (PHR) – web-based portal that allows patients to access their personal health information – • DIRECT Mail (DIRECT) – enables directed, secure exchange of personal health information between providers and between patients and their health care teams using the Direct secure email protocol MPA Mission Drivers • Ensure the privacy, integrity, security of personal health information (PHI) and personally identifiable information, such that the Indian health system can effectively and safely carry out its mission while ensuring our patients’ trust in us • Bind T/U sites to the requirements of HealtheWay’s DURSA for query-based exchange and DirectTrust for directed, secure email exchange • Ensure compliance with HIPAA, Privacy Act, FISMA, and other laws, which are incorporated in the proposed IHS policies and MPA • Avoid compromising our mutual trust vis-à-vis the RPMS Network, other tribes, our business associates, and other external exchange partners • Simplify the process by combining multiple agreements into one where possible (e.g. Business Associate Agreement, Interconnection Security Agreement, and End User Agreement); reducing the number of executed agreements from 900 to 300 • Enable equitable information sharing and a level playing field between tribes, honoring tribal sovereignty, while establishing a federated trust framework • Aligning processes with those of other HIEs, HISPs and federated exchanges at the national, state, or regional level • Maintaining integrity of the agreements through one, consistent master MPA and a single, consistent signing document (the Joinder Agreement) Articles I. Definitions)