CS 493 Project Definition

1. CS 493 Project Definition • The project assignment is a simplified version of the Integrating Healthcare Enterprise (IHE) Cross-Enterprise Document Sharing (XDS) Profile • Web site: http://www.ihe.net/Technical_Framework/ • A number of simplifying assumption is made and a few corners cut to make this a viable class project • Goal of the project is to be able to do the following: • Ability to build a distributed solution using web services infrastructure • Ability to build RELIABLE distributed systems • Ability to build distributed solutions that utilizes both synchronous and asynchronous messages

2. IHE Cross-Enterprise Document Sharing (XDS) Profile • Ability for a source of clinical documents to register and store documents in a repository • Ability for a consumer of clinical documents to query registry and retrieve documents from a repository Website: Volume 1: (ITI TF-1): Integration Profiles Volume 2: (ITI TF-2): Transactions

3. Number of simplifying and not so simple assumptions • One patient identifier domain • Few (two to three) document sources • One registry – but in this project will call for replicated registry to increase reliability and availability • Only look at some of the key required transactions and completely ignore optional transactions defined in this integration profile

4. Actors

5. Actors and Transactions

6. IHE XDS Scheme Patient Identity Source Ignore for the purpose of the project Patient Identity Feed [ITI-8] Document Registry Document Consumer Query Registry [ITI-16] Register Document Set [ITI-14] Document Repository Document Source Retrieve Document [ITI-17] Provide Document Set [ITI-15]

7. Project Implementation Configuration Document Registry Document Source + Document Repository Document Consumer Document Source + Document Repository

8. Relevant Sections Volume I • 10 Cross-Enterprise Document Sharing (XDS), pg 69-96 provides background information Volume II • 3.14 Register Document Set pg 86-127 • {Ignore the following sections: • 3.14.4.1.2.3.4 , • 3.14.4.1.2.3.5, • 3.14.4.1.2.5, • 3.14.4.1.2.9, • 3.14.4.1.2.10, • 3.14.4.1.2.15 } • 3.15.4.1.2.3.1.1 General structure and header, pg 131 • 3.16 Query Registry pg 139-144. • 3.17 Retrieve Document pg 159-163

9. General Requirements • Documents that needs to be submitted: can be one of: • CDA documents {I will provide samples} • PDF or Word documents • Must simulate sample clinical data • Document Metadata that needs to be captured • Patient Id • Service start and stop time • Document Creation time • Document Class Code and Display Name • Healthcare Facility Type Code and Display Name • Availability Status • Document Unique Id • Registry Implementation • Should use replication to improve reliability

10. Project Teams • You can do it alone • You can do it in a team of two or three • Project scope will be scaled up and down based on whether it is a team or not.

11. Project Timeline • March 9th • Sequence Diagrams, Requirements that are going to be addressed & Preliminary Design – 6 Pts • March 23rd • Design Documents – Class diagrams – 6 Pts • April 6th • First demonstration – Submission of documents to registry – 9 Pts • April 27th • Project Final demonstration – Full scenario – 9 Pts