1) 1.1
=> can we add that for certification process 2 milestones are mandatory
=> Demo your application to HTC (Health Tech Committee) (ABDM Sandbox Journey, point#9 replace "demo your app to NHA team"
2) 1.2
=> Under "What is an ABHA address?" can we include the below points:
Key features of ABHA address :
ABHA address can be created using mobile number, email address and ABHA number
It is recommended to link ABHA number and ABHA address. Max of 6 ABHA addresses can be associated with one ABHA number, however, it is recommended that only one ABHA address be linked;
Purpose of having more than one ABHA address : Patient may want to keep his/her health records segregated. i.e, may keep all the ortho related records linked with one ABHA address, neurology related records linked with another ABHA address, and so on
ABHA address can never deleted / deactivated. If a ABHA number is linked with ABHA address is deleted then ABHA address is not deleted. Only the link is lost/deleted.
Health records are linked with ABHA address
=> we may please elaborate that one of the foundation of ABDM is being based on 'federated' architecture which implies all the health related data/information resides at source.
=> Under the heading, "How does a HIE-CM create a longitudinal Health record" we can rewrite "The HIE-CM as keeps track of all consents provided by the user." as "The HIE-CM keeps track of all consents provided by the user as well maintains all the ABHA address links. Currently, we have one HIE-CM in production which is identified by @abdm and another one in Sandbox identified by @sbx.
3) 1.6
=> Can we please also include the following, as we get many integrators asking about these
Request ID - UUID or in response from the API (UUID and response requestIDcan not be same in one call) where UUID is a 128-bit universally unique identifier.
X-HIP ID - we can explain a little more sharing how to obtain this from HFR registration and by Registering as HIP service through the API
X-HIU ID - Obtained from HFR registration and Register as HIU service through the API
1) 1.1 => can we add that for certification process 2 milestones are mandatory => Demo your application to HTC (Health Tech Committee) (ABDM Sandbox Journey, point#9 replace "demo your app to NHA team"
2) 1.2
=> Under "What is an ABHA address?" can we include the below points:
Key features of ABHA address :
=> we may please elaborate that one of the foundation of ABDM is being based on 'federated' architecture which implies all the health related data/information resides at source. => Under the heading, "How does a HIE-CM create a longitudinal Health record" we can rewrite "The HIE-CM as keeps track of all consents provided by the user." as "The HIE-CM keeps track of all consents provided by the user as well maintains all the ABHA address links. Currently, we have one HIE-CM in production which is identified by @abdm and another one in Sandbox identified by @sbx.
3) 1.6 => Can we please also include the following, as we get many integrators asking about these
Request ID - UUID or in response from the API (UUID and response requestIDcan not be same in one call) where UUID is a 128-bit universally unique identifier. X-HIP ID - we can explain a little more sharing how to obtain this from HFR registration and by Registering as HIP service through the API X-HIU ID - Obtained from HFR registration and Register as HIU service through the API