Milestone 2
Description of Milestone 2: Building Health Information Provider (HIP) services to share digital records via any Personal Health Records (ABHA) app.
Test Cases
Health Information Provider initiated for Health Records (Any of the 4 methods defined must be demonstrated for HIP Initiated Linking. It is recommended to implement all the 4 methods)
Test Cases for Health Information Providers (HIP)
| S.No | Function | Functionality | Test Case | Steps To Be Executed |
|---|---|---|---|---|
| 1.1 | Health Record Creation | Mandatory Creation of Health Records (Health_RECORD_CREATION_101) | The system should have a provision to create digital health records | 1. Check if digital Health Records are being created in HIP systems (valid for HI types as applicable to the integrating entity). 2.Recommend to have the health record in FHIR format. |
| 2.1 | HIP Initiated Health Record Linking Using Mobile OTP | Mandatory Link record via mobile OTP (HIP_INTI_LINK_201) | The system should have provision to link patient’s Health record with ABHA address | 1. Enter patient’s ABHA address on the System. 2. OTP receive by the patient. |
| 2.2 | HIP Initiated Health Record Linking Using Mobile OTP | Mandatory OTP validation (HIP_INTI_LINK_203) | The user shares the OTP with the HIP for validation | 1. Share Mobile OTP with HIP System. 2. Validate the OTP. 3. Upon successful validation of OTP |
| 2.3 | HIP Initiated Health Record Linking Using Mobile OTP | Mandatory Linking of Health Records (HIP_INTI_LINK_205) | HIP system links the ABHA Number / Address with the patient records | 1. Link Health Records. 2. Through PHR Application |
| 3.1 | HIP Initiated Health Record Linking Using Aadhaar OTP | Mandatory Link record via aadhaar linked mobile OTP (HIP_INTI_LINK_301) | The system should have provision to link patient’s Health record with ABHA address | 1. Enter patient’s ABHA address on the System. 2. OTP receive by the patient. |
| 3.2 | HIP Initiated Health Record Linking Using Aadhaar OTP | Mandatory OTP validation (HIP_INTI_LINK_303) | The user shares the OTP with the HIP for validation | 1. Share Mobile OTP with HIP System. 2. Validate the OTP. 3. Upon successful validation of OTP |
| 3.3 | HIP Initiated Health Record Linking Using Aadhaar OTP | Mandatory Linking of Health Records (HIP_INTI_LINK_305) | HIP system links the ABHA Number / Address with the patient records | 1. Link Health Records. 2. Through PHR Application |
| 4.1 | HIP Initiated Health Record Linking Using Direct Auth | Mandatory for the Govt. Integartors Direct Auth mode for Linking of Health Records (HIP_INTI_LINK_401) | The system should have provision to link patient’s Health record with ABHA address | 1. Enter patient’s ABHA address on the System. 2. The user logs into their PHR Application |
| 4.2 | HIP Initiated Health Record Linking Using Direct Auth | Mandatory Linking of Health Records (HIP_INTI_LINK_404) | HIP system links the ABHA Address with the patient records | 1. Link Health Records. 2. Through PHR Application |
| 5.1 | HIP Initiated Health Record Linking Using Demographic Auth | Mandatory for the Govt. Integartors Link record via Demographic Auth (HIP_INTI_LINK_501) | The system should have provision to link patient’s Health record with ABHA address. | 1. for the verified ABHA Address of the patient in the HIP System. 2.The user provides their demographic details (name, gender, DOB, mobile number). 3. Enter user/patient’s demographic details in the HIP System |
| 5.2 | HIP Initiated Health Record Linking Using Demographic Auth | Mandatory Validate the demographic details (HIP_INTI_LINK_503) | The HIP validates demographic details of patient | 1. Validate Demographic Details ( Provided by the user and fetch by the ABHA address). 2.Upon successful validation of OTP |
| 5.3 | HIP Initiated Health Record Linking Using Demographic Auth | Mandatory Linking of Health Records (HIP_INTI_LINK_505) | HIP system links the ABHA Address with the patient records | 1. Link Health Records. 2. Through PHR Application |
| 6.1 | Sending Notification for deep link workflow | Mandatory Sending notification to the patient on their mobile with deep link (HIP_INIT_NOTIFY_HIECM) | HIP should notify HIE-CM when a new health record is generated & ABHA address is not available. This test case is applicable when patient has shared mobile number and has NOT shared ABHA address with HIP during patient registration. | 1. New health record like Diagnostic report, Prescription, etc is created on EMR/HMIS system for a patient. 2. Mobile number of patient is available in EMR/HMIS system and ABHA address of the patient is NOT available in EMR/HMIS system. 3. EMR/HMIS system will call the SMS/notify2 API on the gateway to inform of available of new health record (only the mobile number and the HIP ID is to be shared). 4. ABDM should be sending notification to the patient on their mobile with deep link. 5. Patient should be able to download/launch PHR app of their choice. 6. PHR app will make a discovery request to the HIP. 7. Care context for New patient record must be correctly discoverable in the PHR app. |
| 7.1 | Grant Consent Request | Mandatory HIP must save consent (s)granted for a ABHA address in their system (HIP_INIT_GRANT_CONSENT_) | 1. Initiate a new consent request for HIP on HIU web interface on sandbox. 2. Grant the request for this consent on PHR app. 3. HIP will be notified of granted consent request. 4.Verify the HIP has saved the granted consent request as part of EMR/HMIS system | |
| 8.1 | Revoke Consent Request | Mandatory HIP must delete consents for a ABHA address in their system when it is revoked (HIP_INIT_REVOKE_CONSENT) | 1. Select a granted consent request for this HIP in the PHR app. 2. Revoke consent on PHR app. 3. HIP will be notified of revoked consent. 4. Verify the HIP has deleted the consent as part of EMR/HMIS system upon revoke by patient | |
| 9.1 | Expire Consent Request | Mandatory HIP must delete consents for a ABHA address in their system when it is expired (HIP_INIT_EXPIRE_CONSENT) | 1. Initiate a new consent request for HIP on HIU web interface on sandbox. 2. Grant the consent on PHR app; Set the expiry to a short expiry time. 3. HIP will be notified of granted consent request. 4. HIP will be notified of the expired consent post expiry time. 5.Verify the HIP has deleted the expired request as part of EMR/HMIS system | |
| 10.1 | ABHA Deactivation | Mandatory HIP must delete ABHA address & all associated consents in their system when patient opts out of ABDM (HIP_INIT_ABHA_OPTOUT_DEACTIVATE ) | HIP must delete ABHA address & all associated consents in their system when patient opts out of ABDM. | |
| 11.1 | Data Transfer & Share | Mandatory HIP must share health records associated with care context on request (HIP_INIT_SHARE_CARECONTEXT) | 1. Initiate a ““Get data”” for a linked care context in the PHR app. 2. HIP will receive a request to share information along with the consent id & end-point URL where the data must be pushed. 3. HIP must verify that there is a valid consent for sharing this data with the specific HIU making the request. 4. Health records must be shared only for allowed HIP types withing the date ranges granted in the consent. 5. HIP should encrypt the health records to be shared with the HIU public key. 6. HIP should push the encrypted data to the end-point URL. 7. On successful transfer, HIP must notify HIE-CM of successful transfer by calling health information notify API. 8. Transfer must be completed within 2 hours of receiving the request. |
Test Cases for PHR Applicationlication
| S.No | Function | Functionality | Test Case | Steps To Be Executed |
|---|---|---|---|---|
| 1.1 | User Initiated Health Record Linking | Mandatory Search for Facility/ HIP (USER_INIT_LINK_602) | 1. Patient logs in PHR Application. 2. PHR Application must provide an option to search health providers (provider can be hospitals, labs, clinics, nursing home, doctor, govt Health program, telemedicine provider | 1. Search for required HIP. 2. Select that HIP |
| 1.2 | User Initiated Health Record Linking | Mandatory Share User Profile Details with Facility/ HIP (USER_INIT_LINK_603) | PHR Application must share user’s profile details (Mobile no., ABHA Number, ABHA Address, Name, Gender, Year of Birth and Patient ID (optional) with the Facility/HIP. | Profile Details will be shared. |
| 1.3 | User Initiated Health Record Linking | Mandatory Fetch Health Records (USER_INIT_LINK_604) | PHR Application must fetch/ receive Health Records available with the selected HIP/ Facility for the shared profile details. | Receive list of Health Records that are available with the Facility/ HIP |
| 1.4 | User Initiated Health Record Linking | Mandatory Provide Consent for Health Record Linking (USER_INIT_LINK_605) | PHR Application will prompt to enter an OTP received on the user’s mobile number. | 1. Select “Link Health Records” on PHR Applicationlication. 2. Receive OTP on mobile number. 3. Enter OTP and provide consent for health record linking. |
| 1.5 | User Initiated Health Record Linking | Mandatory Pull Records (USER_INIT_LINK_607) | In PHR Application user will able to pull the records. | Through PHR Applicationlication,check if the linked records can be pulled |
| 2.1 | SHARE PROFILE | Mandatory Share Patient Profile (SHARE _PATIENT_PROFILE_701) | User will scan the QR code which is placed the facility premises. | 1. Log into PHR Application. 2. User will scan the QR code which is placed the facility premises. 3. Post scanning, patient profile details are displayed including ABHA number, ABHA address, Name, Gender, DoB, Mobile No and Address. Below this consent language is displayed - “You consent to the above information to be shared with (HIP Name). They can use this information for your registration and linking your health records” and both “Cancel” / “Share” buttons are provided. 4.Check that after clicking on “Share” button, user profile is successfully shared with the HIP and if user click on “Cancel” button then user profile is not shared with the HIP. 5. User clicks on share and gets a token number. 6. User clicks on ok and gets token number with validity of 30 minutes. |