1 / 15

Atsushi Amano Medical Imaging Systems Committee

JAHIS / IHE-J Activity Update - Re: Endoscopy Domain -. Atsushi Amano Medical Imaging Systems Committee Japanese Association of Healthcare Information Systems Industry (JAHIS). JAHIS Endo Data Exchange Protocol Ver2.0 IHE Endoscopy Technical Framework

lottiet
Download Presentation

Atsushi Amano Medical Imaging Systems Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JAHIS / IHE-J Activity Update - Re: Endoscopy Domain - Atsushi Amano Medical Imaging Systems Committee Japanese Association of Healthcare Information Systems Industry (JAHIS) 20/11/2009 DICOM WG13

  2. JAHIS Endo Data Exchange Protocol Ver2.0 IHE Endoscopy Technical Framework About IHE Endoscopy Domain Establishment (preliminary…) Contents 20/11/2009 DICOM WG13

  3. JAHIS Endo Data Exchange Protocol Ver2.0 JAHIS & IHE-J • JAHIS (Japanese Association of Healthcare Information Systems Industry) is one of the member groups that established IHE-Japan. • JAHIS/IHE-J studied the contents of IHE Endoscopy VolⅡ(Transaction) after publishing VolⅠ( trial implementation version). JAHIS/IHE-J determined to proceed HL7 part of IHE Endoscopy as JAHIS data exchange protocol. Ver1.0 has been published last summer. Now, we are about to complete Ver2.0. 20/11/2009 DICOM WG13

  4. Done Future Work JAHIS Endo Data Exchange Protocol Ver2.0 JAHIS & IHE-J Document ＜IHE Endoscopy＞ IHE Endoscopy VolⅠ Profile IHE Endoscopy VolⅡ Transaction ＜JAHIS Endo Data Exchange Protocol＞ HL7 Part JAHIS Endo Data Exchange Protocol Ver1.0 We categorized the scope of IHEVolⅡfrom technical point of view and determined to complete each part one by one. Order Transaction Performed Data Transaction Ver2.0 DICOM Part About to be completed 20/11/2009 DICOM WG13

  5. JAHIS Endo Data Exchange Protocol Ver2.0 Transactions ＥＩＳ ＰＡＣＳ ②Patient Information notification ②Patient Information notification ⑤Endoscopy notification ＨＩＳ ④Endoscopy order ⑥Endoscopy result query Image Status etc. ①Patient Information Query ③Endoscopy order query ②Patient Information notification ⑦Patient arrival notification ⑤Endoscopy notification ⑩Performed Data notification ⑧Observation report status notification ＲＥＰＯＲＴ ⑨Observation report notification 20/11/2009 DICOM WG13

  6. JAHIS Endo Data Exchange Protocol Ver2.0 How to send performed data?(1) • OMI （Event Z23) Imageing Order Message • MSH Message Header • [ { NTE } ] Notes and Comments (for Header) • PID Patient Identification • [ { NTE } ] Notes and Comments (for Patient ID) • PV1 Patient Visit • [ PV2 ] Patient Visit 2 • [ { AL1 } ] Allergy • { • ORC Order Common • { • TQ1 Timing/Quantity • [ { TQ2 } ] Timing/Quantity Order Sequence • } • OBR Observation Request • [ { NTE } ] Notes and Comments (for Detail)) • [ { • OBX Observation/Result • [ { NTE } ] Notes and Comments (for Results) • } ] • [{ • ZE1 Billing Segment • [ { OBX } ] Observation/Result • }] • { IPC } Imaging Procedure Control • } 20/11/2009 DICOM WG13

  7. JAHIS Endo Data Exchange Protocol Ver2.0 How to send performed data?(2) • Z segment (ZE1) to send procedure data • Performed Procedure • Following OBX to describe the details about the procedure • Performers • Equipments used • Materials used (medicine etc.) • Performed time (start, end, biopsy execution time , etc.) • Additional information for the Japanese insurance system • ……. 20/11/2009 DICOM WG13

  8. JAHIS Endo Data Exchange Protocol Ver2.0 Comments at previous meeting • Why didn’t we use Charge Posting profile? • As I noted, we are not intending to send only billing data but more comprehensive data set as performed information. • What if HL7 be enhanced to describe Japanese billing situation? Some confusion may happen on the usage of z-segment. • As stated above, more comprehensive data should be sent. • Also if it happens, we can control Japanese domestic situation. 20/11/2009 DICOM WG13

  9. JAHIS Endo Data Exchange Protocol Ver2.0 Schedule • 2009 November: Completion of the draft • 2009 December-2010 January: Public Comment • 2010 February: To be Published • English version should be prepared soon! 20/11/2009 DICOM WG13

  10. Scope of Anatomic Pathology ADT → 6 Pre-procedure PPS → 7 Modality PPS in Progress → 8 Specimen PPS → 9 Modality PPS Completed → 24 Post-procedure PPS ← 1 Pt.Registration ← 21 Pt.Update → 1 Pt.Registration → 21 Pt.Update Placer Order Management　→ e-Order Filler Order Placer Pathology Order Filler ← 2 Placer Order Management → 3 Filler Order Management → Patient Arrival／Report Completion ← 4 Procedure Scheduled ↓ 4 Procedure Scheduled ↓ 25 PtUpdate ↓26 Procedure Update ↑ 13 Image Availability Query e-PPS Manager Pre/Post Procedure Terminal Image Manager Image Archive → 7 Modality PPS in Progress → 9 Modality PPS Completed ↑ 10 Modality Image Stored ↑ （11 Modality Presentation State Stored） ↑ 12 Storage Commitment → 5 Modality Worklist Provided Acquisition Modality ←　7 Modality PPS in Progress ←9 Modality PPS Completed → 5 GP Worklist Provided Specimen Manager Specimen Ｌａｂｅｌ Printer ← 8 Specimen PPS ← 14 Query Images ← (15 Query Presentation State) ← 16 Retrieve Images ← (17 Retrieve Presentation State) Report Creator Image Display Report Manager → 4 Procedure Scheduled → 25 PtUpdate　→ → 26 Procedure Update ← Report Status → Pathology Order Message Report Repository Blue: HL7 Messages Green: DICOM Messages Report Reader Manual Input by Men IHE Endoscopy Technical Framework Integration Profile “Endo” HIS EIS PACS Report 20/11/2009 DICOM WG13

  11. IHE Endoscopy Technical Framework Challenges and Solutions • It describes everything in one profile. • Not many users intend to implement all of them at a time. • Small facility does not need everything described here. • We need a guide line about, • What should be implemented the first? • What level of implementation should be preferable? • We determined to reconstruct integration profile. • Based on implementation load map. • Adoption of ITI-PAM for patient data communication. 20/11/2009 DICOM WG13

  12. IHE Endoscopy Technical Framework Implementation Load Map Goal：actors are interoperable based on one standard…Paradise! 1.First you should define interoperability between HIS & EIS (Department System). The 3rd Step Image Archiving System The 2nd Step Reporting System 3.Then you should complete the endoscopy system. 2. Next, you should standardize the most important function in the endoscopy suite. The 1st Step Interoperability between HIS &EIS Scope of the first draft of Endoscopy TF1&2 20/11/2009 DICOM WG13

  13. IHE Endoscopy Technical Framework Endoscopy Workflow -- EWF Order Trigger Manager OP HIS • Endoscopy Order (Required) • Patient Arrival Notification (R) • Endoscopy Report Notification for Path Order (R) • Performed Data Notification (R) • Endoscopy performance Order (Optional) • Report Status Notification (O) ① ② ④ ③ ⑤ Execution Information Creator Report EOF Endoscopy System ⑥ 20/11/2009 DICOM WG13

  14. About IHE Endoscopy Domain Establishment (preliminary…) IHE Endo Domain Establishment • Who should be the domain Spons0r? • JAHIS may be the domain sponsor. (Preliminary: Under discussion & negotiation in JAHIS) • Expected schedule? • 2009 Nov. Final decision in JAHIS • 2010 Mar. Application from IHE-J/JAHIS • ---- Preparation Meeting? ------ • 2010 November. Starting Activity Officially • How about user participation? • During domain establishment, we (all of us here today!) should actively work on user association (JGES, ACG, OMED ,etc) to participate IHE. 20/11/2009 DICOM WG13

  15. Thank youfor your attention 20/11/2009 DICOM WG13

More Related