We do this exact thing within the MDR-TB module. We have Smear, Culture
and DST lab results entered as normal observations, but also upload the
actual PDF test result report that comes back from the lab as a complex
obs. I'm pretty sure we originally implemented this with a custom
handler, but later I think Mark actually rolled this into core. I'll
let him respond to the details of that if so...
On 09/09/2011 12:31 PM, Darius Jazayeri wrote:
Shaun,
This is indeed what complex obs are for. In the core distribution we
only have handlers for Image and for Plain Text, but a module could
easily add PDF. (And that seems like something we'd want to bundle in
the standard distribution too.)
If you look at this enounter on the demo server today (since its db
resets nightly) you'll see that I've added a png image as one of the
obs whose concept is Darius Test Complex Obs or something like that:
http://demo.openmrs.org/openmrs/admin/encounters/encounter.form?encounterId=44345
-Darius
On Fri, Sep 9, 2011 at 8:57 AM, Bill Lober <[email protected]
<mailto:[email protected]>> wrote:
Shaun, others?
Could one use complex obs to store an URI, and possibly
credentials, to an external repository.
That's the model used by the Cross Document Sharing profiles (XDS)
of IHE.
One could reference either a document store in a "Document Store
Module" (to be written, I think), an external light-weight
document store, a query string into an existing object store, or a
document reference in a commercial document management system.
It would be a very flexible approach.
I came across Complex Obs not too long ago - is anyone using them?
Is this an appropriate use?
Thanks,
Bill
-----Original Message-----
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] On Behalf Of Shaun Grannis
Sent: Friday, September 09, 2011 8:38 AM
To: [email protected]
<mailto:[email protected]>
Subject: [OPENMRS-IMPLEMENTERS] attaching files to a patient encounter
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 <tel:317.423.5523> / Fax 317.423.5695
<tel:317.423.5695>
_________________________________________
To unsubscribe from OpenMRS Implementers' mailing list, send an
e-mail to [email protected]
<mailto:[email protected]> with "SIGNOFF
openmrs-implement-l" in the body (not the subject) of your e-mail.
[mailto:[email protected]
<mailto:[email protected]>?body=SIGNOFF%20openmrs-implement-l]
_________________________________________
To unsubscribe from OpenMRS Implementers' mailing list, send an
e-mail to [email protected]
<mailto:[email protected]> with "SIGNOFF
openmrs-implement-l" in the body (not the subject) of your e-mail.
[mailto:[email protected]
<mailto:[email protected]>?body=SIGNOFF%20openmrs-implement-l]
------------------------------------------------------------------------
Click here to unsubscribe
<mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l> from
OpenMRS Implementers' mailing list
_________________________________________
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]
