Hi Bert,
We designed some archetypes based on openehr demographic rm, and taking into account ISO/WD 22220 (Identification of subjects of health care), ISO WD for Provider Identification and our knowledge of how Brazilian health system works. I will send them to you in a separate e-mail. Note that they are still a draft and are in Portuguese. Eventually I may translate them to English, but in the meantime feel free to ask any questions and use them as you wish. I will also send a copy to Thomas Beale so that openEHR Foundation may use them as it sees fit. Cheers, Sergio De: openehr-clinical-bounces at openehr.org [mailto:openehr-clinical-bounces at openehr.org] Em nome de Bert Verhees Enviada em: segunda-feira, 8 de setembro de 2008 08:25 Para: For openEHR clinical discussions Assunto: Re: demographic archetypes Please excuse me for coming back to this, almost a year later. Again I am on the point where I want to maintain code for the EHR-structure. Still I have the same questions..... The point is, I can hardly find archetypes based on this, but I find more archetypes based on more generic data-structures like CLUSTER, like the nhs-archetypes, listed below, URL has changed since, but they still exist. But there are almost no archetypes published based on the Demographic subtree of the RM-model. Thomas Beale schreef: > Another question, how do people from the NHS, who built many many > archetypes, but none on demographic base construct their EHR's? > in the NHS so far there is no real EHR, only something called PSIS aka the 'Spine' (see http://www.connectingforhealth.nhs.uk/resources/systserv/spine-factsheet). This has only a very basic architecture at the moment. They have not really decided on an EHR architecture yet. That is OK, then, we are not to use the NHS archetypes, I understand. Thomas Beale schreef: > Does that mean that the demographic classes in the Reference Model > will > go the same way? > Hi Bert, on the contrary, demographic archetypes and demographic a archetype editor capability will have increased development around them in 2008. The latest version of the Archetype-editor from Ocean (may, 2008) does still no support this kind of archetypes. Again, what is the future of the Demographic part of the RM-model? Still there are not many examples (almost none) and no software-tooling-support. What are the reasons for this? Thomas Beale schreef: > Now my question, how can we facilitate an EHR-construction, as > described > in the documentation, using the available archetype-editors? > can you be more precise about what you mean here - building an EHR itself is not the business of an archetype editor.... I don't understand this. In my opinion, an EHR is build up in datastructures which are defined by archetypes, some of them are of based on Demographic. Thus, it is not possible to construct an EHR, using the archetype-editors as available. (It is no problem, one can always build an archetype in vi, and test it afterwards.) I just want to know what I misunderstand. Thomas Beale schreef: > Or is it more or less that that we are to use the Party-ref as an > Object-ref, and do not take the specifications to literally? (because, > they, f.e. will be updated in the future) > can you be more precise here? This was more or less a joke, an EHR-Status contains a Party-Ref. If the demographic would disappear, (or like NHS, are not used) it is not possible to create an EHR according to the specs. But as I said, this was more or less a joke. Nevertheless, the practical issues around the demographic puzzle me still. So I have two questions - Is there a repository in which (example) demographic archetypes are? - When will the Ocean Archetype-editor start supporting demographic archetypes? Thanks, Bert Ian McNicoll schreef (19-nov-2007): Currently at http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.person_address.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.person_demographics.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.person_name.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.person_telecoms.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.professional_role.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.care_professional.v1.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.address.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.organisation.v2draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.individual_personal.v1draft.adl http://svn.openehr.org/knowledge/archetypes/dev-uk-nhs/adl/openehr/ehr/clust er/openEHR-EHR-CLUSTER.individual_professional.v1draft.adl Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20080911/282fca72/attachment.html>
