Multiple visits at the same time

[paul (Paul Biondich)]

@mseaton

In terms of configuration and control, I would love for us to have some more formalized configuration constructs that allow us to represent valid combinations of Programs, Encounter Types, Forms, Patient Identifiers, Visit Types, Attributes, etc and to build workflows and UI/UX around these.

This comment relates to this:

@mseaton

@mksd, I don’t know the answer but am curious to hear from @paul, @burke and @darius around their thoughts/recollection of whether validating was deliberately kept out of core and put in emrapi to keep this option open, or if there were other intents.

I’m just the old codger to this conversation, but when we conceived OpenMRS, we believed pretty strongly in conventions… ie, the data model was meant to support clinical care in as much detail as possible to avoid drift in how people stored data. In this thread, we’ve seen a couple of examples of that drift, which is kinda hard to totally avoid.

I wonder if we’ve lost sight of the definitions of the objects, or maybe not made it clear to implementers what the conventions were?

https://guide.openmrs.org/en/Getting%20Started/openmrs-information-model.html

There’s lots of pages out there like this one that I think do a pretty good job of distinguishing visits from encounters. What role do we have as a community to help make those conventions known, and more importantly, what should we do to support cases where implementations become stuck once those conventions are misunderstood or broken?

That help you understand my perspective?