Difference between revisions of "IDCO"

From IHE Wiki
Jump to navigation Jump to search
(There isn't a See Also yet - add it back when there is some actual content)
(Just added opening para from the supplement document. Should be improved.)
Line 2: Line 2:
 
__TOC__
 
__TOC__
  
 +
[[Category: PCD Pages Needing Work]]
 
==Summary==
 
==Summary==
This page is WIP.  Content coming soon.
 
  
{{{2|''<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.>''}}}
+
This Supplement adds a new profile to the IHE Patient Care Device Technical Framework
 
+
describing a means to transfer information from an interrogated implantable cardiac device to
''<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.  .>''
+
information management systems. This profile is named Implantable Device – Cardiac –
 
+
Observation or IDCO for short.
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
 
  
 
==Benefits==
 
==Benefits==

Revision as of 09:49, 31 August 2009

Implantable Device - Cardiac - Observations (IDCO) communicates implantable cardiac device data to EMRs and device management systems.

Summary

This Supplement adds a new profile to the IHE Patient Care Device Technical Framework describing a means to transfer information from an interrogated implantable cardiac device to information management systems. This profile is named Implantable Device – Cardiac – Observation or IDCO for short.

Benefits

<List the key benefits the profile provides (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>

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.>

<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.>

<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.>

  • PACS systems may store, manage, and/or display Evidence Documents.
  • Display systems may query, retrieve and display Evidence Documents.
  • Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Trial Implementation

Documents:

Underlying Standards:


This page is based on the Profile Overview Template