This may have already been discussed in this long thread, but I want to point out, from an architectural standpoint, these would be independent features:
- Prescribing (e.g., Order Entry Service)
- Dispensing (e.g., a Pharmacy Module)
- Administration (e.g., a Medication Administration Module)
In other words, each of these can benefit from the existence of the others, but we should avoid bundling these into one service/module or creating dependencies between them.
Some examples of common use cases in which OpenMRS is or will be used and can be supported if prescriptions, dispensing, and administration are independent:
- Electronic prescriptions (order entry), paper-based dispensing, no tracking of administration
- Paper-based prescriptions, electronic dispensing, paper-based administration
- Electronic prescriptions, dispensing, and administration all within OpenMRS + modules
- Electronic prescriptions in OpenMRS, a separate commercial pharmacy system used for dispensing, a separate commercial MAR (medication administration record) system used for administration
It's probably safe to assume that order entry, if done electronically, would be done within OpenMRS. Just as with lab systems, those implementations doing electronic dispensing & administration might start with OpenMRS modules, but could easily evolve to replace those modules with enterprise level systems over time, so would migrate from doing these in OpenMRS to integration OpenMRS with external systems for these functions that would be out of scope for an EMR (see below).