Difference between revisions of "Cross-Community Access for Imaging"

Latest revision as of 15:23, 25 May 2018

Summary

Cross-Community Access for Imaging(XCA) - Supports the means to query and retrieve patient relevant medical imaging data held by other communities.

The XCA-I Profile extends the IT Infrastructure XCA Profile. XCA provides access to all medical data including diagnostic reports and imaging manifests. XCA-I provides access to the images referenced in the imaging manifests.

Benefits

Image access between Communities
Common health information infrastructure with non-imaging data

Details

The Cross-Community Access for Imaging profile supports the means to query and retrieve patient relevant medical image data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism. Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc.

Such communities may be XDS Affinity Domains which define image sharing using the XDS-I profile. This profile addresses sharing between such communities.

The XCA-I Profile extends the IT Infrastructure XCA Profile for Imaging. XCA provides access to Diagnostic reports and Imaging Manifests. XCA-I provides access to the imaging objects referenced in the Manifests.

Systems Affected

Systems involved in this profile include:

PACS or RIS systems may store, manage, and display imaging documents.
EMR's and other patient management systems which will access and display imaging documents.
HIE's, Image Exchange Systems, and VNA's which store, manage and display imaging documents for multiple systems.

Actors & Transactions:

The shaded actors are NOT included in this profile but are shown to illustrate the full set of actors that play a role other endpoint of transactions that ARE part of the profile (e.g., the Document Registry Actor is an endpoint for the Registry Stored Query Transaction).

Specification

Profile Status: Final Text

Documents:

IHE Radiology Technical Framework:

Volume 1 Section DICOM
Volume 2 Section DICOM

Cross-Community Access for Imaging (XCA-I)]

Underlying Standards:

DICOM
ebRIM OASIS/ebXML Registry Information Model v3.0
ebRS OASIS/ebXML Registry Services Specifications v3.0

[XCA] Cross-Community Access allows to query and retrieve patient electronic health records, including the reports and image manifests held by other communities.
[XDS] Cross Enterprise Document Sharing share and discover electronic health record documents between healthcare enterprises, physician offices, clinics, acute care in-patient facilities and personal health records within the community.

[XDS-I.b] Cross-enterprise Document Sharing for Imaging.b Update extends XDS to share images, diagnostic reports and related information across a group of care sites.

@@ Line 1: / Line 1: @@
-'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''
-''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
-''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
-''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
-''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
 __TOC__
 ==Summary==
-''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''
+Cross-Community Access for Imaging(XCA) - Supports the means to query and retrieve patient relevant medical imaging data held by other communities.
-''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+The XCA-I Profile extends the IT Infrastructure XCA Profile.  XCA provides access to all medical data including diagnostic reports and imaging manifests.  XCA-I provides access to the images referenced in the imaging manifests.
-''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
 ==Benefits==
-''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+* Image access between Communities
+* Common health information infrastructure with non-imaging data
 ==Details==
-''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+The '''Cross-Community Access for Imaging''' profile supports the means to query and retrieve patient relevant medical image data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism. Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc.
+Such communities may be XDS Affinity Domains which define image sharing using the XDS-I profile. This profile addresses sharing between such communities.
-''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
+The XCA-I Profile extends the IT Infrastructure XCA Profile for Imaging.  XCA provides access to Diagnostic reports and Imaging Manifests.  XCA-I provides access to the imaging objects referenced in the Manifests.
-''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 ==Systems Affected==
-''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+Systems involved in this profile include:
-* ''PACS systems may store, manage, and/or display Evidence Documents.''
+* '''PACS or RIS systems''' may store, manage, and display imaging documents.
-* ''Display systems may query, retrieve and display Evidence Documents.''
+* '''EMR's and other patient management systems''' which will access and display imaging documents.
-* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+* '''HIE's, Image Exchange Systems, and VNA's''' which store, manage and display imaging documents for multiple systems.
 '''Actors & Transactions:'''
-''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+[[File:XCA-I.jpg]]
+The shaded actors are NOT included in this profile but are shown to illustrate the full set of actors that play a role other endpoint of transactions that ARE part of the profile (e.g., the Document Registry Actor is an endpoint for the Registry Stored Query Transaction).
 ==Specification==
 '''Profile Status:''' [[Comments| Final Text]]
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 '''Documents:'''
-''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+:* Volume 1 Section [http://dicom.nema.org DICOM]
+:* Volume 2 Section [http://dicom.nema.org DICOM]
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+Cross-Community Access for Imaging (XCA-I)]
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 '''Underlying Standards:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
 :* [http://dicom.nema.org DICOM]
-:* [http://www.hl7.org HL7]
+:* ebRIM OASIS/ebXML Registry Information Model v3.0
-:* ...
+:* ebRS OASIS/ebXML Registry Services Specifications v3.0
 ==See Also==
-''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
+* [[Document Sharing]]
 '''Related Profiles'''
-''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
+* [XCA] [[Cross-Community Access]] allows to query and retrieve patient electronic health records, including the reports and image manifests held by other communities.
+* [XDS] [[Cross Enterprise Document Sharing]] share and discover electronic health record documents between healthcare enterprises, physician offices, clinics, acute care in-patient facilities and personal health records within the community.
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
-* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
-* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
-* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
-* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
-'''Consumer Information'''
-The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
-The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
-'''Implementer Information'''
-The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
-'''Reference Articles'''
-''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract   or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
+* [XDS-I.b] [[Cross-enterprise Document Sharing for Imaging]].b Update extends XDS to share images, diagnostic reports and related information across a group of care sites.
-This page is based on the [[Profile Overview Template]]
 [[Category:Profiles]]
+[[Category:DocShare]]
-<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
+[[Category:RAD Profile]]
+[[Category:DICOM]]

Difference between revisions of "Cross-Community Access for Imaging"

Latest revision as of 15:23, 25 May 2018

Contents

Summary

Benefits

Details

Systems Affected

Specification

See Also

Navigation menu

Search