You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since an endpoint's name and url can change over time, it is useful and important to have an unique identifier in the endpoint data JSON download file from https://lantern.healthit.gov/?tab=downloads_tab#shiny-tab-downloads_tab. Without such an identifier, it can be very difficult to track an endpoint over time as its name and/or URL changes.
Certified API developers Epic, Allscripts, and Cerner include unique identifiers in their FHIR bundles and the NPPES provides a unique NPI number.
Ideally the merge procedure in the Lantern backend would retain and include both identifiers, where available, in the merged output for the database and in the downloadable endpoint data JSON file.
The text was updated successfully, but these errors were encountered:
Since an endpoint's name and url can change over time, it is useful and important to have an unique identifier in the endpoint data JSON download file from https://lantern.healthit.gov/?tab=downloads_tab#shiny-tab-downloads_tab. Without such an identifier, it can be very difficult to track an endpoint over time as its name and/or URL changes.
Certified API developers Epic, Allscripts, and Cerner include unique identifiers in their FHIR bundles and the NPPES provides a unique NPI number.
Ideally the merge procedure in the Lantern backend would retain and include both identifiers, where available, in the merged output for the database and in the downloadable endpoint data JSON file.
The text was updated successfully, but these errors were encountered: