Wes,
This looks quite ambitious! I wondered why you combined so much functionality 
into a "registration" module. It seems that many of the functions are better 
separated out for patient interaction. Seems that registration shouldn't 
include actual visits, etc. Do you have a use case document which describes the 
actors and functions that will use this system?

I am sure that Hamish and many others would be quite interested.

BTW, great project!
Good luck!
Andy
 
-------------------- 
Andrew S. Kanter, MD MPH 


Asst. Prof. of Clinical Biomedical Informatics and Clinical Epidemiology

Columbia University
Email: andrew.kan...@dbmi.columbia.edu 
Mobile: +1 (646) 469-2421
Office: +1 (212) 305-4842
Skype: akanter-ippnw
Yahoo: andy_kanter



>________________________________
> From: Wesley Brown <w...@weslandia.org>
>To: openmrs-deve...@listserv.iupui.edu 
>Sent: Friday, May 18, 2012 7:53 AM
>Subject: [OPENMRS-DEV] OpenHMIS Registration Module - Design
> 
>
>Hello fellow OpenMRS developers!
>
>
>My name is Wesley Brown and I am writing on behalf of the OpenHMIS team to  
>get some feedback on the design for our Registration Module.  The OpenHMIS 
>Registration Module is the entry point of the data for all of our 
>patient-related activities.  All forthcoming OpenHMIS modules that deal with 
>patient data will rely on this registration module in some fashion, if only 
>for the data that is collected.  As such, the registration module 
>functionality will likely grow to support the additional interfaces and 
>requirements over time.  
>
>
>The features that will be included in our initial release are:
>       * Gather Patient Registration Details
>       * Support Multiple Registration Queues (e.g. Inpatient, Outpatient, etc)
>       * Gather Patient Visit History
>       * Patient Visit Slip Generation
>       * Support Flexible Patient Queries
>       * Patient Data Lifetime
>       * Registration Notifications
>       * Support for Patient Sponsorship
>       * Appointment Scheduling
>       * Patient Record Accessibility
>Each of these features is discussed in more depth on our wiki 
>page: https://wiki.openmrs.org/display/docs/OpenHMIS+-+Registration+Module
>The OpenHMIS code is currently hosted at 
>github: https://github.com/OpenHMIS/registration  Note that the features above 
>have not yet been implemented so there isn't very much in the way of code to 
>look at.
>
>
>It seems like there are a number of groups working on adding more robust 
>registration capabilities to OpenMRS, as well as other hospital management 
>features.  I have heard of at least two: a group from PIH and a group from 
>AMPATH.  However I have not been able to find any public information about 
>their progress or overall design.  Has there been any discussion about 
>collaborating with each other so that we don't duplicate our efforts and end 
>up with a bunch of fragmented HMIS modules?  If not, is there any interest to 
>do so?
>
>
>We would also like to get some feedback from the OpenMRS development community 
>and hopefully utilize existing work rather than reinvent the wheel.
>
>
>Thanks!
>-Wes Brown
>________________________________
> Click here to unsubscribe from OpenMRS Developers' mailing list 
>
>

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
lists...@listserv.iupui.edu with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l]

Reply via email to