Queries for ABDM Integration

General Query
#1

Hi @all
@Ramandeep1, @Govind_Deshmukh, @Shubhanshu_S

We are on the implementation of ABDM. M1 is integarted successfully. Now we are on working with M2 and M3. Please look at the following Queries and update the proper response.

  1. Linking token we got for linking care context has no expiry until it is used for linking a care context. right? I generated a linking token and didn’t use it for linking. After a day or two, if i try to link care context using the same linking token, I couldn’t. some errors will be generated. Then I need to generate another linking token and need to link care context using the new linking token.
  1. Each time Patient requests for a data pull, HIP should process the request and make a bundle, encrypt and send over against each time?
  1. Can we use this API for Validating FHIR Json (https://inferno.healthit.gov/validatorapi/validate?profile=http://hl7.org/fhir/StructureDefinition/Bundle)?
    Each time need to validate and send back fhir data?
    Is validation mandatory?

Suppose, prescription and diagnosticreport data are requested, when validating prescription validated ok and diagnosticreport failed to validate. then how we manage the failed one?
only need to send successfull fhir data to requester?

  1. Which Timezone needed to use (UTC or Asia/Kolkata)?
  1. In consent grant screen in ABHA App, when try to edit the consent before grant, We can select HIPs with check box, but under HIP, we couldn’t uncheck any of the care context. If we do so, Update button disabling(can’t update)
  1. Suppose in a granted consent, 3 care context with 4 HiTypes, The HIP should Create a bundle for each HiType and for all 3 care context…ie, 4 Bundles x 3 care context = 12 bundles and this need to encrypt and send to HIU.
    Correct me if I’m wrong.
  1. HIU once pulled a record from HIP, can HIU save this record and view from database?
    Next time same consented request can viewed from Database by ignoring all the consent fetch, encryption etc…?
    or .Each time encrypt and decrypt fhir data on run and deliver to request?

Please look at these queries and update response asap.

Thanks and Regards
SALAHUDHEEN

createdAt is coming in IST instead of UTC
#2

Hi @All Answering all Questions:-

  1. Answer it will be valid for only 24 Hour from the time of Creation.
  2. Answer Yes you have to Encrypt and Send over against each time.
  3. Answer You can use this API for Validating FHIR Json:-
    https://validator.fhir.org/
  4. Answer You have to use UTC only in this formate:
    const moment = require(‘moment’);
    pm.globals.set(“timestamp”, moment.utc().format(“YYYY-MM-DDTHH:mm:ss.SSSSSS”));
  5. Answer We have Made a jira ticket ABHAAPP-603, 604 and Will Update you on this.
  6. Answer Yes you need to do so.
  7. Answer No HIU Cannot save this Record in Database.
#3

Hi @All Linking tokan will be valid for 6 Hours. correct for Answer 1

#4

Hi @Deepak-LTI

Thanks for the update and it will be very helping in the development.

That means we need to reset the linking token already got after 6 hours, if it’s not used for a care context linking. right?

Regards
SALAHUDHEEN

#5

Yes you need to do so

#6

Ok. Thanks @Deepak-LTI