Hi Vinkesh,
Is it safe to say that the separation of “Observations”, “Diagnosis”, and “Consultation” is more due to the technical detail of how this data is stored in the backend, and less about the logical grouping of functionality? Or was it a user request to have separate “Observations” and “Diagnosis” tabs?
Saying “providers need not care if diagnosis is stored in backend as an obs. Having it in separate tab gives that abstraction” implies that users actually care or have knowledge about the distinction between data stored in the obs table vs. some other data structure, and want their UI divided up to represent this. Is this true?
Like Christian, I have also found the “Observations” tab as distinct from the “Diagnosis” tab as more of a reflection of our data modeling and a convenience to developers, than as the optimal clinical UI. But this is just my impression - I’d love to hear more about how this has evolved with JSS and other hospitals that you originally designed this for.
Thanks! Mike