Dear Thomas and Bill, Perhaps a services based architecture should be considered rather than a single "server." By envisioning the services that we need to provide and then creating a component architecture that fits that model we may be better prepared for the future.
Also, I would recommend taking a look at the ebXML registry which is a federated Open Source registry which is currently available. Also, Sun is implementing OWL support within the registry (which may be handy for users interested in direct reasoning from Archetypes). Warm regards, Peter Peter L. Elkin, MD Professor of Medicine Director, Laboratory of Biomedical Informatics Department of Internal Medicine Mayo Clinic, College of Medicine Mayo Clinic, Rochester (507) 284-1551 Fax: (507) 284-5370 -----Original Message----- From: owner-openehr-technical at openehr.org [mailto:[email protected]] On Behalf Of Thomas Beale Sent: Monday, October 04, 2004 8:58 AM To: Bill Walton Cc: Openehr-Technical Subject: Re: Latest ADL workAtlanta bench and Clinical Archetype Editor Bill Walton wrote: >Is the development effort going to be open to outside developers who want to >contribute? If so, how will that work? > > Hi Bill, we still have to develop the roadmap for the development. There are a number of issues, including: - not many people (as far as we know) have developed an archetype-enabled data kernel before of the kind we envisage, apart from the Ocean Informatics team; previous and current work by CHIME at UCL and by the DSTC are close. Realistically, I don't think that too many people will want to buy into this part of the development, since the logic is quite complex. The code will of course be freely visible, testable and if others 'get it' and want to join in, then it is just a matter of doing so. - there are decisions to be made about architectural deployment. I am in favour of a route which enables a common core code base for all deployments (J2EE, .Net, others like Python/Zope), but this may or may not be realistic in today's fractured world. The process will be more or less as for any other development - it will be visible, and interested developers can offer their input, in which case (after a bit of conversation) they can be added to a team. All they have to do is agree to the commonopenEHR change management process and tools. Where developers contribute, never having met face to face, a rock-solid description of interfaces will of course be needed to ensure components fit together. We will publish a roadmap for other developers to read and discuss within the next 6-8 weeks. I encourage people on this list who would like to be involved in development, or might have resources to offer to discuss their interests here. I hope this answers your question. - thomas - If you have any questions about using this list, please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
