Org Address 1: 100 Exchange Street Org Address 2: Org City: Philadelphia Org State: PA Org Zip: 19103 Org Telecom: 215 888 1000 Assumptions about the version supported for various standards can be applied to explore information exchange challenges that may arise for this storyboard. HISP systems Health Information Service Providers are a different kind of system actor from an HIE. They exist to securely transport and deliver health information within the health ecosystem. While Health Information Exchange systems may also provide this transport function, their connections tend to be established via persistent data communication channels developed between organizations that have agreed to share data. They may offer a view and download option, but non-persistent data communication channels are not a part of the HIE design. The functionality of non-persistent data communication is attributed to a HISP system. Some HIEs are beginning to also support HISP functionality. For the purpose of this storyboard artifact, HIE and HISP functionality are considered as being delivered by distinct system actors. EMR systems, other patient Each organization running a system to manage patient/member/personal health information may management and member produce any of the following types of CDA documents: C32, C-CDA R1.1 documents, or C-CDA R2.1 management systems and personal Documents. Some systems may have some FHIR API capabilities implemented in FHIR DSTU 2 and health record systems other may have implemented FHIR STU 3, in which case, FHIR resources, profiles, and operations may be utilized to share information among care team members from distinct legal entities. Note, the present care paradigm makes it difficult to express the patient and family members involved in care as part of the set of care team members. While other care team members easily can be described as belonging to different legal entities, there is no that the patient and the “organization” family members belong to. Personal, familial and legal relationships to the patient may organize certain care team members in support of the patient, they don’t belong to an in the “organization” same sense that the employed doctors, nurses, and other care team members do. This structural difference causes a within the natural situation we are attempting to model and “misalignment” describe.
Org Address 1: 100 Exchange Street Org Address 2: Org City: Philadelphia Org State: PA Org Zip: 19103 Org Telecom: 215 888 1000 Assumptions about the version supported for various standards can be applied to explore information exchange challenges that may arise for this storyboard. HISP systems Health Information Service Providers are a different kind of system actor from an HIE. They exist to securely transport and deliver health information within the health ecosystem. While Health Information Exchange systems may also provide this transport function, their connections tend to be established via persistent data communication channels developed between organizations that have agreed to share data. They may offer a view and download option, but non-persistent data communication channels are not a part of the HIE design. The functionality of non-persistent data communication is attributed to a HISP system. Some HIEs are beginning to also support HISP functionality. For the purpose of this storyboard artifact, HIE and HISP functionality are considered as being delivered by distinct system actors. EMR systems, other patient management and member management systems and personal health record systems Each organization running a system to manage patient/member/personal health information may produce any of the following types of CDA documents: C32, C-CDA R1.1 documents, or C-CDA R2.1 Documents. Some systems may have some FHIR API capabilities implemented in FHIR DSTU 2 and other may have implemented FHIR STU 3, in which case, FHIR resources, profiles, and operations may be utilized to share information among care team members from distinct legal entities. Note, the present care paradigm makes it difficult to express the patient and family members involved in care as part of the set of care team members. While other care team members easily can be described as belonging to different legal entities, there is no “organization” that the patient and the family members belong to. Personal, familial and legal relationships to the patient may organize certain care team members in support of the patient, they don’t belong to an “organization” in the same sense that the employed doctors, nurses, and other care team members do. This structural difference causes a “misalignment” within the natural situation we are attempting to model and describe.