I think the requirement that I had stated in the project page is included in the design - but I thought I will reiterate the features that will be really helpful for implementations once more : ==================================================================================================A. Clinical Summary Template function : Users (Doctors) should be able to select concepts to define the template for a clinical summary. It can be implemented as a) Tag in HTMLForm (example: A tag to display a table of lab results) b) A wizard like tool , where the user can choose the different concepts and ordering of the concepts in the form c) An ideal solution will be to have a WYSIWYG editor, which combines the wizard concept as well as the formatting concept d) The doctor may decide to include specific "Encounters" that are important to create a final template of clinical summary e) The doctor may save this template , so that it can be used by other doctors.
The most important thing will be that the end user (ideally Doctor, or the implementer who have some idea of HTML) can easily configure it and change it . Two points to keep in mind is, 1) the concepts in the clinical summary will be different (A oncologist will like to see the ECOG performance score right up at the top of the summary while other doctor's will not be interested at that score all) 2) and/or it may be based on specific encounter, specifically the very first encounter which covers several important historical information that will be different for different type of group of doctor's but they are under the same hospital, thus using the same openmrs instance. The idea is, the doctor (non-technical users) can decide what data of patients (in openMRS termionology which concepts in specific encounter) will show up in the patient summary. It will be ideal, if one doctor can configure this and save/share it as a template which can be used by other doctors. ============================================================== ________________________________ From: Joaquín Blaya <[email protected]> To: [email protected] Sent: Wednesday, March 21, 2012 5:18 PM Subject: Re: [OPENMRS-DEV] Design Discussion: Patient Summary I would like to add that if the Patient Summary could be imbedded into a tab of the patient page and not just a link in the summary tab to do a pop-out i.e. be able to view the patient summary directly in the summary tab in the patient page. Joaquín ___________________________________________________________________ Gerente de Desarrollo, eHealth Systems Research Fellow, Escuela de Medicina de Harvard Moderador, GHDOnline.org On Wed, Mar 21, 2012 at 4:58 PM, Ben Wolfe <[email protected]> wrote: Looks like your requirements are: > >1) reusable template for a summary >2) drag and drop / wysiwyg UI >3) interface for Android, jsp page, pdf > >Anyone else have feature requests for a redesigned patient summary / clinical >summary? > >Win, can you start a (small) project page for this? > >On the design call today, Win agreed to try and mock up a quick summary using >the reporting module due to Mike's encouragement. We're looking forward to >your feedback from that! > >Ben > > > >On Wed, Mar 21, 2012 at 11:14 AM, Nyoman Ribeka <[email protected]> wrote: > >Hi all, >> >>For everyone interested in patient summary, I would like to throw in >>some of the things I would like to discuss in the design discussion. >> >>Few things I want to come out from the design discussion are: >> - we need a way to model the template for the summary >> - potentially means creating more Data object in the reporting if >>we're using reporting framework >> - we need a way to manage the template (drag and drop ui) >> - we need a way to send the model to different type of viewer >> - serializer for the model (and each of the data element) and display >>them in android devices, patient dashboard or print them out >> >>This is an example of the serialized patient summary output: >>http://pastie.org/3641337 >> >> >>-- >>Thanks, >> >>Nyoman Ribeka >> >>_________________________________________ >> >>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] >> > > >________________________________ >Click here to unsubscribe from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe 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]
