So far in our gap analyses with Palladium/KenyaEMR, PIH/CompanerosEMR, and Ampath/AMRS-POC, there are 2 common needs everyone has for the Registration page:
- Configurable: Need for the Registration Forms to be configurable (even per site or per department, not just per organization) - 1 size does not fit all. (The same is true for Vital Signs/Triage)
- Address Hierarchy: This is missing in 3.x right now (issue: [O3-328] Support Address Hierarchy - OpenMRS Issues)
I think essential forms like these should be built using the same Form Builder tech that’s used to build Clinical Forms. Should we try to build-in an address hierarchy “widget” or feature into our 3.x Form Engine?
- Based on >70 user/org interviews and market research, I believe EASE OF CONFIGURABILITY needs to be one of the major differentiators of OpenMRS 3.x going forward. I.e. Our system should be easy enough for non-technical BAs/PMs to configure essential forms. This helps address speed of implementation, ability for implementers to scale their business/impact, and reduce the menial task burden on development (my impression is devs would like more meaningful work than basic config changes here and there).
- “But Grace, you really only need to configure the Registration form once and then you’re fine.” Is this really others’ experience? My response is:
- Scenario A: Scale. Implementers often have many, many sites to set up, with varying requirements (so maybe you only configure the registration form 1-2x per department; but if you have hundreds of go-lives over a few years, that really adds up!!)
- Scenario B: Evolving Requirements. Clinicians and Managers and Funders often adjust their requirements. In my pre-OMRS form implementation days, we though Registration forms would be standard, but we found that over and over again sites wanted or needed tweaks to context-specific registration forms, which created painful forking complexity even for a single site. Eventually we had to make Reg forms easily configurable by folks like me.
(Note on priority: Medium. Right now clinical testing at Ampath (and I expect at future pilot sites) is focused on the clinician workflow, and the registration is still happening with the site’s legacy frontend. However since @vasharma05 has been working on the registration epic quite a lot lately, I’d like to figure out a pathway forwards.)