Difference between revisions of "PCD Implantable Device Cardiac Observation"
(add text) |
(add first text) |
||
| Line 8: | Line 8: | ||
==Benefits== | ==Benefits== | ||
| + | *Standards based translation and transfer of summary device interrogation information | ||
| + | |||
| + | *Improved workflow efficiencies in Cardiology and Electrophysiology practices from management of “key” summary implantable rhythm control device interrogation information in a central system such as an electronic health record system (EHR) or a device clinic management system. | ||
==Details== | ==Details== | ||
Revision as of 10:49, 31 August 2009
Implantable Device - Cardiac - Observation (IDCO) communicates IDC / "pacemaker" information to enterprise applications such as EHRs.
Summary
This profile describes 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
- Standards based translation and transfer of summary device interrogation information
- Improved workflow efficiencies in Cardiology and Electrophysiology practices from management of “key” summary implantable rhythm control device interrogation information in a central system such as an electronic health record system (EHR) or a device clinic management system.
Details
The Implantable Device - Cardiac - Observation (IDCO) Integration Profile supports communication of ...
The Device Observation Reporter (DOR) actor receives data from IDCs and maps the received data to transactions providing consistent syntax and semantics.
The Device Observation Consumer (DOC) is the actor responsible for receiving IDC data from the Device Observation Reporter.
Systems Affected
...
See Also
...
References
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >