I'd say it's fine to create a new encounter for the order or orders. With 1.9 we're clarifying that "encounter" doesn't mean what its English definition implies (that would be a visit) but rather an encounter is just a transaction to group data collected together.
So using new encounters to hold orders (and presumably giving them their own special encounter type) will be consistent with the way 1.9 will work when you eventually upgrade. -Darius (by phone) On Jan 24, 2012 7:22 AM, "Ben Wolfe" <[email protected]> wrote: > I vote for the "upgrade to 1.9 and use visits" one. :-) > > If not, then the first one. orders.encounter_id so it should be possible > to create encounterless orders. I think those are taken into account in > code when editing, moving, etc. > > Ben > > On Tue, Jan 24, 2012 at 5:55 AM, Rowan Seymour <[email protected]> wrote: > >> We have two modules under development here at the Rwandan MOH which >> relate to orders - one for drug orders and one for lab test orders. The >> drug order module currently has a dashboard tab portlet where new drug >> orders can be added to a specific encounter. The lab test order module also >> has dashboard tab portlet where new lab test orders are created - but these >> are added to a newly created encounter. >> >> Neither of these solutions seem ideal - the former requires the clinician >> to search for an encounter which is awkward. The latter creates an extra >> encounter. So I was wondering what the best practice here is. The options >> as I see them are: >> >> 1. Create the orders without an encounter (I think this is >> possible...) >> 2. Add them to an existing encounter created (e.g. the encounter from >> the consultation form like the drug orders) >> 3. Create a new encounter to hold the orders (like "lab test order" >> encounter) >> 4. Add sections for lab tests and drug orders to the whatever >> consultation form is being used (this isn't implemented in htmlformentry >> yet tho?) and this would make sure all the orders end up in that one >> encounter. >> 5. Upgrade to 1.9 and group everything into a "visit"? (obviously not >> happening anytime soon) >> >> Advice appreciated >> >> Rowan >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing 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]
