Tuesday, June 2, 2020
Saturday, May 30, 2020
- CSV Format NFI:
- PDF Format NFI:
- PDF Format NFI Update:
|Drug Unique Code|
|Generic Drug Code|
|Generic Drug Name|
|Brand Drug Code|
|Brand Drug Name|
|Route of administration|
|Drug Restriction (Max Dosage)|
|Drug Drug Interaction|
|Alternate Drug (generic drug)|
|Medication package type|
Friday, May 22, 2020
A federated health worker registry is proposed that will be maintained by the Central Government and will store “identified minimum required informative fields” and will assign a “unique identification number” for every ASHA worker. The ASHA registry will have pointers to the state ASHA enrollment repositories or databases (DBT, HR etc) that will push relevant data to the central registry for every new ASHA enrollment, any information updation or change in employment status or location.
Whenever a new ASHA health worker gets selected for final recruitment, gets enrolled through an online common cloud-based portal or application by a trained staff appointed by the district health dept or a private enrollment agency at the PHC or assigned anganwadi center maintained at village or district level.
The enrollment process mandates ADHAAR card number authentication with the UIDAI and assigns a unique health worker identification number in the centralized registry. This Unique ID is unique across the country and ensures the portability of health workers from one district or state to another and provides a global mapping of the health worker ID with services delivered at the health and in various vertical health and nutrition IT programs.
This enrollment process may include an enroller-approver flow to get a final approval from the nodal/district health officer to foolproof the recruitment process and only after the approval a new ASHA can be assigned the Unique ID.
The DBT database at state level is required to be linked to the centrally maintained registry for every new enrollment as a prerequisite for activating the DBT service. Since an ADHAAR number is already a mandatory requirement for authenticating the DBT account, the same ADHAAR number should be used to authenticate every new ASHA enrollment and will facilitate single source for non-repudiable data.
It is suggested that a DBT account of the newly recruited ASHA will only be created after the unique ID is assigned to her. Unique ID becomes a pre-requisite for DBT payments. Any national or state program that requires assistance from ASHA on various health or nutrition activities, will have to use a look up service to the central registry to enroll the ASHA in their respective application and program that task tracking and workload assessment for payments can be made easier and automated.
For all the existing ASHAs for whom information is maintained currently by states either in the DBT database or ASHA soft etc would be required to push data to the central registry for the identified minimum required fields.
The enrollment agency or district department whoever is responsible for the end to end enrollment or data migration work, will be required to setup a maker-checker workflow so that, only verified or correctly mapped information gets uploaded in the central ASHA registry.
A registry update process/mechanism on regular intervals precisely annually will be required to be implemented. Central registry may trigger annual reminder like that in vase of Voter update system for updation or confirmation of the updated information to ensure reliability of information. These reminders will be part of the workflow that can be sent to the assigned enrollment agency or the district health department that will be responsible for enrollment and updation.
Services for self-updation will also be required similar to in the address etc update process in ADHAAR at the anganwadi or PHC centers with OTP service or on approval by the district health.
For every critical process (like Mobile no. updation, last name change, village/district change etc in case of transfers or inactive ASHA update) in the entire the lifecycle of an ASHA that affects the information in the central registry directly or indirectly will have associated manual and electronic form and processes that will have to be completed through the same common portal or application with role based access.
Thursday, April 16, 2020
- ePrescription and eEncounter FHIR based Objects for Telemedicine interoperability.
- The same eObjects can also be used for Referral across Primary, Secondary and Tertiary care.
- Epidemiological Surveillance is the next big thing. We will need eEncounter, ePrescription and eDischarge Objects to fetch the data from disparate OPD/IPD HIS/EMR systems.
- eObjects act as a Standard Output Format in these use cases.
- eEncounter Note
- ePrescription and
- eDischarge Summary
- Presentation on what are eObjects and How to use it
- eObjects v1 Details: Version Deprecated but kept for Historical reference.
- eObjects v2 Details: Current version in use.
- eDischarge Summary v3 Including the recommendations from NRCeS
- Download Sample eEncounter in JSON Format
- Download Sample ePrescription in JSON Format