Hi Viet, A visit is intended to be a single visit to the hospital (either inpatient or outpatient).
At some point we intend to add Episodes of Care<https://wiki.openmrs.org/x/_gBl>, which will be used for grouping visits, but this isn't yet scheduled for a specific OpenMRS release. -Darius On Tue, Aug 9, 2011 at 1:55 AM, Viet Nguyen <[email protected]> wrote: > Hi Darius, > > I think this will be very useful for our current system. There are some > cases that we will implement it > > 1. To have a case history, for example we need to list a history of all > visits of a patient in our patient dashboard. Each visit will have > information such as diagnosis, lab investigations, OPD out come, IPD out > come etc.. > 2. Manage patient attribute that changes over time, which each visit it > may have different value. In that case we can use visit attribute instead > of > patient attribute. > > Because we do not use openmrs default patient dashboard so most of > implementation will be done at service layer. > > A question: > Does a visit mean one time patient goes to hospital or it includes many > times ? > If it mean one time, can we have a group a visit , or linkage between > visit. > > Thanks > > > On Fri, Aug 5, 2011 at 9:50 PM, Bob Jolliffe <[email protected]>wrote: > >> Hi Darius >> >> This looks interesting as a way of grouping encounters and possibly >> for organising billing. I'm sure it is useful. >> >> In terms of the Shimla system I guess there is a notion of who is >> currently "visiting" in terms of whether they are in one or other >> queue. This is to manage the real time flow of patients, whereas the >> Visit notion you refer to seems more useful in terms of >> retrospectively looking at what encounters a patient had (useful for >> billing amongst other things). >> >> The "currently in visit" indication goes some way towards marrying the >> two. It *might* be useful to be able to enhance this to be able to >> say currently visiting X-Ray though I am not sure if there is a real >> requirement for that yet. >> >> If the system were to move to 1.9 I can see that it might make sense >> for a visit to be created at registration, rather than an encounter >> and for a registration/billing clerk to be able to view visits (with >> encounter summary info) rather than encounters directly - not really >> 100% sure. >> >> Cheers >> Bob >> >> On 4 August 2011 15:01, Darius Jazayeri <[email protected]> wrote: >> > 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. >> > > > > -- > Viet Nguyen > > _________________________________________ 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]
