Hi HISP India people, We've started to implement the idea of "Visits" in OpenMRS, and this will be released in 1.9 later this year. Since you have a use case that visits could support, I'm interested to get your feedback about whether what we've implemented will be useful to you.
As far as the data model, we've added a new Visit class with: - patient (who it belongs to) - startDatetime, stopDatetime (what date range the visit covers) - location (where it takes place) - visitType (the list of possible visit types is admin-configurable) - indication (an optional concept which can indicate the primary reason or billing code for the visit) - list of attributes (the admin can configure "Visit Attribute Types" for whatever they want, e.g. billing code, insurance number, hospital wing, etc) In addition encounters may now (optionally) be assigned to belong to one visit. Finally there are some minor tweaks to the standard UI, e.g. the patient dashboard shows a "currently in a visit" message at the top if a patient is currently in the middle of a not-yet-stopped visit. Any thoughts about this approach? Things you like? Anything you'd have expected to see done differently? Do you think you'll be able to use this to improve your hospital-based implementation? -Darius PS- I've cc'd the OpenMRS developers list. Also, please let me know if I should switch around my HISP India contact list. _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
