Page Comparison

Table of Contents

style	none

Introduction

For partners that wish to submit and or receive a Service Request using the CIE Hub this playbook will explain the requirements needed for partners who wish to provide the user interface functionality to send and receive Referrals through the CIE Hubfor that functionality.

Integration Use Cases

The requirements can be broken down into four main use cases. Below is a brief description of what user each use case with a main flow of the user case following.

As a partner of the CIE Hub I want to submit a electric an electronic referral on behalf of a community member to provide request support to that community member.
1. User selects a organization’s service through the MI211 directory
2. User fills out the community members information including Name, contact phone number, address (optional)
3. Call User system calls the Patient POST API
4. User fills out the Service Request given providing a category and code that describes the request
5. Call User system calls the CIE Bundle API with the Service Request and any observations
As a partner of CIE Hub I want to receive a list electric of electronic referrals that are open to contact have been designated for my organization to service by contacting the community member and provide providing support.
1. User selects to get a list of Service Requests that are assigned to them.
2. Call the CIE Hub API to get the ServiceRequests
As a partner of the CIE Hub I want to update the status of the Service Request to provide a update to the sender of the Service Request.
1. User selects the Service Request to update
2. User selects the status from a drop down
3. Call CIE Hub API to update the Service Request
As a partner of the CIE Hub I want to get information on a Service Request that I have submitted to the CIE Hub.
1. User selects the Service Request that was submitted
2. Call the CIE Hub API to get the Service Request
3. Show the user the information