The EMEDIX extension is a private workplace tool for a single hospital. It copies
claim records that the hospital's own authorised staff are already viewing on the
Government of India PM-JAY / NHA provider portal (provider.nha.gov.in)
into that same hospital's own EMEDIX tracker server.
The extension's code runs on provider.nha.gov.in and nowhere else. It
does not run on, read, or observe any other website.
It is not a consumer product. It does nothing until the hospital's own staff install it, sign in to their own portal account, configure their own tracker address, and enter their own extension key.
While a member of the hospital's staff is signed in to the PM-JAY / NHA provider portal, the extension reads the claim records that are already on the screen or already returned to that browser tab by the portal's own API. These records can include:
This is patient health information, and it includes financial information about the hospital's claims. It is handled only as described below.
It reads nothing from any other website. It does not read browsing history, other tabs, bookmarks, or the content of any page outside the PM-JAY / NHA provider portal.
The extension never asks for, reads, or stores your portal username or password. Sign-in happens on NHA's own pages, exactly as it always has.
To read the remaining pages of a long status list, the extension calls the portal's own API host on your behalf. To do that it reuses the authorisation header the portal itself has already issued to that browser tab for the session you are already signed in to. Two facts about that token:
provider.nha.gov.in, apisprod.nha.gov.in). It is not
sent to any other destination.The extension also holds one credential of its own: the extension key issued by the hospital's own tracker, which the hospital types into the extension's settings. It is stored as described in §5 and is sent only to that hospital's own tracker, to prove the request came from that hospital.
All data is sent to one destination only: the tracker server address that the hospital
itself types into the extension's own settings. For hospitals using the hosted edition
this is their own subdomain of pmjaytracker.emedix.co.in; hospitals running
the offline edition point it at a server on their own premises or their own network,
including on the same computer as the browser.
The data is never sent anywhere else. Specifically it is never sent to:
The data is never sold, rented, or shared with anyone, and it is never used for advertising, profiling, creditworthiness, or any purpose other than populating the hospital's own claim tracker.
The extension keeps a small amount of working state in Chrome's own local extension storage, on that computer only:
This is operational state, not a patient database. It stays on that computer, is never transmitted anywhere except to the hospital's own tracker as part of normal syncing, and is deleted when the extension is removed.
The portal authorisation token described in §3 is not among these — it is never written to storage of any kind.
| Permission | Why |
|---|---|
| storage | to keep the tracker address, extension key and sync progress described in §5 |
| alarms | to run scheduled syncs at the times the hospital configures |
| notifications | to tell the staff member when a sync finishes or needs attention |
| https://provider.nha.gov.in/* | the PM-JAY / NHA provider portal — the only site the extension reads records from |
| https://apisprod.nha.gov.in/* | the portal's own API host, used to collect the remaining pages of a status list |
| http://127.0.0.1/* http://localhost/* | the on-premises edition of the hospital's own tracker, running on the same computer as the browser. These are fixed, local-only addresses that cannot reach any third party. |
| optional http://*/* https://*/* | Not granted at install. The extension requests one origin at a time — the tracker address the hospital itself types into its settings — and Chrome asks that hospital about that one host. The address cannot be known in advance: hosted hospitals use their own subdomain of pmjaytracker.emedix.co.in over https, and hospitals on their own network use a private LAN address or hostname. Only the origin entered is ever granted or used. No other host is contacted, and the extension does not read, modify or observe any other website. |
The extension itself retains nothing beyond the working state in §5. How long the records are kept after they reach the hospital's tracker is decided by that hospital, under its own record-keeping obligations. Uninstalling the extension removes everything it held in the browser.
Traffic to a hosted tracker travels over HTTPS. Every request carries a per-hospital extension key; a key issued to one hospital is rejected by every other hospital's server. Access to the tracker itself is controlled by the hospital's own accounts and passwords. Hospitals running the offline edition are responsible for the security of their own network and machines.
Only authorised staff of a hospital that already holds a PM-JAY / MJPJAY provider login and its own EMEDIX tracker. The extension does not create, grant or bypass any access — a staff member sees through it exactly what their own portal account already permits them to see, and nothing more.
The extension is used by hospital staff, not by patients, and is not directed at children. Records handled may relate to patients of any age, including newborns; they are handled exactly as described above regardless of the patient's age.
Material changes will be published here and the "last updated" date changed. If a change ever widened what is collected or where it is sent, it would be announced in the extension's own release notes as well.
Questions, requests or complaints about this policy or about data handled by this extension:
EMEDIX Pvt. Ltd. — emedixtechnology@gmail.com
Patients wishing to exercise rights over their own records should contact the treating hospital, which is the controller of those records.