Request for Registration Module Feedback

[Wesley Brown]

Greetings!

My name is Wes Brown and I am a part of a group creating a set of general-purpose HMIS modules for OpenMRS; a project that we are calling OpenHMIS.  One of our primary goals is to create modules that are flexible enough to work in as many institutions as possible, in hopes of reducing the amount of baseline work needed to create institution-specific modules.  

As part of this effort we would like to get your feedback on the current registration modules that are in use.  We are going to create a registration API module that will handle much of the core back end registration activities and we want to make sure that we include as many of the core features as possible.  What we are looking for is information about the current registration module that you are using (or developing) and the features that you would consider are integral to it or, conversely, that are missing from it.  We will then gather this information and come up with a list of the 'core' registration features that we will support, hopefully in a manner that makes it easy for other module developers to reuse.

If there is sufficient interest, we would also like to discuss this at an upcoming Design Forum.  There is so much great HMIS work that has been done already for OpenMRS and we do not want to unnecessarily duplicate this work; our hope is that we can collaborate together so that these type of efforts do not have to start from nothing each time!

Thanks,

-Wes Brown

[Cross posted from the OpenMRS Impementers list - my apologies if I am breaking some unwritten rule]

[Michael Seaton]

Hi Wes,

I really appreciate this effort that you are making, and have been meaning to respond for some time.  Rather than go into great detail here, I'll summarize to say that at PIH we have 3 different patient registration modules / applications at 3 different implementations, and have spent considerable effort over the past couple of years designing and developing these.  Suffice to say that it is a goal of mine to find the common ground between our 3 approaches, as well as the other efforts that have gone on in this space, in order to promote best practices, re-usability, easier maintenance, less duplication of effort, etc, etc.  I certainly feel that you are on the right track by focusing on building a common API platform and back-end services to start with, as the actual workflow, UI, and device of choice has tended to be pretty implementation specific for us, as we have tried to optimize and streamline the registration process and hit local requirements.

I would be happy to be involved in any sort of working group that you are putting together in this space, and will start working on gathering as much documentation as I can on our existing systems in order to better communicate the work that we have already done.

Regards,
Mike

-- OpenMRS Developers: http://go.openmrs.org/dev
Post: d...@openmrs.org
Unsubscribe: dev+uns...@openmrs.org

[Bill Lober]

Jan Flowers already comments on this, but we’ve put together a “registration” module to mimic a function in the iSante EMR, where iSante can serve both as a registration system and as a master patient index for other facility level systems.  We’ve used the PIX/PDQ profiles (as Jan remarked).  We’d be happy to be part of a group looking at registration – particularly the infrastructure/messaging/interaction side.  We’re interested in the workflow/UI side also, of course, but maybe our more valuable contributions are the profile implementation/architecture stuff.

 

Best,

 

Bill Lober

Jan Flowers

Jim Sibley

 

(University of Washington I-TECH)

[Wesley Brown]

For those that are interested, I am purposing that we discuss this at an upcoming design forum, maybe June 6th?  I'm not sure if that meeting already has other things planned as I cannot see the upcoming topics on the wiki page but that date would work well for us.

I am gathering all the features that have been mentioned so that we can have a concrete list to discuss and putting it up here.  Feel free to add to, update, or comment that page.

Thanks!

-Wes

[Ben Wolfe]

Discussing next week should be fine.  I have added it to the agenda for June 6th: http://notes.openmrs.org/Design-Forum-2012-06-06
If you (or anyone else) has more ideas you can add them either to that agenda page or as a comment on the HMIS/registration page you started: https://wiki.openmrs.org/display/docs/OpenHMIS+Registration+API+Design

Ben

-- OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org

[mvila]

Hi all, 

We have a registration module running in a Hospital in India since last year and I would like to share some feedback we got from the users, and some other features we identified as useful when implementing the system in different hospitals.

I just saw you are discussing it today...hope is not too late

I copy the comments here, but I also added them to the wiki, as you required...

Search

• Advance Search Option
  
• Filters patients by gender
  
• Age +-Range
  
• Last Visit
  
• Relative Name
  
• Telephone Number
  

General

• Manage user Categories
• Create new categories
• Define category Type 
  
• Define incompatibilities amongst categories and patient restrictions
  
• Dynamic design of the available fields  in the registration form selecting from person attributes
  
• Integrate with a patient queue system that send the patient to the selected ward
  
• Print patient slip after registration
  
• Dynamic design of the print layout
  
• Configure the precision on the calculated age to show (years, months, days)
  

 

UI 

• Design a screen-size layout to avoid scroll while registering
  

Hope is useful!

Regards,

Marta

Unsubscribe: implementers+unsubscribe@openmrs.org

Unsubscribe: implementers+unsubscribe@openmrs.org

[Wesley Brown]

Marta,

Thanks for contributing this!  We are going to discuss this at the design forum later today, 2PM ET, which may be a bit late depending on where you are located.  If it's not, I hope that you can join.

-Wes

[Marta Vila]

a bit late here in India...

will check the notes!

thanks

[Wesley Brown]

My apologies for the long silence!  One of the things that came from this design forum was that it might be helpful for to be able to review the custom registration modules that have been built and attempt to determine the commonality between them.  Part of this effort is the OpenHMIS Registration API Design page but it would also be very helpful if I could see these modules in action.

If you have created a custom registration module I would like to set up a Skype or an Adobe Connect session to review what you have done and continue to add to the API Design page.  If a live session is not possible screenshots with descriptions would also be fine.  My goal is to review as many of the OpenMRS registration modules as possible so that I can spec out a base registration module that can be reused in as many registration processes as we can.

If you are interested in helping with this please contact me here or via email (w...@weslandia.org).

Thanks!

-Wes

Unsubscribe: implementers+unsubscribe@openmrs.org

[Paul Biondich]

Wes, thanks for doing this work over the 4th holiday. :)

It seems like getting this work on the OpenMRS design forum queue
would be important. Kiran/Chris, has this happened yet?

Do you need help Wes reaching those that have done specific work
around registration? Do you need me to help you shake the trees?
Totally behind what you're attempting to do here, and thanks for
showing leadership!

Best,
-Paul

>>> Unsubscribe: implementers...@openmrs.org

>>
>>
> -- OpenMRS Implementers: http://go.openmrs.org/implementers
> Post: implem...@openmrs.org

> Unsubscribe: implementers...@openmrs.org

[Burke Mamlin]

We've already had the initial design call on this.  At this point, Wes needs to get demos of any existing registration systems.  Shaking the trees might help get this to actually happen (e.g., PIH, AMPATH, anything Jembi might have done, work in India, etc.).  The more Wes can be exposed to, the better chance that he'll be able to architect a solution that can work across implementations.

-Burke

[Wesley Brown]

Burke/Paul,

As Burke mentions, at this point I am looking for demos of existing systems.  My last post was an attempt to move that forward however the response has been underwhelming soI think I will now go with a more targeted bothering of people :)

I have contacts at PIH, AMPATH, and HISP India that I will, um, contact; but if there are other registration efforts that you know a little tree-shaking would be helpful!

-Wes

-Burke

>>> Unsubscribe: implementers+unsubscribe@openmrs.org

>>
>>
> -- OpenMRS Implementers: http://go.openmrs.org/implementers
> Post: implem...@openmrs.org

> Unsubscribe: implementers+unsubscribe@openmrs.org

[Jeremy Keiper]

Wes, nothing beats on-site exposure.  ;-)

Jeremy Keiper
OpenMRS Core Developer
AMPATH / IU-Kenya Support