Cross Community Access - Discussion: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Witting (talk | contribs)
Witting (talk | contribs)
Line 6: Line 6:


= Tcon March 28, 2007 =
= Tcon March 28, 2007 =
The purpose of this tcon is to resolve issues discussed during the face-to-face, which are:
* Rename bridge actor
* Large volume data and significant delay of response
* Uniquely identifying the patient
* Managing metadata from external communities
* Interaction with XDS actors
* Privacy and Security
== Rename bridge actor ==
== Large volume data and significant delay of response ==
== Uniquely identifying the patient ==
== Uniquely identifying the patient ==
== Managing metadata from external communities ==
== Interaction with XDS actors ==
== Privacy and Security ==

Revision as of 08:10, 28 March 2007

Introduction

The Cross Community Access profile supports sharing of patient health information across communities. A community is defined as a coupling of facilities/enterprises for the purpose of sharing patient-relevant medical information. A community must have an established mechanism for sharing medical information among the organizations belonging to the community. An example of a community is an XDS Affinity Domain which defines document sharing using the XDS profile. This profile supports sharing of medical documents across XDS Affinity Domains. This profile should allow for extensions which support sharing of patient health information between communities other than XDS Affinity Domains. These extensions are out of scope for this profile.

In 2006 a White Paper was developed by the ITI technical committee proposing a set of profiles that supports cross community patient data access. This proposal is one of the profiles specified in the White Paper.

Tcon March 28, 2007

The purpose of this tcon is to resolve issues discussed during the face-to-face, which are:

  • Rename bridge actor
  • Large volume data and significant delay of response
  • Uniquely identifying the patient
  • Managing metadata from external communities
  • Interaction with XDS actors
  • Privacy and Security

Rename bridge actor

Large volume data and significant delay of response

Uniquely identifying the patient

Uniquely identifying the patient

Managing metadata from external communities

Interaction with XDS actors

Privacy and Security