Presentación Cardio-DRPT

380 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
380
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentación Cardio-DRPT

  1. 1. Displayable Reports Profile (DRPT) Marco Eichelberg OFFIS Technical Manager, IHE Europe Cardiology Slides by Harry Solomon, Co-chair, IHE Cardiology Technical Committee
  2. 2. The Problem <ul><li>Most existing reporting applications operate with paper paradigm </li></ul><ul><ul><li>Print </li></ul></ul><ul><ul><li>Scribble (signature) </li></ul></ul><ul><ul><li>Fax </li></ul></ul><ul><li>“ Advanced” apps have some electronic capabilities </li></ul><ul><ul><li>Storage / database </li></ul></ul><ul><ul><li>Electronic signature </li></ul></ul><ul><ul><li>Fax from system </li></ul></ul><ul><li>Increasing demand for electronic report to central repository </li></ul><ul><ul><li>Inconsistent requirements for how to do this </li></ul></ul>
  3. 3. Displayable Reports Profile Abstract / Scope <ul><li>Management of Portable Document Format (PDF) formatted clinical reports </li></ul><ul><ul><li>PDF retains many desirable features of paper-based reports, e.g., controlled display format, graphics </li></ul></ul><ul><li>Creation, signature/release, and distribution </li></ul><ul><li>Report repository/archive </li></ul><ul><ul><li>Archive at one level (nominally the department) is required </li></ul></ul><ul><ul><li>Additional archive at second level (enterprise) supported </li></ul></ul><ul><li>Standard format for electronic submission to central enterprise repository/registry </li></ul><ul><ul><li>PDF document, or only document reference (URL) </li></ul></ul>
  4. 4. Displayable Reports Profile Value Proposition <ul><li>Many clinical reporting applications use, or can be readily adapted to use, PDF for their display-ready reports </li></ul><ul><li>PDF supports graphical content (critical to cardiology reports) </li></ul><ul><li>PDF allows the source system to control the “look” of the report, which is important for both clinical and business reasons </li></ul><ul><ul><li>In certain areas, it may also be a legal requirement for the presentation of a report to be identical in all presentation contexts </li></ul></ul><ul><li>The Displayable Reports Profile specifies a consistent set of actors and transactions supporting the creation, revision, intra- and inter-department transmission, and reading of reports in PDF format </li></ul><ul><li>Image Manager/Image Archive may be leveraged as departmental Report Repository </li></ul><ul><li>Distributed enterprise report storage architecture supported </li></ul>
  5. 5. Example Displayable Reports
  6. 6. Displayable Reports Profile Transaction Diagram Encapsulated Report Storage [CARD-9] Report Repository Report Manager Enterprise Report Repository Encapsulated Report Query [CARD-10] Encapsulated Report Retrieve [CARD-11] Report Reader Report Creator Encapsulated Report Submission [CARD-7] Storage Commitment [RAD-10] Encapsulated Report Submission [CARD-7] Display Retrieve Specific Info for Display [ITI-11] Retrieve Document for Display [ITI-12]        Information Source   Report Reference Submission [CARD-8] Retrieve Information for Display (RID) Profile
  7. 7. Displayable Reports Profile Actors <ul><li>Report Creator – A system that generates and transmits clinical reports. </li></ul><ul><li>Report Manager – A system that manages the status of reporting, and distributes reports to report repositories. </li></ul><ul><li>Report Reader – A system that can query/retrieve and view reports encoded as DICOM objects. </li></ul><ul><li>Report Repository – A departmental system that receives reports and stores them for long-term access. </li></ul><ul><ul><li>Must be grouped with Information Source actor - A system that responds to requests for specific information or documents and returns ready-for-presentation information to be displayed by the requesting actor. </li></ul></ul><ul><li>Enterprise Report Repository – A system that receives reports and/or references (pointers) to reports, and stores them for access throughout the healthcare enterprise. </li></ul>
  8. 8. Displayable Reports Profile Standards Used <ul><li>PDF – report content format </li></ul><ul><li>HL7 v2 – Encapsulated Report Submission, and Report Reference Submission </li></ul><ul><ul><li>ORU </li></ul></ul><ul><li>DICOM – Encapsulated Report Storage, Query, and Retrieve </li></ul><ul><ul><li>Encapsulated PDF Storage </li></ul></ul><ul><ul><li>Storage Commitment </li></ul></ul><ul><ul><li>Query </li></ul></ul><ul><ul><li>Retrieve </li></ul></ul>
  9. 9. DRPT - Standards Used Encapsulated Report Storage [CARD-9] Report Repository Report Manager Enterprise Report Repository Encapsulated Report Query [CARD-10] Encapsulated Report Retrieve [CARD-11] Report Reader Report Creator Encapsulated Report Submission [CARD-7] Storage Commitment [RAD-10] Encapsulated Report Submission [CARD-7]        Report Reference Submission [CARD-8] Display Retrieve Specific Info for Display [ITI-11] Retrieve Document for Display [ITI-12] Information Source   But how can a non-DICOM Report Manager play? MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… HL7 MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1| ED |11528-7^LN… HL7 MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1| RP |11528-7^LN… http://serv.hosp.org/app?requestType=DOCUMENT&documentUID=”1.2.3”&preferredContentType=”application/pdf” HL7 (0008,0005) IR_100 (0008,0012) 20061113 (0008,0013) 1109 (0008,0016) 1.2.8401008.… DICOM (0008,0005) IR_100 (0008,0012) 20061113 (0008,0013) 1109 (0008,0016) 1.2.8401008.… DICOM HTTP
  10. 10. Displayable Reports Profile Options and Actor Groupings <ul><li>Report Manager may support DICOM Storage option </li></ul><ul><ul><li>For use of Image Manager/Archive as Report Repository, using DICOM Encapsulated PDF </li></ul></ul><ul><li>If DICOM option not implemented, Report Manager must be grouped with Report Repository </li></ul><ul><ul><li>Allowed to implement proprietary internal communication </li></ul></ul><ul><li>DICOM Encapsulated PDF Query/Retrieve is an option for Report Repository </li></ul><ul><ul><li>If not implemented, workstations must use RID to access reports </li></ul></ul><ul><li>Enterprise Report Repository may receive either encapsulated documents, or document references </li></ul><ul><ul><li>Report Manager must support both formats (configurable) </li></ul></ul><ul><ul><li>Document reference is RID Retrieve Document for Display URL </li></ul></ul>
  11. 11. DRPT – Grouped Report Manager and Repository Report Repository Report Manager Enterprise Report Repository Encapsulated Report Query [CARD-10] Encapsulated Report Retrieve [CARD-11] Report Reader Report Creator Encapsulated Report Submission [CARD-7] Encapsulated Report Submission [CARD-7]      Report Reference Submission [CARD-8] Display Retrieve Specific Info for Display [ITI-11] Retrieve Document for Display [ITI-12] Information Source   DICOM option not implemented MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… HL7 MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1| ED |11528-7^LN… HL7 MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1|ED|11528-7^LN… MSH|^~$|… PID|1|0123456‑1||R… OBR|1|X89‑1501^… OBX|1| RP |11528-7^LN… http://serv.hosp.org/app?requestType=DOCUMENT&documentUID=”1.2.3”&preferredContentType=”application/pdf” HL7 HTTP
  12. 12. Summary of Requirements – Report Creator <ul><li>Create PDF report </li></ul><ul><li>Create HL7 v2 ORU message </li></ul><ul><ul><li>Include DICOM Study UID in OBX segment if associated with a DICOM Procedure </li></ul></ul><ul><ul><li>Encapsulate PDF in OBX segment </li></ul></ul><ul><ul><li>Set status in ORC and OBX segments </li></ul></ul><ul><ul><li>Send to Report Manager </li></ul></ul><ul><li>Does NOT persistently (long-term) store reports </li></ul><ul><ul><li>Report Manager is responsible for content of released report, and any local storage on Report Creator may become inconsistent with official report (e.g., on Patient Update) </li></ul></ul>
  13. 13. Summary of Requirements – Report Manager <ul><li>Receive PDF encapsulated in HL7 v2 ORU message </li></ul><ul><li>Manage release of report </li></ul><ul><ul><li>May release preliminary, or only final (per product feature or configured rules) </li></ul></ul><ul><ul><li>Optionally manage electronic signatures </li></ul></ul><ul><ul><li>Add cover page in PDF with correct demographics and signature/status </li></ul></ul><ul><li>Store report </li></ul><ul><ul><li>Via DICOM Encapsulated PDF to ungrouped Report Repository </li></ul></ul><ul><ul><li>Via unspecified means to grouped Report Repository </li></ul></ul><ul><li>Forward report to Enterprise Report Repository </li></ul><ul><ul><li>Via encapsulated PDF and/or via RID URL, as configured </li></ul></ul>
  14. 14. Report Manager Issues <ul><li>Must support external Report Creators, even if product groups a Report Creator with Report Manager </li></ul><ul><li>Report Manager may not restrict types of reports (report titles) it supports </li></ul><ul><ul><li>Unlike a DICOM Image Manager, which may restrict the types of images it supports </li></ul></ul><ul><ul><li>All Displayable Reports are fundamentally the same – an encapsulated PDF, which is not semantically processed </li></ul></ul><ul><li>Report Manager actor also appears in Patient Information Reconciliation Profile </li></ul><ul><ul><li>For Patient Update and Procedure Update transactions </li></ul></ul><ul><li>Report Manager may be an enterprise-level actor </li></ul>
  15. 15. Summary of Requirements – Report Repository (ungrouped) <ul><li>Receive PDF encapsulated in DICOM message </li></ul><ul><li>Serve report via RID Information Source using HTTP Get </li></ul><ul><ul><li>Summary List of Reports </li></ul></ul><ul><ul><li>Bare PDF report document </li></ul></ul><ul><li>Serve report via DICOM </li></ul><ul><ul><li>DICOM Query/Retrieve of Encapsulated PDF </li></ul></ul><ul><li>Reasonable functionality to add to Image Manager / Image Archive (PACS) </li></ul>
  16. 16. Summary of Requirements – Report Reader <ul><li>Query/Retrieve DICOM Encapsulated PDF </li></ul><ul><ul><li>Allows access to report in context of study images and evidence – retrieve of complete DICOM study will also retrieve report </li></ul></ul><ul><li>Render PDF content </li></ul><ul><li>Reasonable functionality to add to Image Display (workstation) </li></ul>
  17. 17. Summary of Requirements – Enterprise Report Repository <ul><li>Receive PDF encapsulated in HL7 v2 ORU message or Receive PDF reference in HL7 v2 ORU message </li></ul><ul><li>Serve report to enterprise via unspecified mechanism </li></ul><ul><ul><li>Additional to RID service from Report Repository actor </li></ul></ul><ul><ul><li>Enterprise Report Repository may implement references only (fully distributed architecture) </li></ul></ul>
  18. 18. DRPT and XDS <ul><li>Displayable Reports Profile specifies production of reports within an organization </li></ul><ul><li>Cross-enterprise Document Sharing (XDS) Profile specifies distribution of reports outside the organization </li></ul><ul><li>Typically, only a subset of internally generated reports will be shared outside </li></ul><ul><li>Externally shared reports must be identified with Patient ID used in the XDS “Affinity Domain” </li></ul><ul><li>XDS Document export is a reasonable function to group with the Enterprise Report Repository </li></ul>
  19. 19. More information…. <ul><li>IHE Web sites: www.ihe.net </li></ul><ul><li>Technical Frameworks, Supplements </li></ul><ul><ul><ul><li>Cardiology Technical Framework </li></ul></ul></ul><ul><ul><ul><li>IT Infrastructure Technical Framework </li></ul></ul></ul><ul><ul><ul><li>Displayable Reports Supplement </li></ul></ul></ul><ul><li>Non-Technical Brochures : </li></ul><ul><ul><ul><li>Calls for Participation </li></ul></ul></ul><ul><ul><ul><li>IHE Fact Sheet and FAQ </li></ul></ul></ul><ul><ul><ul><li>IHE Integration Profiles: Guidelines for Buyers </li></ul></ul></ul><ul><ul><ul><li>IHE Connect-a-thon Results </li></ul></ul></ul><ul><ul><ul><li>Vendor Products Integration Statements </li></ul></ul></ul>
  20. 20. <ul><li>Providers and Vendors </li></ul><ul><li>Working Together to Deliver </li></ul><ul><li>Interoperable Health Information Systems </li></ul><ul><li>In the Enterprise </li></ul><ul><li>and Across Care Settings </li></ul>W W W . I H E . N E T

×