Thanks for the kind welcome! We would love to discuss what functionality should and should not belong within the OpenMRS ecosystem; we have been having much the same discussions ourselves and could certainly benefit from you experience. Given our similar goals and our relatively close proximity it seems like we should definitely try to get together at some point. Dr Letchford had wanted us to try to arrange a trip out there to meet with you folks and see the work you've done; perhaps we could set something like that up? Though if you or any of the AMPATH team are ever in Nairobi we should definitely try to meet up!
We are really just getting started and will being having design meetings to create the specifications for the first two modules we plan on building (registration and finance) in the upcoming weeks. Because this is a new effort I am hoping to just use github from the start, rather than have to transition to it at some point in the future. I haven't used the issue tracking or wiki but I assume that they are good enough for what we'd need, at least at the start. Our next stage, as I see it, is really to create the specs for the registration and finance modules and then see how well that fits with what is currently available. On that note, it may not make sense to try and force a finance system into OpenMRS but my thinking is to try and include as much as possible in it to reduce the number of external dependencies. We have been thinking about this for a long time and are excited to be finally working on it! Hopefully we can work together to benefit both of our efforts. I look forward to (hopefully) meeting you in the future! -Wes On Mon, Feb 20, 2012 at 5:08 PM, Jeremy Keiper <[email protected]> wrote: > Jambo, and welcome to OpenMRS! > > I work from the USA with AMPATH in Eldoret and would love to talk sometime > about our common efforts. Our experience so far has been to focus on > OpenMRS as the master patient record and build systems either to interface > with it or be embedded based on their use. It is definitely easier to > write a module and utilize the OpenMRS infrastructure, but some systems can > be more quickly or more efficiently built on top of other open source > projects. If the information is medical in nature, or useful to evaluating > the patient record, it certainly makes sense for that application to be a > module. If the application simply needs access to certain patient > information, perhaps it belongs outside. > > We also have hosted several modules in the OpenMRS-provided subversion > repository, and have a few projects in JIRA related to those modules. > These modules are meant to be shared with the community, so it makes sense > for us. We also have an area in the subversion repository for custom > builds for AMPATH, although we stopped needing custom builds since 1.8 came > out. We also maintain our own JIRA for internal development issues that > are unrelated to the OpenMRS community, and we hope to move to Git sometime > in the future as OpenMRS slowly gets there. > > Again, welcome to the community! Members of the AMPATH development team > are frequently in Nairobi, so perhaps we can meet in person sometime soon. > > Jeremy Keiper > OpenMRS Core Developer > AMPATH / IU-Kenya Support > > > > On Mon, Feb 20, 2012 at 8:33 AM, Andrew Kanter <[email protected]>wrote: > >> Wonderful! So it appears that you received your funding and are now >> underway! This is a great project and obviously we are interested in >> collaborating in Kenya. There is also the question about linking to DHIS2 >> there as well. I will leave these questions up to the dev community to >> provide feedback, but I am very excited to hear that you are moving forward! >> >> Best wishes, >> Andy >> >> *-------------------- >> Andrew S. Kanter, MD MPH >> >> - Director of Health Information Systems/Medical Informatics* >> *Millennium Villages Project, Earth Institute, Columbia University* >> *- Asst. Prof. of Clinical Biomedical Informatics and Clinical >> Epidemiology* >> *Columbia University* >> >> Email: [email protected] >> Mobile: +1 (646) 469-2421 >> Office: +1 (212) 305-4842 >> Skype: akanter-ippnw >> Yahoo: andy_kanter >> >> ------------------------------ >> *From:* Wesley Brown <[email protected]> >> *To:* [email protected] >> *Sent:* Monday, February 20, 2012 6:26 AM >> *Subject:* [OPENMRS-DEV] Request for Feedback >> >> Greetings! >> >> OpenMRS provides a great clinical data gathering and analyzation tool as >> well as a wonderful platform for an integrated hospital management >> information system (HMIS). However, the business management pieces to >> implement such a comprehensive HMIS within OpenMRS are not complete and >> those pieces that do exist lack an overall cohesiveness. The Christian >> Health Association of Kenya (CHAK) would like to fill that gap and add a >> comprehensive HMIS suite that is built on top of OpenMRS. >> >> Our goal is to be the go-to solution for HMIS software at hospitals that >> cannot afford expensive commercial software packages. We will create the >> core modules required to work within an HMIS ecosystem which we will >> define. This will eventually entail creating modules to handle every >> aspect of hospital management along with the necessary connections to other >> modules, though this is a goal that may not be reached for some time. >> While we will be working with specific hospitals for our implementations >> we will design each module to be used in many varied environments. >> >> We know that some modules to do this type of work already exist and, >> where possible, we would like to extend these modules. In a quick survey >> of the current OpenMRS modules that provide some HMIS features we found the >> following: >> >> Billing Module <https://wiki.openmrs.org/display/docs/Billing+Module> >> Facility Data >> Module<https://wiki.openmrs.org/display/docs/Facility+Data+Module> >> Radiology Module <https://wiki.openmrs.org/display/docs/Radiology+Module> >> Register Module <https://wiki.openmrs.org/display/docs/Register+Module> >> Registration >> Module<https://wiki.openmrs.org/display/docs/Registration+Module> >> >> Simple Pharmacy >> Module<https://wiki.openmrs.org/display/docs/Simple+Pharmacy+Module> >> >> If there are other applicable modules that we have missed please let us >> know. >> >> We are writing here to both announce our effort to the OpenMRS >> development community and ask for your help. We are currently in the >> design phases of this project and hope to take advantage of the great >> wealth of information the OpenMRS developers have to share. As mentioned >> before, we also hope to build on top of some of the excellent HMIS modules >> that already exist, unless there are objections to this. >> >> Questions Going Forward >> >> 1. Can/Should we reuse any of the OpenMRS supporting services. Like >> any software project we will need: >> 1. Project management space >> 2. Bug tracking >> 3. A public web site >> 4. A wiki and documentation >> 5. Source code hosting >> 6. A build server >> >> We have already set up an empty github repository at >> https://github.com/OpenHMIS/OpenHMIS as that provides many of the >> above for free and will add members to it as requested. >> >> 2. Can/Should this be created as just a set of modules or >> something more concrete that sits on top of OpenMRS? >> >> >> Thanks very much, we appreciate any feedback that you may have! >> -The OpenHMIS Team >> >> *OpenHMIS Team Info* >> Vincent Kiarie >> HMIS Manager >> CHAK, Nairobi KENYA >> >> Stephen Letchford, MD FACP FAAP >> Medical Director >> CHAK Working Group member >> AIC Kijabe Hospital, Kijabe KENYA >> >> Meshack Kawinzi >> Medical Informatics Intern >> CHAK, Nairobi KENYA >> >> Wes Brown >> Senior Software Developer >> CHAK, Nairobi KENYA >> [email protected] >> IRC: ibewes >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>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]
