“Manual lab result entry (for implementations without a LIMS)” surely is in-scope for an EMR. Bahmni includes this as Order Fulfillment.
I also think that knowing the status of an order also belongs in OpenMRS’s domain. (I said this to you on another thread last week: Best Practice for Modelling Order Fulfillment?, and as I said then, FHIR includes it as ProcedureRequest.status.) I don’t know offhand if we’d want this as a single mutable field on Order, or in another table so that we could track the history. But I support adding this to the core data model.
(If you’re tracking specimens or samples, this belongs in a LIMS. If you’re tracking Orders, it belongs in the EHR.)
A few quick thoughts:
- approach this as a microservice that you can swap out later. (okay to actually implement using omod/owa)
- plan for a future where some orders are handled by this mechanism and others are not (e.g. radiology orders go to an external system, but lab orders are still handled here)
- some level of configurability about what can be manually managed with this app
- also probably the UI should support a workflow where you first choose an order type
- you don’t always have exactly one result per order. You mention “results templates” but you can also consider using existing form entry tooling for this
- I would expect the results to be displayed on the main patient dashboard (although I guess you’d still be allowed to see them via this app)