Skip to content

Instantly share code, notes, and snippets.

@khavinshankar

khavinshankar/ABDM M2 Testing.md

Created April 26, 2023 14:36
Show Gist options
  • Save khavinshankar/5dcd9c89830c72aae7c5c70acb87bb23 to your computer and use it in GitHub Desktop.
Save khavinshankar/5dcd9c89830c72aae7c5c70acb87bb23 to your computer and use it in GitHub Desktop.
Download ZIP
ABDM M2 Testing
Raw
ABDM M2 Testing.md

1. USER_INIT_DISCOVER_CARE_CONTEXT_01

  1. User logs in PHR app
  2. User seraches for health provider ( provider can be hospitals, labs, clinics, nursing home, doctor, govt health program, telemedicine provider) It is important that the HIP should be easily identifiable by the user to search for their health records. User can add a specific identifier provided by the health provider to improve discovery. (for example - Hospital Patient id)
  3. User consents to sharing their demographic details with HIP
  4. HIP get Demographic information including verified and unverified identifier.
  5. HIP searches their records for any of the verified identifers; Most commonly search should be first done on ABHA address; if no match then search with Mobile number. On mobile number match HIP to do a fuzzy logic match on matched records.
  6. HIP does a fuzzy demographic match ( similarity on name ; +/-2 on age ; gender - exact match)
  7. HIP returns list of care context for the matched user.

image

2. USER_INIT_LINK_CARE_CONTEXT_02

  1. User does a discovery request with the provider and get the list of care context.
  2. User should be able to select a care context ( multiple selection - in future - under development) and initiate linking.
  3. HIP must send a OTP to the verified id ( typically, mobile / email)
  4. User to enter OTP on PHR app
  5. HIP must link the care context if the OTP matches

image

3. HIP_INIT_LINK_CARE_CONTEXT_01

  1. New health record like Diagnostic report, Prescription, etc is created on EMR/HMIS system for a patient
  2. ABHA address of the patient is available in EMR/HMIS system
  3. EMR / HMIS system checks if it has unused linking token. This linking token is obtained usually during registration.
  4. If no linking token is available then system obtains new token by performing a demographic auth on the gateway.
  5. Care Context is linked with the ABHA address on the HIE-CM
  6. Display text in the care context must provide information to the patient that helps them recognize the type of health records.

image

4. HIP_INIT_NOTIFY_HIECM_02

  1. New health record like Diagnostic report, Prescription, etc is created on EMR/HMIS system for a patient
  2. ABHA address of the patient is available in EMR/HMIS system
  3. EMR / HMIS system checks if health record will be part of an already exsting care context
  4. EMR/HMIS system will call the notify API on the gateway to inform addition of new health record to an existing care context.

image

5. HIP_INIT_NOTIFY_HIECM_03

  1. New health record like Diagnostic report, Prescription, etc is created on EMR/HMIS system for a patient
  2. ABHA address of the patient is NOT available in EMR/HMIS system
  3. Mobile number of patient is available in EMR/HMIS system
  4. 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)

image

6. HIP_INIT_GRANT_CONSENT_04

  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

image

7. HIP_INIT_REVOKE_CONSENT_05

  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

image

8. HIP_INIT_EXPIRE_CONSENT_06

  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

image

9. HIP_INIT_ABHA_OPTOUT_07

image

10. HIP_INIT_SHARE_CARECONTEXT_08

  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 its long term private 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.

image

11. HIP_INIT_HEALTHRECORD_TYPE_09

  1. Create a health record for each type of posible records in the EMR / HMIS system for a patient
  2. Link the care context and initiate a data transfer
  3. Obtain copy of all the type of records in a test HIU system

image

12. HIP_INIT_HEARTBEAT_10

  1. Ensure heartbeat API has been implemented by the EMR / HMIS

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment