OpenMRS uses "Complex Observations <https://wiki.openmrs.org/x/wxEz>" for this workflow. FYI – we are working to expand this to a more generic notion of "Custom Datatypes <https://wiki.openmrs.org/x/ZwERAQ>" that can serve not only for observations, but also for adding implementation-specific person & visit attributes as well as new global property types.
Complex observations require a complex obs handler that is responsible for persisting as well as rendering the data. For each complex observation, an observation is created with an internal reference created by & used by the handler to get to the complex value. Since the handler is in complete control, it can store the data within a local table or even store & retrieve values from an external system. You use complex obs handlers by defining a concept with a datatype pointing to the handler. There are generic image & file complex obs handlers provided by core. Others can be provided by modules. Cheers, -Burke On Fri, Sep 9, 2011 at 11:37 AM, Shaun Grannis <[email protected]>wrote: > Has a workflow to attach external files been deployed in OpenMRS? For > example, consider the following scenario: > > 1) A patient receives care at an OpenMRS site. > 2) An encounter is created, a referral to a specialist is ordered. > 3) Patient leaves. > 4) Days later, the specialist's dictated paper note is sent to the clinic. > It is scanned and the electronic note must be "attached" to the previous > encounter. > > Given the above, a desirable workflow would be: > > 1) User selects the patient. > 2) User selects "Encounters". > 3) User selects "Edit" to edit the previous encounter. > 4) User selects "Add Observation". > > Steps 1-4 exist today, here's the new, hypothetical workflow: > > 5) Select an observation that indicates the result is an external file > (e.g., an observation like, "PDF Referral note" -- let's not focus on the > observation name yet, it may not be quite the right model; it's just a > concept to trigger the next steps in the workflow): > 6) Selecting "PDF Referral note" surfaces an "attach PDF file" option. > 7) User selects "Select file" > 8) User finds file and clicks "Upload" (this is much like an email > attachment workflow) > 9) File is uploaded. > 10) The observation "PDF Referral note" is added to the encounter. > 11) When user clicks on "PDF Referral note" in the appropriate encounter, > the PDF file is displayed in an external viewer (again, much like an email > attachment is handled by an external application) > > My question: > > Has a workflow similar to this been implemented in OpenMRS? Is it in core > and I'm missing it? In a module? > > Thanks for your feedback! > > Shaun > -- > Shaun J. Grannis, MD MS FAAFP > Research Scientist, Regenstrief Center for Biomedical Informatics > Director, Indiana Center of Excellence for Public Health Informatics > Associate Professor, Dept of Family Medicine > Indiana University School of Medicine > 410 West 10th Street, Suite 2000 > Indianapolis, IN 46202 > Voice 317.423.5523 / Fax 317.423.5695 > _________________________________________ > > To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-implement-l" in the > body (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l] > > _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
