|
From: lemoene <le...@bi...> - 2011-11-09 12:35:05
|
Hi Alfonso > BIKA was finally accepted as a solution for lab and the start of service will begin on January 2, 2012 on an experimental basis to begin final production activities on February 1. > Under this scenario, we have the following considerations: > - BIKA be integrated with a medical management system (Medical), medical records (OpenMRS) and business (ERP), for which there are various connectors. I think it is going to be impossible to get everything in place at your suggested implementation date Alfonso. We are going at full tilt, but our Bika 3 LIMS trunk is 85% complete today and only after its completion will we be branching Bika Health again and I cannot see it being ready by 2 January, even without these interfaces. Re connectors, Mirth is definitely the best for HL7 messaging and we have some experience with it already. > - We would love to work with GNU Health (Medical), however, there was no concrete support from its developers and because of a business decision will have to do a fork (or maintain compatibility with OpenERP Medical).- That is not being supported anymore? > We would have liked to eliminate the dependence on OpenERP, however, all business conditions are practically built, while Tryton still has a lot of work Thanks for the heads-up. Tryton/GNU Health is a big requirement amongst our other prospects > .- Together the experience of a Chilean project, led by Victor Aravena, to integrate OpenMRS for records management as a backend. We demoed an OpenMRS interface 2 years ago, there was no uptake from the OpenMRS community and this too will have to be revisited. At the time the OpenMRS data structure only allowed one analysis result per 'encounter' - they might've modified that since > - Will be enhanced system management in mobile devices. We are investigating http://webandmobile.mfabrik.com/ for this purpose > - All software stays on as a contribution from the clinic and republished under the terms of the license. Bika is strictly GPL, so that's good to know > This, then, we must focus on: > > - BIKA must manage connections to SQL databases: mysql and postgresql. > If not, we must develop it. You might've seen the Plone Relstorage and ContentMirror discussions here earlier. That makes the SQL option quite simple to implement and we don't foresee any problem with that (famous last words) > - My company have 3 developers for the project (paid), 2 of them will be in Peru, but another may be appointed by the foundation (in something like a Summer of Code and paid by my company) until February > 2012. Do they have Plone experience? Its quite a steep learning curve > - My company will have an interface designer (HTML / CSS) to assist in the project. That could be useful, though we don't find much wrong with Plone's default Sunburst theme. We do have the odd problem with tables overlapping because it uses percentages for setting widths. It'll be great if that can be sorted > - We will handle the translation into Castilian. Some work has been done in Spanish. Though Bika 3 has to be walked through to make sure all tags are prepped for translation, the translation itself entails the the conversion of a .po file of terms only > - Develop guides for use in video (Castilian). Nice > - Will also work with laboratory equipment available in the Peruvian market. It could be most productive if your developers can start with the instrument server design <http://www.bikalabs.com/softwarecenter/bika/roadmap/7/BLISSpec/view> we discussed earlier? Since it is free standing we won't get into one another's way on the Bika code itself. > Because it is a turnkey project will add several features or modules, which will publish a document shortly. In Spanish/Castillian ?-) In Google translate we trust! > It is important to clarify that this business opportunity for my company generates important conditions: > - A clinic that wants to implement the solution. > - A clinic you want to fund what is not done. Loud applause goes round the room...-) > - A clinic for sharing the code and understand the value of FLOSS. All of these are hugely appreciated > We want to make clear that we do not want to compromise the foundation, but seek to help it so you can work collaboratively without double efforts. > > BIKA additionally is being taken to the Ministry of Health to state medical facilities with this solution, as with our partners in Chile, as part of social assistance. Thanks for all of this, great stuff. I am a born pessimist, but those implementation dates, 8 weeks from now with the silly season in between, are impossible. The Instrument server in itself could take a any number of weeks depending on the number of instruments in the equation. From our side we'll do all we possibly can to make this work out. Am looking forward to your document Bests l |