1. IHE – Reporting viewed from Radiology Christoph Dickmann March 2007

2. What is “reporting”? Data flow = content and transport –Report formats –Messages transporting reports/ references/ statuses Workflow = control who does what on the report –Order / scheduling –Tasks/ steps –Codes  Separate these - decompose

3. Scoping: create “Imaging space” DICOM SR create make available HL7 CDA PDF SINR (+) DRPT RID + + map Q/R vs. push reports?

4. Scoping: Q/R, receive “External space” DICOM SR (MWL ref.) DICOM SR Q/R, receive display, use, store HL7 CDA (ORM, OMI) Note: grouping is not shown, although combinations may be discussed (e.g. with RID Display) DICOM enc. PDF PDF SWF, ARI DRPT, RID SWF + map SWF + HL7 CDA MWL/ GPWL ref.

5. DICOM reporting strategy on CDA

6. Resulting systems view RIS Report Creating App. Modality Evidence Creating App. DICOM App., PACS Report Translator PDF CDA Report Repository/ PACS DICOM, e.g. image, evidence, SR, MWL HL7, e.g. MDM, OMI, ORM Optional (HL7, DICOM) CDAPDF * * * Either RIS-pre- fetched encapsu- lated doc. or pointers to docs. in WL  Mod. console! ? Both for Rep.Cr. The Report Crea- ting App. should not need to query for “any” report. But it may be grouped with an RID Display. The RIS should not need to query for “any” report. But it may be grouped with an RID Display or XDS(-I) Consumer. Department boundary

7. Insight on “Data Flow” Existing reporting profiles cover much of the needs  no completely different new profiles needed –New profiles cannot guarantee faster/ better acceptance and product implementation Rather re-use/ extend existing profiles Rather clarify existing profiles (e.g. Report Manager)

8. Proposed next steps Decide about approach –Separate data and work flow –Role of DICOM strategy –Assess pros/cons of existing profiles incl. content-related role of Report Manager Decide about content and data flow –What if there is no RIS? –Recommend actor groupings? Decide about workflow