Just to add to Tim's reply, there is a workplan here: http://www.openehr.org/specifications/spec_roadmap_2008.html . Each row in the table is a major work item and has or will have its own wiki page, found under this page: http://www.openehr.org/wiki/display/spec/Specifications+Home
Currently the groups who work on the specifications are formed by those who are interested registering on the wiki page / or with the team lead. All changes large or small are documented by CRs, and all CRs are publicly online at the Jira server - http://www.openehr.org/issues . You can look here at any time and see the current status of CRs in the next release (the next release right now is 1.0.2). openEHR doesn't use a committee structure like the standards bodies because we have not found it useful for developing good quality engineering specifications or implementations. (It is also very expensive in time, money and costly for the environment). Committees might one day be created for review purposes, but the implementation community already performs the main role here. (Personally I think official standards organisations would be far more useful by providing a review function on IP developed elsewhere by proper analysis/design/build processes than trying to create their own IP, which is generally not very good. This is how ISO, IEC, CCITT and many other SDOs worked in the past. Somehow some of them have become confused about their role and competence in the e-health space.) With respect to what standard a given piece of software adheres to, it will always be one of the official releases of the openEHR specifications. You can always see a detailed view of each release here: http://www.openehr.org/issues/browse/SPEC?report=com.atlassian.jira.plugin.system.project:changelog-panel (this link is Home page > Specifications > Change History). It is up to the project team releasing the software to indicate which release the software conforms to. So for example, if two different archetype editors both implement Release 1.0.1 ADL specification (ADL 1.4) then they should be able to communicate .adl and .xml archetypes. This is indeed currently the case. hope this helps - thomas beale Tim Cook wrote: > Hi Adam, > > On Wed, 2008-07-16 at 13:31 +0100, Adam Flinton wrote: > >> Dear All, >> >> I have raised 2 changes wrt archetypes (wrt regex'es and superclass >> content in subclasses) & a thought occurred which had been troubling me >> for a while which is: >> >> Where exactly are these changes made/agreed to etc? >> > > >> i.e. wrt say HL7 (or other std orgs I have been involved with (e.g. the >> W3C) there are technical committees where I would put these changes, >> possibly there would be a trac/bugzilla so that things don't "slip off >> the radar", votes would be taken & recorded etc. >> >> > > The changes to the RM,AM, etc are handled by the Architecture Review > Board (ARB). > > There is a formal change process documented here: > http://www.openehr.org/specifications/specs_governance.html > > and here: > > http://www.openehr.org/svn/specification/TRUNK/publishing/CM/CM_plan.pdf > > and you can enter your problem Report/Change Request here: > http://www.openehr.org/issues/browse/SPEC?report=com.atlassian.jira.plugin.system.project:changelog-panel > > > >> I have been looking at the java archetype code & have been considering >> putting some time in there but.....how would I know that the code is up >> to a given standard (e.g. say if the regex requirement was changed or >> the super/subclass thing was resolved) given I can find no such committee? >> >> > > You should ask this question on the Java project mailing list: > http://www.openehr.org/projects/java.html I'm not sure what their bug > management process is but the Python project uses Launchpad: > https://launchpad.net/oship/ > > >> This can only be the case if the changes/standards etc are out in the >> open such that coders can have sufficient pre-warning of impending >> changes (or indeed possibly wholly new structures) in advance so that >> different tooling in different languages by different groups be the >> coordinated. >> > > This is certainly the case as you'll see from the above links. > > >> i.e. if I were to generate XML from ADL using the ocean tools will I get >> the same result as if I were to wrap the java tools as ant tasks & use >> them for the same purpose? How would I know? >> > > A question that others can answer as well. ;-) > > HTH, > Tim > > > > ------------------------------------------------------------------------ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -- *Thomas Beale Chief Technology Officer, Ocean Informatics <http://www.oceaninformatics.com/>* Chair Architectural Review Board, /open/EHR Foundation <http://www.openehr.org/> Honorary Research Fellow, University College London <http://www.chime.ucl.ac.uk/> * *
