Handling Multiple Patient Identifiers across the Reference Application

[Craig A.]

Hi Everyone,

I haven't been able to find how to include multiple Patient Identifiers in the reference application. If this exists, please let me know. It seems that organizations would need to enter multiple patient identifiers in the registrationApp, display them in the patient header fragment and edit them once the user clicks "edit" in patient header. How would you go about this? Do others agree that this would be a good feature in RA 2.3? 

Sincerely,

Craig

[Mark Goodrich]

Craig,

If you are talking about identifiers of different types admittedly, it's not well-documentated (or documented at all) but there is a global property that allows you to specific additional patient identifier types to display in the patient header (this should be a comma-separated list of identifier type uuids):

GP_EXTRA_PATIENT_IDENTIFIER_TYPES = "emr.extraPatientIdentifierTypes"

Right now the registration app only allows the entry of a single identifier of the primary identifier type, but we most likely will be expanding this functionality in the near future as we will be needing it for our implementation.

Mark

--
OpenMRS Developers: http://om.rs/dev
Post: d...@openmrs.org | Unsubscribe: dev+uns...@openmrs.org
Manage your OpenMRS subscriptions: http://om.rs/id
 
Visit OpenMRS Talk at http://om.rs/talk for chat and discussions!
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@openmrs.org.

[Craig A.]

Hi Mark,

That global property only seems to be in the PIH emr module config.xml file. I'll add it to my local global properties, but should this be included in the coreapps module? 

Sincerely,

Craig

[Mark Goodrich]

It should be in the EMR-API module config.xml if it isn't already.  We certainly could have missed copying it over from the old EMR module.

Take care,
Mark

[Craig A.]

Thanks Mark. I'll create a Pull request in the morning.

Sincerely,

Craig

[Darius Jazayeri]

@Mark, the code that handles this is all in the core apps module, right? Offhand I think the GP should move there instead of emrapi.

-Darius (by phone)

[Mark Goodrich]

Darius,

There's a List<PatientIdentifier> getExtraIdentifiers(Location location) method within the Patient Domain Wrapper in EMR-API, so if we want to maintain that, we'd need to keep the GP in EMR-API.

Mark

[Darius Jazayeri]

Ah, okay, emrapi it is.

-Darius

[Craig A.]

Thanks for the clarification! I'll make the change in the morning.

Sincerely,

Craig

[Craig A.]

Here's the Pull Request.

Sincerely,

Craig