SYSTEM INTEGRATION Gbor Garnyi System Integrator 1 What
SYSTEM INTEGRATION Gábor Garányi System Integrator
1. What is system integration? • Developing an interface for the software to establish communication • Both Case. Center and HIS/LIS (Hospital/Lab Information System) need an interface to communicate • Main Case. Center integration features: o. Barcode parsing o. Folder structure and slide names o. Provide Links
1. What is system integration? The first steps: • Do they have a HIS/LIS? • Fill the online questionnaire • What type of integration do they need? (Type 1 -2 -3? ) • What communication method should we use? (XML or HL 7 based? ) • The main goal is to implement the main integration features
1. What is system integration?
2. Case. Center integration types Integration types: 1. Case. Center System Integration Support 2. Case. Center Basic XML/HL 7 Integration 3. Case. Center Custom XML/HL 7 Integration
2. Case. Center integration types 1. Case. Center System Integration Support: • • • Using the exising interface of Case. Center 3 DH hands over the documentation and specification and provides support for the LIS developers The LIS vendor has to develop an interface HL 7 and IHE Pa. LM standards Utilizes all the main integration features of Case. Center
2. Case. Center integration types 2. Case. Center Basic XML/HL 7 Integration: • Development on 3 DH side or the LIS vendor side, or maybe on both sides • Common communication protocol • Basic integration features only, no new feature development
2. Case. Center integration types 3. Case. Center Custom XML/HL 7 Integration: • Development on 3 DH side or the LIS vendor side, or maybe on both sides • Common communication protocol • Custom integration features can be implemented after feasibility check
3. Case. Center communication types XML based communication: • both human-readable and machinereadable • supports Unicode for different human languages • is able to represent most of the general computing data structure (record, list, tree. . . ) • self-documenting (or self-describing) code • free and open standard
3. Case. Center communication types XML message examples: ADD or DELETE slide Link to an image
3. Case. Center communication types Various data in XML message:
3. Case. Center communication types HL 7 based communication: • the first standard protocol for communication between Electronic Health Record components • independent of the vendor • connect to any system that supports this particular part of the standard, both now and in the future
3. Case. Center communication types HL 7 based communication: • HL 7 implementations differ between vendors as well. The reasons why it’s not a plug-and-play solution is due to missing fields and values, duplication of data in fields and formats and different versions • HL 7 is supported by more than 1, 600 members from over 50 countries
3. Case. Center communication types Simplified HL 7 communication example step by step:
4. Case. Center integrations Hospital or Laboratory Location HIS/LIS vendor HIS/LIS name Comm. type Kantonsspital St. Gallen (CH) Basysdata Patho. Win WEB based Atrium Medical Center Heerlen (NL) Palga Foundation Palga XML Jan Yperman Hospital Development time 3 man-week (incl. Support) 2 man-week (1 man-month with Support) Bács-Kiskun Megyei Kecskemét (HU) Kórház Skyline Computer Custom Application XML no development on our side 2 -3 man-month (the first CC integration project) PAL, Laboratorium voor Pathologie Dordrecht (NL) Finalist Noord Nederland B. V. LMS/Fina. Lims 3+ man-month Ieper / Ypres (BE) Pegasus WEB based
4. Case. Center integrations Hospital or Laboratory Hetényi Géza Kórház Memorial Sloan Kettering Cancer Center Synlab / Technipath Location Szolnok (HU) New York (US) Limonest (FR) HIS/LIS vendor Globe. Net Cerner Log. System HIS/LIS name Med. Work. S Co. Path. Plus Cyan Comm. type Development time HL 7 5 man-week CC, 3 -4 man-week CV, +Quality management, +background work, +validation HL 7 3 -4 man-week (incl. Support) XML 2 -3 man-month (2 years project) University Hospitals of Paris-Sud Bicêtre. Paris (FR) Infologic Diamic Shiga Hospital Japanese Distributor Custom Application File-based custom 2 -3 man-week Ritto (JP)
4. Case. Center integrations Hospital or Laboratory SOTE I. Patológia Location Budapest (HU) SOTE II. Patológia Budapest (HU) Multiple hospitals/labs Soproni Gyógyközpont HIS/LIS vendor ISH KFT. T-Systems Multiple endpoints (DE) Nexus AG Sopron (HU) Globe. Net HIS/LIS name Med. Sol Comm. type Development time XML 1 -2 man-week Med. Sol HL 7 1 -2 man-week, incl. Track&Sign Nexus/Pathologie HL 7 initial state, incl. Track&Sign Med. Work. S
5. DICOM Integration with: • • Scanners Servers, Workstations, Printers Network Hardware Picture Archiving and Communication System (PACS) Multiple manufacturers Widely adopted standard Licensed, not free
5. DICOM in Whole Slide Imaging: • Today’s PACS are only for radiology • PACS can’t hande big files • Other vendors can import DICOM images, but they can be opened with their viewer only • Every vendor is creating its own format • DICOM writes other data (e. g. patient ID) in the files but Whole Slide Images are not prepared for this • No fully functional systems yet, lack of compatibility
5. DICOM and 3 DHISTECH: Participating in DICOM Work. Group-26 Opening DICOM slides in Case. Viewer DICOM snapshot in Case. Viewer Supporting FL scans Storing data in other files besides MRXS (100% compatible with DICOM PACS) • Our DICOM slides are meeting the requirements of Supplement 145 • Creating own worlist server • • •
Thank you for your attention! Visit our website and follow our social media channels:
- Slides: 21