Bahmni Registration module provides an extension for linking/verifying other identifiers for patients. Implementers can plugin in their custom requirements leveraging this extension.
Implementers are expected to leverage the extension point “org.bahmni.registration.identifier". As of now, only “link” type are supported. This means that an implementer can specify an URL to a sub-system/UI and Bahmni will launch in an IFRAME. It is expected that such an extension will return a basic FHIR patient resource (JSON) and send that as a message to the parent window.
Defining Extensions points on Registration page:
File to be updated: openmrs/apps/registration/extension.json
The source to be loaded on click of defined button
Contains additional parameters which include extra identifier’s name, button name and so on
one or more identifier type name. Note, if different identifier types require different source integration, define separate extensions.
defines attributes which needs to be non-editable after extra Identifier linkage
defines button display name
address map that maps the address FHIR object (returned from the link to registration page) to field in registration page
The link specifies the path to the UI that needs to be rendered on click of the link identifier button.
The external link returns an FHIR patient object to be mapped to Registration Page fields.
The returned payload is expected as a simple FHIR Patient resource.
Note: A complete patient resource is not required - only fields like identifier(s), name, birthdate, gender and address, those you want to be updated with a value from FHIR patient in registration page are expected.
If you provide patientUuid in FHIR patient id field, it will redirect to that patientUuid dashboard and update the respective details passed as a part of FHIR object. If id not defined, it will redirect and update details in the create new patient dashboard.
For example: consider the following FHIR Patient object