Dear Molly, It was very good to meet you in Cape Town. I'm sorry that I was not able to arrange to attend the OSHCA conference.
This mailing list has been very quiet and I assume that it is because you are all busy at the conference. I was hoping that those of us who could not attend would have updates on all of the activities of the meeting. Is there a place where we can get an archive of the sessions, presentations, discussions, etc.? It looks like you are in the process of setting up another list. I'm not clear on how this new list differs in purpose from the 'OpenHealth' list. Could this be clarified? Best wishes, Mark Spohr --- In openhealth@yahoogroups.com, Molly Cheah <[EMAIL PROTECTED]> wrote: > > > > > Dear Lee, > > > > Thanks for taking this initiative to put the interoperability question > > here. Clearly, this mailing list may not be appropriate as people may > > unsubscribe from this list after the conference. The purpose of this > > participants list is also for subsequent conferences/workshops. > > > > OSHCA can easily set up another list, not specifically to address > > interoperability but more for followup discussion and brain storming > > that took place at the KL Conference so that we don't loose the > > momentum that was started. I'm grappling with the name of this new > > discussion list. Here's the suggested list and I invite your views and > > proposals.. > > 1. [EMAIL PROTECTED] > > 2. [EMAIL PROTECTED] > > 3. [EMAIL PROTECTED] > > 4. [EMAIL PROTECTED] (set up but not activated) > > 5. [EMAIL PROTECTED] (set up but not activated, besides there is a > > openhealth list at yahoogroups that was migrated from the original > > list at Minoru Corporation while waiting for OSHCA to be registered.) > > > > There are three activities to be followed up, of which funding is > > available. > > > > 1. Refining the proposal for an Interoperability Grant, focusing on > > "Gap Analysis for Data Portability amongst current FOSS health > > applications". Related to this will be the enhancement of the OSHCA > > Web-portal to provide the electronic working environment for the > > activities of this proposal - IOSN ASEAN+3 > > Lee's suggestions below will provide the content for this content > > management system. > > > > 2. Cost analysis and comparison of deploying FOSS and proprietary > > systems in health care (specifically hospital/clinic/public health > > systems or a variation of focus) - ?IDRC > > 3. Modelling for capacity building in FOSS for health care in > > developing countries (emphasis of Africa, Latin America and Asia) - > > UNU-IGH. > > > > We're working on the membership list to add to the OSHCA members > > mailing list in preparation for the AGM before the end of 2007. The > > planned AGM didn't happen during the conference. > > > > Many of you were at the training on the 4th day when future road maps > > were discussed. So we welcome suggestions here or at the new list to > > be set up. > > > > Rgds, > > Molly > > Lee Seldon wrote: > > > >> Dear OSHCA leaders, > >> > >> To actually start working on inter-operability, I suggest that OSHCA > >> set up a separate mailing list. Each application should have 1-2 > >> members - those responsible for implementing inter-operability - on > >> the list. > >> > >> An informal suggestion - to canvas your opinions on how to move forward: > >> 1) establish a common vocabulary / minimum data set > >> For this, find a mapping between SNOMED, HL7 v2.x or 3, LOINC, CCR > >> (ASTM E2369 Continuity of Care Record, as different from the new HL7 > >> Continuity of Care Document), etc. Distribute to the open-source > >> developers and ask them to map their existing data fields to one or > >> more of the standard vocabularies. Then find a "greatest common > >> denominator" of data fields. > >> 2) select a communications standard. (Preferably an XML-based one, > >> e.g. HL7 v2.3-2.5 XML, HL7 v3, CCR). > >> 3) depending on which standard is selected, implementation will vary > >> > >> 2 major barriers to the adoption of FOSS in healthcare are > >> 1) lack of (IT) training of healthcare workers > >> 2) lack of support for applications > >> To address (1), OSHCA should develop "health informatics" modules > >> which can be delivered (face-to-face, hands-on and locally) to > >> healthcare workers in various countries. > >> With a view towards later establishing a "support" network for FOSS > >> applications (ad 2), I believe that you will need a "commercial" > >> company that has employees and can sign contracts. E.g. Redhat Linux. > >> > >> Lee > >> _______________________________________________ > >> participants mailing list > >> [EMAIL PROTECTED] > >> http://mailman.oshca.org/mailman/listinfo.cgi/participants > >> > >> > > > > _______________________________________________ > > participants mailing list > > [EMAIL PROTECTED] > > http://mailman.oshca.org/mailman/listinfo.cgi/participants > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: > > 269.7.0/804 - Release Date: 5/14/2007 4:46 PM > > > > >
