1 / 5

Use Case 1 (Physician Initiated Consultation)

A system for facilitating physician-initiated and patient-initiated consultations, transfers, and document exchanges in healthcare settings. Supports specific disciplines, scheduled workflows, and organizational boundaries.

woneil
Télécharger la présentation

Use Case 1 (Physician Initiated Consultation)

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. Use Case 1 (Physician Initiated Consultation) Consulting Physician Patient Referring Physician Special Handling Consultation Transaction (new) Select Consultant Referring Requester Dispatch 4 2 Document Source 3 Specific Discipline Scheduled Workflow Transaction Existing XD* Transactions Document Consumer 1 XD* Existing XD* Transactions Must take place before Consultation transaction Patient Specific Discipline Scheduled Workflows Organizational Boundary (XD* location is not significant)

  2. Use Case 2 (Patient Initiated Consultation) Consultation Transaction (option A) Consulting Physician Referring Physician Patient 2 Special Handling Token Delivery (option B) Select Consultant Token Acceptance (option B) 3 5 Referring Requester Dispatch Document Source Consultation Transaction (option B) 4 Specific Discipline Scheduled Workflow Transaction Existing XD* Transactions Document Consumer XD* 1 Existing XD* Transactions Must take place before Consultation transaction. (Media transaction can be simultaneous) Specific Discipline Scheduled Workflows Organizational Boundary (XD* location is not significant)

  3. Use Case 3(Physician Initiated Transfer) Consulting Physician Patient Referring Physician Special Handling Transfer Transaction (new) Select Consultant Referring Requester Dispatch 4 2 Document Source 3 Specific Discipline Scheduled Workflow Transaction Existing XD* Transactions Document Consumer XD* 1 Existing XD* Transactions Must take place before Consultation transaction Existing XD* Transactions Specific Discipline Scheduled Workflows Transfer transaction includes acknowledgement of Responsibility by the Consulting Physician. Organizational Boundary (XD* location is not significant)

  4. Use Case 4 (Patient Initiated Transfer) Transfer Transaction (option A) Consulting Physician Referring Physician Patient 2 Special Handling Token Delivery (option B) Select Consultant Token Acceptance (option B) 3 5 Referring Requester Dispatch Document Source Transfer Transaction (option B) 4 Specific Discipline Scheduled Workflow Transaction Existing XD* Transactions Document Consumer 1 XD* Existing XD* Transactions Must take place before Consultation transaction. (Media transaction can be simultaneous) Existing XD* Transactions Specific Discipline Scheduled Workflows Organizational Boundary (XD* location is not significant)

  5. XD* Document List • Must comply with an IHE Discipline list of required objects. These will include CDA documents (e.g., PCC Referral documents), and may include other documents (e.g., DICOM SOP Instances). The ITI will depend on disciplines to specify their minimum list. A documents like those defined in PCC are the expected minimum list, but this might also be used in areas that need different documents. • Consultation and Transfer Transactions will convey a list of referenced documents (UUIDS, OIDS) so that dispatcher can use XD* to obtain documents • XD* is used throughout to remind us that this should work with media, not just with healthcare networks. • The Transfer and Consultation transactions will not be documents. There are likely to be documents created that record the performance of these transactions.

More Related