SELECT count(c/uid/value) FROM ehr e...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How to set external terminology validation](https://discourse.openehr.org/t/how-to-set-external-terminology-validation/3755)
> I'm trying to use external terminology validation, right now there is no validation as I'm able to set any value. The default configuration ( [8. Terminology Validation — EHRbase documentation](https://ehrbase.readthedocs.io/en/latest/08_terminology_validation/index.html#configuration)) the validation.external-terminology.enabled=false by default in the application.yml, how can I set that value to true to have external terminology validation?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Typos in ODIN specification](https://discourse.openehr.org/t/typos-in-odin-specification/3753)
> A few typos for the backlog...
- 'funded in by the' should be 'funded by the'
- 'identiers' should be 'identifiers'
- 'in the this specification' should be 'in this specification'
- 'informatoin' should be 'information'
- 'optionally following by a version' should be 'optionally followed by a version'
- 'grammaar' should be 'grammar'
- 'comma-separated lists of item,' should be 'comma-separated lists of items,'
- 'seriliased' should be 'serialised'
- 'straighforward' should be...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Typos in AOM 1.4 specification](https://discourse.openehr.org/t/typos-in-aom-1-4-specification/3752)
> Spotted some typos in the spec.
- Uuniversity should be University
- archteype technology should be archetype technology
- an node representing should be a node representing
- 'An archetype is a modelled' should be 'An archetype is modelled' (Section 3.1)
- 'identfication' should be 'identification'
- 'constraints on a object' should be 'constraints on an object'
- ' The `any_allowed` function a node' should be ' The `any_allowed` function of a node'
- 'standard aproach' should be...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Querying more than one template (JOIN)](https://discourse.openehr.org/t/querying-more-than-one-template-join/3751)
> Probably this is an overkill or there is somebody out there who has faced the same issue.
I am trying to perform a simple "join" (as per SQL terms) to count patients that are contained in the 3 different templates (different archetypes), but I cannot seem to get a response. I am not sure of the behaviour hence seeking for help here, hopefully someone can guide me a.
However, if I try the count on individual templates, I do get the desired result.
I am using Better openEHR...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Error with web template and FLAt example API in EHRbase](https://discourse.openehr.org/t/error-with-web-template-and-flat-example-api-in-ehrbase/3741)
> Hi,
I am running the latest EHRbase using standard docker-compose file. Getting 500 - internal server error for the following APIs
```
/ehrbase/rest/ecis/v1/template/{{template_id}}/example?format=FLAT&exampleFilter=OUTPUT
/ehrbase/rest/ecis/v1/template/{{template_id}}
```
Can someone tell me where I am making a mistake? Are the paths correct?
regards
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [DocumentReference in EHRbase](https://discourse.openehr.org/t/documentreference-in-ehrbase/3739)
> Hello,
I am trying to create new DocumentReference using FHIR Bridge, but my response for that is:
```
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "Unknown resource type 'DocumentReference' - Server knows how to handle: [Condition, Immunization, Composition, DiagnosticReport, Patient, QuestionnaireResponse, Consent, Observation, Encounter, Procedure, AuditEvent,...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [How to record whether a cancer condition is new, relapsed or a secondary cancer?](https://discourse.openehr.org/t/how-to-record-whether-a-cancer-condition-is-new-relapsed-or-a-secondary-cancer/3736)
> In a use case related to cancer, it is a request to classify the cancer condition within the three values:
* New cancer
* Relapse
* Secondary cancer
There are various elements in both Problem/Diagnose and Problem/Diagnosis qualifier, but none does quite fit the value set. I do not want to split into several elements, so which one to chose?
Problem/Diagnosis qualifier has two possible elements, maybe...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [2023 Nominations for openEHR International Board Directors](https://discourse.openehr.org/t/2023-nominations-for-openehr-international-board-directors/3734)
> We have 3-Director positions due for election to the openEHR International Board this year, one to represent each of the membership levels below:
* **Organisational Member** (currently Mikael Nyström)
* **Industry Partner** (currently Bjørn Næss)
* **Individual / Professional Member** (currently Rachel Dunscombe)
Current Board members may re-stand for nomination should they wish to do so, and nominations are now open for existing members.
If you are not currently a paid-up member and wish...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR Educator Recognition Program](https://discourse.openehr.org/t/openehr-educator-recognition-program/3730)
> openEHR International are delighted to announce the [Educator Recognition program](https://openehr.org/programs/education/recognition), developed by the Education Program Board (EPB) for individuals offering openEHR courses.
Assessment ensures that they have the relevant skills and expertise, and will protect the openEHR name by encouraging course and teaching quality.
Individuals who successfully complete assessment will be listed under [openEHR professional...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [About the Entity/demographics category](https://discourse.openehr.org/t/about-the-entity-demographics-category/3721)
> Discussions about openEHR Demographics and Entity models and more generally MPIs & similar.
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [Issues and ideas on the demographic model](https://discourse.openehr.org/t/issues-and-ideas-on-the-demographic-model/3720)
> Hi all, I'm progressing with a demographics data repository and demographics REST API and found some issues I would like to share to have your opinions.
For reference, this is the demographics UML:
1. many to one association between ACTOR and ROLE
ACTOR has a reference to 1 or many ROLEs
ROLE has a reference to 1 ACTOR
When creating those objects, since the references between them are bidirectional and mandatory, you...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Data deletion process / slides / stuff](https://discourse.openehr.org/t/data-deletion-process-slides-stuff/3717)
> Helllooooo....
I've been asked to provide an overview of the process and nature of soft deleting in openEHR and wondered if anyone had already done something similar? I need to detail what happens to the data, how the audit works for a clinical group and reinventing the wheel is not a preferred option.
Thanks!
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Announcing the formation of the openEHR Clinical Program Board](https://discourse.openehr.org/t/announcing-the-formation-of-the-openehr-clinical-program-board/3713)
> openEHR International has great pleasure in announcing the formation of the [Clinical Program Board ](https://www.openehr.org/programs/clinical/board_members)(CPB), which is the governing group for the Clinical Program, the part of openEHR responsible for clinical modelling and related areas.
We received a large number of applications for positions on the CPB and its associated Clinical Program Board Experts Panel (CPBXP). We have opted to create the CPB with a minimum core group of just...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Inforsalud 2023, 21-23 March 2023](https://discourse.openehr.org/t/inforsalud-2023-21-23-march-2023/3709)
> Dear all,
[Inforsalud 2023](https://seis.es/inforsalud-2023/), the Spanish health informatics congress will be held in Madrid from 21th to the 23th of March 2023. [Here is the program](https://seis.es/wp-content/uploads/2023/03/Programa-Inforsalud-2023.pdf)
I would like to invite you all to the presentation on the 23th by my colleague Alberto Maldonado about the importance of modelling for the use and reuse of clinical data.
I know for a fact that there will be more Spanish 'openehrs'...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [New Swedish openEHR platforms and tools RFI](https://discourse.openehr.org/t/new-swedish-openehr-platforms-and-tools-rfi/3682)
> Region Östergötland is making a Request For Information on openEHR platforms and tools. We are really happy to tell that it is done in collaboration with several other regions, which means that the 4 or 5 largest healthcare regions in Sweden are part of this RFI!
Region Östergötland has the intention to proceed with a procurement after this RFI. The other regions will soon state whom they are along with their individual goals.
The planned official announcement date for the RFI is **April...
**[News](https://discourse.openehr.org/c/community-news/25)** - [Prof David Ingram's new book Health Care in the Information Society](https://discourse.openehr.org/t/prof-david-ingrams-new-book-health-care-in-the-information-society/3672)
> Dear openEHR colleagues,
Exciting news: the father of health informatics education and research in the UK, Prof emeritus David Ingram, has written a book on the history of computing in the healthcare domain, called Health Care in the Information Society. In what seems a moment of synergy too good to be true, I am posting this on the 20th birthday of openEHR (born 13 Mar 2003).
> **David**: the book draws together history of people, ideas, and events, from times before the computer and...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR Conference Barcelona - 6th of June 2023](https://discourse.openehr.org/t/openehr-conference-barcelona-6th-of-june-2023/3671)
> Dear friends
We are finally announcing the [openEHR International](https://www.linkedin.com/company/openehr-international/) conference to be held in Barcelona the 6th of June 2023. The conference will be organised by [Sistema de Salut de Catalunya](https://www.linkedin.com/company/salutcat/) and [Fundació TICSALUT](https://www.linkedin.com/company/fundacio-ticsalut/).
We have booked the main conference room at the Faculty of Medicine of [Universitat de...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Bug in export of ORDINAL texts defined in templates](https://discourse.openehr.org/t/bug-in-export-of-ordinal-texts-defined-in-templates/3670)
> Hi!
When trying to be [a bit too clever](https://discourse.openehr.org/t/how-to-use-the-symptom-sign-screening-questionnaire-archetype/1984/13?u=erik.sundvall) and use the (now multilingual!) support to make ORDINAL type selection and value list definition in templates (rather than only in archetypes), then I encountered what I believe to be an export bug in Archetype Designer (AD).
The **text labels of ordinals defined at template level** (as opposed to archetype level) **do not get...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Medication summary" ready for publication](https://discourse.openehr.org/t/medication-summary-ready-for-publication/3666)
> The archetype ‘[Medication summary](https://ckm.openehr.org/ckm/archetypes/1013.1.2825)’ has been through two review rounds, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on March 17th.
Kind regards on behalf of the editors,
John Tore Valand
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Specimen_summary" ready for publication](https://discourse.openehr.org/t/specimen-summary-ready-for-publication/3665)
> The archetype ‘[Specimen_summary](https://ckm.openehr.org/ckm/archetypes/1013.1.6013)’ has been through two review rounds, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on March 17th.
Kind regards on behalf of the editors,
Liv Laugen
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Persisting "% change" of an OBSERVATION](https://discourse.openehr.org/t/persisting-change-of-an-observation/3661)
> As part of implementing [PASI score](https://ckm.openehr.org/ckm/archetypes/1013.1.5395), the requirement has come up to record % change since a previous recording. Has anyone else had this requirement, and if so how did you handle it? My initial thought was to use the INTERVAL_EVENT with a math function, but this has two issues (that I've identified, there may be more):
1. There's no math function for % change, just for (absolute) change
2. Recording the % change for each data element would...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [I can't access to cluster's attributes](https://discourse.openehr.org/t/i-cant-access-to-clusters-attributes/3655)
> Hi! I'm using PostMan in order to create a composition with different observations and instructions, and the creation of the composition it's ok, all attributes that I set were created, but when I try to execute an aql query in order to get some attributes of a cluster that it's an attribute of an instruction, i don't know why it seems as it doesn't exists by the path I'm giving to the aql query, because the path it's correct.
This is the instruction that i'm creating:
{
...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Storing a query with no version - correct behavior when the query already exists?](https://discourse.openehr.org/t/storing-a-query-with-no-version-correct-behavior-when-the-query-already-exists/3634)
> The API [spec](https://specifications.openehr.org/releases/ITS-REST/latest/definition.html#tag/Query/operation/definition_query_store.yaml) does not define a 409 response for this operation. If a query already exists with the specified name, what is the correct behavior of the endpoint? My guess is to increment the patch number in the semver, but I'd like confirmation.
**[Regional communities](https://discourse.openehr.org/c/reg-com/110)** - [About the Regional communities category](https://discourse.openehr.org/t/about-the-regional-communities-category/3623)
> (Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:
- Why should people use this category? What is it for?
- How exactly is this different than the other categories we already have?
- What should topics in this category generally contain?
- Do we need this category?...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [What would you like to see in a new openEHR CDR?](https://discourse.openehr.org/t/what-would-you-like-to-see-in-a-new-openehr-cdr/3621)
> Hi all, most here might not know we are working on Atomik, a new openEHR CDR.
Soon we will release a set of demos, tutorials and documentation that would help as educational materials for anyone interested. We would like to know if you have anything in particular you would like to see on those educational materials, for instance in the video demos.
About Atomik, it's derived from EHRServer which was the first open source implementation of an openEHR CDR. In Atomik we improved and optimized...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [FHIR Bridge db connection](https://discourse.openehr.org/t/fhir-bridge-db-connection/3609)
> Hey everyone,
So at this point I am trying to analyze in depth the ehrbase construction regarding the relations. My setup for now is full environment for fhir bridge and the issue is that I am not able to check the relations for postgres/ehrbase user. Although I am creating templates/ehr's, there is always "Did not find any relations.". I am not very into java/spring framework (I am doing as python junior), so I guess there is some spring flavour as the reason, but I can not find anything on...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Imaging Examination - which Archetype to use](https://discourse.openehr.org/t/imaging-examination-which-archetype-to-use/3608)
> Hello! Absolute novice here. I don't fully understand how these Archetypes are supposed to be used but I need to use them for a software project.
There is this generic Archetype: [Imaging examination](https://ckm.openehr.org/ckm/archetypes/1013.1.1494/mindmap)
And there is [OCT](https://ckm.openehr.org/ckm/archetypes/1013.1.1464), which is - if I'm not mistaken - not a specialisation of the generic Archetype, even though it is a different type of imaging examination.
Which of these...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Channels - how to make a new, and by who?](https://discourse.openehr.org/t/channels-how-to-make-a-new-and-by-who/3602)
> New functionality: Now it is possible to have private chats and also Channels. This can replace Slack. But who can make a new channel, and how? I would also prefer to link to a channel in a topic within a discussion in one of the categories to be able to sort of jump out to a channel chat from a topic, and keep it within that topic as a link.
Regards, Vebjørn
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Fhir-bridge keeps failing](https://discourse.openehr.org/t/fhir-bridge-keeps-failing/3600)
> Hello everyone,
I am trying to use **fhir-bridge** for integrating **Medplum** and **ehrbase**, **mvn clean install & mvn package** worked fine. However, **java -jar target/fhir-bridge-1.5.5.jar** keep throwing an error (see as attached in the image)
What could I be doing wrong?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Cancer treatment in general, Particle therapy, OMOP, DigiOne, European Particle Therapy Network](https://discourse.openehr.org/t/cancer-treatment-in-general-particle-therapy-omop-digione-european-particle-therapy-network/3599)
> Hi, everyone
In Norway we're currently working with all mentioned in the header. No less! At least I have nightmares about how wide this is and how much work is ahead of us, so asking you all: Have you made anything related to this recently that we can tap into, or anyone to work together with? I know the HighMed group have made some archetypes about radiation therapy and or particle/proton. And I know there are work in Christie regarding cancer treatment, especially proton, but not openEHR?...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [I can't do a valid body to "Create CONTRIBUTION" of EHR API](https://discourse.openehr.org/t/i-cant-do-a-valid-body-to-create-contribution-of-ehr-api/3596)
> I have this body:
{
"uid": {
"value": "6eb91861-faa9-4989-a811-078f674d570a"
},
"versions": [
{
"_type": "VERSIONED_COMPOSITION",
"lifecycle_state": {
"_type": "TERMINOLOGY_CODE",
"terminology_id": "openehr",
"code_string": "532"
},
"data": {
"_type": "COMPOSITION",
"name": {
"_type": "DV_TEXT",
...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Found an interesting case when an OPT might be invalid and I think modeling tools are not checking it](https://discourse.openehr.org/t/found-an-interesting-case-when-an-opt-might-be-invalid-and-i-think-modeling-tools-are-not-checking-it/3594)
> Someone reported a problem with the RM data generator and validation on EHRBASE on our openEHR SDK https://github.com/ppazos/openEHR-OPT/issues/149
Context: I understand in AOM 1.4 if a sibling C_OBJECT has the same node_id, the name should be different, so we could have CLUSTER.items containing an ELEMENT at0002 that has name "xxx", another ELEMENT at0002 that has name "yyy" and yet another ELEMENT at0002 with name "zzz".
If that is correct, we need to consider what happens is someone adds...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [LOCATABLE name with a SNOMED code](https://discourse.openehr.org/t/locatable-name-with-a-snomed-code/3593)
> I want to encode the RM locatable name with a terminology.
Archetype designer allows only DV_TEXT and no option to change it into DV_CODED.. any idea how to do that except for editing the ADL everytime ?
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How do i add ml/m2 in the archetype designer](https://discourse.openehr.org/t/how-do-i-add-ml-m2-in-the-archetype-designer/3592)
> I wanted to add that using curly braces, but its a Volume/Area which is not allowed with curly braces.
VOLUME/MASS works but only with cm2.
Any other option left other then the change request for the xml in jira ?
related: https://discourse.openehr.org/t/adding-to-the-dv-quantity-units-options/1964
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Social context screening questionnaire" ready for publication](https://discourse.openehr.org/t/social-context-screening-questionnaire-ready-for-publication/3587)
> Dear all
The Social context screening questionnaire has been through one review round. There were some misunderstanding of the difference between the abstract screening questionnaire archetypes, of which this is an example, and the specific archetypes designated for persistent storage in an EHR. The editor feedback is hence detailed and educational.
Otherwise there were no major push-back. Editorial group realised two elements were unnecessary, and removed. A use case of for example...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [SpO2 scale 2 decision](https://discourse.openehr.org/t/spo2-scale-2-decision/3586)
> Hi
[NEWS2 archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.3342) requires a trigger to select SpO2 scale 1 or SpO2 scale 2, the 'default' being the former and the exception being scale 2.
The trigger is a clinical decision to put a patient on scale 2, based on an arterial blood gas result indicating the patient has hypercapnic respiratory failure (HCRF) and/or other factors.
We have discussed using the [Problem diagnosis...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Archetype Designer doesn't support other ITEM_STRUCTUREs besides ITEM_TREE](https://discourse.openehr.org/t/archetype-designer-doesnt-support-other-item-structures-besides-item-tree/3585)
> I'm trying to test the differences between Ocean AE and and Better AD but can't create an entry with an ITEM_LIST or ITEM_SINGLE in the AD.
Maybe there is someone with more experience in this tool than me that knows why those types are not available, or maybe I'm not finding them in the UI.
Thanks!
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Do all modeling tools remove c_objects with occurrences 0..0?](https://discourse.openehr.org/t/do-all-modeling-tools-remove-c-objects-with-occurrences-0-0/3581)
> Hi all, I'm working on the validation part of the openEHR Conformance Verification Framework, and I'm wondering if it's possible to have OPTs with C_OBJECTs that have occurrences 0..0.
Similar question for C_ATTRIBUTEs with existence 0..0
Thanks!
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [HL7 CDA template implementation to OpenEHR OPT](https://discourse.openehr.org/t/hl7-cda-template-implementation-to-openehr-opt/3579)
> Hi everyone. So this is my first post here, so please bear in mind that I may not know all the posts yet in this topic. I have a qustion regarding the polish HL7 CDA implementation of e.g. clinial document as OpenEHR file. The case is that, I am trying to remap Clinical document (like: https://www.cez.gov.pl/HL7POL-1.3.2/plcda-html-1.3.2/plcda-html/tmp-2.16.840.1.113883.3.4424.13.10.1.18-2020-06-08T000000.html ) into template with proper archetypes. Could you give me any advice on that, I...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EhrBase: Implementation with remote databases available?](https://discourse.openehr.org/t/ehrbase-implementation-with-remote-databases-available/3576)
> Hey I'm looking to implement the openEHR server. From what I understand it's a docker image that I can deploy on something like a Kuberentes cluster. However, after reading through the documentation I can't see how to define the database URL. Is there a way in which I can point to an RDS on AWS or Cloud SQL for Google cloud for instance? I'd like to have snapshots and I don't want to trust persistent data to a Docker container. All we need is that compute instance to go and everything will be...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Export Template in ADL2 format](https://discourse.openehr.org/t/export-template-in-adl2-format/3572)
> Is it possible to export a template in ADL2 format?
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [Connecting openEHR CDRs to Tableau data visualisation tools?](https://discourse.openehr.org/t/connecting-openehr-cdrs-to-tableau-data-visualisation-tools/3562)
> Hi!
**Question**
Is anybody aware of existing (or planned) integrations from an openEHR CDR to *Tableau* data visualisation tools?
**Background**
We have seen similar integrations from openEHR CDRs to the statistics tool/language "R" in the form of code that transform openEHR AQL query reponses to R-native data structures (There are also similar approaches for Python) See e.g. links in the thread...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Possible error in AOM 1.4](https://discourse.openehr.org/t/possible-error-in-aom-1-4/3559)
> https://specifications.openehr.org/releases/AM/Release-2.2.0/AOM1.4.html#_c_multiple_attribute_class
In C_MULTIPLE_ATTRIBUTE invariants:
***Members_valid***: `members /= Void and then members.for_all(co: C_OBJECT | co.occurrences.upper <= 1)`
Then we have archetypes like:
events cardinality matches {1..*; unordered} matches {
POINT_EVENT[at0002] occurrences matches {0..*} matches {
a. events is C_MULTIPLE_ATTRIBUTE
b. POINT_EVENT is a C_OBJECT in the CMA.members and...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Download older version of Archetype](https://discourse.openehr.org/t/download-older-version-of-archetype/3552)
> Hi,
I'm new here and starting to play around. Question that came up:
how to download an older version of an archetype. For example:
I want to download archetype Dosage v1 instead of v2. Is that possible? How to do?
Any help appreciated!
Br,
Richard
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Welcoming ECOSYSHUB as openEHR Industry Partner members](https://discourse.openehr.org/t/welcoming-ecosyshub-as-openehr-industry-partner-members/3546)
> We are delighted to welcome [ECOSYSHUB](https://www.ecosyshub.com/) to membership, who have [joined openEHR International as Bronze Industry Partners](https://openehr.org/community/industry_partners_detail/ecosyshub-llc).
Headquartered in California US, ECOSYSHUB is a technology company that focuses on delivering innovative solutions for data-driven analytics. Their approach of abandoning centralised data management and adopting cloud-based platforms has helped companies to improve their...
**[RM](https://discourse.openehr.org/c/rm/42)** - [How data access control or filter is applied when creating an EHR_EXTRACT](https://discourse.openehr.org/t/how-data-access-control-or-filter-is-applied-when-creating-an-ehr-extract/3540)
> Considering scenario where a patient has medicine list and problem list and these are saved as persistent composition instances. This patient has a few problems and medicines that are considered as sensitive so the patient doesn't want to share these sensitive information with other healthcare providers.
When an EHR EXTRACT is created, how the sensitive information (particular entries in the persistent compositions) could be filtered/excluded in the EHR_EXTRACT_CONTENT? In another word,...
**[RM](https://discourse.openehr.org/c/rm/42)** - [EHRs with different system_id in the same server?](https://discourse.openehr.org/t/ehrs-with-different-system-id-in-the-same-server/3535)
> Hi! Just checking a thing
The EHR root object has a system_id attribute defined in https://specifications.openehr.org/releases/RM/latest/ehr.html#_ehr_class saying “The identifier of the **logical** EHR management system **in which this EHR was created**.”
This raises the question:
Can an instance of an EHR server contain a mix of system_id strings (for different EHR objects of course) if EHRs for example have been imported from different systems (e.g. the patient moved their entire EHR...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Issue with STRUCTURED format](https://discourse.openehr.org/t/issue-with-structured-format/3528)
> Hi all,
I'm busy building a 'vendor neutral application' and retrieving compositions from EHRBase and Better using the structured format. I understand this format is not yet formally a standard but this was the result with a text item.
EHRBase returns
"phenotype_description": [
{
"|formatting": "plain",
"|value": "Skeletal dysplasia"
}
]
Better returns
"phenotype_description":...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL and ADL syntax highlighting in Discourse](https://discourse.openehr.org/t/aql-and-adl-syntax-highlighting-in-discourse/3526)
> Continuing the discussion from [Formatting AQL in new topics](https://discourse.openehr.org/t/formatting-aql-in-new-topics/3464):
[quote="siljelb, post:1, topic:3464"]
(Also, is it possible to add ADL and AQL syntax highlighting to Discourse?)
[/quote]
@ian.mcnicoll @thomas.beale Please feel free to move this topic if #specifications:aql isn't the right place. @siljelb asked if this is possible - as far as I am aware **yes** it is, but **we would need a HLJS-compliant syntax highlighter to...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [‘Glasgow Outcome Scale - Extended (GOSE)’ is ready for publication](https://discourse.openehr.org/t/glasgow-outcome-scale-extended-gose-is-ready-for-publication/3522)
> Dear all,
The archetype ‘[Glasgow Outcome Scale - Extended (GOSE)](https://ckm.openehr.org/ckm/archetypes/1013.1.6671)’ has been through one review round, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on February 10th.
Kind regards on behalf of the editors,
Hanne Marte Bårholm
**[RM](https://discourse.openehr.org/c/rm/42)** - [Archetypes with intervals](https://discourse.openehr.org/t/archetypes-with-intervals/3507)
> Hi !
Can someone please help me to create an Archetype which contains Intervals? (ex : **Interval of Duration**, **Interval of DateandTime**)?
Thank you ! :slight_smile:
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [Equivalent to FHIR Annotation](https://discourse.openehr.org/t/equivalent-to-fhir-annotation/3505)
> Hi everybody,
my colleague at vitragroup raised an issue regarding the way how clinicians might annotate data. Any idea how we should handle FHIR's [Annotation](https://hl7.org/fhir/datatypes.html#Annotation) data type (e.g. as used in [Condition.note](https://hl7.org/fhir/condition-definitions.html#Condition.note))?
I think the main issue is to assign a repeating element like "comment" in the problem/diagnosis archetype (at the moment, it has 0..1 though) some additional information that...
**[General Discussion](https://discourse.openehr.org/c/general-discussion/132)** - [Detected a potential breaking change in Common IM that doesn't seem to be documented](https://discourse.openehr.org/t/detected-a-potential-breaking-change-in-common-im-that-doesnt-seem-to-be-documented/3503)
> From RM 1.0.2 common.pdf section 5.1 (https://specifications.openehr.org/releases/1.0.2/architecture/rm/common_im.pdf):
` A FOLDER instance contains more FOLDERs and/or items, which are references to other (usually versioned) objects`
Note the "usually".
The description in RM 1.1.0 is the same (https://specifications.openehr.org/releases/RM/Release-1.1.0/common.html#_overview_4) but the UML clearly shows a binding of the items OBJECT_REF to VERSIONED_OBJECT, which determines that the...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Facing issue in AQL when queried across different templates across different archetypes](https://discourse.openehr.org/t/facing-issue-in-aql-when-queried-across-different-templates-across-different-archetypes/3499)
> Facing issue while executing AQL, where it has two templates with different archetypes. Used same ehr_id for composition insertions.
AQL:
SELECT
e/ehr_id/value
FROM ehr e CONTAINS
COMPOSITION c[openEHR-EHR-COMPOSITION.encounter.v1]
CONTAINS
(OBSERVATION o[openEHR-EHR-OBSERVATION.problem_screening.v1]
OR
OBSERVATION...
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [FHIR Content-Type](https://discourse.openehr.org/t/fhir-content-type/3498)
> Hi everyone,
I am trying to create a **patient app** that implements fhir to create a patient resource, I kept getting an error message that **HAPI-0956: No body was supplied in request**. The project I'm working on can be found [here](https://www.github.com/behordeun/fhir_demographics) following the tutorials from videos 1 and 2 of this [YouTube channel](https://www.youtube.com/watch?v=pCp7O5OptzY&list=PLUr-PTsPYKV5cM0tu_pydn0QJE_CDpIvY). I have attached a screenshot of the error...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [openEHR REST API compressed formats in current CDRs](https://discourse.openehr.org/t/openehr-rest-api-compressed-formats-in-current-cdrs/3495)
> The openEHR REST APIS now allow sufficient header information to be passed to a compliant CDR to work with the FLAT and STRUCTURED json formats but it looks as if neither Ehrbase or Better CDR support these via the formal REST API.
e.g this call returns a format not supported error in both.
```
curl --location --request POST 'http://165.227.231.224:8080/ehrbase/rest/openehr/v1/ehr/700d884e-324a-4060-9783-28a805a65c5a/composition' \
--header 'Content-Type:...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [How do we update the compositions if we modify/update a template?](https://discourse.openehr.org/t/how-do-we-update-the-compositions-if-we-modify-update-a-template/3492)
> Good afternoon,
I have a question about updating templates and their associated compositions.
Imagine the case in which you have your CDR with compositions and templates and there comes a time when it is necessary to update one of them because it has been seen that you can better define the use case by adding a new field.
How would this affect the old compositions?
Would it be necessary to update all of them or are they left as they are and only the new ones are updated?
Thank you so much!
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [openEHR API implementation in Rust](https://discourse.openehr.org/t/openehr-api-implementation-in-rust/3489)
> Hi there!
I want to implement an API from scratch, to be an alternative to EHRBase. I've already started some work here: [ehrust](https://github.com/pintariching/ehrust/) (not sure about the name). I'm reading the documentation mainly from [here](https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html). Are there any other good sources I should look up?
I'm wondering if I should make it as similar as possible as EHRBase? I'm not entirely about the exact specifications of the...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [When do i use null flavours and when the archetype absence?](https://discourse.openehr.org/t/when-do-i-use-null-flavours-and-when-the-archetype-absence/3469)
> I guess null flavours are more for representing stuff that was missed out by an ETL e.g. mapping from HL7?
And exclusions when e.g. filling out an Anamnesis ?
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Canadian use of openEHR](https://discourse.openehr.org/t/canadian-use-of-openehr/3466)
> I'm currently working for a customer in Canada, looking at their healthcare architecture as they look to improve it over the coming years.
Does anyone have any knowledge or material you could share regarding the use of openEHR in Canada?
Thanks
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Formatting AQL in new topics](https://discourse.openehr.org/t/formatting-aql-in-new-topics/3464)
> Could we add to the description of this category the suggestion to format all posted AQL queries before posting a new topic? This way it's much easier for people to read and respond to the question.
Example:
```
SELECT c FROM COMPOSITION c[openEHR-EHR-COMPOSITION.report.v1] CONTAINS EVALUATION d[openEHR-EHR-EVALUATION.problem_diagnosis.v1] WHERE d/name/value = 'Primary diagnosis' AND (d/data[at0001]/items[at0002 and name/value='Diagnosis']/value/defining_code/code_string = 'C50' OR...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL fetch issue when Two different templates has same archetype in version 23](https://discourse.openehr.org/t/aql-fetch-issue-when-two-different-templates-has-same-archetype-in-version-23/3461)
> Hi Team,
We have created two templates with same archetype sign/symptom created using same composition encounter v1,
While inserting data we have inserted two data points one is observation, and other is for cluster for template1
Where as, for the second template we have inserted for only cluster.
SO, when we try to fetch the data inserted for both templates, we are getting only one row for template1 where we had inserted for both data points(observation and cluster), but expected was 2...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Help! The "Review" menu option is gone for me](https://discourse.openehr.org/t/help-the-review-menu-option-is-gone-for-me/3450)
> Hi, I am logged in in the CKM but all of a sudden the top bar menu option Review has disappeared. What have I done? And how do I get it back? Ironic, since I just got the translation rights I wanted.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Creating FHIR care plan in openEHR](https://discourse.openehr.org/t/creating-fhir-care-plan-in-openehr/3446)
> apologies! This is a beginner question. I am trying to model the [FHIR care plan](https://build.fhir.org/careplan.html) via openEHR archetypes/templates. as far as I know there is already [care plan archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.1656/mindmap), but that looks like an abstract container. So, I was wondering how I should link it to other archetypes ? Could you please link me to a resourse/document about this topic. Thank you!
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Medication management archetype: Transition from Administrations suspended to Medication start date/condition set](https://discourse.openehr.org/t/medication-management-archetype-transition-from-administrations-suspended-to-medication-start-date-condition-set/3443)
> Summary of the discussion held on CKM.
We are checking the use of Medication Order instruction and Medication Management action for a potential implementation of this archetypes for internal hospital medication prescription.
Checking the Medication Management archetype transitions, we found that when the medication administration has been suspended and the conditions to continue with the medication administration are in place, the transition **"Medication start date/condition set"** leads...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How to add unit {index_val} from UCUM?](https://discourse.openehr.org/t/how-to-add-unit-index-val-from-ucum/3440)
> Hi all!
I am using LOINC where one of the units is referred as using {index_val} but i can't find a way of adding it in ADL designer.
Does anyone knows how to do it or does it have to be added to the property file?
eg: https://build.fhir.org/valueset-ucum-units.html
@siljelb @borut.fabjan
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Extract audit details (time committed) in AQL?](https://discourse.openehr.org/t/extract-audit-details-time-committed-in-aql/3435)
> Hi,
We want to store the time the composition is stored in the CDR (ehrBase).
Is it possible to store and extract the audit details class which stores this information in `time_committed` . If so can you please provide the flat json and the aql for the same.
Note, we do not want to store the composition commit time in c/context/start_time. This is reserved to store the time of encounter.
Any guidance will help.
Thanks
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Translation editor rights?](https://discourse.openehr.org/t/translation-editor-rights/3414)
> Hi, we are about to start reviewing Swedish translations of archetypes, in the Laboratory Test Order & Results Reporting project to start with (middle of January). There are 3 persons within openEHR Sweden that administer translations and reviews, and all three of us need translation editor rights so that we can manage the work. Currently I am translation editor only in the Common project. What should we do to get this role in other projects as well? When asking for membership in a project I...
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR Terminology (TERM) Release 2.4.0 published](https://discourse.openehr.org/t/openehr-terminology-term-release-2-4-0-published/3412)
> The [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) has published [TERM Release 2.4.0](https://specifications.openehr.org/releases/TERM/Release-2.4.0) today.
This release contains a number of terminology codes and vocabulary additions and updates:
**New Feature**
- [SPECTERM-4](https://openehr.atlassian.net/browse/SPECTERM-4) Add new terminology groups for EHR Extract Release 1.0.3 changes.
-...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [A status to record that the data was erroneous and has been corrected before inserting?](https://discourse.openehr.org/t/a-status-to-record-that-the-data-was-erroneous-and-has-been-corrected-before-inserting/3409)
> Hi,
Can a status be recorded in composition/archetype level indicating that the original data was erroneous and has been corrected before inserting?
Note the original data is stored in **feeder_audit**
Thanks
Chaya
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Querying composer's identifiers for where condition](https://discourse.openehr.org/t/querying-composers-identifiers-for-where-condition/3405)
> Hi all.
Does anyone know how to query a value that's inside an Array List?
In my case, I would like to get the value of `id`, `type`, `issuer`, and `assigner`. Here is the sniped composer data:
What can I achieve so far is this query below:
```
SELECT c0, c0/composer/identifiers
FROM COMPOSITION c0[openEHR-EHR-COMPOSITION.encounter.v1]
...
WHERE ...
```
With that query, I can only capture the value as an object, which is an array...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR News Summary and Merry Christmas](https://discourse.openehr.org/t/openehr-news-summary-and-merry-christmas/3393)
> It's been a great year for openEHR. Here's a round-up of what's been happening in 2022, as well as some of the things we're looking forward to in 2023. **[VIEW IN BROWSER](https://members.openehr.org/openEHR-Xmas)**
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR REST APIs Release 1.0.3 published](https://discourse.openehr.org/t/openehr-rest-apis-release-1-0-3-published/3392)
> The [openEHR Specifications Editorial Committee (SEC) ](https://www.openehr.org/programs/specification/editorialcommittee)has published [ITS-REST Release 1.0.3 ](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.3).
This release contains several changes needed to migrate specifications to OpenAPI format:
- [SPECITS-66](https://openehr.atlassian.net/browse/SPECITS-66) Migrate REST API specs to OpenAPI format.
We hope this proves useful for the community, and would like to...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic openEHR Collaboration Meeting February 2023](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-february-2023/3383)
> **Purpose of meeting**
Connect with the Nordic openEHR community to explore ways of collaborating towards common goals related to the use of openEHR.
**When and where**
Monday February 6th 11:00-14:00 CET
Remote participation available via Teams
**How to join**
Contact Pirkko Kortekangas, @e25cc02c, or Mikael Nyström, @mikael, [mikael.nystrom@cambio.se](mailto:mikael.nystrom@cambio.se)
**Preliminary agenda**
11:00-11:15 *Welcome and introductions* (15 min)
11:15-11:45 **Pirkko...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Ankle brachial pressure index](https://discourse.openehr.org/t/ankle-brachial-pressure-index/3362)
> We're looking for an "ankle brachial pressure index" archetype.
We did not find anything in CKM. But we did find such an archetype in norwegian ckm by @siljelb.
https://arketyper.no/ckm/archetypes/1078.36.1765
I wondered why the pressure measurements are part of the archetype. In my opinion the brachial pressure would best be recorded as observation.blood_pressure. And the ankle pressure as OBSERVATION.intravascular_pressure (since it's not a surrogate for the *systemic* arterial pressure)....
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Body segment discrepancy" is ready for publication](https://discourse.openehr.org/t/body-segment-discrepancy-is-ready-for-publication/3354)
> Dear all,
The archetype ‘Body segment discrepancy’ ([Clinical Knowledge Manager ](https://ckm.openehr.org/ckm/archetypes/1013.1.6534)) has been through one review round, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on December 23th.
Kind regards on behalf of the editors,
John Tore Valand
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Is adding a protocol to an archetype really a breaking change?](https://discourse.openehr.org/t/is-adding-a-protocol-to-an-archetype-really-a-breaking-change/3350)
> I've recently received an unexpected response from CKM when trying to upload a new revision of an archetype, where the main change was adding a 'protocol' section.
The CKM claims this is a breaking change. @sebastian.garde has since explained to me that adding a 'protocol' section is technically a breaking change because it's constraining it to being an 'ITEM_TREE' even though nobody is actually using any other structures than ITEM_TREEs for building archetypes anymore.
Should we really...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Problem with saving my changes in a Github public repo](https://discourse.openehr.org/t/problem-with-saving-my-changes-in-a-github-public-repo/3346)
> Hello everyone! I am getting the following exception when saving my changes in a Github public repo. I would be grateful if someone help me with that. Thank you!
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Constrain timezone in date/time fields](https://discourse.openehr.org/t/constrain-timezone-in-date-time-fields/3345)
> Currently, ADL has no way of constraining timezone as part of date/time constraints. I'm not currently aware of any expressed need to do this from the clinical modelling community, but technically speaking, it is missing from the ADL standard.
Within the Specifications Editorial Committee (SEC), it has been suggested that we could add it in into [AM Release 2.3.0](https://openehr.atlassian.net/projects/SPECAM/versions/12548/tab/release-report-all-issues). If we do that, tool builders would...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Svenska openEHR-förvaltningen har fått ett namn - openEHR Sverige](https://discourse.openehr.org/t/svenska-openehr-forvaltningen-har-fatt-ett-namn-openehr-sverige/3341)
> Den svenska openEHR-förvaltningen har äntligen fått ett riktigt namn - openEHR Sverige! I och med det behöver vi se över hur förvaltningen syns utåt på till exempel Conluence-wikin. Där finns vi under namnet "Swedish archetypes and templates". Är det något som hindrar ett namnbyte på den sidan till "openEHR Sverige"?
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Invitation to nominate for the openEHR Clinical Program Board (CPB) - Extended](https://discourse.openehr.org/t/invitation-to-nominate-for-the-openehr-clinical-program-board-cpb-extended/3328)
> Following the recent invitation to nominate to the new openEHR Clinical Program Board, the openEHR International Board has decided to:-
* **delay the formation of the Clinical Program Board until late Jan 2023**. This is due to (a) the large number of applications received, including from a significant number of individuals new in the community, and (b) requests from various organisations that have potential nominees but have not been able to organise applications in time;
* **continue to...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [‘Lenke classification system’ is ready for publication](https://discourse.openehr.org/t/lenke-classification-system-is-ready-for-publication/3304)
> Dear all,
The archetype ‘‘Lenke classification system’ The archetype ‘Lenke classification system’ ([Clinical Knowledge Manager ](
https://ckm.openehr.org/ckm/archetypes/1013.1.6527)) has been through one review round, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on December 12th.
Kind regards on behalf of the editors,
John Tore Valand
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Simplified Tanner-Whitehouse III assessment' is ready for publication](https://discourse.openehr.org/t/simplified-tanner-whitehouse-iii-assessment-is-ready-for-publication/3303)
> Dear all,
The archetype ‘Simplified Tanner-Whitehouse III assessment’ ([Clinical Knowledge Manager ](https://ckm.openehr.org/ckm/archetypes/1013.1.6526)) has been through one review round, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on December 12th.
Kind regards on behalf of the editors,
John Tore Valand
**[RM](https://discourse.openehr.org/c/rm/42)** - [Updating directory, what's the subfolder identification strategy?](https://discourse.openehr.org/t/updating-directory-whats-the-subfolder-identification-strategy/3297)
> Some CDRs choose to store the FOLDER.uid for all folders inside EHR.directory.
In that case, when creating the directory, the root directory will have an OBJECT_VERSION_ID in the UID since it's versionable, but the subfolders would have an UID as a HIER_OBJECT_ID or a GENERIC_ID.
When updating the EHR.directory, the version tree part is modified in the root OBJECT_VERSION_ID uid. Consider the subfolders don't change in the update, do subfolders of the new directory version have the same...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Virtual content, citation and linking](https://discourse.openehr.org/t/virtual-content-citation-and-linking/3291)
> Starting to make some progress on this question [on this wiki page](https://openehr.atlassian.net/wiki/spaces/spec/pages/2088140801/openEHR+Virtual+EHR+Content+and+Citation) to cover the various kinds of 'virtual content', citations and other kinds of inclusion, linking etc.)
I believe we need a holistic analysis that covers RM additions, ADL/AOM changes, querying semantics and extract / document / interop questions.
One thing is now clear to me: citations and virtual content are not the...
**[Community](https://discourse.openehr.org/c/community/10)** - [What are the benefits of openEHR membership? ](https://discourse.openehr.org/t/what-are-the-benefits-of-openehr-membership/3290)
> Hello all,
I’m putting together some promotional articles for the openEHR website and first up is ‘The benefits of openEHR membership’. Rather than cover all formal perks - rights to vote and nominate, join the board and program committee etc - I really want to talk about what being an openEHR member means to you: as a user, a clinician, a researcher, as part of the community….
As well as your own personal experience of using openEHR, I’m looking for quotes I can include - and possibly...
**[ITS](https://discourse.openehr.org/c/its/41)** - [REST API unkown RM version for non-locatable objects like CONTRIBUTION](https://discourse.openehr.org/t/rest-api-unkown-rm-version-for-non-locatable-objects-like-contribution/3285)
> CONTRIBUTIONs are not LOCATABLEs so they don't have a field to specify the rm_version.
When parsing CONTRIBUTION on POST /ehr/$id/contribution, the server doesn't know which RM version was used to define such payload. Consider this flow:
1. parse JSON CONTRIBUTION => internal JSON object
2. validate JSON object with JSON schema => validation errors
3. if (errors) => return error
4. else => map JSON object to a list of VERSION and an AUDIT_DETAILS
5. process versions and audit (validate...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Error in published 'Spirometry result' archetype](https://discourse.openehr.org/t/error-in-published-spirometry-result-archetype/3276)
> The recently published 'Spirometry result' archetype had an error, a unit for the element 'Flow rate/Result' was given as 'L/m' (liters per meter) rather than the correct 'L/min' (liters per minute).
Correcting this is a breaking change, and we'll republish the archetype as v2 on December 6th unless there are any objections before then.
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Impact of changes in openEHR Terminology XML files](https://discourse.openehr.org/t/impact-of-changes-in-openehr-terminology-xml-files/3275)
> For an upcoming release on Terminology specifications, I am exploring the possibilities and the impact on making small changes in [openEHR terminology xml files](https://github.com/openEHR/specifications-TERM/tree/master/computable/XML). These might be trivial as just adding few new attributes (`openehr_id`, `version`, `status`, etc), but there might be a need also to add or rename some nodes (which is considered to be a breaking change). Changes will be however supported by a new XSD...
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Changes in openEHR Terminology XML files](https://discourse.openehr.org/t/changes-in-openehr-terminology-xml-files/3274)
> For an upcoming release on Terminology specifications, I am exploring the possibilities and the impact on making small changes in [openEHR terminology xml files](https://github.com/openEHR/specifications-TERM/tree/master/computable/XML). These might be trivial as just adding few new attributes (`openehr_id`, `version`, `status`, etc), but there might be a need also to add or rename some nodes (which is considered to be a breaking change). Changes will be however supported by a new XSD...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Clinical governance questions on Archetype publication and separate CKM instances](https://discourse.openehr.org/t/clinical-governance-questions-on-archetype-publication-and-separate-ckm-instances/3272)
> Hey everyone. I'm currently in the process of learning more about the clinical modeling side of openEHR. I've read content in the confluence, like [this (A)](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2949205/Archetype+Publication+Status) and [this (B)](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2949146/Authoring+Review+and+Publication+Overview), but I still have some open questions about the governance. I want to understand what it takes to actually publish an...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [EY join openEHR International as Industry Partners](https://discourse.openehr.org/t/ey-join-openehr-international-as-industry-partners/3269)
> We are delighted to welcome EY to membership, who have joined openEHR International as Diamond Industry Partners.
EY teams are helping organisations across the entire health spectrum, with harnessing the transformative power of new technology and data. This requires ecosystems to be built around the needs of the individual supported by technical standards, open data models and empowered by governance systems that deliver trust. ‘EY people are drawing on their capabilities, talents and...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [openEHR in POLAND - Country Group Request?](https://discourse.openehr.org/t/openehr-in-poland-country-group-request/3266)
> Hello, I am new to openEHR but I already try to promote the standard on local and national forums (meetings and conferences) while learning about OpenEHR with my team.
Would it be possible to open Country Group? I can see the German and Netherlands Groups?
Best Wishes,
Jakub
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Psoriasis Area Severity Index (PASI)' is ready for publication](https://discourse.openehr.org/t/psoriasis-area-severity-index-pasi-is-ready-for-publication/3265)
> Dear all,
The archetype ‘Psoriasis Area Severity Index (PASI)’ ([Clinical Knowledge Manager ](https://ckm.openehr.org/ckm/archetypes/1013.1.5395)) has been through one review round, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on December 5th.
Kind regards on behalf of the editors,
Hanne Marte Bårholm
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Support to join two composition on ehrid](https://discourse.openehr.org/t/aql-support-to-join-two-composition-on-ehrid/3262)
> We have two compositions
(COMPOSITION c1 CONTAINS OBSERVATION o1) OR
(COMPOSITION c2 CONTAINS EVALUATOIN e1)
We want to join these two composition .
First template has sign and symptom screening which has symptom values like 'Depression'
and second is a Person details which has Gender 'Female/Male'.
We want to be able to get count of all Female(from c2) who have Depression(from c1)
Following AQL does not work:
SELECT c1 FROM EHR e
CONTAINS
(COMPOSITION c1 CONTAINS OBSERVATION o1)...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Dr Sidharth Ramesh joins openEHR SEC Experts Panel](https://discourse.openehr.org/t/dr-sidharth-ramesh-joins-openehr-sec-experts-panel/3249)
> We are very pleased to welcome Dr Sidharth Ramesh as the latest addition to the [openEHR Specifications Editorial Committee Experts Panel](https://www.openehr.org/programs/specification/board_members#dr-sidharth-ramesh).
Sidharth is an MD in Tamil Nadu who in recent years has become an innovator in the open source App building space with his company [Medblocks](https://medblocks.org/), which provides solutions based on openEHR, HL7 FHIR and other standards, as well as some great [training...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Problem/Diagnosis qualifier - ready for republication as a new major version](https://discourse.openehr.org/t/problem-diagnosis-qualifier-ready-for-republication-as-a-new-major-version/3248)
> Based on requested changes and discussion among editors, the [Problem/Diagnosis qualifier](https://ckm.openehr.org/ckm/archetypes/1013.1.1451) archetype will be republished as a new major version.
The major changes from the [latest published version](https://ckm.openehr.org/ckm/archetypes/1013.1.1451/16) (27.06.2019) are as follows:
* Changed the "First occurrence?" boolean element to "Occurrence" coded text, with the values "First occurrence" and "Recurrence"
* Removed "Partial remission"...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Symptom/sign - ready for republication as a new major version](https://discourse.openehr.org/t/symptom-sign-ready-for-republication-as-a-new-major-version/3246)
> After discussion in [Discourse](https://discourse.openehr.org/t/revisiting-symptom-sign/1867/47) and among editors, the [Symptom/sign archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.195) will be republished as a new major version.
The major changes from the [last published revision](https://ckm.openehr.org/ckm/archetypes/1013.1.195/21) (25.04.2018) are as follows:
* 'Nil significant' element deleted. This was always an uncomfortable modelling choice, and is now covered in a much...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Using EHRbase to store existing clinical data as pdf documents](https://discourse.openehr.org/t/using-ehrbase-to-store-existing-clinical-data-as-pdf-documents/3239)
> Hi,
Can EHRbase be used to manage the existing clinical data as documents(pdf, jpeg etc.)?
We have a lot of the existing clinical data stored as physical or electronic files. It is important that these are also included while implementing a CDR. Can EHRbase be used to manage these documents as well.
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Invitation to nominate for the openEHR Clinical Program Board (CPB) - Ends 4 Dec 2022](https://discourse.openehr.org/t/invitation-to-nominate-for-the-openehr-clinical-program-board-cpb-ends-4-dec-2022/3237)
> Are you or the organisation you work for interested in the **future of openEHR clinical modelling**?
The openEHR **Clinical Program** is being formally established by openEHR International, and will be managed by the **Clinical Program Board (CPB)**, along with a **Clinical Program Experts Panel (CPXP)**. The description of the Program may be [found here](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2081227103). Its formal [Terms of Reference is available...
**[News](https://discourse.openehr.org/c/community-news/25)** - [The Catalonian government launches a tender to procure a transactional information system for pharmacy for the Catalan Health System - open for proposals until 15 December 2022](https://discourse.openehr.org/t/the-catalonian-government-launches-a-tender-to-procure-a-transactional-information-system-for-pharmacy-for-the-catalan-health-system-open-for-proposals-until-15-december-2022/3235)
> [Sistema de Salut de Catalunya](https://www.linkedin.com/company/salutcat/) is launching another tender. This one is focused on the transactional information systems for pharmacy for the Catalan Health System, using openEHR as persistence storage in a CDR, for the pharmaceutical process data. Here you have a LinkedIn post ([Walking towards an integrated therapeutic...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Ehrbase: How to drop all data](https://discourse.openehr.org/t/ehrbase-how-to-drop-all-data/3227)
> Hey guys,
I have a running installation of ehrbase and the underlying postgres via two docker images (ehrbase and ehrdb). This should be the default installation. How can I reset the the database, that is, delete all data and begin from a fresh installation?
Thanks!
**[News](https://discourse.openehr.org/c/community-news/25)** - [Catalan Health System launches tender for openEHR Clinical Data Repository service - closes 21-dec-2022](https://discourse.openehr.org/t/catalan-health-system-launches-tender-for-openehr-clinical-data-repository-service-closes-21-dec-2022/3223)
> [Sistema de Salut de Catalunya](https://www.linkedin.com/company/salutcat/) are taking the next step in defining and delivering their [#infostructure](https://www.linkedin.com/feed/hashtag/?keywords=infostructure&highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6999346453609390080). The region has recently published a Request for Proposals, which "aims to procure the CKM platform service according with the openEHR standard". The tender, will be open for proposals until 21st December 2022....
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Archetype instances](https://discourse.openehr.org/t/archetype-instances/3205)
> Apologies if this is in the wrong forum...
As I am delving deeper into my understanding of archetypes, it would be really good to see some example instances of data represented by archetypes (rather than just the Archetype ADL).
Does anyone know of any publically available archetype data that I could reference?
thanks
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Composition Archetypes are generated with atcode in EventContext](https://discourse.openehr.org/t/composition-archetypes-are-generated-with-atcode-in-eventcontext/3202)
> If I create a new Composition Archetype then ehr generated adl code is
```
definition
COMPOSITION[at0000] matches { -- test
category matches {
DV_CODED_TEXT[at0001] matches { -- Coded text
defining_code matches {
[openehr::433]
}
}
}
context matches {
EVENT_CONTEXT[at0002] matches {*} -- Event Context
}
}
```
but I think this should be
```
definition
COMPOSITION[at0000] matches { -- test
category matches {
DV_CODED_TEXT[at0001] matches { ...
**[OHDSI OMOP](https://discourse.openehr.org/c/omop/103)** - [OpenEHR-OMOP working group creation](https://discourse.openehr.org/t/openehr-omop-working-group-creation/3199)
> During last general assembly we discussed the creation of a working group for the mapping between openEHR and OMOP CDM. I want to use this message get feedback on the status of every organization that is currently mapping openEHR to OMOP CDM, and also know the people interested on joining this working group.
The purpopse of the working group will be gathering all current efforts and generating a white paper with best practices and recommendations
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Typos - AOM2](https://discourse.openehr.org/t/typos-aom2/3184)
> A few typos below:
"Uuniversity College London" - should be University
"new elements in its defnition" - should be definition
"any serialsed form " - should be serialised
"from the the openEHR BASE " - duplicate 'the'
"identify archteype nodes" - should archetype
"referring to a terminologyvalue set." - missing space
"done with an appopriate " - should be appropriate
"all their meta-data from from the " - duplicate from
"subject to tool accesibility; " - should be accessibility
"functions...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Typos - Architecture Overview](https://discourse.openehr.org/t/typos-architecture-overview/3183)
> I noticed a few typos in the document, perhaps these could be addressed in the next issue.
"Change Reqests" --- should be 'requests'
"to fulfill a goal" --- assume UK English and hence fulfil
"the perpretrator" --- should be perpetrator
"Versioned Object indentified by the GUID" - should be identified
"Under the openEHR aproach' - should be approach
"(ie no relationships)" - should be i.e.
Also, there is frequent reference to "Oid" should this be "OID"?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Reporting specification issues](https://discourse.openehr.org/t/reporting-specification-issues/3182)
> Hello all
What's the correct way to report issues in specifications (e.g. typos etc)?
Also, I have spotted a couple with the openEHR website - how do I report those?
Many thanks
**[ADL](https://discourse.openehr.org/c/adl/40)** - [ADL validity codes now directly linkable](https://discourse.openehr.org/t/adl-validity-codes-now-directly-linkable/3176)
> For those who care about ADL tooling and have implemented or use the AOM, for example in Archie, you will know that the AOM2 spec defines numerous validity codes [like these](https://specifications.openehr.org/releases/AM/latest/AOM2.html#_validity_rules_c_attribute).
If you are using an Archetype modelling tool, and it reports a validity error code like VSONCO (one that we are just upgrading), you can now use the codes as direct anchors added to the URL of the spec, i.e....
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL to retrieving data for an element with cardinality 0..*](https://discourse.openehr.org/t/aql-to-retrieving-data-for-an-element-with-cardinality-0/3153)
> Hi All,
I am having issue in AQl while retrieving data for an element with cardinality 0..*
I am using Symptom/sign screening questionnaire archetype with Specific symptom/sign as 0..* within the encounter composition.
I have inserted 3 elements with Symptom or sign name and Presence?
0th element has
Symptom or sign name = Depression
Presence = No
1st element has
Symptom or sign name = Anxiety
Presence = No
2nd element has
Symptom or sign name = Feeding/eating
Presence =...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Self-reported data' is ready for publication](https://discourse.openehr.org/t/self-reported-data-is-ready-for-publication/3144)
> Dear all,
The archetype ‘[Self-reported data](https://ckm.openehr.org/ckm/archetypes/1013.1.6343)’ has been through two review rounds, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on November 14th.
Kind regards on behalf of the editors,
Silje Ljosland Bakke
**[General Discussion](https://discourse.openehr.org/c/general-discussion/132)** - [Missing type id property '_type' (for POJO property 'items') in EHRBase](https://discourse.openehr.org/t/missing-type-id-property-type-for-pojo-property-items-in-ehrbase/3125)
> Hi,
I start by saying that I already checked the similar "Missing type id property error in Ehrbase" .
My couple template/composition is at this link: https://easyupload.io/v3ufjy
The template has been created with the free Archetype Designer. The composition is derived , through the example method, from the template.
The composition can be posted successfully but it cannot be retrieved.
The GET returns the error:
"error":"Bad Request","message":"DB...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR PR / Marketing Support - welcoming Pete Bouvier](https://discourse.openehr.org/t/openehr-pr-marketing-support-welcoming-pete-bouvier/3123)
> We welcome [Peter Bouvier](https://www.linkedin.com/in/ACoAAAKCbVABzQnfPWfpaN10mANeyfyP5pULvEA) to the openEHR community. @Pete_Bouvier will be helping openEHR with PR / marketing support. Over the coming weeks Peter will be making connections with Industry Partner marketing teams and others with a view to posting about what they are doing with openEHR.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Citations and references - Care Plan example](https://discourse.openehr.org/t/citations-and-references-care-plan-example/3122)
> In a similar vein to the [post on citations in BMI](https://discourse.openehr.org/t/citations-and-references-bmi-example/3117), here is another example - Care Plan. Please refer to the BMI post for the general question. Here I will just post a graphic showing what I take to be the kind of thing @joostholslag and other clinical modellers want to do to represent a Care Plan. (Don't worry too much about whether my Care Plan design is right or not, just meant to be...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Differences between EHRBase and Better platform](https://discourse.openehr.org/t/differences-between-ehrbase-and-better-platform/3121)
> Hi, I have been evaluating both EHRBase and Better Platform and I have discovered some different behaviors when executing aql queries.
I expected the same query to return the same result in both systems (provided they contain the same data), but this is not the case. I am not sure which implementation is correct.
# Difference 1
In EHRBase, you can filter on object_id and get the latest composition matching that id. In Better, the same query yields an empty result. To get the same result in...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Citations and references - BMI example](https://discourse.openehr.org/t/citations-and-references-bmi-example/3117)
> (Older discussions [here](https://discourse.openehr.org/t/linking-in-openehr-goals-and-problems/1032) and [here](https://discourse.openehr.org/t/cross-reference-citations-and-a-solution-for-managed-lists/1355).)
Following the discussion on today's SEC call re: supporting linking in Archetypes, it became clear we needed a more sophisticated idea of what kinds of links / citations are needed just in the data. @ian.mcnicoll gave the example of BMI and nested problem list. @joostholslag [has...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Archetyping links and references](https://discourse.openehr.org/t/archetyping-links-and-references/3112)
> For a very long time we have wanted a way of constraining links of various kinds in the RM (or anywhere) such that the constraint can say what kind of thing the link target points to - both at RM level (e.g. must be an EVALUATION) and semantic level (e.g. must be problem-diagnosis). On the clinical side, @ian.mcnicoll, @siljelb and @joostholslag might want to have a think about this proposal, likewise tool builders @pieterbos , @borut.fabjan , @borut.jures , @yampeku , @damoca ,...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Correct procedure to translate an archetype in various languages](https://discourse.openehr.org/t/correct-procedure-to-translate-an-archetype-in-various-languages/3110)
> Hi,
I am currently in the works to translate an archetype in the CKM to french and german.
I have created a new branch where i translated the archetype from english to french.
Now I need to translate it from english to german.
For that where should I click to translate archetype now to german? In the trunk again or in the new branch I have created before to translate it initially to french?
I don't know how the process in the...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Historical archetype 'data' cardinality modelling error?](https://discourse.openehr.org/t/historical-archetype-data-cardinality-modelling-error/3109)
> Hi all,
We're wondering if there's a historical modelling error (possibly because of default settings in older tools?) in a lot of archetypes where the cardinality of the 'data' section is set to `1..*`, `2..*`, `3..*` or similar, instead of `0..*`. This leads to some issues when using these archetypes in low code development.
Are there any reasons why we shouldn't change these archetypes make the cardinality of 'data' `0..*`? This should be a non-breaking change.
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [openEHR-tool](https://discourse.openehr.org/t/openehr-tool/3108)
> We at crs4 have created a simple GUI for EHRBase. The project still in beta is at the following url:
https://github.com/sasurfer/openEHR-tool
It has most of the main methods from the openEHR API specification.I hope to extend it to other backends.
Enjoy it
**[News](https://discourse.openehr.org/c/community-news/25)** - [New discussion groups for integration & HIT standards](https://discourse.openehr.org/t/new-discussion-groups-for-integration-hit-standards/3105)
> We have created new dedicated for various HIT standards and other technologies related to integration, under a top-level category called [Integration](https://discourse.openehr.org/c/integration/100).
These groups are intended to discuss the semantics of mappings, technical relationships, etc with these standards. For discussions on openEHR implementations of mappers, bridges and so on, please see the [Implementation/Integration](https://discourse.openehr.org/c/implem/integration/63)...
**[ISO 13606](https://discourse.openehr.org/c/iso13606/105)** - [About the ISO 13606 category](https://discourse.openehr.org/t/about-the-iso-13606-category/3104)
> Discussions on the relationship between openEHR and ISO 13606.
**[IHE](https://discourse.openehr.org/c/ihe/104)** - [About the IHE category](https://discourse.openehr.org/t/about-the-ihe-category/3103)
> Discussions on mapping openEHR APIs to [IHE APIs](https://www.ihe.net/).
**[OHDSI OMOP](https://discourse.openehr.org/c/omop/103)** - [About the OHDSI OMOP category](https://discourse.openehr.org/t/about-the-ohdsi-omop-category/3102)
> Discussions about how openEHR data and clinical models map to the [OHDSI OMOP model](https://www.ohdsi.org/omop/).
**[HL7 v2](https://discourse.openehr.org/c/hl7v2/102)** - [About the HL7 v2 category](https://discourse.openehr.org/t/about-the-hl7-v2-category/3101)
> Discussions on mapping between [HL7v2 messages](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185) and openEHR.
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [About the HL7 FHIR category](https://discourse.openehr.org/t/about-the-hl7-fhir-category/3100)
> Discussions on mapping between [HL7 FHIR](https://www.hl7.org/fhir/) and openEHR.
**[Integration](https://discourse.openehr.org/c/integration/100)** - [About the Integration category](https://discourse.openehr.org/t/about-the-integration-category/3099)
> For discussions on integrating to other systems, including via HIT standards, APIs, products.
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Microsoft join openEHR International as Diamond Industry Partners](https://discourse.openehr.org/t/microsoft-join-openehr-international-as-diamond-industry-partners/3096)
> We are delighted to welcome Microsoft as an openEHR International Diamond Industry Partner.
Headquartered in the US, Microsoft’s mission is to empower every person and organisation to achieve more. Striving to see better health globally, Microsoft offers technology solutions that empowers patients, care providers and organisations. Their healthcare products range from patient engagement-solutions to operational analytics that utilise data to improve the delivery of care provided by other...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [CLUSTER.exam-specializations are expecting a previous version of CLUSTER.exam archetype](https://discourse.openehr.org/t/cluster-exam-specializations-are-expecting-a-previous-version-of-cluster-exam-archetype/3093)
> Hi! I am having some issue in the archetypes versions.
I am using a lot of CLUSTER.exam specializations such as
CLUSTER.exam-muscle,
CLUSTER.exam-heart,
CLUSTER.exam-neck,
etc etc
but all of these point to a parent archetype CLUSTER.exam.v1 and on the CKM there's CLUSTER.exam.v2
In order to keep everything consistent, should I download CLUSTER.exam.v1 instead and keep...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Missing "web template" format in many (all?) CDR "Definitions"-API implementations](https://discourse.openehr.org/t/missing-web-template-format-in-many-all-cdr-definitions-api-implementations/3090)
> Hi!
My colleague Abebe Hailu discovered that the standardised way of downloading templates in "Web templates"...
...is not supported in any of the CDR implementations we have tested (inlcuding EHRbase and Cambio) and it is not listed as supported in Better's EHRscape either:
** - [Practical approach to FOLDER OPTs](https://discourse.openehr.org/t/practical-approach-to-folder-opts/3081)
> Been struggling with this idea for a while, maybe others can help me out.
Since FOLDER is LOCATABLE, it can, and actually should, be archetyped, and since most systems work with templates, there should actually be FOLDER OPTs out there saying how the internal structure of different FOLDERs should look like.
The first challenge with FOLDERs is they are a recursive structure, though is like SECTION or CLUSTER, there is one big difference: for SECTIONs and CLUSTERs the structure is stable once...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Operative Procedure Coding {OPCS,HRG}](https://discourse.openehr.org/t/operative-procedure-coding-opcs-hrg/3080)
> Hi all,
I am a vascular surgeon interested in EHRs/EMRs. I am relatively new to OpenEHR. Is there a representation in the openEHR framework analogous to "OPCS procedure codes" or "HRG Codes" that can represent different surgical/radiological procedures?
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [openEHR data validation](https://discourse.openehr.org/t/openehr-data-validation/3075)
> For anyone interested in #openEHR data validation, I'm fixing the official JSON schemas and working on test cases, including demographics! You can find some examples here https://github.com/ppazos/openEHR-OPT/blob/master/src/test/groovy/com/cabolabs/openehr/opt/ValidationFlowTest.groovy Contributions are welcome!
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Template Better in XML?](https://discourse.openehr.org/t/template-better-in-xml/3072)
> when reading out the template in XML, these contents appear:
false
Does anyone know what this means?
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Closing the two final holes in openEHR's FAIR support?](https://discourse.openehr.org/t/closing-the-two-final-holes-in-openehrs-fair-support/3069)
> In [FAIRness of openEHR Archetypes and Templates](https://www.semanticscholar.org/paper/FAIRness-of-openEHR-Archetypes-and-Templates-B%C3%B6nisch-Sargeant/60f6f9564d035676ac380caa5d1fae312f51ed6a), two remaining potential holes in openEHR's FAIR support are identified, namely:
and
I think A2 can be remedied by using published archetypes. A published resource can be deprecated...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Imaging archetypes for regions related to gynaecological/pregnancy examination ready for publication](https://discourse.openehr.org/t/imaging-archetypes-for-regions-related-to-gynaecological-pregnancy-examination-ready-for-publication/3068)
> Dear all,
The following archetypes have been developed as part of a family of archetypes and have undergone parallel review as a group. The archetype scope of each has been deliberately constrained to a simple, expected and non-controversial data points, to facilitate rapid publication. Outstanding possible future data elements suggested during review but not yet included as data elements have been captured as change requests against each archetype.
* [Examination of an...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Display of terminology bindings to runtime name constraints](https://discourse.openehr.org/t/display-of-terminology-bindings-to-runtime-name-constraints/3065)
> Hi all,
The [Spirometry result archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.1414) has a set of SNOMED CT bindings to its lists of different spirometry tests, but these bindings are not displayed in the CKM. Is this intentional, or just not implemented?
**[Releases](https://discourse.openehr.org/c/releases/51)** - [Clinical Knowledge Manager (CKM) Release 1.18.0](https://discourse.openehr.org/t/clinical-knowledge-manager-ckm-release-1-18-0/3064)
> The recent upgrade to Clinical Knowledge Manager (CKM) Release 1.18.0 incorporates the changes of a total of 91 Jira Cards: 34 cards with new or significantly enhanced functionality, 35 mostly minor bug fixes and 22 changes “under the hood” of CKM, giving a myriad of improvements and extensions for CKM Editors and Clinical Knowledge Administrators. [Read more...](https://www.openehr.org/news_events/community_news/379)
**[General Discussion](https://discourse.openehr.org/c/general-discussion/132)** - [Inconsistency in demographic specs](https://discourse.openehr.org/t/inconsistency-in-demographic-specs/3052)
> In https://specifications.openehr.org/releases/1.0.2/architecture/rm/demographic_im.pdf
```
ACTOR.roles is 0..1
ACTOR.languages is 0..1
```
In https://specifications.openehr.org/releases/RM/Release-1.0.2/demographic.html (same spec and version, just the HTML version
```
ACTOR.roles is 1..*
ACTOR.languages is 1..*
```
I believe the PDF version is using the existence cardinality and the HTML version is using the cardinality of the list. Though if the attribute can be optional `(existence...
**[General Discussion](https://discourse.openehr.org/c/general-discussion/132)** - [Interesting discussion on Linedin about the role of FHIR/openEHR repositories in the context of EHRs and HIE](https://discourse.openehr.org/t/interesting-discussion-on-linedin-about-the-role-of-fhir-openehr-repositories-in-the-context-of-ehrs-and-hie/3051)
> I have reposted a thread started on Twitter (https://twitter.com/ppazos/status/1579272075420004352) to Linkedin and it blew up, with an interesting collection of opinions and discussions, which I really appreciate and found healthy to have out in the open. Thanks to everyone, even if we don't agree, every opinion counts.
Post on Linkedin: https://www.linkedin.com/posts/pablopazosgutierrez_fhir-ehr-cda-activity-6984723205701681152-eV38
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Intervals in ADL, templates, and data](https://discourse.openehr.org/t/intervals-in-adl-templates-and-data/3050)
> After encountering my first DV_INTERVAL I fear that their use is not consistent in the implementations.
For example, the archetype openEHR-EHR-EVALUATION.death_summary.v0 contains two alternatives in the Date/time of death, one of them being DV_INTERVAL
So far so good. However, if we create a template for this it ends up like this
This...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Which are the top ten commonly used archetypes?](https://discourse.openehr.org/t/which-are-the-top-ten-commonly-used-archetypes/3049)
> When planning to translate many archetypes (in our case to Swedish) it would be good to cover the ones that are most commonly used, the ones that are applicable in a wide range of use cases. The list below is a guess based on nothing, but we would really appreciate some guidance here. Are there 10 archetypes covering 80% percent of the use cases (roughly)? This helps us to prioritize the translation work.
COMPOSITION
Encounter
Report
Result report
CLUSTER
Anatomical location
Medical...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [US-centric spec aliasing?](https://discourse.openehr.org/t/us-centric-spec-aliasing/3048)
> For years the openEHR specs were not widely accepted in the US, part of it could be because the UK centric aspects of the current spec. Besides the specs being born and developed in the UK, some terms, spelling and modisms in the specs are not used in the US, like organiSation or null_flavoUr. Though I'm not a native Ensligh speaker, I have worked with a lot of US based companies and I write and talk US biased English :slight_smile:
My general question would be if it does make sense to...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Status for Laboratory Test Panel](https://discourse.openehr.org/t/status-for-laboratory-test-panel/3047)
> In the CKM I can see that the cluster Laboratory test panel has the current state of "review suspended" and has been so since 2019.
What is the intention of the archetype going forward? Is working being done right now to change it or what is the status?
I am working with creating a template for chemistry lab results reports and this cluster would be perfect to use for us since all our analyte results are grouped into panels. However we also have the need for having a comment on each...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [DEMOGRAPHIC model: does it make sense to have contacts and identities for ROLE?](https://discourse.openehr.org/t/demographic-model-does-it-make-sense-to-have-contacts-and-identities-for-role/3043)
> ROLE inherits from PARTY, PARTY has identities and contacts, which seem reasonable for a PERSON, ORGANIZATION or AGENT, which inherit from ACTION which inherits from PARTY, but I can't see what's the use of those fields for ROLE. Those fields seem to be more suitable for ACTOR than for PARTY IMO.
Does anybody have a use case for ROLE that uses identities or contacts?
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR International Annual General Meeting 25 October 09:00-10:00 BST](https://discourse.openehr.org/t/openehr-international-annual-general-meeting-25-october-0900-bst/3037)
> The openEHR International Board are holding its Annual General Meeting by Zoom conference call at 09:00 – 10:00 BST on Tuesday 25th October 2022, and are inviting openEHR members to join the meeting.
Please email any matters, issues, suggestions etc that you would like to raise at the meeting to [comms@openehr.org](mailto:comms@openehr.org) so that items can form part of the meeting agenda, which will be shared with members nearer the meeting date.
Agenda, Zoom detail, Minutes from the last...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Specialized node ids are lost on OPT export](https://discourse.openehr.org/t/specialized-node-ids-are-lost-on-opt-export/3036)
> We have found a bug regarding OPT export and sibling nodes with specialized node ids. When exporting, specialized node id is changed into the original one, which in the end the makes the OPT lose the descriptions of all the sibling nodes. The error can be easily reproduced by creating some sibling specialized nodes and then exporting the OPT.
As an example, take a look at the following template
Each one of the analytes has its own...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [How to create demographic archetypes with LinkEHR](https://discourse.openehr.org/t/how-to-create-demographic-archetypes-with-linkehr/3032)
> Hi, I'm using LinkEHR to create demographic archetypes.
I have created a PERSON archetype and can model the PERSON.details: ITEM_STRUCTURE field, but it is not possible to archetype the PERSON.contacts.addresses.details: ITEM_STRUCTURE or PERSON.identities.details: ITEM_STRUCTURE fields.
I can see in linkehr/data/rm/openEHR/DEMOGRAPHIC/archetypes/PERSON.adl that the fields are there, but can't access them from the GUI to add...
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Tool for mapping data to openEHR compositions](https://discourse.openehr.org/t/tool-for-mapping-data-to-openehr-compositions/3029)
> Hi, at CRS4 we have developed a tool called [flatehr](https://github.com/crs4/flatehr) for converting data to openEHR. It allows to generate compositions in flat format mapping source fields (at the moment XML and JSON are supported) to template nodes. There is also a small script for ingesting the generated compositions to an openEHR server.
It is actually still experimental and absolutely not bug-free. I hope someone can find it useful. Any feedback is welcome!
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [‘Spirometry result’ is ready for publication](https://discourse.openehr.org/t/spirometry-result-is-ready-for-publication/3025)
> Dear all,
The archetype ‘Spirometry result’ (https://ckm.openehr.org/ckm/archetypes/1013.1.1414) has been through three review rounds, and the editors recommend it for publication.
If any objections or comments, please add them here in due time for planned publication on October 7th.
Kind regards on behalf of the editors,
Hanne Marte Bårholm
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Capillary electrophoresis results and the waveform archetype](https://discourse.openehr.org/t/capillary-electrophoresis-results-and-the-waveform-archetype/3022)
> Hi!
One of the laboratories at Karolinska University Hospital is exploring ways to include [capillary electrophoresis](https://en.wikipedia.org/wiki/Capillary_electrophoresis) curves as further details of the laboratory (analyte) result stored in an openEHR CDR in order to later compare measurements to each other and to be able to automate future analysis better.
**Question 1**: Are you aware of anybody else working with or interested in archetypes/templates for this?
**Feel free to...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Is using EVENT in archetypes an inconsistent way of modeling "any event"?](https://discourse.openehr.org/t/is-using-event-in-archetypes-an-inconsistent-way-of-modeling-any-event/3015)
> If you check the OBSERVATION archetypes in the CKM, some have the EVENT type in HISTORY.events
That represents at that point there could be a POINT_EVENT or INTERVAL_EVENT in the OBSERVATION object instance that complies with that archetype.
Now consider EVENT is an abstract class.
In other cases of having abstract classes and allowing "any type", the pattern is not to put the abstract class in the archetype but to add alternatives to C_ATTRIBUTE.children.
So, shouldn't EVENT work in the...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [AOM: how do you differentiate between sibling C_OBJECT if both are ARCHETYPE_ROOT and have the same archetype_id?](https://discourse.openehr.org/t/aom-how-do-you-differentiate-between-sibling-c-object-if-both-are-archetype-root-and-have-the-same-archetype-id/3013)
> I'm working with some complex OPTs, verifying data validation rules. From the OPT I'm generating a COMPOSITION instance and then validating the COMPOSITION against the OPT.
This OPT has several SECTION in COMPOSITION.content and have the same archetype openEHR-EHR-SECTION.adhoc.v1, but each SECTION has it's own items, some have OBSERVATIONS, other ACTIONS, etc.
When I have a SECTION instance from the COMPOSITION object, need to get the defining C_OBJECT from the OPT, then finding by...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Is there any modeling tool that supports creating EHR_STATUS archetypes and templates?](https://discourse.openehr.org/t/is-there-any-modeling-tool-that-supports-creating-ehr-status-archetypes-and-templates/3009)
> I have tested Better Designer and VeraTech LinkEHR and none support EHR_STATUS artifact definition.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Representation of scales total score meaning](https://discourse.openehr.org/t/representation-of-scales-total-score-meaning/3007)
> Hello,
We are working with the [International prostate symptom score (IPSS)](https://ckm.openehr.org/ckm/archetypes/1013.1.2361) archetype from CKM. We have been asked to add the interpretation for the total score, which ranges from 0 to 35 and that is currently represented as a DV_COUNT:
* 0-7: Mild
* 8-19: Moderate
* 20-35: Severe
We have several options here.
* **Option 1**. Maintain the total score as a DV_COUNT and just add the interpretation a part of the comment of that element....
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Rm_version is needed at the EHR to be able to schema validate and parse JSON/XML correctly](https://discourse.openehr.org/t/rm-version-is-needed-at-the-ehr-to-be-able-to-schema-validate-and-parse-json-xml-correctly/3006)
> I'm working on reviewing the JSON schemas based on the RM and adapting them to the API payloads.
Since my use case is openEHR spec conformance verification, I need to be able to consider any version of the RM serialized to JSON or XML. For LOCATABLE types (COMPOSITION, FOLDER, EHR_STATUS, etc.) we have the archetype_details.rm_version which tells which RM version is used. But when we deal with EHRs in JSON/XML, the EHR is not LOCATABLE and doesn't have any information inside that allows to...
**[Community](https://discourse.openehr.org/c/community/10)** - [[Final Report] Region of Catalonia - RFI on technological elements to build an open platform using openEHR](https://discourse.openehr.org/t/final-report-region-of-catalonia-rfi-on-technological-elements-to-build-an-open-platform-using-openehr/3005)
> As many of you already know, last year CatSalut published a preliminary market survey for procurement (RFI) of an openEHR-based health information platform. We would like to thank all the 15 companies that participated in the call, especially for the time and resources invested to prepare the high quality offers we received. This contribution has been of great value and has allowed us to acquire state-of-the-art knowledge about the market in relation to clinical data repositories based on the...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Multi RM JSON schema validation and current schema issues](https://discourse.openehr.org/t/multi-rm-json-schema-validation-and-current-schema-issues/3002)
> I've been playing around with the JSON Schemas and found some issues in the published ones.
First, the entry points to validate the root nodes are missing some types (ITEM_LIST, ITEM_SINGLE, ITEM_TABLE, ELEMENT, HISTORY, etc.)
Then some types for OBJECT_REF could be constrained. For instance EHR.ehr_access and EHR.ehr_status have PARTY_REF available as a possible type and this won't happen, and I believe for EHR.ehr_status the ACCESS_GROUP_REF won't happen either. There are some other...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [openEHR - ETL - sharing is caring](https://discourse.openehr.org/t/openehr-etl-sharing-is-caring/3000)
> We, DIPS AS, have been working on the need to make openEHR data available for data analytics. The structured clinical data must be aligned with other (not openEHR) data sources. Thus there is a need to do ETL transformations on openEHR data.
AQL is a great query language for openEHR data. We use AQL as a the key building block for our ETL process. To support the target system (relational database) we annotate the AQL.
Here I will share one example to illustrate how it works. The example...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How to create an archetype with DV_scale in 'Archetype Designer'](https://discourse.openehr.org/t/how-to-create-an-archetype-with-dv-scale-in-archetype-designer/2985)
> I am new to the open ehr community and still learning on things. Can some one please help me to create an archetype which includes DV_Scale element in it? [I am using archetype designer.] :slight_smile:
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - ["Persistent" Compositions not persistent](https://discourse.openehr.org/t/persistent-compositions-not-persistent/2982)
> There are in the CKM several Composition archetypes that seem to imply a persistent category but have the event code fixed to event. This happens at least on all the composition list archetypes (adverse reaction list, medication list, problem list). They all have a description that starts with "A persistent and managed list of xxxx", but have a category code fixed to 433 (event). Shouldn't the code be fixed to 431 (persistent)?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Moving of nodes in an item tree](https://discourse.openehr.org/t/moving-of-nodes-in-an-item-tree/2978)
> Recently for the archetype the node “digital representation” at0060 was moved from inside the cluster at0058 “directive location” to the main item tree. https://ckm.openehr.org/ckm/archetypes/1013.1.4274
I like this change. But it’s done in a minor update to the archetype (v1.2.0). This is imho a breaking change.
(At least it brakes our software, editor only for now).
It’s listed in the revision log as a major change (along with others), so I wondered why the archetype did not get a major...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Restrict mime-type in DV_MULTIMEDIA](https://discourse.openehr.org/t/restrict-mime-type-in-dv-multimedia/2960)
> Hello,
I'm designing an archetype (ADL2) that can be used to upload photos. For this I am using a `DV_MULTIMEDIA`.
It all works, but what I want to do next is restrict (in the archetype) the mime-type of the file to image/jpeg.
How do I go about this? I was thinking something like:
```
ELEMENT[id5] occurrences matches {1} matches {
value matches {
DV_MULTIMEDIA[id6] matches {
media_type matches {[at1]} -- image/jpeg
}
}
}
```
Where I make a...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Help in drafting specification for building and distributing "Apps" on top of openEHR and FHIR](https://discourse.openehr.org/t/help-in-drafting-specification-for-building-and-distributing-apps-on-top-of-openehr-and-fhir/2936)
> Hello everyone,
I am interested in writing a draft specification for building and distributing reusable apps. The idea is to get to an iPhone or Android like "App marketplace" where we can download and reuse applications on top of vendor neutral APIs.
This is the [original...
**[openEHR.pt](https://discourse.openehr.org/c/openehr-portugal/44)** - [OpenEHR em Portugal](https://discourse.openehr.org/t/openehr-em-portugal/2933)
> Olá
Após algum tempo de maturação no processo de estruturação do grupo, decidiu-se por incorporar a [E-MAIS](https://www.e-mais.pt/) e criar o Grupo de Trabalho para o OpenEHR. Iremos continuar a utilizar este espaço (com mais dinamismo 😊) para divulgação de eventos e notícias relevantes. Renovamos o convite para integrar o grupo a quem estiver interessado em participar mais ativamente. Para isso basta enviar e-mail para [openehr@e-mais.pt](mailto:openehr@e-mais.pt).
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Clinical Program reboot - Request for Comments (ends 16 Sep 2022)](https://discourse.openehr.org/t/clinical-program-reboot-request-for-comments-ends-16-sep-2022/2932)
>
**EXTENDED TO 30 SEP 2022**
-------------
An expert panel working on the Clinical Program 'reboot' has produced a draft Program definition and Terms of Reference for the new Clinical Program. Today openEHR is launching a [public RFC (Request for Comment) for 1 month on these materials](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2030436353/Clinical+Program+reboot+-+RFC).
This RFC is designed to refine the Clinical Program priorities, scope and Terms of Reference sufficiently...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Missing fields in uploaded composition](https://discourse.openehr.org/t/missing-fields-in-uploaded-composition/2925)
> Hey guys,
I downloaded the `GECCO_Laborbefund` template (https://ckm.highmed.org/ckm/templates/1246.169.1229/export) for testing purposes and pushed it on my EHRBase server. This seems to work, as I can retrieve an example of it via `/ehrbase/rest/ecis/v1/template/GECCO_Laborbefund/example?format=FLAT`, which looks like this:
```
{
"laborbefund/category|terminology": "openehr",
"laborbefund/category|value": "event",
"laborbefund/category|code": "433",
...
**[Education](https://discourse.openehr.org/c/education/88)** - [openEHR step by step](https://discourse.openehr.org/t/openehr-step-by-step/2924)
> This is a series of videos I'm making, the idea is to show how to work with any openEHR CDR that I can get access to, using the same models (archetypes and templates) and the same data (compositions).
These first two videos show three topics:
1. How to create archetypes and templates
2. How to generate test data from operational templates
3. How to use the EHRBASE API to create and query data
https://www.youtube.com/watch?v=mqV6QQ-aaDA&list=PLjcikWLLyg6uAM6SVBLFuUdfpjq_d8Iti
Next videos...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Expanded Version lifecycle - implementers need to consider impact](https://discourse.openehr.org/t/expanded-version-lifecycle-implementers-need-to-consider-impact/2922)
> All,
[SPECRM-107](https://openehr.atlassian.net/browse/SPECRM-107) is the one @joostholslag got us started on, which was to add some kind of obsolete or archived state to the Version state machine. The main scenario was something like a Care Plan or other episodic Composition that has become no longer pertinent to care. We eventually settled on the new state name `inactive`.
Further analysis by the smart people at Nedap exposed the fact that just one extra state won't do what is needed,...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [New Discourse Tool Support categories](https://discourse.openehr.org/t/new-discourse-tool-support-categories/2921)
> We have expanded our set of dedicated community support discussion forums on Discourse for tools that are free to use and/or open source. Please make sure you WATCH categories of interest to be notified of new posts!
Tool support discussion categories:
* [REQUESTS](https://discourse.openehr.org/c/tool-support/tool-requests/95): for new features generally
* Better's [Archetype...
**[MS VisualStudio](https://discourse.openehr.org/c/visual-studio/96)** - [About the MS VisualStudio category](https://discourse.openehr.org/t/about-the-ms-visualstudio-category/2920)
> Community support for use of Microsoft VisualStudio for openEHR, e.g. plug-ins etc.
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [About the REQUESTS category](https://discourse.openehr.org/t/about-the-requests-category/2919)
> Community feature requests for general tool types (for specific tools, use the appropriate discussion category).
**[ADL Workbench](https://discourse.openehr.org/c/adl-workbench/94)** - [About the ADL Workbench category](https://discourse.openehr.org/t/about-the-adl-workbench-category/2918)
> Community support for [ADL Workbench](https://openehr.github.io/adl-tools/adl_workbench_guide.html)
**[Template Designer](https://discourse.openehr.org/c/template-designer/93)** - [About the Template Designer category](https://discourse.openehr.org/t/about-the-template-designer-category/2917)
> Community Support for [Ocean Template Designer](https://oceanhealthsystems.com/software/template-designer)
**[openEHR Toolkit](https://discourse.openehr.org/c/openehr-toolkit/92)** - [About the openEHR Toolkit category](https://discourse.openehr.org/t/about-the-openehr-toolkit-category/2916)
> (Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:
- Why should people use this category? What is it for?
- How exactly is this different than the other categories we already have?
- What should topics in this category generally contain?
- Do we need this category?...
**[Text Editors](https://discourse.openehr.org/c/editors/91)** - [About the Text Editors category](https://discourse.openehr.org/t/about-the-text-editors-category/2915)
> (Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:
- Why should people use this category? What is it for?
- How exactly is this different than the other categories we already have?
- What should topics in this category generally contain?
- Do we need this category?...
**[MedBlocks](https://discourse.openehr.org/c/medblocks/90)** - [About the MedBlocks category](https://discourse.openehr.org/t/about-the-medblocks-category/2914)
> Community support for [MedBlocks](https://medblocks.org) openEHR web app builder
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [About the CKM category](https://discourse.openehr.org/t/about-the-ckm-category/2913)
> Community discussions on [Clinical Knowledge Manager](https://ckm.openehr.org/ckm/) (CKM)
**[ITS](https://discourse.openehr.org/c/its/41)** - [React help needed](https://discourse.openehr.org/t/react-help-needed/2911)
> Hi,
In the SEC working group we are now exploring possibilities to render and publish our openEHR REST Specifications in openAPI format. (relates to https://discourse.openehr.org/t/rest-api-specifications-in-openapi-format/2767).
We are looking mainly to [Stoplight](https://stoplight.io/) and it [Elements](https://stoplight.io/open-source/elements), which we would also like to use it - but I have insufficient knowledge and experience to work it out and also to fix issues generated by (I...
**[Education](https://discourse.openehr.org/c/education/88)** - [Pointers to get to speed fast on openEHR](https://discourse.openehr.org/t/pointers-to-get-to-speed-fast-on-openehr/2898)
> Hi!
I'm a university professor/researcher in the Artificial Intelligence domain. I'm working with applications of AI on healthcare, like chatbots (see e.g. https://doi.org/10.1016/j.ijmedinf.2021.104473 ). I've just started to learn about openEHR. I'm interested in topics like mapping textual data to structured openEHR using NLP techniques. If you have some good pointers so that I can learn more about openEHR and such existing applications, I would be glad if you tell me.
Yours,
Sergio...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Procedure screening questionnaire", "Symptom/sign screening questionnaire", "Problem/Diagnosis screening questionnaire", "Medication screening questionnaire" and " Management screening questionnaire" ready for publication](https://discourse.openehr.org/t/procedure-screening-questionnaire-symptom-sign-screening-questionnaire-problem-diagnosis-screening-questionnaire-medication-screening-questionnaire-and-management-screening-questionnaire-ready-for-publication/2896)
> The archetypes "Procedure screening questionnaire", "Symptom/sign screening questionnaire", "Problem/Diagnosis screening questionnaire", "Medication screening questionnaire" and "
Management screening questionnaire" has been through three review rounds. The recommodations after the last review round were “Minor Revision” or “Accept”.
There has been made som clarifications to the archetypes "Header" sections and to some descriptions. Descriptons to the values in the elements containing...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Erhbase: REST API client-code generators and Content-Type](https://discourse.openehr.org/t/erhbase-rest-api-client-code-generators-and-content-type/2895)
> Hi,
Some OpenEHR REST API methods require the specific Content-Type header, for example, "/rest/openehr/v1/definition/template/adl1.4" (createTemplateClassic)
Let's take a look at the code generated by NSwag:
```javascript
createTemplateClassic(openEHR_VERSION: string | undefined, openEHR_AUDIT_DETAILS: string | undefined, content_Type: string, accept: string | undefined, prefer: string | undefined, body: string): Promise {
let url_ = this.baseUrl +...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [openEHR Template vs. Composition](https://discourse.openehr.org/t/openehr-template-vs-composition/2890)
> Hello fellows!
I'm working my way through the concepts of openEHR and struggle to understand the following explanation from the specifications:
> An openEHR Template is a specification that defines a tree of of one or more archetypes, each constraining instances of various reference model types, such as Composition, Section, Entry subtypes and so on
My understanding so far, however, was that a Composition is nothing else than a template filled with data and that within a Composition we can...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Task planning implementation using executable flows](https://discourse.openehr.org/t/task-planning-implementation-using-executable-flows/2887)
> I made some progress on implementing task planning for RCHOPS-21.
I managed to complete the first drug regimen diagram. It should be the same as the version on openEHR site ([Figure 4. RCHOPS21 administration phase](https://specifications.openehr.org/releases/PROC/Release-1.6.0/process_examples.html#_plan_definition)).
This diagram is executable(!).
The platform I'm using has support for creating simple UI dashboards...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRbase: Stuck in "2.5. Step 4: Load Data"](https://discourse.openehr.org/t/ehrbase-stuck-in-2-5-step-4-load-data/2885)
> I'm new to EHRBase and use docker images to learn EHRbase. According to the document, I have successfully performed the first three steps of "2. Getting Started" (including Data Models, Upload a Template and Create an EHR) .
When trying Step 4: Load Data:
I firstly built the Client Library from "https://github.com/nedap/ehrbase_client_library". But when I tried to create the Java classes from the OPT, “nullPointerException” was reported. It seems that the Client Library cannot correctly...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [JavaScript SDK for openEHR](https://discourse.openehr.org/t/javascript-sdk-for-openehr/2883)
> While working on a TaskPlanning implementation I realized that I've created a JavaScript library for openEHR as a side effect.
I used my Dart SDK and compiled it to JavaScript:
1. openEHR specifications
2. generate Dart SDK
3. use [Dart compiler](https://dart.dev/tools/dart-compile) to compile it to JavaScript SDK
Would this be useful for frontend developers?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRBase using PUT in create EHR with UUID](https://discourse.openehr.org/t/ehrbase-using-put-in-create-ehr-with-uuid/2881)
> From documentation (https://ehrbase.readthedocs.io/en/latest/03_development/05_technical_docs/index.html#ehr) It seems to imply that the functionality to create EHR with a given UUID is currently being merged into the createEHR method. I tried to pass the UUID as the subject in the ehrstatus with no luck (a completely new UUID is being used and returned).
Per spec creating an EHR method with UUID is a PUT operation. So tried to launch that operation directly. Even if I try to launch a PUT...
**[GDL editor](https://discourse.openehr.org/c/gdl/77)** - [Problems when instantiating multiple of the same archetype/element](https://discourse.openehr.org/t/problems-when-instantiating-multiple-of-the-same-archetype-element/2878)
> I am using the GDL2 editor to create medical guidelines with recommendations. I think that I encountered some bugs and I would like to bring those to your attention.
According to one of my guidelines, recommendations should be generated when a certain type of procedure has been performed multiple times. Therefore, I instantiated the archetype 'openEHR-EHR-ACTION.procedure.v1' with its element 'procedure name' twice, and set up a rule for both procedure names to equal the same value. Testing...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Cannot upload OPT template using EHRBase Java SDK v1.19.0](https://discourse.openehr.org/t/cannot-upload-opt-template-using-ehrbase-java-sdk-v1-19-0/2864)
> Hi, I'm new to OpenEHR & EHRBase. I have studied the OpenEHR specification. I found that many concepts are interesting. I want to make a proof of concept to use Spring Boot with EHRBase as a backend with some business logic.
I have already tried angular-SDK-example. I now want to start my own API development using Java, following the example but with different package versions. (I'm not Java Developer. I usually use Typescript.). Here is my stack
* Java 11
* Spring Boot v2.7.1
* EHRBase SDK...
**[openEHR Toolkit](https://discourse.openehr.org/c/openehr-toolkit/92)** - [What do you think about these improvement ideas for the openEHR Tookit?](https://discourse.openehr.org/t/what-do-you-think-about-these-improvement-ideas-for-the-openehr-tookit/2856)
> It's been a while since we released the [openEHR Toolkit](https://toolkit.cabolabs.com/) and we have a lot of new users (luckily it's been very active).
We have a bunch of tools to be added from our TODO list and since we are going to add more and more tools, the current GUI might not be optimized for all these tools.
The current GUI is based on a normal admin layout, text menu on the left dividing the app sections, then a set of tools inside each section. Here just a sample flow:
1....
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [FHIR vs openEHR](https://discourse.openehr.org/t/fhir-vs-openehr/2854)
> Hello all,
I am just reading into FHIR and openEHR technology and have read several times that FHIR is commonly used as a communication protocol and openEHR for data persistency.
Now I had a FHIR workshop and also here data can be stored with FHIR. Now I have not understood exactly what really justifies the effort of FHIR to openEHR mappings, if you could do everything with FHIR?
Does anyone here have a concrete example where I see why you should rather do the storage with openEHR and not...
**[Community](https://discourse.openehr.org/c/community/10)** - [Paper about openEHR as Conceptual independence published](https://discourse.openehr.org/t/paper-about-openehr-as-conceptual-independence-published/2853)
> A new article about openEHR in the context of conceptual independence and outsourcing has been published this month 2022.
The article reports about the flexibility of supliers of EHR software in case healthcare organizations request changes in functionality. In the quotes the managers of the IT departments give examples from practice.
The research has been performed in 2019.
(https://www.igi-global.com/article/investigating-the-impact-of-outsourcing-on-it-flexibility/299955)
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Regarding Stored Query](https://discourse.openehr.org/t/regarding-stored-query/2846)
> I stored one AQL Query in OpenEHR with paramters. When I provide the values for those parameters to the stored query, I was facing the following issue
"Could not perform SQL query:org.postgresql.util.PSQLException: ERROR: operator does not exist: text < integer\n Hint: No operator matches the given name and argument types. You might need to add explicit type casts.\n Position: 1105,
Request Body :
{
"query_parameters": {
"ehr_id": "ehrid value",
"deficit": "integer"
...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [InterHealth2022: Scientific School on semantic interoperability in healthcare, 10-14 October 2022](https://discourse.openehr.org/t/interhealth2022-scientific-school-on-semantic-interoperability-in-healthcare-10-14-october-2022/2842)
> Dear all,
CRS4 is organising the Scientific School **InterHealth2022** - *Interoperability in Healthcare: Approaches and Perspectives to Preserve the Semantics of Clinical Data and Improve their Quality*, scheduled from 10th to 14th October 2022 at the Technology Park of Sardinia in Pula, Italy. Deadline for applications is 31st July 2022.
InterHealth2022 will explore the perspective of semantic interoperability through a 5-day-training program with lectures and practical tutorials, with...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Constraining DV_EHR_URI](https://discourse.openehr.org/t/constraining-dv-ehr-uri/2833)
> I have a usecase where I want [one (careplan) composition template](https://archetype-editor.nedap.healthcare/advanced/plan/archetypes/openEHR-EHR-COMPOSITION.plan.v0.1.0) to index multiple other [compositions of sub care plans](https://archetype-editor.nedap.healthcare/advanced/plan/archetypes/com.nedap::openEHR-EHR-COMPOSITION.care_plan-problem_goal_action.v0.0.1). using DV_EHR_URI this should work. Accept that it’s not possible to constrain the element to only link to compositions from a...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Develop RM toward OpenEHR](https://discourse.openehr.org/t/develop-rm-toward-openehr/2831)
> Hi,
I would like to know how I can develop RM to represent something in OpenEHR. I need to develop a privacy reference model, but I haven't found any clear documentation on how to create an OpenEHR oriented RM.
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [5th openEHR Asia Summit, 30th July, 2022 by Zoom](https://discourse.openehr.org/t/5th-openehr-asia-summit-30th-july-2022-by-zoom/2820)
> Dear all,
This is an announcement for the 5th openEHR Asia summit. We will make it online and welcome attendants from all over the world.
Registration available form here: https://openehr.connpass.com/event/254378/
- Date and time 9:00-12:00 AM(JST) on July 30
- Venue Online(Zoom)
## Programme
1. Opening remark and openEHR updates 2021-2022, Shinji Kobayashi, NPO openEHR Japan(9:00-9:15)
2. Modelling clinical knowledge, Heather Leslie, Atomica Informatics(9:15-9:45)
3. Toward...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Public Test Servers](https://discourse.openehr.org/t/public-test-servers/2812)
> Hi all,
I am new to openEHR and I was wondering if there is any public online openEHR server that implementers can use for testing purpose. I am particularly interested in testing REST APIs.
An online EHRBase or EHRServer would be great, so we don't have to deploy one in a local machine.
Thanks in advance
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [BI Capabilities on openEHR](https://discourse.openehr.org/t/bi-capabilities-on-openehr/2809)
> Hi all,
I am analizyng openEHR capabilities but I cannot find information regarding on BI and Analitycs.
I am not wrong, information model is oriented to store a complete xml into a field but, what options do we have to extract information and add some reports, charts, ... to it?
Thanks in advance
**[RM](https://discourse.openehr.org/c/rm/42)** - [EHR_ACCESS is left as an exercise for the reader](https://discourse.openehr.org/t/ehr-access-is-left-as-an-exercise-for-the-reader/2804)
> I'm looking for more information on the EHR_ACCESS class. At Cambio, we're in the design stage for a set of services (outside the CDR) to help make compliance with the Swedish patient data laws easier for our clients. It would be nice to leverage as much openEHR access framework as possible, but it's unclear exactly what this class is intended for.
As far as I can tell, you just have your basic LOCATEABLEs and then an ACCESS_CONTROL_SETTINGS class that's undefined. What are people's thoughts...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Which archetype should be used to represent a microbiological culture findings?](https://discourse.openehr.org/t/which-archetype-should-be-used-to-represent-a-microbiological-culture-findings/2803)
> We are starting to integrate some laboratory analyte results, but it seems that the archetype “Laboratory analyte result” isn’t suitable for record microbiological culture findings (urine, blood , etc.). Should I use “Conclusion” or/and “Test diagnosis” from the archetype “Laboratory test result” ?
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [SynPuf: syntetic data (into openEHR)](https://discourse.openehr.org/t/synpuf-syntetic-data-into-openehr/2802)
> I'm thinking in generating a way of load existing SynPuf data into openEHR data repository (probably via openEHR REST API). I have several questions to the community in order to make it more useful/more easily available. First a little summary:
DE-SynPuf is a realistic looking syntetic data set with information from persons, claims, and prescriptions. SynPuf is organized in a way that you can get a percentage of patients from the total you want loaded into the system (each batch contains a...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Finally I was able to run EHRServer with docker-compose](https://discourse.openehr.org/t/finally-i-was-able-to-run-ehrserver-with-docker-compose/2797)
> Clone the repo: https://github.com/ppazos/cabolabs-ehrserver
Have Grails 3.3.10 installed: https://grails.org/download.html
$ cd cabolabs-ehrserver
$ grails war
$ cd docker-compose
$ docker-compose up
localhost:8080 will be **#Adminer** (a **#MySQL** manager)
localhost:8888 will be **#Tomcat** (running EHRServer)
**#openEHR** OSS Platform https://github.com/ppazos/cabolabs-ehrserver
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Fetal biometry' is ready for publication](https://discourse.openehr.org/t/fetal-biometry-is-ready-for-publication/2796)
> Dear all
The archetype 'Fetal biometry' (https://ckm.openehr.org/ckm/archetypes/1013.1.5922) has been through one review round. Most reviewers accepted or suggested only minor changes. There were suggestions for additional elements, which can be further investigated and added in in a future version, and grow when there is a clear understanding of the needs, experts consulted, clinical guidance and scientific papers investigated and, if possible, early drafts of the extended archetype used in...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Translations after archetype version update - how to overcome confusions](https://discourse.openehr.org/t/translations-after-archetype-version-update-how-to-overcome-confusions/2793)
> Hi!
A hint to others getting confused. I didn't quite understand the CKM translation upon/after version change.
Since the archetype was now in v1 and is missing Swedish translation (also see P.S. below) I thought I'd create a new translation for for v1, but when I tried to, it instead opeed my existing (still open) branch for translation from v0 and (even though I clicked on the start translaton under the v1 archetype - a bit confusing).
It was not possible to start a new translation for...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [[EHRBase] Postman collection for JWT issuing on EHRBase](https://discourse.openehr.org/t/ehrbase-postman-collection-for-jwt-issuing-on-ehrbase/2789)
> Hi all,
Would anyone mind sharing a small Postman collection to demonstrate the calls to acquire an EHRBase JWT token, showing the request body for either Admin or User, and target URL, please?
Regarding the target URL, I am using http://localhost:8081/auth/realms/ehrbase, though I see KeyCloak mentioned throughout the documentation: "SPRING_SECURITY_OAUTH2_RESOURCESERVER_JWT_ISSUERURI=https://keycloak.PROJECT.
com/auth/realms/ctr"
What would typically be the considerations when choosing...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [ACTION.laboratory_test required](https://discourse.openehr.org/t/action-laboratory-test-required/2788)
> The ACTION.procedure archetype mentions that it is not to be used to record details about laboratory investigations - use ACTION.laboratory_test for this purpose. Unfortunately, this particular archetype is missing. Are there any plans currently to address this?
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Terminology_id versioning](https://discourse.openehr.org/t/terminology-id-versioning/2783)
> I am currently struggling with having the version of codesystem inside the repository.
By default the teminology_id just has only Value, as ```ICD-10M720```
But I would like to have the version as well as ```ICD-102021M720```
** - [Widen scope of Self monitoring composition or add new Self reported data composition?](https://discourse.openehr.org/t/widen-scope-of-self-monitoring-composition-or-add-new-self-reported-data-composition/2776)
> The Self Monitoring archetype (still in v0) has [an open change request](https://ckm.openehr.org/ckm/archetypes/1013.1.2430/changerequests) to get a widened scope to instead cover all kinds of self reported data.
Would that be a good idea or should we keep self monitoring as it is and create a new (wider) archetype for 'Self reported data'? (E.g. with a concept description like 'A composition to record data reported by the individual who is the subject of the record'.)
We need such a...
**[Integration](https://discourse.openehr.org/c/integration/63)** - [[EhrBase-SDK] Can Fhir-Bridge be extended as dependency in project](https://discourse.openehr.org/t/ehrbase-sdk-can-fhir-bridge-be-extended-as-dependency-in-project/2768)
> Hi,
We are trying to extend fhir-bridge capabilities in our project as dependency in pom, so that we can convert/map few of the resources to templates according to our specification. This is done so that existing code of bridge is not modified and also any further upgrade of versions can be easily managed since we are not modifying bridge code or are we maintaining it at our end.
When we tried this method, we are facing issues saying certain classes of bridge is not able to find like...
**[ITS](https://discourse.openehr.org/c/its/41)** - [REST API Specifications in OpenAPI format](https://discourse.openehr.org/t/rest-api-specifications-in-openapi-format/2767)
> I am investigating a rewrite of our [current REST API Specification](https://specifications.openehr.org/releases/ITS-REST/latest) (now in [Api-Blueprint format](https://github.com/openEHR/specifications-ITS-REST/tree/master/src)) as [OpenAPI 3.1](https://spec.openapis.org/oas/v3.1.0) or 3.0 format. Has anybody already done this and is willing to share it? then it will be helpful and highly appreciated - please contact me or respond here.
**[ITS](https://discourse.openehr.org/c/its/41)** - [openEHR: revisión de terminología en español](https://discourse.openehr.org/t/openehr-revision-de-terminologia-en-espanol/2766)
> Estimados, tenemos una traducción propuesta para la terminología de openEHR en español, obviamente sólo hispano-parlantes pueden revisar que esté bien. Les pido para quien tenga unos momentos de revisar el archivo de traducciones y comentar en el Pull Request si encuentran algo incorrecto:
https://github.com/openEHR/terminology/pull/14/files
¡Muchas gracias!
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Structured name of a person' ready for publication](https://discourse.openehr.org/t/structured-name-of-a-person-ready-for-publication/2764)
> ‘Person’, 'Organisation', ' Address' and 'Electronic communication' archetypes have all recently been published for use as part of standardised clinical documentation within the EHR.
The final archetype in this family, 'Structured name of a person' has now completed the review process and is ready for publication
Feedback from all reviews, including the latest review, can be found here: [Structured name of a person](https://ckm.openehr.org/ckm/archetypes/1013.1.5359/reviewscontent)
Unless...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Limitation preventing multilingual repeated parts in the OPT (operational template) export format](https://discourse.openehr.org/t/limitation-preventing-multilingual-repeated-parts-in-the-opt-operational-template-export-format/2760)
> Hi!
My former colleague Elham Gholami discovered a strange behaviour of template content when exporting operational templates (OPT-files) with modified repeated (e.g. with renamed fields) occurences of an archetype inside a template. If you export the template with only one language you won't notice the limitation though.
We reported this to Better and discovered it was a known limitation of the (now pretty old XML based) OPT format. Newer formats (including ADL2-based ones) do not have...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [2nd openEHR-NL conference (2022)](https://discourse.openehr.org/t/2nd-openehr-nl-conference-2022/2752)
> On 3rd of June, the @openehr-netherlands affiliate held its yearly conference in Houten (Netherlands).
More information about the event can be found at https://www.openehr.nl (in Dutch language).
You can watch the recordings (in English) at [2nd openEHR-NL conference (2022)](https://youtube.com/playlist?list=PLEeWddjlNkA2D7POCqua2KRukkj_CuLnH).
We would like to thank all participants, and especially all speakers and sponsors - you all made a good meeting; we couldn't have done this...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Tool or process to fix obsolete references in archetypes? Example: media_capture renamed to media_file](https://discourse.openehr.org/t/tool-or-process-to-fix-obsolete-references-in-archetypes-example-media-capture-renamed-to-media-file/2742)
> I have several times found (and reported) references to no-longer-existing archetypes in different archetypes. Perhaps the CKM should be enhanced with a function to scan and detect these things as they happen.
(An analogy: Programmers would hate to refactor a codebase without automated tooling for renaming a class that also changes references to the class they are renaming.)
Such obsolete references in archetypes are sometimes found in descriptive text (e.g. the use/misuse metadata field)...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Specimen container' and 'Transportation of an item' (previous 'Specimen transportation' are ready for publication](https://discourse.openehr.org/t/specimen-container-and-transportation-of-an-item-previous-specimen-transportation-are-ready-for-publication/2733)
> "Specimen container" (CLUSTER.specimen_container) and "Transportation of an item" (CLUSTER.item_transport) has been through two review round each.
The "Transportation of an item" was originally called "Specimen transportation" (CLUSTER.specimen_transport), but after the review and the feedback we changed the concept so this archetype is more generic, and can be used for transportation of other items than only specimen and specimen container.
The editorial decision is to publish this with...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Why use AQL instead of SQL in openEHR?](https://discourse.openehr.org/t/why-use-aql-instead-of-sql-in-openehr/2719)
> Would someone be able to articulate clearly for non-technical types like me why Archetype Query Language (AQL) has been developed for and used in openEHR, instead of the widely available generic alternatives?
There is quite a bit online about AQL, but I haven't yet found anything that explains it clearly to the layperson.
It would be great to have a 'short version' and a 'long version'!
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Image with image map for circular anatomic direction/location](https://discourse.openehr.org/t/image-with-image-map-for-circular-anatomic-direction-location/2717)
> Hi!
I tried googling for some open sourced image with corresponding image map of "clock based" circular direction, but failed. The intention was to use it as a demo in a GUI for the "coded text" option in the archetype [Circular anatomical location](https://ckm.openehr.org/ckm/archetypes/1013.1.1995) in form building tools like Better's EHR Studio:
So I quickly hacked one using wikimedia image...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [OHDSI symposium 2022](https://discourse.openehr.org/t/ohdsi-symposium-2022/2713)
> Is anyone from the openEHR community planning on attending the OHDSI symposium? It would be great to discuss omop transformation experiences
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [General archetype of clinical score/scale for templating measurement instruments](https://discourse.openehr.org/t/general-archetype-of-clinical-score-scale-for-templating-measurement-instruments/2702)
> # Background
Currently my team and I are contributing to a national bioregistry platform development in Indonesia (see: [BGSI](https://bgsi.dto.kemkes.go.id/)). This bioregistry platform will be used as a semi-automated electronic data capture, where it will integate manual input by enumerators and automatic data retrieval from connected EHR systems. We chose `OpenEHR` to store the clinical data considering its two-level data model which we believe will help retaining the semantic relations...
**[RM](https://discourse.openehr.org/c/rm/42)** - [COMPOSITION.category definitions](https://discourse.openehr.org/t/composition-category-definitions/2696)
> In the current spec we have:
> Temporal category of this Composition, i.e.
>
> 431|persistent| - of potential life-time validity;
>
> 451|episodic| - valid over the life of a care episode;
>
> 433|event| - valid at the time of recording (long-term validity requires subsequent clinical assessment).
>
> or any other code defined in the openEHR terminology group 'category'.
What is the meaning of "valid" in this context?
I understand the `clinical statements` in the...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [ACTION.medication_management / method](https://discourse.openehr.org/t/action-medication-management-method/2695)
> Just working on an exercise using Medication Mgt ACTION archetype...
I see that 'administration method' is just a DV_TEXT. I would have expected a CLUSTER, since you might want to say something that needs a few bits of information. E.g. in chemotherapy:
method:
* type = infusion
* duration=1:30
I don't think it would be hard to come up with other examples where more than just a text or coded text was needed.
Thoughts?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [How accurately do we model "copied" data?](https://discourse.openehr.org/t/how-accurately-do-we-model-copied-data/2691)
> openEHR templates will frequently feature data from other repositories. In the context of a clinical referral letter, results may be added in to the narrative of the text and this is itself a copy of the source data from the pathology system. We have to be aware that this data exists and should not be used i.e. query only the source systems.
We have to make a decision on how accurately we model this data i.e. as an observations, SNOMED CT codes etc with accurate values. Or do we only store...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Karnofsky Performance Status scale ready for publication](https://discourse.openehr.org/t/karnofsky-performance-status-scale-ready-for-publication/2688)
> Dear all
The archetype OBSERVATION.karnofsky_performance_status_scale has been through one review round. Of the reviews in the international CKM, there were only “Minor Revision” or “Accept”. The comments have been answered consistent with editorial policy and textual improvements have been made to accommodate feedback. No significant changes are made to the archetype compared to the version that went out for review.
Changes in the archetype after review is only updating comments and...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Can the CKM GUI be translated to the user's language?](https://discourse.openehr.org/t/can-the-ckm-gui-be-translated-to-the-users-language/2687)
> I'm not sure if the international CKM allows the user to select his/her language for the GUI items, or if we can contribute with translations for the CKM itself to make that possible. Thanks.
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Any idea about medication order archetype >> compound drug dispense amount issue](https://discourse.openehr.org/t/any-idea-about-medication-order-archetype-compound-drug-dispense-amount-issue/2686)
> Hi
I'm working on POC medication order archetype but got stuck about dispensing quantity.
At first medication archetype look like it can handle most of the medication order complexity.
compound drug( like Ceftriaxone 2 grams + 5%DW 100 ml IV drip in 30 min)
or
tapering drug( like prednisolon 3 tab twice a day in day 1 and 2 tab twice a day between day 2-5 )
but 1 big issue I can't solve is when combine this with dispense amount.
such as compound drug
Ceftriaxone 2 grams + 5%DW 100 ml IV...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Spine -clinical modelling](https://discourse.openehr.org/t/spine-clinical-modelling/2685)
> Together with one of our customers (hospital) we are looking into structured data to follow up patients with problems in the spine. The use-case is structured data from first encounter into potential surgery. Then there will be reports to a national quality registry.
The data will cover comobordities, nevrological findings, imaging findings, etc.
I assume most of these datasets will have global reuse potential.
Have anyone here developed such models before? Anyone interested in joining in...
**[Education](https://discourse.openehr.org/c/education/88)** - [About the Education category](https://discourse.openehr.org/t/about-the-education-category/2676)
> Discussions on education and training.
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [openEHR RM v2.0: points to improve/simplify the openEHR reference model](https://discourse.openehr.org/t/openehr-rm-v2-0-points-to-improve-simplify-the-openehr-reference-model/2664)
> Since a recent discussion about date/time types the idea of summarizing several improvements to the openEHR RM proposed and discussed from time to time into a list we can review and discuss over something concrete, I did a quick review of the specs to bring this discussion over the table, mainly checking the UML diagrams and remembering some issues I had when implementing the specs in the [EHRServer](https://cloudehrserver.com/) and the [openEHR Toolkit](https://toolkit.cabolabs.com/). This...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [Referring to demographic entities in data](https://discourse.openehr.org/t/referring-to-demographic-entities-in-data/2659)
> We have various conversations going on around demographic data. I think we may have to look at a modification to the RM that would support a need that @ian.mcnicoll and @heather.leslie have long been asking for (and it's in a thread here that I can't put my finger on right now).
So, to put it in context, there are two potential types of demographic 'reference'.
* One is what we support, which is references (via `PARTICIPATION`, in `ENTRY.other_participations`, `COMPOSITION.participations`,...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Dedalus join openEHR International as Diamond Industry Partners](https://discourse.openehr.org/t/dedalus-join-openehr-international-as-diamond-industry-partners/2654)
> We are delighted to welcome Dedalus to membership, who have joined openEHR International as Diamond Industry Partners.
Headquartered in Italy, Dedalus are a leading provider of clinical and diagnostic software whose aim is to support the whole continuum of care, adopting multiple international standards to accelerate incremental innovation and to rapidly deliver value to patients, healthcare professionals, healthcare providers and institutions.
*“We are delighted to have joined openEHR...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL querying on ISM and Careflow Steps](https://discourse.openehr.org/t/aql-querying-on-ism-and-careflow-steps/2650)
> Hi all,
we are currently diving a bit deeper into this topic and I got some questions. To my understanding, an Activity inside an Instruction is referenced by an action entry within the instruction_details.
Now, we want to query the latest careflow_step of all activities within a specific archetype (e.g. medication) for a patient and maybe filter using the current state of an action. To my understanding, this will require to execute multiple AQL queries which seems like a rather...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Organisation, Address & Electronic communication archetypes - ready for publication](https://discourse.openehr.org/t/organisation-address-electronic-communication-archetypes-ready-for-publication/2649)
> The ‘Person’ archetype has recently been published.
Other members of the EHR demographic family have gone through simultaneous reviews and today the Editorial feedback for 'Organisation', 'Address' and 'Electronic communication' have been finalised and are also ready for publication
They have all been through 3 review rounds, although some of the content reviews for 'Electronic communication' were carried out inline within 'Person' and 'Organisation'
Feedback from all reviews, including...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Modelling pattern - imaging examination - what do you think?](https://discourse.openehr.org/t/modelling-pattern-imaging-examination-what-do-you-think/2648)
> There is a new pattern in development for imaging examination. The pattern is based in specialisation.
See the structure from this archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.5915
I am ambivalent. In many modelling situations I tend to use expansion by extensions (slots). This is a robust pattern which makes expansions flexible and independent. Still there might be situations where specialisation is the right approach.
What I fear with the suggested pattern is an explosion...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [General modeling question for DV_QUANTITY with multiple properties](https://discourse.openehr.org/t/general-modeling-question-for-dv-quantity-with-multiple-properties/2647)
> I was creating some examples for my clinical modeling students, and one example that I wanted to create was to allow recording different units for different physical properties in the same DV_QUANTITY, then realized the Archetype Editor didn't allow multiple "properties" in the same DV_QUANTITY.
Spec-wise, in general, without considering any specific use case, would it be possible to create such archetype / ADL?
I think it's not possible if using the archetype_profile class C_DV_QUANTITY...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [New archetype process](https://discourse.openehr.org/t/new-archetype-process/2645)
> So, just testing the water ....
We have a potential client that is looking to invest in an existing medical device already in use across several countries. I'm making suggestions they should create a data model to represent the maximal data collected by their device, clearly that could present itself as an openEHR archetype/template.
I appreciate it's quite vague at this point, but typically how long does it take for an archetype to travel through the archetype development process? I am...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Are DV_TIME_SPECIFICATION classes used on implementations or supported by modeling tools?](https://discourse.openehr.org/t/are-dv-time-specification-classes-used-on-implementations-or-supported-by-modeling-tools/2640)
> For the conformance data validation test cases I have some test cases pending for DV_GENERAL_TIME_SPECIFICATION and DV_PERIODIC_TIME_SPECIFICATION classes from https://specifications.openehr.org/releases/RM/Release-1.1.0/data_types.html#_time_specification_package
But I'm not sure if those classes are really used or not (like DV_PARAGRAPH) in the real world. So I don't want to create test cases for something nobody implements.
Thanks!
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Conformance data validation question: counterintuitive C_TIME.range constraints](https://discourse.openehr.org/t/conformance-data-validation-question-counterintuitive-c-time-range-constraints/2637)
> In the conformance specification I have a test case for the check of C_TIME.range constraint over DV_TIME to validate time data.
In another thread I was arguing that there are some date/time/datetime expressions that are not strictly comparable, even though the current spec says otherwise. I have double checked semantics with ISO8601-1_2019 and this is a summary:
There is an open issue in the comparability of two date/time/datetime expressions with different precisions but shared values for...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Point_Interval vs. Proper_Interval vs. Interval types](https://discourse.openehr.org/t/point-interval-vs-proper-interval-vs-interval-types/2636)
> I'm in the process of reviewing the data_types and aom specs in detail for the conformance test cases for data validation, and I'm finding little things that make some noise and would like to discuss to understand them better.
Until RM 1.0.3 we had the assumed type Interval that is concrete https://specifications.openehr.org/releases/RM/Release-1.0.3/support.html#_assumed_library_types
Then in RM 1.0.4, when the `support` classes were moved to the `foundation`spec...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [EVALUATION.social_network ready for publication](https://discourse.openehr.org/t/evaluation-social-network-ready-for-publication/2635)
> Dear all
The archetype EVALUATION.social_network has been through one review round. Of 17 completed reviews in the international CKM, there were only one "Major Revision", the rest were either "Minor Revision" or "Accept". The comments from the user giving "Major Revision" has been dealt with.
Changes in the archetype after review is mostly updating comments and descriptions for clarity and minor additions to metadata and descriptions for purposes of clarity.
The editors suggest...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [How to link openEHR with ERP?](https://discourse.openehr.org/t/how-to-link-openehr-with-erp/2633)
> right now I can make my first template (Medication order) and simple app for insert data to EHRbase.
For further step I want the app to send drug code and quantity to finance service.
From my understanding this have to work separately from openEHR right? But I also want the order ID insert to OpenEHR metadata So I can have a primary key between finance service and openehr service.
But I don’t know how to do that
Could you help me out?
Regards,
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Is valid_iso8601_duration correct?](https://discourse.openehr.org/t/is-valid-iso8601-duration-correct/2631)
> Two things to note:
1. the valid format doesn't mention the fractional seconds which are allowed in openEHR durations, we even have a specific constraint for that in C_DURATION.fractional_seconds_allowed in the AOM spec;
2. IMO the description of the parameter `s` should be separated from the expected result: `s` being any string, and result being: if `s` has this form ... then the result is `true`, the result will be `false` otherwise. (also noting the way other methods of Time_Definitions...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [After pulling latest image, Migrating Schema EHR takes long](https://discourse.openehr.org/t/after-pulling-latest-image-migrating-schema-ehr-takes-long/2623)
> Hello,
yesterday I did run a `docker-compose pull ehrbase` to update my ehrbase server to the latest available version. However, after pulling the latest image and running `docker-compose up ehrbase` the docker logs show
```
2022-05-16 13:29:32.180 INFO [] 9 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2022-05-16 13:29:32.306 INFO [] 9 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2022-05-16...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR @ Vitalis 2022, May 17-19, Gothenburg, Sweden](https://discourse.openehr.org/t/openehr-vitalis-2022-may-17-19-gothenburg-sweden/2621)
> There are several openEHR-related activities at the nordic health IT-conference Vitalis, Gothenburg 17-19 May.
All days
* Representatives and activities in the booths of
* Cambio (B04:02), https://www.cambio.se/traffa-oss-pa-vitalis/
* Mikael Nyström – Den svenska openEHR-förvaltningen och Cambio
* Tisdag 13:00
* Onsdag 9:00
* Torsdag 11:00
* Martin Grundberg – Vikten av öppna system och standardiserad data
* Tisdag 10:00
...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Cannot query all compositions of an EHR only with identifier "c"](https://discourse.openehr.org/t/cannot-query-all-compositions-of-an-ehr-only-with-identifier-c/2619)
> Hey Folks!
I usually used `Select c from EHR [ehr_id/value='02bb7f40-df72-491e-b44e-ca004b2a5932'] Contains Composition c` to get an overview over the compositions of an EHR. However, this now gives me
```
{
"error": "Bad Request",
"message": "Could not process query/stored-query, reason: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0"
}
```
Strangely, when using `c/name` instead of `c`, like `Select c/name from EHR ...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Duplicate check during composition upload](https://discourse.openehr.org/t/duplicate-check-during-composition-upload/2618)
> Hey folks!
I'm currently working on a proof of concept to transform data from an existing medical information system to my test ehrBase server. I am currently ready to send my old data through my parser and create new compositions.
It has happened to me a few times now that I have created several compositions for e.g. laboratory result, because I have restarted my parsing process.
Does openEHR/ehrScape not offer the possibility to recognize exactly identical compositions during the...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic openEHR Collaboration Meeting September 2022](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-september-2022/2615)
> **Purpose of meeting**
Connect with the Nordic openEHR community to explore ways of collaborating towards common goals related to the use of openEHR.
**When and where**
Thursday September 8th 10.00-16.00 CET
[Karolinska Universitetssjukhuset](https://www.karolinska.se/en/karolinska-university-hospital/), Eugeniavägen 3, Solna/Stockholm. See [maps and travel hints in comment below](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-september-2022/2615/5).
Room: "B4-12...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [What to do if template I need is using old version of archetype?](https://discourse.openehr.org/t/what-to-do-if-template-i-need-is-using-old-version-of-archetype/2614)
> Hi I'm quite new to openEHR
I have an existing template that I want to use
[https://ckm.openehr.org/ckm/templates/1013.26.80](https://ckm.openehr.org/ckm/templates/1013.26.80)
I try to modify this template with archetype designer but when I try to import oet file
there was an error
> **ePrescription (FHIR).oet**
>No such concept: archetypeId=openEHR-EHR-INSTRUCTION.medication_order.v0
I understand that medication order v0 was obsolete since it is v3 now.
but I'm not sure how to handle...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Is it possible to edit existing template?](https://discourse.openehr.org/t/is-it-possible-to-edit-existing-template/2612)
> Hi
Im new to openEHR and right now doing a POC for my company.
I found existing template about prescription which is interesting to me
https://ckm.openehr.org/ckm/templates/1013.26.80
But I don't know how to edit it and make another template from it.
Could anyone give me an advice?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Question about template ID format in current baseline spec](https://discourse.openehr.org/t/question-about-template-id-format-in-current-baseline-spec/2607)
> In AM 2.2.0 there is a specification for the template ID format with some suggestions https://specifications.openehr.org/releases/AM/Release-2.2.0/AOM2.html#_template_identifiers
In the same baseline spec version, in the Base Types 1.2.0 the TEMPLATE_ID type has no comment about the specific format for the ID value https://specifications.openehr.org/releases/BASE/Release-1.2.0/base_types.html#_template_id_class
Shouldn't the TEMPLATE_ID type be consistent with the AM spec in that something...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [Online openEHR2FHIR transformer](https://discourse.openehr.org/t/online-openehr2fhir-transformer/2606)
> It has been in closed "beta" for a few months, so I'm finally officially releasing the online front-end for the transformation of openEHR archetypes and templates to several FHIR profiles (Observation, Questionnaire) and artifacts (LogicalModels). This uses the same principles [already](http://standardsmania.blogspot.com/2020/05/generating-fhir-logical-models-from.html) [discussed](http://standardsmania.blogspot.com/2019/10/using-linkehr-to-generate-fhir.html)...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Developing standards for units of measurement](https://discourse.openehr.org/t/developing-standards-for-units-of-measurement/2603)
> The following has links to some developing standards for units:
https://www.nature.com/articles/d41586-022-01233-w
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Care plans in the real world](https://discourse.openehr.org/t/care-plans-in-the-real-world/2601)
> Hi all,
I'm curious to understand more about the extent of care planning implementation experience in the wild. If anyone is willing to provide some insights into their approach to developing and managing care plans it would be appreciated.
Ping @heath.frankel/@Seref from Ocean, @joostholslag from NEDAP.
Others?... there must be many other implementations - ranging from simple to very complex; stand-alone to integrated/shared.
In particular, I'd like to get some insight if the current...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRBase Cloud Setup](https://discourse.openehr.org/t/ehrbase-cloud-setup/2596)
> I am new to EHRBase and have installed it on the localhost and now I would like to deploy/migrate to a cloud environment preferably AWS . Please can some one share any info on the setup process and if it is possible?
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [OBSERVATION.Imaging examination result and CLUSTER.imaging.exam ready to be published](https://discourse.openehr.org/t/observation-imaging-examination-result-and-cluster-imaging-exam-ready-to-be-published/2594)
> Dear all
Since the first upload of "OBSERVATION.imaging.exam" in 2013, there has been work on one or several archetypes to cater for findings during radiological examinations. The work has been done by several people and at several occations until now. The pattern of physical examination archetypes has now been used as a pattern for imaging, and three archetypes were sent for review in March 2022. Those were
* OBSERVATION.imaging_exam_result
* CLUSTER.imaging_exam
*...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [New online resource: BFO2 IS-A hierarchy](https://discourse.openehr.org/t/new-online-resource-bfo2-is-a-hierarchy/2590)
> Dear all,
I've transferred a copy of the main BFO2 IS-A hierarchy and class descriptions [to our openEHR UML portal](https://specifications.openehr.org/releases/UML/latest/index.html#Diagrams___19_0_3_8fe028d_1652093019886_864595_5188).
The documentation was taken from [this online copy of the BFO specification](http://gbadske.org/Files/BFO2-Reference.pdf) - it's probably a bit out of date with respect to the new ECMA standard, but I don't have a copy of the latter yet. [BFO home is...
**[openEHR & standards](https://discourse.openehr.org/c/standards/69)** - [Que estandar devo aplicar en historia clinica](https://discourse.openehr.org/t/que-estandar-devo-aplicar-en-historia-clinica/2575)
> Hola, estoy en produccion de software para la gestion de historias clinicas, y necesito implementar un estandar, devo implementar openEHR
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Epworth sleepiness scale](https://discourse.openehr.org/t/epworth-sleepiness-scale/2572)
> Hello everyone,
Pleased to meet you all and become a part of your community. I am new to the world of modelling, and I am eager and excited to learn as much as possible. I am a medical doctor and a neuroscience PhD student.
I’ve spent a couple of days familiarizing myself with archetypes, templates and the tools that you use, and I created one archetype (mostly to test how good my understanding is), which I wanted to hear your opinion on.
It is the Epworth Sleepiness Scale (which can be used...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How create an EHR directly with a status?](https://discourse.openehr.org/t/how-create-an-ehr-directly-with-a-status/2568)
> Hey guys,
I'm barely new to openEHR and trying to create a new EHR with a Status inside the body. I took the following body from the official docs: [EHR API (openehr.org)](https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#ehr-ehr-post):
```
{
"_type": "EHR_STATUS",
"archetype_node_id": "openEHR-EHR-EHR_STATUS.generic.v1",
"name": {
"value": "EHR Status"
},
"subject": {
"external_ref": {
"id": {
"_type": "GENERIC_ID",
"value":...
**[openEHR.uk](https://discourse.openehr.org/c/openehr-uk/22)** - [openEHR and FHIR UKCore](https://discourse.openehr.org/t/openehr-and-fhir-ukcore/2564)
> Are there any active projects/discussions on documenting mappings between the (slowly) emerging UK Core FHIR profiles and openEHR?
If so, I'd like to get involved...
@ian.mcnicoll I'm guessing you might have some visibility of anything that is going on in this area.
**[Releases](https://discourse.openehr.org/c/releases/51)** - [Archie 2.0 and OpenEHR Visual Studio Code extension 0.5](https://discourse.openehr.org/t/archie-2-0-and-openehr-visual-studio-code-extension-0-5/2559)
> Recently we at Nedap Healthcare released Archie version 2.0, a java library for creating applications working with OpenEHR Archetypes and Reference Model data. It introduces support for the latest ADL/AOM features: soft terminology constraints and RM overlays. The first allows for terminology constraint codes to be specified with an example, preferred, extensible or required binding strength, allowing for more options in specialisation or in templates. The RM overlay allows for attributes in...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ['Cultural and ethnic identity' archetype is ready for publication](https://discourse.openehr.org/t/cultural-and-ethnic-identity-archetype-is-ready-for-publication/2557)
> Hi everyone,
The 'Cultural and ethnic identity' archetype has gone through 1 review round and, pleasingly, surprisingly, has reached a consensus view and is now deemed good for publication. The Editors deliberately kept the archetype small, simple and as generic as we could. This is an important concept in terms of recording aspects of self-identity that contribute so much to social and emotional well-being and this is notoriously badly recorded, if at all, in current EHRs. There is no doubt...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Assisted reproduction treatment cycle summary" ready for publication](https://discourse.openehr.org/t/assisted-reproduction-treatment-cycle-summary-ready-for-publication/2555)
> Hi
The EVALUATION.art_cycle_summary.v0 archetype has been through one review round. It is a highly specialised archetype with purpose described as "Summary or persistent information about a single cycle of assisted reproduction treatment."
There has been no demands for major changes in neither the Norwegian review nor the international review. The editors are confident that after the minor changes done, it is ready for publication.
The altered archetype can be viewed here:...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [ Archetype/RM for information privacy](https://discourse.openehr.org/t/archetype-rm-for-information-privacy/2551)
> I'm working on research on ways to provide privacy in EHR systems. So basically my idea is to provide privacy requirements for EHR systems as consent, integrity, auditing, auto logoff and so on. I saw in the documentation that there are some requirements that the systems developed by EHR must have. However, I would like to know how I can model this type of requirements within openEHR, for example if they would be through archetypes or reference models even if there are other ways to model...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Using matches operator in AQL](https://discourse.openehr.org/t/using-matches-operator-in-aql/2547)
> To date, the use of the [matches operator in AQL](https://specifications.openehr.org/releases/QUERY/latest/AQL.html#_matches) has been limited to:
* primitive value matching
* URI matching
* special functions like `TERMINOLOGY()`
However, we could use AQL matching in a generalised ADL mode, which pretty much replicates what GraphQL does, but better.
Here's an example that I can parse with my current EL parser. We can ignore the `val :=` at the start, it's just for testing. The `baby_weight`...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Seeking applications - establishment of openEHR Education Program Board (EPB)](https://discourse.openehr.org/t/seeking-applications-establishment-of-openehr-education-program-board-epb/2545)
> An initial Education Program Board (EPB) is being established by the openEHR International Board, and will be composed of up to 7-members, which will be chosen according to qualifications.
Applicants should be existing openEHR members, either Individual or as an employee of an Industry Partner or Organisational member.
Nominated individuals will be asked to indicate acceptance (if not self-nominated).
Applications are sought for candidates satisfying the EPB qualifications, demonstrating...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Person archetype - ready for publication](https://discourse.openehr.org/t/person-archetype-ready-for-publication/2543)
> Hi everyone,
The ‘Person’ archetype has gone through 3 review rounds and is now ready for publication. It is part of a family of archetypes that are intended for use within the clinical recording process and in form building.
Feedback from all reviews, including the latest review, can be found here: https://ckm.openehr.org/ckm/archetypes/1013.1.5358/reviewscontent. There were 2 reviewers who suggested a Major revision in the latest review round, but their feedback related to data that will...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Alvearie and openEHR?](https://discourse.openehr.org/t/alvearie-and-openehr/2538)
> HI!
Has anybody played around with the combination of https://alvearie.io/ and openEHR yet?
I imagine it woulde be nice to add an openEHR CDR to the Data Persistence box in [their architecture diagram](https://alvearie.io/architecture)...
...there is a hole in the diagram ready to be filled :slight_smile:
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic openEHR Collaboration Meeting May 2022](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-may-2022/2530)
> Purpose of meeting
Connect with Nordic openEHR community to explore ways of collaborating towards common goals related to the use and adoption of openEHR in the Nordics.
How to connect
Optional registration [here:](https://teams.microsoft.com/registration/GclGLxF8ZUSEsuNU-4CZeQ,N8Dj3ZIqmEyWjLKJYrSyhg,9dNLkPo2CkWpkUuIL_iUXA,VwxlNykcx0yKCjWUXirA_Q,MN-4mV8Kk0uOGZjBqUPXkg,VaZXh8z_YEm2-XyEhk5JzQ?mode=read&tenantId=2f46c919-7c11-4465-84b2-e354fb809979)
[Click here to join the meeting (MS...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Creating optional questions](https://discourse.openehr.org/t/creating-optional-questions/2523)
> Hello! I'm just learning about OpenEHR and I'm trying to convert one of our existing questionnaires to OpenEHR. One crucial part for us is the ability for make questions "optional", i.e. if you answer YES to Q1, then show/go-to Q2, if NO show/go-to Q3. Can/how do you model this in OpenEHR? Is it at the Archetype level? Or the Template level?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Passing additional headers while configuring FHIR terminology server](https://discourse.openehr.org/t/passing-additional-headers-while-configuring-fhir-terminology-server/2515)
> Hi,
I have a terminology server that uses Apikeys for security. This key is required to be passed as a header parameter for every call. Is there anyway to configure this while configuring the provider url in Ehrbase?
dileep
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [1st in series of International openEHR Events provided by openEHR Netherlands - 12 May 1100 CET](https://discourse.openehr.org/t/1st-in-series-of-international-openehr-events-provided-by-openehr-netherlands-12-may-1100-cet/2514)
> Series of international openEHR events provided by openEHR Netherlands
**Accelerating digitalisation in healthcare: The importance of open data**
**openEHR International Use-Cases**
The goal of openEHR community is to fundamentally change the perception of data in healthcare to Improve outcomes in clinical healthcare, public health, and the value of secondary data use.
**1st Online webinar -** 12 May 2022 at 11:00 CET for 1-hour
**Cattedra: Crossborder collaboration and regional joint...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [1st in series of International openEHR Events provided by openEHR Netherlands 12th May 1100 CET](https://discourse.openehr.org/t/1st-in-series-of-international-openehr-events-provided-by-openehr-netherlands-12th-may-1100-cet/2513)
> Series of international openEHR events provided by openEHR Netherlands
**Accelerating digitalisation in healthcare: The importance of open data**
**openEHR International Use-Cases**
The goal of openEHR community is to fundamentally change the perception of data in healthcare to Improve outcomes in clinical healthcare, public health, and the value of secondary data use.
**1st Online webinar -** 12 May 2022 at 11:00 CET for 1-hour
**Cattedra: Crossborder collaboration and regional joint...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Usage of OID, URI (URL/URN) in DV_IDENTIFIER fields?](https://discourse.openehr.org/t/usage-of-oid-uri-url-urn-in-dv-identifier-fields/2508)
> Sometimes we need to use URIs or OIDs as content for the `id` field of the [DV_IDENTIFIER Class](https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_identifier_class) (e.g. in the [Organisation archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.371)).
URIs are often kind of self-explanatory and may implicitly carry information about type/issuer/assigner. Most OIDs are also interpretable using lookup services.
Questions:
1. Is it reasonable to skip the...
**[Issue list](https://discourse.openehr.org/c/issues/76)** - [Test data set identifiers and organisation](https://discourse.openehr.org/t/test-data-set-identifiers-and-organisation/2500)
> All,
I have been looking at the question of organising the `_resources` area more systematically for the openEHR copy of the EhrBase test framework.
Today it looks like this:
So all those files in the first group really belong under the template Minimal_observation. I thought about making a directory called that, and pushing all the files down into it. In some cases we might want to improve the name, but a name like...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Do Contributions have any semantic meaning outside of the initial transaction?](https://discourse.openehr.org/t/do-contributions-have-any-semantic-meaning-outside-of-the-initial-transaction/2495)
> As far as I can tell, a CONTRIBUTION is just a transactional wrapper that contains one or more COMPOSITIONs at various states in their version history. Is there any wider semantic or clinical meaning behind it?
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Adding custom QUANTITY units](https://discourse.openehr.org/t/adding-custom-quantity-units/2494)
> Hi all,
We are currently using the Archetype Designer to create a template for recording historical medications.
One of the issues we've come up against is adding custom units to the list available in the "Dose" node (Quantity type).
Specifically, we want to be able to add things like "Tablets", "Puffs", "Drops", etc to the list. So when a medication with a specific dose is selected, the clinician can use one of these units to accurately record the dose.
e.g. Medication = Paracetamol...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Named element - and occurences](https://discourse.openehr.org/t/named-element-and-occurences/2492)
> A customer of us are using Archetype Designer (tools.openher.org) to create templates. It is possible to give the element a specific name and still have the element occurrences to unlimited.
In the generated OPT the definition is like :
```
-
NEW_NAME_OF_ELEMENT
```
As we understand this the name of the element is constrained to only allow a name like `NEW_NAME_OF_ELEMENT`, which in turn makes it impossible to repeat the element and...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Archetypes for test orders](https://discourse.openehr.org/t/archetypes-for-test-orders/2487)
> What archetypes can be used for test orders related to laboratory, radio-diagnostics, diagnostic? Is this [Clinical Knowledge Manager (openehr.org)](https://ckm.openehr.org/ckm/archetypes/1013.1.204) the most appropriate option or any other(s)?
Thanks!
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Which queries should EHR_STATUS.is_queryable actually affect?](https://discourse.openehr.org/t/which-queries-should-ehr-status-is-queryable-actually-affect/2482)
> Hey,
we want to implement the is_queryable restrictions. So before this is started i wanted to clarify some questions I came across while reading the specs.
https://specifications.openehr.org/releases/RM/latest/ehr.html#_ehr_status_class states that is_queryable will only affect population queries, meaning single EHR queries should still work.
Where i am am a bit unsure is what actually counts as a population...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [HTTP status code/message for requests denied because of EHR_STATUS.is_modifiable](https://discourse.openehr.org/t/http-status-code-message-for-requests-denied-because-of-ehr-status-is-modifiable/2473)
> Hi,
as I am currently implementing the semantics of the EHR_STATUS.is_modifiable flag, i was wondering which status code shall be returned if a request (i.e. POST /v1/ehr//composition) is denied because of EHR_STATUS.is_modifiable=false.
Should it be a simple 400 and the client can figure out what went wrong from the message or should it be more specific?
I was thinking 403 could make sense, because in essence a failed is_modifiable check is a forbidden operation which the...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Recording past history (medical and surgical), age, ethnicity](https://discourse.openehr.org/t/recording-past-history-medical-and-surgical-age-ethnicity/2469)
> Hi,
What could be the best archetypes to capture the following:
Past history (medical and surgical)
Age (DoB would do fine as the relevant age can be computed from the record date if this data item is available)
Ethnicity
Thanks!
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Specimen measurements is ready for publication](https://discourse.openehr.org/t/specimen-measurements-is-ready-for-publication/2468)
> Specimen measurements archetype has been through 3 review round. There seems to be consensus among the reviewers. Unless there are objections the archetype will be published on April 1, 2022.
Link to the archetype:
https://ckm.openehr.org/ckm/archetypes/1013.1.386
Please reply to this topic if you have any objections or comments.
**[SM](https://discourse.openehr.org/c/service-model/82)** - [Compositions list from OpenEHR REST API](https://discourse.openehr.org/t/compositions-list-from-openehr-rest-api/2467)
> I have a probably naive question. Is there a way through the openEHR REST API to get the list of compositions for a selected EHR?
I mean without using a query. In fact, I managed to do it only with the help of an AQL query.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Alcohol Consumption](https://discourse.openehr.org/t/alcohol-consumption/2466)
> Hi all,
Looking for some advice regarding recording alcohol consumption. The alcohol consumption summary is structured to record intake via either "episodes" of intake or by "type" of alcohol.
Clinically I find that patients generally can only report ABOUT how much alcohol they drink per week (or per day for regular drinkers)
We were hoping to be able to record just the overall intake at the "overall" level, similar to how "pack years" are recorded in the tobacco summary.
Does anyone have any...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Inconsistence in inContext in Webtemplate](https://discourse.openehr.org/t/inconsistence-in-incontext-in-webtemplate/2463)
> In the following Webtemplate
The width && time for any_event have "inContext" : true
where width && time for a24_hour_average have no inContext set.
I assumed this is because the second one has fixed values set.
Now the question is: Is this a bug or a feature?
[event_in_context.ehrbase.v0.json|attachment](upload://9qSxnL09wX209k4mouBAhL3szmD.json) (16.8 KB)
[event_in_context.ehrbase.v0.opt|attachment](upload://oQoRcnlFlnvmYL5jPqEf1XOxh9B.opt) (61.0 KB)
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [AQL query for compositions that have been created/updated within a time period](https://discourse.openehr.org/t/aql-query-for-compositions-that-have-been-created-updated-within-a-time-period/2458)
> Hi all,
We are using ehrbase and are successfully adding and updating compositions using the flat format. We would like to create an AQL query that return a list of compositions that have been created or updated within a given time period. Does ehrBase support such a query?
Thanks,
Peter
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Composition Choice for recording a recommendation/management list](https://discourse.openehr.org/t/composition-choice-for-recording-a-recommendation-management-list/2441)
> We are looking to record a simple management/recommendation list at the completion of a clinical encounter using the recommendation archetype. This would be a simply list, initially without actions and will not be a persistent record.
We were wondering what composition to store this in? We were considering either the Encounter or the Progress Note composition.
What are peoples thoughts on this?
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Allow unconstrainted archetype "category" in Archetype Designer](https://discourse.openehr.org/t/allow-unconstrainted-archetype-category-in-archetype-designer/2438)
> There is use for COMPOSITION archetypes where the "category" attribute is not set in the archetype, but rather something that can be set in a template instead. For example an archetype that, depending on context, would be reusable both in an "Episodic" template and also in another template where category "Presistent" or "Event" would be set instead.
Thus an unconstrained alteranative would be good to have in adition to the three radio-button alternatives in the lower right corner of the...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Comprehensive documentation of the FLAT format](https://discourse.openehr.org/t/comprehensive-documentation-of-the-flat-format/2434)
> Hi all,
we just published a comprehensive documentation of the flat format as part of the EHRbase documentation. Ever wondered how the Feeder Audit is represented in flat? Which CTX fields are automatically mapped?
You will find the answers here:
https://ehrbase.readthedocs.io/en/latest/09_flat/index.html
This is an important step towards the standardization of the WebTemplate and Flat format as part of the openEHR specs. We achieved a high level of conformance with Better within our...
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [SNOMED CT URIs in openEHR](https://discourse.openehr.org/t/snomed-ct-uris-in-openehr/2430)
> I believe I and others may sometimes have used the wrong URI-based prefix for SNOMED CT.
When looking closer at https://confluence.ihtsdotools.org/display/DOCURI/3.2+URI+Use-Cases I believe the prefix pattern for SNOMED IDs used in actual (openEHR) data instances (EHR content) should be `http://snomed.info/id/{sctid}` (pointing to an actual SCTID code) not `http://snomed.info/sct/{sctid}` (pointing to an entire SNOMED CT Edition).
What I am asking about is what e.g. goes into the...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [CKM tab with a generated form for a template](https://discourse.openehr.org/t/ckm-tab-with-a-generated-form-for-a-template/2429)
> I heard many times that auto-generated forms in CKM were tried before but didn't work. It was never explained why. Maybe this was good since I kept working on generating forms from OPTs without knowing that it cannot be done.
I just published my first demo version that runs in a web browser: [web demo](https://neoehr.com/openehr/forms) :partying_face:
This version isn't ready for data entry into a CDR but it might be all that is needed for clinical modelers to visualize their archetypes....
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Last menstrual period is ready for publication](https://discourse.openehr.org/t/last-menstrual-period-is-ready-for-publication/2428)
> Last menstrual period archetype has been through 1 review round. There seems to be consensus among the reviewers. Unless there are objections the archetype will be published on March 21, 2022.
Link to the archetype:
[Last menstrual period](https://ckm.openehr.org/ckm/archetypes/1013.1.5655)
Please reply to this topic if you have any objections or comments.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Five archetypes related to Artificial Reproductive Technology ("IVF") ready for publishing](https://discourse.openehr.org/t/five-archetypes-related-to-artificial-reproductive-technology-ivf-ready-for-publishing/2427)
> Hi everyone,
Five archetypes related to Artificial Reproductive Technology have been through one review round each. They're stongly linked to eachother, and should be considred to be part of a "package". There has been some changes, but none of them are considered controversial. The editorial team therefore suggests publishing.
If you have any comments or objections, please note them here, at the latest in one week from now, March 17th 2022.
Link to the...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Default value for precision](https://discourse.openehr.org/t/default-value-for-precision/2426)
> [DV_PROPORTION Class](https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_proportion_class) has an optional "precision" attribute.
When "precision" is not specified in ADL it is unconstrained. What is the default in this case: 0 or -1?
I guess it is -1 but cannot find where this is specified.
```
DV_PROPORTION[id9002] occurrences matches {0..1} matches {
numerator matches {|0.0..1.0|}
type matches {1}
}
```
From the specification: "The value -1 implies no...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Create new endpoints in rest with OpenEHR](https://discourse.openehr.org/t/create-new-endpoints-in-rest-with-openehr/2414)
> Good morning to all,
I am a new user in OpenEHR and in EHRBase. I would really appreciate your help and I'm sure you can help me.
Nice to meet you all.
I apologize if I ask any basic or stupid questions.
I have done the following first step: Run EHRbase + DB with Docker-Compose
https://ehrbase.readthedocs.io/en/latest/03_development/04_docker_images/01_ehrbase/02_use_image/index.html#run-ehrbase-db-with-docker-compose
Afterwards, I have configured the following SDK...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Agreeing on optional user interface hints in templates](https://discourse.openehr.org/t/agreeing-on-optional-user-interface-hints-in-templates/2406)
> **In short:** Let's start experimenting with adding vendor neutral hints (e.g. in templates) that can help both automated user interface generators and "manual" form editors create forms with more logic. Details follow.
**Current use-case background**
There is a current need in multi-vendor projects (at least in Sweden) where we would like at least some GUI/form logic to be possible to author once nationally and then be reused in several different vendor solutions (Cambio,...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Non archetype AQL predicates](https://discourse.openehr.org/t/non-archetype-aql-predicates/2405)
> Hi I have a mappings list as such attached to a DV_TEXT
"mappings": [
{
“_type”: “TERM_MAPPING”,
“match”: “=”,
“target”: {
“terminology_id”: {
“value”: “SNOMED-CT”
},
“code_string”: “345356676789”
}
},
{
“_type”: “TERM_MAPPING”,
“match”: “=”,
“target”: {
“terminology_id”: {
“value”: “UMLS”
},
“code_string”: “1234”
}
]
Is it possible to use AQL predicates over this list to...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Is someone using the FHIR Mapping Language to map openEHR <> FHIR?](https://discourse.openehr.org/t/is-someone-using-the-fhir-mapping-language-to-map-openehr-fhir/2404)
> We did some custom work mapping FHIR to openEHR for HiGHmed in the [FHIR Bridge](https://github.com/ehrbase/fhir-bridge). The mappings are just custom code moving data from a FHIR resource instance to an openEHR composition.
I was checking the [FHIR Mapping Language](https://www.hl7.org/fhir/mapping-language.html), that is used to map HL7 v2.x and CDA to FHIR, and thought that could be used also for openEHR.
Is anybody using that approach?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Example wearables integrations and standardizing in OpenEHR using HL7, etc, for GDL CDS tools?](https://discourse.openehr.org/t/example-wearables-integrations-and-standardizing-in-openehr-using-hl7-etc-for-gdl-cds-tools/2403)
> Companies like https://validic.com/ integrate information from Fitbit, Garmin, Withings, Woop, Oura, Google Fit, Apple Health and others.
Regulations in the EU and North America enable users to request data from any of these wearables companies, and https://www.prifina.com/ enables users to opt-in to their platform and share this data with other apps.
How would this be accomplished on OpenEHR? Have you seen any examples of Fitbit/Garmin/Apple data streamed into OpenEHR?
@johngrant4est...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [OpenEHR and Prescriptions?](https://discourse.openehr.org/t/openehr-and-prescriptions/2397)
> I wanted a little clarification on how we deal with prescriptions in OpenEHR
in my original thinking the archetypes that already exist provide for the capture of medication ordering/instruction, administration and this would be written directly to the CDR
is there any need to have a separate repository solely for the storage/retrieval/analysis of data about prescriptions? Would this be a functionality of a PIMS?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Help with finding open source device expert for clinical use case that supports OpenEHR integration](https://discourse.openehr.org/t/help-with-finding-open-source-device-expert-for-clinical-use-case-that-supports-openehr-integration/2396)
> I am struggling to find open source device manufacturers to solve a critical medical use case.
**Do you have anyone in your network (factory/manufacturer/designer/circuits/microelectronics expert) who would know who could help build an open source vitals measurement platform?**
For example, we need SpO2, blood pressure, height, weight, etc, or some subset thereof, so the data can be entered into OpenMRS automatically.
After finishing my PhD I work at an academic medical center, and through...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Refreshing archetypes related to pathology reporting](https://discourse.openehr.org/t/refreshing-archetypes-related-to-pathology-reporting/2393)
> Hi!
@heather.leslie, @SDubois, I and others have exchanged som emails regarding refreshing archetypes related to pathology reporting and agreed it would be better to continue (and repeat some of) the discussion here on discourse so that more people can join.
**Starting question:** What is the status of the project [Pathology Synoptic Reporting](https://ckm.openehr.org/ckm/projects/1013.8.19)?
**Background:** Several pathologists in Sweden are interested in shared development of...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Should EVENT_CONTEXT.setting be made optional and/or it's associated terminology updated?](https://discourse.openehr.org/t/should-event-context-setting-be-made-optional-and-or-its-associated-terminology-updated/2390)
> A finding from the Swedish openEHR work is that the general usefulness of the attribute "setting" of EVENT_CONTEXT (see diagram below) and the choices available in associated terminology (see XML below) feel a bit too country/organisation specific (and old) to be mandatory in the RM in current form.
Questions:
1. Could/should setting be made optional in a future RM release?
2. What do people from other countries think of the current alternatives in the terminology?
3. In what kind of...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Decision trees for risk stratification deployed at point-of-care on top of openEHR? (Or other informatics / AI / machine learning models)](https://discourse.openehr.org/t/decision-trees-for-risk-stratification-deployed-at-point-of-care-on-top-of-openehr-or-other-informatics-ai-machine-learning-models/2389)
> Hi,
I have built machine learning models that rely on unstructured data such as clinical notes, and structured data such as observations, labs, diagnoses, treatments, conditions, in order to give clinicians a risk score -- for patient readmission, maternal health, mental health, and other areas of medicine. An example is here: https://arxiv.org/abs/1904.05342 that has been used at academic medical centers in the US.
Do you know if anyone or any organization has deployed clinical decision...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [ELEMENT without value in ADL](https://discourse.openehr.org/t/element-without-value-in-adl/2386)
> I cannot figure out how to interpret an empty ELEMENT declaration (last line below).
Which DATA_VALUE type is used for an ELEMENT without a "value matches"?
```
CLUSTER[id1] occurrences matches {0..*} matches { -- Laboratory analyte result
items cardinality matches {1..*; unordered} matches {
ELEMENT[id28] occurrences matches {0..1} matches { -- Analyte result sequence
value matches {
DV_COUNT[id9001] occurrences matches {0..1}
}
...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [For fun: parsing nested decision chains for GDL3 / Task Planning](https://discourse.openehr.org/t/for-fun-parsing-nested-decision-chains-for-gdl3-task-planning/2385)
> Mainly for language geeks, I have the following parsing in my development Antlr4 Expression Language parser.
Geek clinicians like @joostholslag, @siljelb , @varntzen might or might not find it interesting. (You have to pretend you are an oncologist to even potentially be excited).
```
Result :=
choice in
================================================================================
not metastatic: choice in
...
**[SM](https://discourse.openehr.org/c/service-model/82)** - [About the SM category](https://discourse.openehr.org/t/about-the-sm-category/2383)
> For discussions of the [openEHR Service Model](https://specifications.openehr.org/releases/SM/latest) (SM).
**[SM](https://discourse.openehr.org/c/service-model/82)** - [Controlling CDR content creation](https://discourse.openehr.org/t/controlling-cdr-content-creation/2382)
> From the SEC call today, a discussion on a very interesting topic: how would a CDR limit creation of a particular kind of (say) persistent Composition (e.g. Medications list) to one effective instance in the system?
[Wiki discussion here](https://openehr.atlassian.net/wiki/spaces/spec/pages/1970765848/Rules+for+Controlling+Content+Creation+in+a+CDR).
**[openEHR & standards](https://discourse.openehr.org/c/standards/69)** - [Security, privacy and patient identity](https://discourse.openehr.org/t/security-privacy-and-patient-identity/2380)
> Hello, I'm working quite a bit in patient identity and privacy standards in various bodies in the US and EU. I haven't found much discussion in this forum about the topic, and would welcome the discussion.
**[Conformance](https://discourse.openehr.org/c/conformance/73)** - [Conformance Testing: implementation alternatives](https://discourse.openehr.org/t/conformance-testing-implementation-alternatives/2373)
> Hi all, I did some tests trying an alternative to [Robot/Python](https://robotframework.org/) for conformance test implementation.
I'm used to write tests in [Spock Framework](https://spockframework.org/) and created a couple of test cases from the Conformance Test Case Specification
https://github.com/ppazos/openehr-rest-client/blob/master/src/test/groovy/com/cabolabs/openehr/rest/client/OpenEhrRestClientTest.groovy
Spock uses Java/Groovy (which runs in the JVM) and has a DSL to express...
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Storing codes of two external terminologies](https://discourse.openehr.org/t/storing-codes-of-two-external-terminologies/2364)
> Hi.. I would like to store a UMLS code and and a snomed code while storing certain clinical values. The two codes will be needed for two different downstream systems. In the archetype designer I see the possibility of binding a DV_CODED_TEXT value to one terminology, not multiple.
Or is there a better way to address my problem, than binding to 2 terminology codes ?
Thanks much
Sangeeta Bose(Karkinos Healthcare)
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL across compositions with different Root Archetype Id](https://discourse.openehr.org/t/aql-across-compositions-with-different-root-archetype-id/2363)
> Hi @all,
Need to know if an AQL query can fetch data across 2 different template/compositions built with different root archetypes?
e.g.,
SELECT e/ehr_id/value from ehr e CONTAINS COMPOSITION c1[openEHR-EHR-COMPOSITION.encounter.v1] CONTAINS CLUSTER o[openEHR-EHR-CLUSTER.tnm.v1] AND COMPOSITION c2[openEHR-EHR-COMPOSITION.report.v1] CONTAINS observation o1[openEHR-EHR-OBSERVATION.progress_note.v1]
There is no output for the above query. We expected the AND to give the common EHR IDs that...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Where to put organisational levels that do not fit within health_care_facility](https://discourse.openehr.org/t/where-to-put-organisational-levels-that-do-not-fit-within-health-care-facility/2360)
> Hi!
In a [national Swedish openEHR work group](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/1893105737/PDL+i+openEHR) we are trying to (due to Swedish legal access filtering reasons) find the best place in a COMPOSITION+EVENT_CONTEXT to put some extra organisational levels that do not fit easily within `EVENT_CONTEXT.health_care_facility`.
1. In the normal health_care_facility attribute (see diagram below) we would like to put the most granular and clinically relevant...
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [Conformance Schedule progress - data types](https://discourse.openehr.org/t/conformance-schedule-progress-data-types/2358)
> Due to @pablo's ongoing work, I have been able to add his data types content tests to the openEHR Conformance test schedule. The [Content conformance section is here](https://specifications.openehr.org/releases/CNF/latest/platform_test_schedule.html#_content_conformance_2).
These test cases now all have formal identifiers within a global id scheme for all the test cases, i.e. REST API, content, everything.
The specifications-CNF repository also contains a (copy of) all the [robot scripts...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Can we introduce an example tab for templates in e.g. CKM similiar to simplifier?](https://discourse.openehr.org/t/can-we-introduce-an-example-tab-for-templates-in-e-g-ckm-similiar-to-simplifier/2355)
> I know its a tool from ocean and so on, but i would love to have some compositions connected to each template, so its just a tab and users can add 2-3 examples manually (nothing big like 10-20) . As in my ugly picture.
In fhir this examples helped me tremendously to work with the standard as you have data you can test your app with.
I do love @pablo wonderful...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Bmm_Expression implementation for using in archetype rules](https://discourse.openehr.org/t/bmm-expression-implementation-for-using-in-archetype-rules/2351)
> Hi everybody,
We are developing an ADL2 base tool. The first beta version has passed preliminary tests for creating and specializing archetypes and creating templates including operational templates. By the courtesy of "Archie" I created a c# translation, and accordingly refactored version of the 'Flattener'. I also implement BMM for model accessing and validations as much as I needed. Now I am going to implement the "Rules" part of the archetype. So I need to implement the BMM Expression as...
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [Specialize section in the OPT2](https://discourse.openehr.org/t/specialize-section-in-the-opt2/2347)
> I used [Generic lab test result example simple](https://ckm.openehr.org/ckm/templates/1013.26.408) and converted it to OPT2 using Nedap's great VSCode extension.
The resulting "openEHR-EHR-COMPOSITION.report-result.v1.0.4.opt2" has a "specialize" section which is not expected by the ANTLR4 [openEHR/adl-antlr Adl2.g4](https://github.com/openEHR/adl-antlr/blob/master/src/main/antlr/adl/adl2.g4) grammar:
```
operational_template:
SYM_OPERATIONAL_TEMPLATE meta_data?
archetypeHrid
...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Building custom modules using no-code, who is interested in sharing feedback?](https://discourse.openehr.org/t/building-custom-modules-using-no-code-who-is-interested-in-sharing-feedback/2339)
> Hi guys, I am working on a platform that enables you to build advanced modules with minimum to no coding
Main features:
1- connect multiple data sources (including OpenEHR & IoT medical devices)
2- drag & drop visual elements to build custom workflows & reports
3- connect to 3rd-party APIs to integrate AI into your workflow
I would love to give you a demo if you have the time to share some feedback (Calendly link below), also happy to share free access when the platform is...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Mixed absolute value and delta Events in a History](https://discourse.openehr.org/t/mixed-absolute-value-and-delta-events-in-a-history/2337)
> @siljelb [posted an interesting clinical modelling requirement](https://discourse.openehr.org/t/change-over-time-in-an-observation-measurement-represented-as/2329/1) that concerns the use of differential value Events, i.e. 'deltas'.
It made me wonder if we should consider how a mixture of absolute value and delta Events would work. Right now it is perfectly legal, but I doubt if anyone's software would handle it intelligently because it would not be expected. But that could be easily fixed,...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Formalising usability specification of laboratory results through template visualisation](https://discourse.openehr.org/t/formalising-usability-specification-of-laboratory-results-through-template-visualisation/2336)
> I am doing a PhD on the clinical usability of EHR systems through visualisation, and wondering if I can use openehr archetypes and templates as a research output - i.e. whether they are explicit enough to specify chunking of different lab tests, drill-down granularity of results and interactivity.
I am a clinician, so not that tech-minded. But I am stuck between trying to explain visualisation specifications by syntax / description or by model. Ideally, I would like to do the latter in some...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Examination findings CLUSTER archetype, breaking changes](https://discourse.openehr.org/t/examination-findings-cluster-archetype-breaking-changes/2332)
> Our current [Examination findings (CLUSTER.exam)](https://ckm.openehr.org/ckm/archetypes/1013.1.218) pattern was established in 2015, based on five years of trial and error, and published in 2017. It's proven to work very well for both generic use and specialisation to enable representation of the examination of all kinds of assumed normal body structures, as well as query using terminologies.
However, its use of a "No abnormality detected" boolean element makes it unusable for representing...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Percent as DV_PROPORTION or DV_QUANTITY](https://discourse.openehr.org/t/percent-as-dv-proportion-or-dv-quantity/2331)
> Hi all!
This is a conundrum we've been talking about informally for a long time, but never really concluded. openEHR has two possible ways of representing a percentage:
1. DV_PROPORTION with `type = 1`
2. DV_QUANTITY with `unit = %`
We haven't been clear on which one of these should be used for which use cases. I have a hypothesis which I'd like to get some input on:
1. When we're talking about physical concentrations such as saline concentration or oxygen saturation we should probably...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Change over time in an OBSERVATION measurement, represented as %](https://discourse.openehr.org/t/change-over-time-in-an-observation-measurement-represented-as/2329)
> Hi everyone!
Do we have a way to represent a change over time as a proportion rather than as an absolute measurement?
For example:
Weight change from one measurement to the next, we can express that in a number of kg using the OBSERVATION.body_weight and an interval event with the math function "change". However, in some use cases the change needs to be represented as % of weight loss or gain.
```
Measurement 1: 70 kg
Measurement 2: 80 kg
Change in kg: 10 kg
Change in percent: 14...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Apnea, arrest monitored in ICU](https://discourse.openehr.org/t/apnea-arrest-monitored-in-icu/2327)
> I am working on capturing data from ICU monitors/sensors and wondering how to record "apnea" and "arrest(asystole)".
They report "apnea" by respiration pause with duration(sec) and frequency(/hour), as they are monitored in such as C-PAP, capnometer or apnomonitor. At first, I thought this should be described with OBSERVATION.respiration archetype, but did not fit well.
I also wondering a similar case, how to record "asystole" (duratio/sec, frequency/hour) in cardiac monitor and holter...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Link multiple Compositions to a single Visit](https://discourse.openehr.org/t/link-multiple-compositions-to-a-single-visit/2326)
> Hello Guys,
I am new to openEHR.
For a SINGLE Visit, a patient can have multiple compositions from different templates (Vital Signs, Problem Diagnosis, Body Temperature, Lab Order etc...)
How can I link these multiple compositions to the Visit.
Example use case: Generate a report that returns lab orders for a specific problem diagnosis in a single visit. How can i achieve this in openEHR???
Thanks for your help
**[RM](https://discourse.openehr.org/c/rm/42)** - [DV_DATE_TIME and DV_DATE](https://discourse.openehr.org/t/dv-date-time-and-dv-date/2321)
> DV_DATE_TIME and DV_DATE are data types which are often required to be used interchangeably. Currently, if I've understood correctly, they are siblings sharing a common parent, but they can't be constrained into each other like for example DV_TEXT can be constrained to DV_CODED_TEXT.
Finding out this limitation was a surprise to several modellers I talked to about the problem, as it was assumed that one could for example constrain a DV_DATE_TIME to a DV_DATE in a template. There are several...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Uppmärksamhetsinformation i openEHR](https://discourse.openehr.org/t/uppmarksamhetsinformation-i-openehr/2316)
> Under mötet 2022-01-21 i svenska openEHR förvaltningen ([se minnesanteckningar](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/1958019253/2022-01-21+Agenda+m+tesanteckningar+f+rvaltningssm+te)) föreslogs det att vi påbörjar arbete med en implementationsguside för Uppmärksamhetsinformation i openEHR. En [sida för implementationsgusiden finns nu i openEHR-fövaltningens...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [SDK for Operational templates](https://discourse.openehr.org/t/sdk-for-operational-templates/2315)
> I finished my [OPT SDK generator](https://neoehr.com/openehr/sdk). It can generate an object-oriented classes for any OPT2.
Then I had an idea to save the OPT types tree to a JSON to help me debug my code.
I realized this might be an useful to others too. People can use JSON with OPT types (with included properties and constraints) to do anything they need - without dependence on my code generators.
The first reaction to the SDK JSON was: "this looks like Web Templates". What do you...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Sending UID in a new composition](https://discourse.openehr.org/t/sending-uid-in-a-new-composition/2312)
> In the API specs for creating a new composition via POST, the [example](https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#composition-composition-post) shows an included uid. This seems strange to me, since it should be the responsibility of the receiving system to create the uid. Because the root needs to be unique within a system, allowing an externally-created uid root places a heavy burden on the receiver to guarantee uniqueness.
Is this intended or just an oversight?...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Blood type archetype that captures different blood group systems and factors influencing blood type](https://discourse.openehr.org/t/blood-type-archetype-that-captures-different-blood-group-systems-and-factors-influencing-blood-type/2310)
>
Is there a designated archetype for blood group information (potentially a work in progress) accounting for different blood group systems and potential factors influencing blood type status? The only one I've found so far that is heading towards what I'm looking for is this one: https://ckm.apperta.org/ckm/archetypes/1051.32.493. Although blood types are inherited, they can change (i. e. after a bone...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Missing "magnitude" for DV_QUANTITY constraint](https://discourse.openehr.org/t/missing-magnitude-for-dv-quantity-constraint/2307)
> In "openEHR-EHR-EVALUATION.health_risk.v1.1.7.opt2" there is a DV_QUANTITY constraint without "magnitude" attribute which is a [mandatory attribute for DV_QUANTITY](https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class):
```
ELEMENT[id4] occurrences matches {0..1} matches { -- Risk assessment
value matches {
DV_TEXT[id9011] occurrences matches {0..1}
DV_PROPORTION[id9012] occurrences matches {0..1}
DV_QUANTITY[id9013]...
**[Resources](https://discourse.openehr.org/c/resources/71)** - [Archetypes - prescription](https://discourse.openehr.org/t/archetypes-prescription/2305)
> Hi, I'm new to openEHR and I wonder if you can help me with this: what are the main archetypes needed to "prescribe a medicine / medication order for a diabetic patient" starting from doing a lab test. Thank you
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Adding simplified (flat JSON) paths in exported Excel representation?](https://discourse.openehr.org/t/adding-simplified-flat-json-paths-in-exported-excel-representation/2302)
> Hi!
Would it be possible to add another column in the Excel-files that are currently possible to export based on a template in archetype designer? It would simplify some integration work.
A simple stupid example of current format is attached for curious readers.
[test2.xlsx|attachment](upload://8XVDwAMrVSCO023uiOHgbFYyMmg.xlsx) (6.3 KB)
So what I am asking for could for example be added as a new additional last column (K) and contain the kind of path format used in...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Recording attestations for other parties](https://discourse.openehr.org/t/recording-attestations-for-other-parties/2301)
> Hi,
We are looking into using attestations to record patient approval and approval by a senior clinician of a care plan.
The patient or senior clinician should be able to approve the care plan themselves. But it should also be possible for another clinician to register the approval of the client/senior clinician.
We are wondering how to record in openEHR both the party that approved the care plan and the party that recorded that approval.
For compositions there is a clear distinction...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [OpenEHR Spec Compendium](https://discourse.openehr.org/t/openehr-spec-compendium/2296)
>
Dear all,
In order to know if a vendor meet a certain OpenEHR specification, we have to search inside OpenEHR website to find the latest version (i.e. REST API is defined at (ITS-REST) https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/definitions.html). If we want to search for all the specifications, or ask a vendor to check wheter his product meet or not the latest version, it is something not easy.
I would like to know if there is a place where we can find a compendium...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Migrating CDR data to a newer RM release](https://discourse.openehr.org/t/migrating-cdr-data-to-a-newer-rm-release/2291)
> @sebastian.iancu asked whether different versions of RM models can be used/loaded at the same time.
Yes, they can. Each AM/RM release is generated as a separate package/library and they can all be imported at the same time (see #1 below).
The example code is for reading/processing OPTs but a similar approach can be used to:
- Migrate CDR data from one RM release to another (e.g. RM 1.0.4 to RM 1.1.0).
- Convert archetypes to a newer ADL release (e.g. AOM 2.0.6 to AOM 2.3.0).
#2 walks...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Create Composition Performance Benchmarks in EHRBase - For batch insertions](https://discourse.openehr.org/t/create-composition-performance-benchmarks-in-ehrbase-for-batch-insertions/2290)
> Hi,
We have developed data pipelines that insert retrospective clinical data from hospital systems into EHRbase CDR (We have installed using Docker)
The data volume we are piloting with is in the tune of 800K + . Although the insertions work fine, we see that there is a huge performance deterioration after a few 100 insertions. It almost takes 1 second per composition on an average. We also noticed that for every few inserts, there is a delay of 5-6 seconds.
Before we start further...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Dv_coded_text_extended](https://discourse.openehr.org/t/dv-coded-text-extended/2288)
> I just finished reading all the old posts in the ADL category. There are few threads about ELEMENT with DV_CODED_TEXT and DV_TEXT for free text. Some observations after reading them all in a single sitting:
- I noticied that nobody suggested a dedicated DV_CODED_TEXT_EXTENDED type (pick a better name). It would be DV_CODED_TEXT with an additional attribute (e.g. "free_text").
- Coded values would be in "defining_code" and the free text would be in "free_text" attribute. Edit: or...
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [openEHR conformance verification design document](https://discourse.openehr.org/t/openehr-conformance-verification-design-document/2285)
> Hi all! Next week I'll release a document based on the openEHR conformance work I've done for HiGHmed and the exchange at had with openEHR SEC members. This document will help companies to prepare to the openEHR Conformance Verification, and later for openEHR Conformance Certification. Stay tuned!
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Yale Global Tic Severity Scale - Revised (YGTSS-R) - ready for publication](https://discourse.openehr.org/t/yale-global-tic-severity-scale-revised-ygtss-r-ready-for-publication/2283)
> Hi,
The archetype Yale Global Tic Severity Scale - Revised (YGTSS-R) - has been through 1 review round. There have been added description elements as requested from the Norwegian review summary. No major changes to the archetype.
The editorial team suggest publishing.
If you have any comments or objections, please note them here, at the latest in time of the planned publication date, January 28th 2022.
Link to the archetype: [[Yale global tic severity scale...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Menstrual cycle and Menstrual diary ready for publication](https://discourse.openehr.org/t/menstrual-cycle-and-menstrual-diary-ready-for-publication/2282)
> Menstrual cycle archetype has been through 5 review rounds and the Menstrual diary has been through one review round. There seems to be consensus among the reviewers. Unless there are objections the archetypes will be published on January 26, 2022.
Link to the archetypes:
[Menstrual cycle](https://ckm.openehr.org/ckm/archetypes/1013.1.1922)
[Menstrual diary](https://ckm.openehr.org/ckm/archetypes/1013.1.5657)
Please reply to this topic if you have any objections or comments.
**[Conformance](https://discourse.openehr.org/c/conformance/73)** - [Progress - robot tests - new ids](https://discourse.openehr.org/t/progress-robot-tests-new-ids/2280)
> The copy of EhrBase robot scripts now in the openEHR Conformance repo have been given new identifiers as per the SEC-agreed approach. [You can see them here](https://github.com/openEHR/specifications-CNF/tree/master/tests/platform/robot). This organisation of test scripts follows the structure of the platform spec, but of course tests the REST API implementation of each call. This hierarchy seems easy to understand from my point of view - what do others think?
The main [conformance...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [Region of Catalonia - Preliminary market survey for the procurement of an electronic prescribing and medicines administration solution](https://discourse.openehr.org/t/region-of-catalonia-preliminary-market-survey-for-the-procurement-of-an-electronic-prescribing-and-medicines-administration-solution/2275)
> Dear friends,
I hope you had a great entry into the New Year and that you and your relatives are in good health.
I am writing here today because we just published a new market consultation. This time we are aiming to obtain technical information on the existing possibilities to supply the elements for the development of an integrated and interoperable electronic prescribing and medicines administration solution for the Integrated Public Healthcare System of Catalonia. Even though the focus...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic openEHR Collaboration Meeting February 2022](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-february-2022/2271)
> **Purpose of meeting**
Connect with the Nordic openEHR community to explore ways of collaborating towards common goals related to the use of openEHR.
**When and where**
Tuesday February 15th 13.00-15.00 CET, Online
**How to join**
Contact Mikael Nyström (mikael.nystrom@cambio.se)
Feel free to spread the invite to your openEHR network
**Agenda**
* Welcome and introductions (15 min)
* Pirkko Kortekangas, openEHR Finland/Una Oy: openEHR clinical modelling under the umbrella of HL7 Finland...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Concrete DATA_VALUE type for an ELEMENT with multiple objects](https://discourse.openehr.org/t/concrete-data-value-type-for-an-element-with-multiple-objects/2268)
> I'm struggling with an ELEMENT that has a single "value" but multiple objects:
```
ELEMENT[id15] occurrences matches {0..1} matches { -- Location of measurement
value matches {
DV_CODED_TEXT[id9024] occurrences matches {0..1} matches {
defining_code matches {[ac9006]} -- Location of measurement (synthesised)
}
DV_TEXT[id9025] occurrences matches {0..1}
}
}
```
From the above ADL my code generator cannot figure out the type of the concrete...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [ELEMENT with "name" and "value" attributes in ADL](https://discourse.openehr.org/t/element-with-name-and-value-attributes-in-adl/2263)
> Vital signs template includes "openEHR-EHR-OBSERVATION.pulse.v2.0.4.opt2" with ELEMENT definition that has two attributes: "name" and "value".
[ELEMENT](https://specifications.openehr.org/releases/RM/latest/data_structures.html#_element_class) has three optional attributes: "null_flavour", "value", "null_reason".
```
ELEMENT[id1024] occurrences matches {0..*} matches { -- Clinical interpretation
name matches {
DV_CODED_TEXT[id9015] occurrences matches {0..1} matches {
...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [NeoEHR join openEHR as Industry Partners](https://discourse.openehr.org/t/neoehr-join-openehr-as-industry-partners/2254)
> We welcome NeoEHR who have joined openEHR as Micro Industry Partners.
Based in Slovenia, NeoEHR provide an openEHR applications builder.
Founder, Borut Jures said the "reason he fell in love with openEHR" is down to this quote
*"If a human wrote computable specifications then there is no need for another human to implement them in code. The code should be generated by a computer."*
Find out more about this new Partner [HERE](https://openehr.org/community/industry_partners_detail/neoehr)
**[RM](https://discourse.openehr.org/c/rm/42)** - [RM invariants in a computable form](https://discourse.openehr.org/t/rm-invariants-in-a-computable-form/2250)
> In another post Erik noticed a "validate()" method in an OPT model class.
[quote="erik.sundvall, post:7, topic:2144"]
So does the superclass `Element`(or some other ancestor) contain a validator algorithm that makes use of the Constraints?
[/quote]
The idea is to generate validation rules for OPT elements. There are 3 levels:
1. Using generated constraints to validate that the OPT fields are in accordance with the constraints. Each OPT model class will implement a validate() method to...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Blood flow rate & amount of blood treated](https://discourse.openehr.org/t/blood-flow-rate-amount-of-blood-treated/2247)
> Hello!
I got a use case for hemodialysis registry where the blood flow rate is needed, along with the volume of blood treated. I have checked the ckm's and I could not find any candidate for this case, but I also might have searched with the wrong keywords. Just to be sure, are there any archetypes available for these cases?
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Fhirbridge - Building in AllergyIntolerance](https://discourse.openehr.org/t/fhirbridge-building-in-allergyintolerance/2244)
> Hi, I hope this is the right place to discuss the FHIRBridge. I'm looking into adding a mapping for AllergyIntolerance. I was wondering, given the extensive coverage for Covid19, if I've missed something. Is there already some way adverse reactions / allergies are mapped?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Data validation conformance tests for URI data types](https://discourse.openehr.org/t/data-validation-conformance-tests-for-uri-data-types/2242)
> The DV_URI and the DV_EHR_URI have a `value` attribute that should have a specific format, in both bases the value should be compliant with the RFC3986 URI definition, and for DV_EHR_URI the URI `scheme` should be equals to `ehr`.
Since DV_URI.value is String, in archetypes and templates it is possible to define a constraint using the C_STRING pattern or list constraints.
When using the `pattern`, we need to be sure the constraint is compatible with the URI format.
I couldn't find this...
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [Conformance Guide - initial draft](https://discourse.openehr.org/t/conformance-guide-initial-draft/2241)
> A first somewhat coherent but still very rough draft of a [Conformance Guide is now up](https://specifications.openehr.org/releases/CNF/latest/guide.html). This is the README document for the conformance specifications it is based on the older conformance draft and newer content from @pablo .
All feedback welcome.
**[Conformance](https://discourse.openehr.org/c/conformance/73)** - [Status Update - merged WIP](https://discourse.openehr.org/t/status-update-merged-wip/2240)
> I have merged working changes from the branch into master, so you will now see three documents in the [Conformance Component](https://specifications.openehr.org/releases/CNF/latest). They are all still rough, but taking shape. This merge means you can access the working state of all the docs just by going to the normal [specs home page](https://specifications.openehr.org/development_baseline), rather than checking out anything special.
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [Conformance Framework description](https://discourse.openehr.org/t/conformance-framework-description/2239)
> I have done some thinking on how to document the conformance specifications and framework in some detail, based on some of @pablo 's original ideas. You can see his diagrams in the [current (very draft) Conformance Guide](https://specifications.openehr.org/releases/CNF/latest/guide.html), in particular [this one on 'conformance artefacts'](https://specifications.openehr.org/releases/CNF/latest/guide/diagrams/conformance_framework-artefacts.svg).
I propose a new version of this diagram that...
**[RM](https://discourse.openehr.org/c/rm/42)** - [C_DURATION is missing redefined default_value in BMM (and web)](https://discourse.openehr.org/t/c-duration-is-missing-redefined-default-value-in-bmm-and-web/2238)
> C_DURATION in "openEHR_am_206.bmm" (and 210, 220, 230) is missing redefinition of the "default_value" attribute:
```
["default_value"] = (P_BMM_SINGLE_PROPERTY) <
name = <"default_value">
type = <"Duration">
>
```
All [primitive types](https://specifications.openehr.org/releases/AM/latest/AOM1.4.html#_class_descriptions_3) are missing "default_value" redefinition in the web version of the specifications.
---
p.s.
Are we missing "Specification/AM" category?
I'm selecting RM even...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Tooling support for inviting reviewers](https://discourse.openehr.org/t/tooling-support-for-inviting-reviewers/2236)
> Hi, everyone! Happy 2022!
This should possibly also be posted in the Tooling category, I'm not sure how to do that :slight_smile: .
In the review process in the CKM I've encountered some issues that has to be discussed. I could have just asked for a change in the CKM functionality, but would like to get input from a broader audience first. So here it is:
Normally we invite existing users, and match the domain and experience the users have given when they registered, with the requirement...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Who has implemented BMM INDEXED_CONTAINER_PROPERTY?](https://discourse.openehr.org/t/who-has-implemented-bmm-indexed-container-property/2235)
> Due to recent review and fixes to various BMMs due to @borut.jures (Borut Jures) implementation work, I realised that none of the `Hash<>` (= `Map<>` in Java) relationships in the BMMs are using the `P_BMM_INDEXED_CONTAINER_PROPERTY` meta-type (see [here in the P_BMM spec](https://specifications.openehr.org/releases/LANG/latest/bmm_persistence.html#_container_properties)), which generates `BMM_INDEXED_CONTAINER_PROPERTY` instances at runtime ([see here in BMM...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [openEHR Terminology parsable vs. multimedia type and related questions](https://discourse.openehr.org/t/openehr-terminology-parsable-vs-multimedia-type-and-related-questions/2234)
> In the specs, the DV_MULTIMEDIA.media_type is constrained to the openEHR terminology "media types".
The terminology includes several text/*** types, some which might not be for multimedia data but for parsable data: https://github.com/openEHR/terminology/blob/master/openEHR_RM/openehr_external_terminologies.xml#L429-L440
Shouldn't we have a different term sent for parsable and multimedia media types?
I can also see that we don't have a term set for the DV_PARSABLE.formalism, and if an...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [What's the correct openEHR terminology ID](https://discourse.openehr.org/t/whats-the-correct-openehr-terminology-id/2233)
> In the archetypes created using the Archetype Editor, the terminology ID for openEHR is "openehr". In the archetypes created using the Archetype Designer the openEHR terminology ID is "openEHR".
```
DV_MULTIMEDIA matches {
media_type matches {
[openEHR::
387,
388,
389,
...
```
Are our terminology_ids case insensitive or is this a bug in the Archetype Designer?
Thanks.
**[RM](https://discourse.openehr.org/c/rm/42)** - [Interval of N plus/minus M](https://discourse.openehr.org/t/interval-of-n-plus-minus-m/2231)
> The [Interval class](https://specifications.openehr.org/releases/BASE/latest/foundation_types.html#_interval_class) allows an [interval of N ±M](https://specifications.openehr.org/releases/LANG/latest/odin.html#_intervals_of_ordered_primitive_types) and [here](https://specifications.openehr.org/releases/SM/latest/serial_data_formats.html#_openehr_intervals_represented_as_json_string).
The [Interval...
**[RM](https://discourse.openehr.org/c/rm/42)** - [RESOURCE_DESCRIPTION.parent_resource is mandatory but value is missing in templates](https://discourse.openehr.org/t/resource-description-parent-resource-is-mandatory-but-value-is-missing-in-templates/2230)
> RESOURCE_DESCRIPTION.parent_resource is mandatory but value is missing in templates
[RESOURCE_DESCRIPTION](https://specifications.openehr.org/releases/BASE/latest/resource.html#_resource_description_class) has attribute "parent_resource" as mandatory.
This attribute is not provided in templates (e.g. openEHR-EHR-COMPOSITION.encounter.v1.0.7.adls).
Should the attribute RESOURCE_DESCRIPTION.parent_resource be optional in "openehr_base_110.bmm"?
Maybe I don't understand what its value should...
**[RM](https://discourse.openehr.org/c/rm/42)** - [AUTHORED_RESOURCE.translations and RESOURCE_DESCRIPTION.details are List instead of Hash](https://discourse.openehr.org/t/authored-resource-translations-and-resource-description-details-are-list-instead-of-hash/2229)
> AUTHORED_RESOURCE.translations and RESOURCE_DESCRIPTION.details are List instead of Hash in openehr_base_110.bmm
[AUTHORED_RESOURCE](https://specifications.openehr.org/releases/BASE/release-1.1.0/resource.html#_authored_resource_class) has attribute "translations" of type Hash but it is List in "openehr_base_110.bmm".
The same for AUTHORED_RESOURCE in "openEHR_am_206.bmm".
Similar...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Published archetypes are missing "language.translations.author"](https://discourse.openehr.org/t/published-archetypes-are-missing-language-translations-author/2228)
> Some archetypes are missing "language.translations.author" and are published. Validator should prevent that since the "author" is a required attribute.
As part of "Vital signs" and "COVID-19 Pneumonia Diagnosis and Treatment - 7th edition" templates I found that Finnish translations are missing the author attribute:
- openEHR-EHR-COMPOSITION.encounter.v1.0.5;...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Clarifications of C_DURATION constraint validation](https://discourse.openehr.org/t/clarifications-of-c-duration-constraint-validation/2227)
> A duration is an expression of the form `PnYnMnDTnHnMnS`, where each part is optional (years, months, etc.).
C_DURATION has constraints that allow or not each part/component, and also has a range constraint.
The range constraint has upper and lower limits that are of type `Duration`. If we have a range of `P1M..P30M`, does `P1Y` validate against that constraint or not?
Another case: range = `P2Y..P5Y` and value = `P1Y20M`, does that fail because 1Y < 2Y or passes because the 20M is...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Is fractional_seconds_allowed attribute needed in C_DURATION?](https://discourse.openehr.org/t/is-fractional-seconds-allowed-attribute-needed-in-c-duration/2225)
> In the current spec I have found that attribute in https://specifications.openehr.org/releases/AM/Release-2.2.0/AOM1.4.html#_overview_4
By looking at the ISO8601 Wikipedia (hope we can look at the spec soon) there is no fractions for the seconds in a duration. If that is correct, then I don't understand what `fractional_seconds_allowed` is representing.
Any ideas?
Thanks!
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Trying to connect from outside to ehrbase](https://discourse.openehr.org/t/trying-to-connect-from-outside-to-ehrbase/2222)
> 
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [PDL, HSA-id m.m. i openEHR - Remiss 1 (deadline 31 Jan)](https://discourse.openehr.org/t/pdl-hsa-id-m-m-i-openehr-remiss-1-deadline-31-jan/2217)
> I [svenska openEHR-förvaltningens samarbete](https://discourse.openehr.org/t/openehr-se-borja-lasa-har/391) fanns intresse från både vårdgivar- och leverantörshåll av att ta fram en implementationsguide som beskriver rekommenderade sätt att tillämpa den svenska Patientdatalagen (PDL) i openEHR-baserade system på ett gemensamt leverantörsoberoende sätt ([se kanbantavla](https://openehr.atlassian.net/jira/software/projects/SWE/boards/6?selectedIssue=SWE-20)).
## Inbjudan
Du inbjuds härmed...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Specialisations on SLOTs](https://discourse.openehr.org/t/specialisations-on-slots/2211)
> Noting from the specs "An archetype is a specialisation of another archetype if it mentions that archetype as its parent, and only makes changes to its definition such that its constraints are ‘narrower’ than those of the flat parent. "
Are the nominated included archetypes part of the 'definition' of the SLOT?
The use case example is a parent archetype that contains 3 nominated archetypes as suggested or preferred SLOT-fillers. Think of a modelling situation like the large family of...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Is DV_INTERVAL missing invariants?](https://discourse.openehr.org/t/is-dv-interval-missing-invariants/2210)
> Reading the RM 1.1.0 data types spec, in DV_INTERVAL and Interval types I think we are missing an invariant, for instance, if lower_included = true and lower = NULL, is that valid? Same with upper.
I'm not seeing any constraint/invariant that says something about those cases. IMO lower/upper_included should imply lower/upper is not NULL.
REFs:
- https://specifications.openehr.org/releases/RM/Release-1.1.0/data_types.html#_dv_interval_class
-...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Medication order, Medication details, Dosage - ready for republication as a new major version](https://discourse.openehr.org/t/medication-order-medication-details-dosage-ready-for-republication-as-a-new-major-version/2208)
> After discussion in Discourse, Slack and among editors, the following archetypes will be republished as a new major version.
* [INSTRUCTION.medication_order.v2](https://ckm.openehr.org/ckm/archetypes/1013.1.3124)
* [CLUSTER.medication.v1](https://ckm.openehr.org/ckm/archetypes/1013.1.2368)
* [CLUSTER.dosage.v1](https://ckm.openehr.org/ckm/archetypes/1013.1.2751)
At the same time, the following archetypes will be republished as a new minor version, to include the new major versions of the...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Archetype references in archetypes, syntax](https://discourse.openehr.org/t/archetype-references-in-archetypes-syntax/2205)
> When we reference archetypes within other archetypes, it has been customary to include the major version number of that archetype. This is generally unnecessary since a new major version of the same concept has the same (but possibly additional) use cases as the previous major version. It also makes governance harder, since it means every time an archetype is republished as a new major version, even from v0 to v1, all referencing archetypes need to be changed too.
Archetype Designer now...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [ASSERTION in openehr_expression_104.bmm is not in accordance with the specifications](https://discourse.openehr.org/t/assertion-in-openehr-expression-104-bmm-is-not-in-accordance-with-the-specifications/2203)
> The definition of ASSERTION in "openehr_expression_104.bmm" is not in accordance with the specifications.
ASSERTION Class is specified in:
- [ASSERTION Class in AM 2.0.6/AOM1.4](https://specifications.openehr.org/releases/AM/Release-2.0.6/AOM1.4.html#_assertion_class)
- [ASSERTION class in BASE 1.0.4](https://specifications.openehr.org/releases/BASE/Release-1.0.4/expression.html#_assertion_class)
The specifications are not the same (inherits, variables). I guess the one in BASE is the...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Unit property name for "mg/kg(body weight)/day"](https://discourse.openehr.org/t/unit-property-name-for-mg-kg-body-weight-day/2202)
> I'm in the process of adding a new unit property to the Archetype Designer units file, for units like "mg per kg body weight per day" or "ml per m^2 body surface area per day", but I'm not sure about the name of this property. I'm thinking "dose rate", but I'm open to suggestions.
Edit: Perhaps "medication dose rate", to avoid confusion with "radiation dose".
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Duplicate group concept IDs in "openehr_terminology.xml"](https://discourse.openehr.org/t/duplicate-group-concept-ids-in-openehr-terminology-xml/2195)
> I assumed that the IDs in the "openehr_terminology.xml" would be unique across groups. There are a few duplicates:
id="253":
```
```
id="523":
```
Coming back to an old topic. Our current JSON/XML schemas reflect the structures in the RM. Now the serialized representations we use at the REST API level are slightly different than the RM JSON/XML representations, so we can't use the same schemas to validate those.
For instance, POST /ehr returns an EHR in JSON that contains the ehr_status, which is the actual EHR_STATUS serialized to JSON (the last version of the status). In the RM JSON schema, ehr.ehr_status is an OBJECT_REF. So the...
**[ITS](https://discourse.openehr.org/c/its/41)** - [REST API: definition operations query version ids](https://discourse.openehr.org/t/rest-api-definition-operations-query-version-ids/2191)
> I just realised after we dropped the call that on the question of query formalism version id - if it's a non-numeric version id, i.e. just some name or string like '2019-3' or whatever, then the string could be nameversion - there would be no reliable way to distinguish the name part from the version part. Even worse, a query language could just be called something like AcmeQL20, and have numeric version ids.
So we are going to have to either have a separate field, or else a delimiter, e.g...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Is DV_PARAGRAPH used?](https://discourse.openehr.org/t/is-dv-paragraph-used/2187)
> Continuing with my checks for classes that are not currently supported by modelling tools (prev. https://discourse.openehr.org/t/is-dv-state-and-its-profile-constraint-c-dv-state-used-anywhere-in-the-specs/2026), I'm not sure at which extent DV_PARAGRAPH is used or if it's even useful. I know the original design was kind of a model for text data analysis, where part of the text could be just free text, and specific terms/concepts could be coded, and the DV_PARAGRAPH acts as a container for...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Small inconsistency in EHR 1.0.2 PDF vs. HTML versions](https://discourse.openehr.org/t/small-inconsistency-in-ehr-1-0-2-pdf-vs-html-versions/2186)
> In the PDF, EHR.system_id is a String, in the HTML version EHR.system_id is a HIER_OBJECT_ID.
It seems at some point in the HTML generation that change was introduced and was also migrated to newer versions of the EHR spec, though there is no change log associated with the change in the type.
Looking at the JSON schemas, it seems that modification was taken there too, so the type is...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Screening archetypes and SNOMED mapping](https://discourse.openehr.org/t/screening-archetypes-and-snomed-mapping/2185)
> What are your thoughts around snomed mappings for e.g. conditions in the screening archetypes?
We are using these archetypes to screen for specific conditions (e.g. diabetes mellitus) that relate to wound healing. It would be nice to do term bindings in the template and to record mappings in the data.
But we found it to risky in the end. Since mapping to the [Diabetes Mellitus...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Medication order - preparation details](https://discourse.openehr.org/t/medication-order-preparation-details/2184)
> We are using the medication order archetype for a use-case related to cystic fibrosis and the ordering of antibiotics. As part of this we are placing one order with a combination of one or more antibiotics. They are understood as one activity (order).
To model this we want to add multiple CLUSTER defining the different antibiotics. Then we found a problem since it's not allowed to have more than one CLUSTER archetype in the SLOT at0143::Preparation details.
Question is: Why is this SLOT...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Hirsutism scales about to be published](https://discourse.openehr.org/t/hirsutism-scales-about-to-be-published/2182)
> Hi everyone,
The archetype *Hirsutism scales* has been through one review round, and there were no major issues. The editorial team suggests publishing.
If you have any comments or objections, please note them here, at the latest in time of the planned publication date, December 17th 2021.
Link to the archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.5800
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Adding Participation to a Cluster - Inspired Oxygen](https://discourse.openehr.org/t/adding-participation-to-a-cluster-inspired-oxygen/2180)
> Hi all,
We have a need to capture Respirations and Inspired Oxygen, but the Inspired Oxygen observation may be captured independently (apparently!). What is the standard pattern in this case? The neatest solution appears to be replicating the Respirations archetype but nulling the data portion, only capturing Inspired O2 and still making use of the `_other_participation:0|name` as per usual.
Thoughts?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [CANCELLED - Real world openEHR - An update on open platforms for healthcare (Wed 15 Dec 2021 at 09:00)](https://discourse.openehr.org/t/cancelled-real-world-openehr-an-update-on-open-platforms-for-healthcare-wed-15-dec-2021-at-09-00/2179)
> Join us at this Apperta Open Platforms Event for updates on how Open Platforms have been implemented across healthcare in the UK. Listen to our speakers experiences of deploying openEHR in real clinical environments, as well as finding out about how the FOXS stack (FHIR, openEHR, IHE XDS and SNOMED CT) can transform e-health delivery. Come and hear what has been going on and have the opportunity to have your questions answered.
Exact content and timings subject to change, speakers will...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Major version updates for archetypes](https://discourse.openehr.org/t/major-version-updates-for-archetypes/2175)
> Hi all,
I've recently started a topic about the process around doing major version updates for archetypes, and I'd love to get some implementer input: https://discourse.openehr.org/t/requirements-for-republishing-published-archetypes/2162
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Example Generator in EHRbase](https://discourse.openehr.org/t/example-generator-in-ehrbase/2174)
> Continuing the discussion from [Software Development Kit for app development](https://discourse.openehr.org/t/software-development-kit-for-app-development/790/38):
Hi @sangeeta.nbose, allow me to give this one its own topic.
An example generator is high on the priority list and should become available early next year. Any particular requirements you have in mind?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Requirements for republishing published archetypes](https://discourse.openehr.org/t/requirements-for-republishing-published-archetypes/2162)
> Already published archetypes sometimes need to be republished, to incorporate a change. We have clear rules for how different levels of changes affect the versioning of the archetype:
* A patch change such as correcting a typo or adding a translation, leads to a 0.0.1 increase in version numbering.
* A minor change, such as the addition of a data element or changing the text of an element without significantly changing its semantics, leads to a 0.1.0 increase in version numbering.
* A major...
**[Issue list](https://discourse.openehr.org/c/issues/76)** - [EHR/DIRECTORY API proposals (Pablo)](https://discourse.openehr.org/t/ehr-directory-api-proposals-pablo/2160)
> The following is an annex from @pablo's conformance documentation for EHR service directory sub-component (i.e. the part of the EHR API for handling EHR.directory). I'm moving this here to get it out of the specification, which should just contain tests for existing API. (@pablo - feel free to modify any way you like).
Annex: proposal for FOLDER API
=============
REF:...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Standard syntax for including Incomplete data?](https://discourse.openehr.org/t/standard-syntax-for-including-incomplete-data/2159)
> I'm looking into how to implement the changes for Incomplete data from [SPECRM-97](https://openehr.atlassian.net/browse/SPECRM-97), and I am not seeing anything in the AQL guides for the specific syntax for including this data in queries. There were a few thread I found with recommendations, but no consensus I saw.
What is the recommended syntax, and should the AQL guide be updated to reflect it?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Help modelling Procedure based on Swedish National Clinical Models](https://discourse.openehr.org/t/help-modelling-procedure-based-on-swedish-national-clinical-models/2157)
> Hi,
I am trying to model some of the elements of Procedure (in the National Clinical Models) in OpenEHR.
Which element in openEHR-HER-ACTION.procedure.v1 can be equal to the following element:
- Purpose 0..* CD_CV : Code from SNOMED-CT << 363675004 Intents (nature of procedure values) (qualifier value). Code to indicate the purpose of the activity. Used in cases where it does not appear from the class' other attributes and there is a special need to document the purpose. Examples of...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Redirect 404'ing link in the white paper](https://discourse.openehr.org/t/redirect-404ing-link-in-the-white-paper/2146)
> Hello!
Just a heads up that the whitepaper contains some links that are 404s. Might be nice for new comers to create a redirect to capture the old link clicks.
```text
FROM: http://www.openehr.org/industry_partners/index
TO: https://openehr.org/community/industry_partners/
SEE: 3 THE openEHR FOUNDATION "There are now around 10 ‘Industry partner’ (financially supporting) vendor companies"
FROM: http://www.openehr.org/who_is_using_openehr/healthcare_providers_and_authorities
TO:...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Generating GraphQL from OPTs](https://discourse.openehr.org/t/generating-graphql-from-opts/2144)
> There was a discussion on how to simplify working with openEHR in the [Separating Models from Implementation](https://discourse.openehr.org/t/separating-models-from-implementation/2093).
I created a generator for GraphQL to find out if this is a viable approach.
I cannot upload ZIP files to Discourse so the [download link and source code](https://neoehr.com/openehr/graphql) are on my site.
- There is a great Java example in the "java-apollo-android" folder.
- Also "graphql.schema.json" for...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Adding HEAD methods to support RM has_*() operations](https://discourse.openehr.org/t/adding-head-methods-to-support-rm-has-operations/2143)
> I am working on REST specifications to support https://openehr.atlassian.net/browse/SPECPR-307.
The idea is to add `HEAD` method, similar to `GET`, to check whether a resource exists, but without returning any content in the body, just http status 200 or 404.
Although I understand the need from SM perspective, described in https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_i_ehr_service_interface, I wonder what is the real value in REST APIs. If `HEAD` returns...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [New Project creation in CKM](https://discourse.openehr.org/t/new-project-creation-in-ckm/2135)
> Hello ,
We , Karkinos Healthcare would like to start a new project in CKM . We are working in oncology domain and would like to share our work and get expert reviews . Kindly guide.
Thanks
Dr Anjali
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Configurable working folders in Archetype Designer](https://discourse.openehr.org/t/configurable-working-folders-in-archetype-designer/2138)
> [quote="borut.fabjan, post:5, topic:1980"]
Small pre-Xmas cookie -
[/quote]
Great @borut.fabjan !
Would it be possible to also make the default template and archetype working-folder(s) (e.g. used for new tempaltes) user-configurable? I believe they are now just thrown into the /local (working) folder and it would be nice to use configurable subfolders for different projects instead of manually moving the files in...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Invariants are not part of the BMM files](https://discourse.openehr.org/t/invariants-are-not-part-of-the-bmm-files/2132)
> I [just learned](https://discourse.openehr.org/t/basic-validity-in-party-related/2129) about the "Invariants" section of the specifications.
I would like to use them when generating solutions based on the BMM specifications.
I know this is probably a big undertaking but can the invariants be added to the BMMs?
[quote="thomas.beale, post:19, topic:1945"]
and the result is that developers easily create data that is semantically invalid, but the ‘model’ doesn’t detect it, so we get garbage in...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Basic_validity in PARTY_RELATED](https://discourse.openehr.org/t/basic-validity-in-party-related/2129)
> Hallo,
take this PARTY_RELATED
```
{
"@class": "PARTY_RELATED",
"relationship": {
"@class": "DV_CODED_TEXT",
"value": "mother",
"defining_code": {
"@class": "CODE_PHRASE",
"terminology_id": {
"@class": "TERMINOLOGY_ID",
...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [ACTION.medication - evaluate effect](https://discourse.openehr.org/t/action-medication-evaluate-effect/2124)
> We are doing some modelling for a solution to follow patients with Cystic fibrosis. They have intensive periodes of antibiotic medication treatment. A part of this is to evaluate the effect of the cure.
Based on microbiological test results the doctor will ordinate some medication. This is given at a outpatient contact. After a few weeks the effect of the medication is evaluated.
The question is: Which careflow step in the archetype should be used for such an action?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [How should deal with Metadata](https://discourse.openehr.org/t/how-should-deal-with-metadata/2119)
> Hi,
I am wondering how can we deal with the Description part (including Details and Authorship) when we are modifying one archetype and also when we are creating a new template?
Is that OK if the original authors and description be replaced with the new one?
**[Issue list](https://discourse.openehr.org/c/issues/76)** - [Why is archetype provisioning included in conformance?](https://discourse.openehr.org/t/why-is-archetype-provisioning-included-in-conformance/2117)
> Not sure if this is the correct coordinate (given github and all forum categories we have) but let me try here first:
Why is the conformance spec including archetype operations? I can understand opt operations, as we've included in the REST API as well, but I'm a bit confused about why uploading/querying archetypes would be necessary.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [OpenAPI schemas generated from BMM files](https://discourse.openehr.org/t/openapi-schemas-generated-from-bmm-files/2116)
> @erik.sundvall [mentioned](https://discourse.openehr.org/t/separating-models-from-implementation/2093/61) that my generator could also generate OpenAPI schemas. I've spent the past few hours writing a generator of OpenAPI schemas from the BMM files.
Please download the generated schemas and report what needs to be fixed:
[Download OpenAPI schemas](https://neoehr.com/openehr/openapi)
I haven't implemented generic classes. Anybody knows how should generic classes be described in...
**[ITS](https://discourse.openehr.org/c/its/41)** - [REST API for creating compositions with id](https://discourse.openehr.org/t/rest-api-for-creating-compositions-with-id/2113)
> The current REST specifications does not seem to support creation of compositions by passing an id (similar to creating ehr with id). Is there any plans to support this feature?
This will be useful in situations when migrating data from one CDR to the other. Creating new compositions ids can have implications as the id may be referenced within and outside the CDR and will all need to be updated.
regards
**[Community](https://discourse.openehr.org/c/community/10)** - [openEHR International Vision](https://discourse.openehr.org/t/openehr-international-vision/2107)
> We're in the process of establishing the Education Program. This requires the adoption of key criteria against which educator and course certification can be evaluated. We all desire an increased uptake of the openEHR IP , the education program plays an important role in assuring that we all deliver the same message. I'd like the openEHR community to participate in the development of a key promotional pitch. This requires us to consider the communities we serve.
The openEHR International...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Support for normal range values for qantity in EHRbase using FLAT format](https://discourse.openehr.org/t/support-for-normal-range-values-for-qantity-in-ehrbase-using-flat-format/2106)
> Does EHRbase support the addition of normal range values for quantity data type, when FLAT Format is used?
Tried using the following, but got error that the server (0.17.3 snapshot) in unable to process the paths.
```
"vital_signs/vital_signs:0/blood_pressure:0/any_event:0/systolic/normal_range|lower": 100,
"vital_signs/vital_signs:0/blood_pressure:0/any_event:0/systolic/normal_range|upper": 140,
```
regards
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Implementing multitenancy in openEHR CDR](https://discourse.openehr.org/t/implementing-multitenancy-in-openehr-cdr/2104)
> Hi, I would like to know the best practices around implementing multitenancy in openEHR CDR. I understand that openEHR natively supports data federation. It would help if the community can point me to Do's and Don'ts kind of practical guidelines. Thank you!
**[GDL editor](https://discourse.openehr.org/c/gdl/77)** - [About the GDL editor category](https://discourse.openehr.org/t/about-the-gdl-editor-category/2102)
> Community support for Cambio [GDL guideline editor tools](https://gdl-lang.org/the-project/guides-tutorials/gdl2/gdl2-editor-primer/).
**[GDL editor](https://discourse.openehr.org/c/gdl/77)** - [Problem when loading a GDL file containing a duration element into the GDL2 editor](https://discourse.openehr.org/t/problem-when-loading-a-gdl-file-containing-a-duration-element-into-the-gdl2-editor/2100)
> Hi everybody,
I get an error message when trying to load a GDL file into the GDL2 editor: *text cannot be parsed to a duration*.
The only duration element that I have in the file is the attribute *chronological age*, of the archetype *openEHR-EHR-OBSERVATION.age.v0*. Therefore, the problem should be in the way that I have set up a rule for this attribute. Here is an example of how I did this:
"$gt0028|Chronological age|>=P60Y"
As I do make use of the ISO8601 notation, I do not understand...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Must a forms runtime app support different AOM/RM releases?](https://discourse.openehr.org/t/must-a-forms-runtime-app-support-different-aom-rm-releases/2099)
> I only have Region Östergötland procurement documents but they don't specify whether their forms runtime app will have to support OPTs with different AOM/RM releases in the same app.
How I imagine a forms app use-case:
- There are specific apps for different user's roles.
- Each app has one or more OPTs that a user can select and enter data for.
It would be great if all the OPTs in the same app would use the same AOM/RM releases. Is this a realistic assumption?
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Which Task Planning release is used in an operational template?](https://discourse.openehr.org/t/which-task-planning-release-is-used-in-an-operational-template/2097)
> OPT2 JSON specifies which AOM and RM release is used:
- "adl_version" : "2.0.6",
- "rm_release" : "1.0.4",
How do we know which Task Planning release is used in an operational template?
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Graphical data mapping tools supporting openEHR?](https://discourse.openehr.org/t/graphical-data-mapping-tools-supporting-openehr/2096)
> Is anybody aware of a commercial or open source solution that in an easy, preferrably graphical, way supports creating readable template-node-name-based mappings from non-openEHR data formats to openEHR formats?
The resulting mapping should be directly usable to do data instance conversion to official openEHR formats (canonical or simplified/flat) e.g. by generating conversion code.
Examples of interesting solutions would be plugins to tools like https://www.altova.com/mapforce...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Separating Models from Implementation](https://discourse.openehr.org/t/separating-models-from-implementation/2093)
> Although OpenEHR is now getting more traction there is a still a considerable learning curve and barrier to adoption. I quick review of other posts suggest it takes at least a year of continual study to gain a good understanding of OpenEHR.
We would all benefit if the models produced by the CKM were much more widely used across the industry. (they should be ubiquitous).
I know first hand from talking to a number of companies and investors that this learning curve is just too steep, and...
**[Issue list](https://discourse.openehr.org/c/issues/76)** - [Feedback about current conformance tests](https://discourse.openehr.org/t/feedback-about-current-conformance-tests/2089)
> Hi everybody.
Duplicate here our email discussion.
On the last call, you talked about feedback on conformance tests.
We analyzed difficulties that we had met in tests run from the "develop" branch of the "EHR base" repository.
And we decided to share with you steps that should be completed to run tests and some of our minds.
1. It seems to us that the base suite setting for easy running is too difficult (URL, login, password, etc):
* suite_settings.robot contains many variables
* some...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Z-scores and percentiles](https://discourse.openehr.org/t/z-scores-and-percentiles/2087)
> [Z-scores, or standard scores](https://en.wikipedia.org/wiki/Standard_score), and [percentiles](https://en.wikipedia.org/wiki/Percentile) are used for a whole range of clinical measurements. We haven't been modelling these into archetypes as of yet, and I'm not sure this would be a good way to represent them, since they're closely bound to each measurement. So this made me think; could Z-scores and percentiles be represented using an additional RM element of the DV_QUANTITY (edit: or maybe...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Which AOM2 release are AWB/Nedap using for exporting OPT2 to JSON?](https://discourse.openehr.org/t/which-aom2-release-are-awb-nedap-using-for-exporting-opt2-to-json/2084)
> Are they using the latest AOM2 release?
The release 2.3.0 has attributes marked as mandatory and they are missing in the JSON I get from AWB:
- [OPERATIONAL_TEMPLATE](https://specifications.openehr.org/releases/AM/latest/AOM2.html#_operational_template_class)
- terminology_extracts (this is optional in the latest release)
But even the latest release has some attributes marked as mandatory that are missing in the JSON:
-...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Not receiving GitHub notifications for the specifications-ITS-BMM repository](https://discourse.openehr.org/t/not-receiving-github-notifications-for-the-specifications-its-bmm-repository/2083)
> I'm not receiving notifications for the [specifications-ITS-BMM repository](https://github.com/openEHR/specifications-ITS-BMM).
I have it set to "All Activity" (like many other openEHR repositories) and this is the only one that doesn't send me notifications.
@sebastian.iancu @pieterbos Did you receive the latest changes @thomas.beale made (last one was 4 days ago)?
There are 11 watchers: https://github.com/openEHR/specifications-ITS-BMM/watchers
Is everybody receiving notifications?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Specifications website usability survey](https://discourse.openehr.org/t/specifications-website-usability-survey/2075)
> Possible initial ideas (notes from SEC call 15 Nov 2021):
* specifications website; move conformance down?
* dev v tool builder flavours?
* SI: integrate specs into integrated page layout - ongoing
* other flavours…
* ask your devs!!!!!
Discuss on Discourse - informal survey on ‘what would you like on the specs site, what’s annoying?'; what order; what docs do you most often use? First time versus experienced use.
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Unnecessary ancestor for AUTHORED_ARCHETYPE](https://discourse.openehr.org/t/unnecessary-ancestor-for-authored-archetype/2073)
> AUTHORED_ARCHETYPE defined in [components/AM/openEHR_am_230.bmm](https://github.com/openEHR/specifications-ITS-BMM/blob/fef7bf1580fc36243b1aa21206811be624dbc88a/components/AM/openEHR_am_230.bmm#L153) has two ancestors:
- ARCHETYPE
- AUTHORED_RESOURCE
```
["AUTHORED_ARCHETYPE"] = (P_BMM_CLASS) <
name = <"AUTHORED_ARCHETYPE">
ancestors = <"ARCHETYPE", "AUTHORED_RESOURCE">
```
However ARCHETYPE already extends AUTHORED_RESOURCE:
```
["ARCHETYPE"] = (P_BMM_CLASS) <
...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Aids and equipment](https://discourse.openehr.org/t/aids-and-equipment/2070)
> Hi all,
We have a use case where we need to record whether a person has any aids or equipment in the context of an urgent care plan. There are two data points: a question with a Yes/No/Don't know answer and a free text box for additional details. I think the equipment recorded here would be mainly mobility or manual handling aids but could cover other types as well, e.g. communication aids. These regularly come up in other anticipatory care planning documents too.
I've looked at the...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Globally unique class names](https://discourse.openehr.org/t/globally-unique-class-names/2068)
> EXPR_TYPE_DEF is specified in two files:
- `components/LANG/Release-1.0.0/openehr_lang_100.bmm`
- `components/BASE/Release-1.0.4/openehr_expression_104.bmm`.
All the other types in "lang_100" have the name "TYPE_abc". Only "EXPR_TYPE_DEF" has the "EXPR_" prefix.
All the types in "expression_104" have the prefix...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [CONTRIBUTION builder supporting collaborative (multi user, multi device) editing? GraphQL? Operational Transformation?](https://discourse.openehr.org/t/contribution-builder-supporting-collaborative-multi-user-multi-device-editing-graphql-operational-transformation/2071)
> This thread is a branch from another GraphQL-related thread:
[quote="erik.sundvall, post:2, topic:1573"]
I’d suggest making something like the “contribution builder” described in part of the same [BMC REST-paper ](https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-13-57) linked above, and make sure that it in addition to the “raw” (verbose) canonical openEHR JSON (and/or XML) format also can use something like the simplified template specific “structured”...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Modularisation vs openEHR monoliths. What would be interesting today?](https://discourse.openehr.org/t/modularisation-vs-openehr-monoliths-what-would-be-interesting-today/2057)
> Data can flow just fine between different openEHR implementations already, e.g. via the [openEHR REST APIs](https://specifications.openehr.org/releases/ITS-REST/). Those APIs also allow frontend and backend to come from different implementations.
But for backend products/deployments the major trend seems to be openEHR **monoliths** presently.
Combining backend modules from different openEHR implementations would be nice for healthcare providers (if implemented well) and also ease the...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Setting up an Archetype Designer repository linked to a private Github repo](https://discourse.openehr.org/t/setting-up-an-archetype-designer-repository-linked-to-a-private-github-repo/2056)
> Hi all
I am trying to manage a Github repo of content models that I would like to keep private for now. It is on our paid for Guthub account, rather than a free account.
I get a 500 error returned when I try and do this, but if I make the Github repo public then AD is quite happy to add it.
Is there anything I can do about this, or do I just need to keep the repo public for now?
Thanks for any advice!
Paul
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Karkinos Healthcare join openEHR as Industry Partners](https://discourse.openehr.org/t/karkinos-healthcare-join-openehr-as-industry-partners/2051)
> We welcome Karkinos Healthcare who have joined openEHR as Gold Industry Partners.
Based in Mumbai City India, Karkinos is a comprehensive oncology platform that provides world class cancer care, whose mission is to provide healthcare solutions where almost no person is deprived of care, for lack of access or affordability.
CEO Mr Venkataramanan Ramachandran said *“We are pleased to be an Industry Partner for the openEHR community. Karkinos has chosen openEHR standard for building our...
**[Issue list](https://discourse.openehr.org/c/issues/76)** - [About the Issue list category](https://discourse.openehr.org/t/about-the-issue-list-category/2050)
> For outstanding issues relating to conformance.
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [DV_INTERVAL of any DV_ORDERED subclass, does it make sense?](https://discourse.openehr.org/t/dv-interval-of-any-dv-ordered-subclass-does-it-make-sense/2049)
> I'm creating test cases for validating different data types and reached the DV_INTERVAL. By the model, we could have DV_INTERVAL which means intervals of DV_ORDINAL, DV_SCALE and DV_PROPORTION are valid, but in modeling tools an implementations I only saw intervals of DV_COUNT, DV_QUANTITY, DV_DURATION, DV_DATE_TIME, DV_DATE and DV_TIME.
Does it make sense to have intervals of ordinal, scale and proportion? Or is just that current implementations lack those types in the interval...
**[Tooling](https://discourse.openehr.org/c/tooling/68)** - [Test case identifiers and text description](https://discourse.openehr.org/t/test-case-identifiers-and-text-description/2039)
> I decided to have a look at the [robot test case files, e.g. here](https://github.com/ehrbase/ehrbase/tree/develop/tests/robot/EHR_SERVICE_TESTS/B.1_CREATE_EHR). I discovered the directories have names like 'B.1_CREATE_EHR' and the files have names like 'B.1__a)_New_EHR.robot'.
In the meta-data documentation I see:
```
*** Settings ***
Metadata Version 0.1.0
Metadata Authors *Wladislaw Wagner*, *Pablo Pazos*
Metadata Created 2019.03.10
Documentation B.1.a) Main flow: Create new EHR
Metadata...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Generating UML diagrams from specifications](https://discourse.openehr.org/t/generating-uml-diagrams-from-specifications/2038)
> I heard @thomas.beale mentioning his wish to have diagrams generated directly from the computable specifications. This might enable him to skip using UML tools that he doesn't like.
I've created a simple UML diagram generator and browser.
Sample class with enum:
Larger diagram:
You can also create your own custom diagrams:
(Recreation of ["The Archetype...
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [About the Roadmap category](https://discourse.openehr.org/t/about-the-roadmap-category/2030)
> (Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)
Use the following paragraphs for a longer description, or to establish category guidelines or rules:
- Why should people use this category? What is it for?
- How exactly is this different than the other categories we already have?
- What should topics in this category generally contain?
- Do we need this category?...
**[Conformance](https://discourse.openehr.org/c/conformance/73)** - [About the Conformance category](https://discourse.openehr.org/t/about-the-conformance-category/2029)
> Topics relating to conformance and product certification.
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [EVENT found in Task Planning and RM](https://discourse.openehr.org/t/event-found-in-task-planning-and-rm/2027)
> I'm trying to use Task Planning Release 1.6.0 (and latest) with RM 1.1.0 (and latest).
An EVENT is found in Task Planning ([1.6.0](https://github.com/openEHR/specifications-ITS-BMM/blob/da24e52dfc6cc890a8e8646671173d0241f135b6/components/PROC/Release-1.6.0/openehr_proc_task_planning_latest.bmm#L1218) and [latest](https://github.com/openEHR/specifications-ITS-BMM/blob/da24e52dfc6cc890a8e8646671173d0241f135b6/components/PROC/latest/openehr_proc_task_planning_latest.bmm#L1217)) and in RM...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Is DV_STATE and it's profile constraint C_DV_STATE used anywhere in the specs?](https://discourse.openehr.org/t/is-dv-state-and-its-profile-constraint-c-dv-state-used-anywhere-in-the-specs/2026)
> I'm working in the Conformance Testing Specification, in the section for data validation. This includes creating test cases for each data type and to express cases considering different constraints from AOM and AOP.
For DV_STATE, it seems that is not used anywhere in the RM, and testing the Archetype Editor and LinkEHR Editor, it doesn't seem to be possible to create a constraint definition in an archetype for DV_STATE, which has a specific C_DV_STATE in the AOP...
**[Tooling](https://discourse.openehr.org/c/tooling/68)** - [Conformance to CKM models?](https://discourse.openehr.org/t/conformance-to-ckm-models/2021)
> Hi all,
Following on from some recent discussions about reuse of the CKM published models, I'm curious about whether we can explore conformance to the CKM published archetypes...
1. Would vendors consider making public which archetypes they use? eg by some way of marking their use on CKM. This could be construed as endorsement for some models (and good from a CKM POV) . In addition, using lots of the models may be seen as a marketing advantage to the vendor. Obviously if not reusing many of...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [TNM codes being withdrawn from SNOMED CT](https://discourse.openehr.org/t/tnm-codes-being-withdrawn-from-snomed-ct/2017)
> From another list
> As a result of a licensing issue between AJCC and SNOMED International, all TNM cancer staging codes will shortly be removed from the next version of the International Edition of SNOMED and, therefore, will in time also be removed from the version of SNOMED that is distributed within the UK.
>
> The TNM cancer staging system has always been the intellectual property of AJCC/UICC and is now on version 9. About 20 years ago, AJCC permitted SNOMED to add around 1000 codes...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Semi structured narrative data](https://discourse.openehr.org/t/semi-structured-narrative-data/2007)
> A lot of our clinical data is in narrative reports form. Let's say for EVALUATION.clinical_synopsis.synopsis there's a DV_TEXT that contains a paragraph of text where some words in an individual sentence could be mapped to e.g. SNOMED.
e.g. :The patient has shown signs of dysuria(http://snomedct.info/id/ 49650001>) warranting a urinary sediment to exclude a UTI (http://snomedct.info/id/68566005>). "
Currently it's only possible to map the entire DV_TEXT to a code system like SNOMED. The...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Where to find AOM2 BMM for the latest stable release (2.3.0)](https://discourse.openehr.org/t/where-to-find-aom2-bmm-for-the-latest-stable-release-2-3-0/2006)
> OPT2 JSON files generated from Nedap's VSCode extension are using the [latest AOM2 release 2.3.0](https://specifications.openehr.org/releases/AM/latest/AOM2.html). This is a Stable release.
@pieterbos has generated an AOM2 BMM file for release 2.0.6 which I'm currently using (it is 5+ years old release).
It would be great to have all stable BMM files in the [ITS-BMM repository](https://github.com/openEHR/specifications-ITS-BMM/tree/master/components). @thomas.beale offered to write the...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic openEHR Collaboration Meeting December 2021](https://discourse.openehr.org/t/nordic-openehr-collaboration-meeting-december-2021/2004)
> **Purpose of meeting**
Connect with the Nordic openEHR community to explore ways of collaborating towards common goals related to the use of openEHR.
**When and where**
Thursday December 9th 13.00-15.00 CET, Online
**How to join**
Contact Mikael Nyström (mikael.nystrom@cambio.se)
Feel free to spread the invite to your openEHR network
**Agenda (tentative)**
* Welcome and introductions, @mikael
* Implementation guides
* Access points e.g. cvc and pvc, @elham2222
* [Informationsdesign...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Different types for TRANSLATION_DETAILS.language in XSD and BMM for OPT 1.4](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003)
> [XML Schemas for OPT 1.4](https://specifications.openehr.org/releases/ITS-XML/latest/components/AM/Release-1.4/) specify TRANSLATION_DETAILS in the [Resource.xsd](https://specifications.openehr.org/releases/ITS-XML/latest/components/AM/Release-1.4/Resource.xsd).
TRANSLATION_DETAILS.language is specified as type CODE_PHRASE in XSD but it has type TERMINOLOGY_CODE in...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Decision Language specification questions](https://discourse.openehr.org/t/decision-language-specification-questions/2001)
> Good afternoon.
I am reading the Decision Language specifications and I have a few questions.
Is the DLM model concrete package related to the subject proxy? If so, how are they related? Especially for tracked variables and quantitative variables, since the proxy service takes currency and quantity of variables into account.
Should variable calls be done in the input section or only in the data binding section? In case a DLM uses data binding to external sources (non-subject-oriented).
Thank...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Coding element and event names](https://discourse.openehr.org/t/coding-element-and-event-names/1998)
> In a lot of cases, it would be useful to be able to code the names of elements and events, when creating templates (and possibly also archetypes). If I understand it correctly, element and event names are of the DV_TEXT data type, which we should be able to specialise to DV_CODED_TEXT. How do we do this?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Dual Diagnosis Screening Instrument (DDSI)](https://discourse.openehr.org/t/dual-diagnosis-screening-instrument-ddsi/1997)
> Got some interest in a solution for an instrument used in abuse and psychiatry today. This instrument was developed and is owned by an organisation in Barcelona.
The English name seems to be : Dual Diagnosis Screening Instrument (DDSI)
Anyone who have #openehr experiences with this? I.e have modelled an archetype?
We will look into it the following weeks.
Some background information : https://www.karger.com/Article/Abstract/351519
**[openEHR & standards](https://discourse.openehr.org/c/standards/69)** - [US Core Data Interop models (USCDI)](https://discourse.openehr.org/t/us-core-data-interop-models-uscdi/1996)
> For those in the community wondering what the US does for 'clinical modelling', here is one effort that is currently running - [USCDI](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi#uscdi-v2), under the auspices of the US Gov ISA (Interoperability Standards Advisory).
It varies between the basic (what we would consider 'reference model') e.g. [Encounter information](https://www.healthit.gov/isa/uscdi-data-class/encounter-information), to various kinds of...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Can POST /directory have an empty body?](https://discourse.openehr.org/t/can-post-directory-have-an-empty-body/1994)
> The POST /directory doesn't specify if the body can be empty.
https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/ehr.html#directory-directory-post
Testing EHRBASE it seems the current implementation requires the body of the request to be non empty.
IMO creating an empty ehr.directory is totally valid. What do others think?
Maybe this should be clarified in the REST API specs.
**[ITS](https://discourse.openehr.org/c/its/41)** - [Is the version_at_time parameter value on the REST API valid when ste in the future?](https://discourse.openehr.org/t/is-the-version-at-time-parameter-value-on-the-rest-api-valid-when-ste-in-the-future/1993)
> There are a couple of endpoints that accept `version_at_time`, like:
- GET composition https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/ehr.html#composition-composition-get-1
- GET directory https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/ehr.html#directory-directory-get-1
I'm executing some test cases for EHRBASE and it seems to work when sending a datetime in the future, but is that semantically valid? Should this case be validated and return an...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Validating against RM schemas in the REST API](https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992)
> How are we handling differences in API request / response payloads to the schemas for canonical JSON and XML?
Some payloads won't validate against the schemas, for instance, missing contribution.uid on POST /contribution, or contribution.versions being a list of VERSION (API schema) instead of OBJECT_REF (RM schema).
Note in the case of the missing fields, like uids, that can be handled by a relaxed schema setting that as optional, but in the case of the OBJECT_REF to VERSION resolution,...
**[Education](https://discourse.openehr.org/c/education/88)** - [Training, education, essential learning for openEHR](https://discourse.openehr.org/t/training-education-essential-learning-for-openehr/1989)
> Hi all
We are looking at options for training our NHS Scotland team of around 60 people (and growing) on openEHR. We have met with @Hanna_Pohjonen a couple of times and really like her material, but to decide what to do next we need to have a better idea of what else is available, if anything.
Asynchronous learning offerings at the moment seem to be very few (only one structured program), and in general learning about openEHR for newbies can be very challenging without some help. You...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [ADL 1.4 embedded ODIN versus ODIN](https://discourse.openehr.org/t/adl-1-4-embedded-odin-versus-odin/1987)
> I'm working on an improved set of Antlr4 grammars, including for ADL 1.4. These are modal grammars, which provide much better ability to deal with changing syntaxes.
So an example of what we can find in an ADL 1.4. archetype is this:
```
ELEMENT[at0002] occurrences matches {0..1} matches { -- X offset
value matches {
C_DV_QUANTITY <
property = <[openehr::122]>
>
DV_COUNT matches {
magnitude matches {|>=0|}
}
}
}
```
Here we have a block of ODIN inline within...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Svensk tillämpning av Setting](https://discourse.openehr.org/t/svensk-tillampning-av-setting/1985)
> I samband med PDL-arbetet noterade vi en sak som inte påverkas av PDL men som vi ändå vi bör hitta en enhetlig svensk tillämpning av: det obligatoriska fältet "setting" i EVENT_CONTEXT, se markering i bild
Bild från https://specifications.openehr.org/releases/RM/Release-1.1.0/ehr.html#_composition_package kapitel 5.
Terminologiurvalet för detta nämns i [Support Terminology...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Create New EHR using Postman - Rest Services](https://discourse.openehr.org/t/create-new-ehr-using-postman-rest-services/1982)
> I am using below URL using POST method to create new EHR using Postman
http://HOST:8080/ehrbase/rest/openehr/v1/ehr
Error Response:
**{**
** "timestamp": "2021-10-25T20:21:56.827+00:00",**
** "status": 500,**
** "error": "Internal Server Error",**
** "path": "/ehrbase/rest/openehr/v1/ehr"**
**}**
**Server side log having below exception:**
{"log":"2021-10-25 20:21:56.822 ERROR 10 --- [nio-8080-exec-3] o.a.c.c.C.[.[.[.[dispatcherServlet] : Servlet.service() for servlet...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [How to use the "Symptom/sign screening questionnaire" archetype](https://discourse.openehr.org/t/how-to-use-the-symptom-sign-screening-questionnaire-archetype/1984)
> In a questionnaire there are often questions directed to the patient like "Do you experience fatigue that affects your daily life?" where do we put those questions to make the lives of form authors easier?
I gusess the “Symptom or sign name” should be saved for shorter descriptioins that the reader of an EHR prefers, e.g. "Fatigue" (including underlying code).
Our current candidate "hack" we are experimenting with is to rename the "Specific symptom/sign" cluster structure to contain the...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Bug when saving to Github Branches with Archetype Designer](https://discourse.openehr.org/t/bug-when-saving-to-github-branches-with-archetype-designer/1980)
> Hi!
Archetype designer seems to have a bug when trying to save templates in branches for Github repositories. Opening a branch (for example our [project/MBA](https://github.com/kardapp/CKM-mirror/tree/project/MBA) branch of [Karolinska's CKM-mirror fork](https://github.com/kardapp/CKM-mirror)) and **reading** the files from it work fine, but when **saving** a template it gets comitted to the `master` branch instead of the `project/MBA` branch. This of course confuses the application (and...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Is unbinded constraint code valid in archetypes / templates?](https://discourse.openehr.org/t/is-unbinded-constraint-code-valid-in-archetypes-templates/1976)
> I'm working in the HiGHmed conformance test framework data sets. One of the templates we use as an example is the RIPPLE conformance template. This template has some issues, some might come from missing checks on modeling tools, like the is_integral function appearing as an attribute constraint for DV_PROPORTION.
Another issue is a DV_CODED_TEXT has a constraint code ac0001 but that doesn't have a definition/binding to any terminology.
My question is if that is even valid?
IMO that...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Adding to the DV_QUANTITY units options](https://discourse.openehr.org/t/adding-to-the-dv-quantity-units-options/1964)
> @borut.fabjan et al,
Is there a recommended way that we can add to the DV_QUANTITY units list so that it can be included in updates. Personally, I've hacked the ADL on multiple occasions but this is clearly not ideal and it isn't there next time I or others need it...
Triggered by @JonJones question... https://discourse.openehr.org/t/medication-amounts-and-units/1935/4
The Gray is an SI unit, defined as the absorption of one joule of radiation energy per kilogram of matter. In the...
**[GDL editor](https://discourse.openehr.org/c/gdl/77)** - [GDL2 editor: problem when creating a guideline with the same archetype instantiated twice as output variable](https://discourse.openehr.org/t/gdl2-editor-problem-when-creating-a-guideline-with-the-same-archetype-instantiated-twice-as-output-variable/1958)
> We are trying to use the GDL2 editor to create some guidelines with recommendations. To create a rule with two *topic* and *recommendation* elements as the output, we instantiated the archetype openEHR-EHR-EVALUATION.recommendation.v2 with those elements, twice.
In the GDL syntax, indeed different gt numbers were generated for each seperately instantiated topic and reccomendation (gt0011, gt0012, gt0026, gt0027 in red, image below).
However, when executing a test case where this rule...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Question to vendors](https://discourse.openehr.org/t/question-to-vendors/1957)
> Hi all,
As a CKA, I'm always pleased to see the archetypes that we develop as a community welcomed and used within systems.
However, there seems to be a significant mismatch between the relatively small number of high value, core reusable archetypes (my bias :sunglasses:) that have gone through the publication process. There must be many more vendor-developed archetypes that have enabled sophisticated clinical functionality to be built into their systems.
Is there a reason why they are not...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Conflicting specifications in Archie's BuiltinReferenceModels class](https://discourse.openehr.org/t/conflicting-specifications-in-archies-builtinreferencemodels-class/1954)
> In Archie there is a list of specifications in [class BuiltinReferenceModels](https://github.com/openEHR/archie/blob/16043403993e010a9952b7770e6363aef6c241a7/referencemodels/src/main/java/org/openehr/referencemodels/BuiltinReferenceModels.java#L42) from which the repository is built.
I used this list to build a repository in my implementation (which is using Dart language).
I get errors due to the conflicting definition of the `EVENT` type. It is defined as a `SimpleType`...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Operating Theatre Models and Templates](https://discourse.openehr.org/t/operating-theatre-models-and-templates/1951)
> Tentatively exploring the potential of operating theatre data in openEHR. Has anyone done work in this space recently or even starting building an electronic op note template? I can see the basic archetypes in there already so it should be doable. Action archetypes for booking status would also be feasible. Not sure how the theatre timings would manifest though - status = Procedure Start is easy...but the myriad of specialty specific differences could prove tricky!
**[OHDSI OMOP](https://discourse.openehr.org/c/omop/103)** - [OMOP and openEHR](https://discourse.openehr.org/t/omop-and-openehr/1948)
> Today we had a SEC meeting presenting some examples on the mapping from openEHR to OMOP CDM. I attach the slides so we can have a broader discussion as a community.
[openEHRtoOMOP.pptx|attachment](upload://ns0kR6AzFHOMk8LekfkElUAqeXI.pptx) (802.8 KB)
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Patient alert archetypes](https://discourse.openehr.org/t/patient-alert-archetypes/1947)
> Hi!
I remember seeing an evaluation (openEHR-EHR-EVALUATION.alert.v1) and composition (openEHR-EHR-COMPOSITION.alerts_list.v0) archetypes for patient alerts on CKM, which I cannot find both anymore, although I have them saved on my computer.
I did some research on them before and decided to use them in the future (now :slight_smile: ) in order to keep compliant with the archetypes on CKM.
What is the reason for the removal of these archetypes?
Are there any substitutes? I see there's an...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Why is value not optional for DvCodedText](https://discourse.openehr.org/t/why-is-value-not-optional-for-dvcodedtext/1945)
> In FHIR the display for a coding is actually optional, which i think is not a bad idea. Im currently mapping those and just asked myself why the *value* for [DvCodedText](https://specifications.openehr.org/releases/UML/latest/index.html#Architecture___18_1_83e026d_1433773263943_52183_5909) is mandatory.
In the end the *value* does only add optional information to the DvCodedText, important and mandatory in the end are the system and the code.
Surely the *value* is especially important to an...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Which archetype could be used to parse and store blood testing data?](https://discourse.openehr.org/t/which-archetype-could-be-used-to-parse-and-store-blood-testing-data/1944)
> I'm a newcomer to OpenEHR. After read the [Architecture Overview](https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html), I found it is still difficult to find a way to store my data.
For example, I have the following data piece.
The data is about test result of blood, and is used to help doctors to do diagnosing related liver functions.
I searched in the CKM repositories, and the only archetype...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Collaboration between programs and tooling vendors](https://discourse.openehr.org/t/collaboration-between-programs-and-tooling-vendors/1942)
> Dear colleagues,
As a CKA, I often feel I operate in a vacuum and it is only by accident that I find out about decisions made by the specs community or updates to the modelling tools I use.
One of the benefits that we promote about openEHR is that clinicians are able to participate in building the archetypes, while the software engineers focus on the specs. And while that separation works well to a point, what both technical and clinical groups miss out on is the richness that comes from...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [Unable to access Better EHR Studio](https://discourse.openehr.org/t/unable-to-access-better-ehr-studio/1939)
> has anyone else been unable to access Better Studio today?
Keisha
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Standardised API for custom GUI-widgets for openEHR-based form editors & renderers?](https://discourse.openehr.org/t/standardised-api-for-custom-gui-widgets-for-openehr-based-form-editors-renderers/1936)
> Most openEHR platform/tooling suppliers with form creation/editing and other GUI-building support will likely need a way for customers to add their own extra custom widgets to forms and some other views - widgets that are not included "in the box" from the platform/product.
I believe at least Better, Cambio, Solit Clouds, Code24 and likely DIPS have thoughts about custom extra widget import or library/store functions, but not neccesarily compatible approaches (yet).
An example of this is...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Medication amounts and units](https://discourse.openehr.org/t/medication-amounts-and-units/1935)
> We should maybe revisit the current modelling patterns for medication amounts and their units. Currently, we have amounts expressed as a DV_QUANTIY with units constrained to '1', and an additional DV_TEXT element for the unit. This undermines the DV_QUANTITY data type, and doesn't work particularly well when using form builders. This pattern is currently used in these archetypes (that I can find):
* [INSTRUCTION.medication_order.v2](https://ckm.openehr.org/ckm/archetypes/1013.1.3124)
*...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [Node name mappings in EHRBase](https://discourse.openehr.org/t/node-name-mappings-in-ehrbase/1930)
> Hello!
Following [this discussion](https://discourse.openehr.org/t/coding-archetype-concepts-and-nodes-using-terminology/347/4) I tried to add a mapping to a node name in a composition and post it to EHRbase (the "archetype_node_id": "at0019" in the snippet below). I had no errors in the upload, but after retrieving the composition through a GET call this part disappeared and it is unreachable even using specific queries. Does EHRBase support TERM_MAPPINGS or am I missing something? If not,...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Obsolete status for care plan composition archetype](https://discourse.openehr.org/t/obsolete-status-for-care-plan-composition-archetype/1927)
> Care plans in our software undergo a lifecycle from, draft -> active -> archived.
where draft -> active depend on stuff like, completeness and sometimes attestation (by other care giver and/or client). And active -> archived usually is caused by changes in the clinical situation, that lead to a new version of the care plan, usually duplicated from the old one, where the old one is 'archived'.
I know there is a lifecycle state for a versioned object. That has an incomplete status which...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Notifications don't seem to be quite right](https://discourse.openehr.org/t/notifications-dont-seem-to-be-quite-right/1925)
> I've noticed that I've missed quite a bit of interesting content in topics that I have participated in, simply being unaware that someone else has replied in that topic.
I've sorted that for myself via [https://discourse.openehr.org/my/preferences/notifications](https://discourse.openehr.org/my/preferences/notifications)
You might want to change the default setting to watching to help that for all your...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Audience specific problem name](https://discourse.openehr.org/t/audience-specific-problem-name/1924)
> Is there anyone with experience on giving a ["Problem/Diagnosis name"] (https://ckm.openehr.org/ckm/archetypes/1013.1.169) multiple names? Where different users see different names in the user interface for the same problem. E.g. nurse sees "broken ankle" in the care plan, while the surgeon see "Weber B ankle fracture" in the treatment plan. But we want to record only one instance of the problem diagnosis archetype.
I know it's possible to record multiple Problem/Diagnosis names, but how do I...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Is terminology_id=local compatible to not specifying a code list in the archetype?](https://discourse.openehr.org/t/is-terminology-id-local-compatible-to-not-specifying-a-code-list-in-the-archetype/1921)
> In the conformance tests data sets I created, I have an OPT with an ELEMENT.value = DV_CODED_TEXT in which the terminology_id = local but there is no code list specified.
Since that is specified in an archetype and wasn't constrained any more, this ends up in the OPT. And when I commit a COMPOSITION complying with that OPT I get a validation error, I guess from Archie, in EHRBASE, because the code specified, which is autogenerated, doesn't match the DV_CODED_TEXT.value. I guess it is looking...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [IN2 Ingenieria de la Informacion, S.L. - join as Industry Partners](https://discourse.openehr.org/t/in2-ingenieria-de-la-informacion-s-l-join-as-industry-partners/1916)
> We are pleased to annouce that [IN2](https://www.in2.es/en/we-in2/) have joined openEHR as Industry Partners.
A technology consultant company, created in 1994, with more than 20-years experience in the health sector. Experts in the development and implementation of solutions based on Open Source technologies that help its customers in their digital transformation process.
José Luis Jorge, Director of Business Unit at IN2 ***"believes that openEHR will be a key asset for our...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [The correct archetype to use for radiotherapy contouring and planning](https://discourse.openehr.org/t/the-correct-archetype-to-use-for-radiotherapy-contouring-and-planning/1912)
> Hello, our group has been discussing what is the correct archetype to describe the completed action of radiotherapy contouring (the process of delineating organs and other structures on radiological images for dose delivery and avoidance purposes) and treatment planning.
Specifically, we have been interested in whether the openEHR-EHR-ACTION.procedure.v1 archetype is the correct one to record information on what structures were contoured and by whom.
Arguments in favor:
* The Purpose...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [ISO 639 language codes](https://discourse.openehr.org/t/iso-639-language-codes/1910)
> Currently we use ISO 639-1 codes to specify languages in archetypes. This works fine for most major languages. We may at some point in the future need to be able to tell the difference between several different Sámi languages of which one exists in ISO-639-1 (se/sme), and two only in ISO 639-2 and -3 (sma, smj).
Is it valid to use ISO-639-2 or -3 in archetypes today? If not, are there any plans to extend the specs to include them?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Multi-tenancy support in EHRBase](https://discourse.openehr.org/t/multi-tenancy-support-in-ehrbase/1906)
> Hi,
Is there a plan to support multi-tenancy in EHRbase?
regards
Dileep
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR and FHIR - Friends or Foes?](https://discourse.openehr.org/t/openehr-and-fhir-friends-or-foes/1905)
> Dear community members,
I kindly like to invite you to our next HiGHmed Symposium on October 14. There is often some confusion about the scope and roles of openEHR and FHIR to build an open and interoperable platform ecosystem in healthcare. Hence, we aim to answer the question "openEHR and FHIR - Friends or Foes?"
We got a fantastic speaker line-up from leading European organizations presenting their cases and views on the topic.
[Erik...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Landsteiner ABO group archetype](https://discourse.openehr.org/t/landsteiner-abo-group-archetype/1896)
> I searched CKM for [ABO blood group](https://en.wikipedia.org/wiki/ABO_blood_group_system), to see if anyone has any archetypes for recording a patient's ABO group and Rhesus status.
This was all I found:
[https://ckm.apperta.org/ckm/archetypes/1051.32.493](https://ckm.apperta.org/ckm/archetypes/1051.32.493)
It doesn't seem to sit naturally as a lab investigation because:
* It's usually done by a separate "branch" of lab medicine (BTS)
* It's used to plan therapy but doesn't have the concept...
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Where do I put patient data in an openehr-based CDR?](https://discourse.openehr.org/t/where-do-i-put-patient-data-in-an-openehr-based-cdr/1894)
> Hello community,
I am trying to develop an ordered CDR. In order to have the patient data sorted and complete, where is it better to add patient data (name, address, phone...) in a CDR based on OpenEHR? Is it better to create a composition with this data? If so, is there any template related to this?
Thank you very much for everything.
Best regards
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Modelling question - what's the best practice?](https://discourse.openehr.org/t/modelling-question-whats-the-best-practice/1893)
> Hi all , I am trying to modelling the following document for Systemic Lupus Erythematosus Disease Activity Index (SLEDAI) - http://www.sledai-2k.com/sledai2k.pdf
But I am in doubt what should be the best modelling approach for this case. I had a talk with @ian.mcnicoll and already found 3 different ways to make the same thing, but I don't know exactly what should be the best or if there are some modelling patterns/styles for this case.
In the following links you can see the 2 archetypes...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [ASA physical status classification system - ready for publication](https://discourse.openehr.org/t/asa-physical-status-classification-system-ready-for-publication/1878)
> Hi everyone,
The archetype *ASA physical status classification system* has been through one review round, and there were no major issues. The editorial team suggests publishing.
If you have any comments or objections, please note them here, at the latest in time of the planned publication date, September 29th 2021.
Link to the archetype: [ASA physical status classification system](https://ckm.openehr.org/ckm/archetypes/1013.1.1336)
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [openEHR grammar generalities](https://discourse.openehr.org/t/openehr-grammar-generalities/1875)
> Following @pablo 's recent post on Terminology Ids, I was having a look at some really basic things, including definitions for Integer, which appear in versions as well as numbers and parts of Reals/floats etc.
We currently define it as follows:
```
INTEGER: DIGIT+ ;
```
But that allows zero-filled integers, which are at least weird, if not usually some sort of stringified 0-filled integer..
I had a look at Kotlin (just picking on a 'modern' language), and it has:
```
IntegerLiteral
:...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Discussions about archetypes, where to have them?](https://discourse.openehr.org/t/discussions-about-archetypes-where-to-have-them/1872)
> Currently we have two parallel places to have persistent (as opposed to the more fleeting chat of the Slack site) discussions about archetypes;
* here on Discourse
* in the CKM, either under each archetype or for the site as a whole
I think this separation makes it harder both to participate in and to relocate discussions. Would it be better if we chose one or the other?
PS! I'm not thinking about the change request functionality of the CKM. I think that has its own purpose in addition to...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Revisiting medication summary / screening](https://discourse.openehr.org/t/revisiting-medication-summary-screening/1869)
> I wonder if there is case for rationalising the current Medication summary archetype and Medication screening. THe use case we have from Wales, for a couple of different projects looks very like Summary - including episodic use but also aspects of screening particularly the 'overall use 'type status.
This is the specialised archetype we are currently using.
https://tools.openehr.org/designer/#/viewer/shared/Pz9zaGFyZWRJZD0xJDQ3NjAxNzk4ZDY4NDQ0YWE4YTJkOTYwN2IwMmUwNWM0
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Revisiting symptom/sign](https://discourse.openehr.org/t/revisiting-symptom-sign/1867)
> The current [Symptom/sign](https://ckm.openehr.org/ckm/archetypes/1013.1.195) archetype was first published in October 2015 following a seven month review process.
Since then the archetype has had several breaking changes applied, and has been sitting in the 'Reassess' state since April 2018.
The COVID-19 related work of early 2020 led to the creation of the new 'screening questionnaire' family of archetypes, of which [Symptom/sign screening...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Correct format for /composer/external_ref in FLAT compositions](https://discourse.openehr.org/t/correct-format-for-composer-external-ref-in-flat-compositions/1858)
> EHRBase 0.17.2 gives the following error if /composer/external_ref not given in FLAT compositions.
` "error": "java.lang.IllegalArgumentException: Message at /namespace (/composer/external_ref/namespace): Attribute namespace of class PARTY_REF does not match existence 1..1\nMessage at /scheme (/composer/external_ref/id/scheme): Attribute scheme of class GENERIC_ID does not match existence 1..1\nMessage at /value (/composer/external_ref/id/value): Attribute value of class GENERIC_ID...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Revisiting adverse reactions](https://discourse.openehr.org/t/revisiting-adverse-reactions/1855)
> The current [Adverse reaction risk](https://ckm.openehr.org/ckm/archetypes/1013.1.1713) archetype was first published in March 2016 after a lengthy modelling and review process detailed in [this blog post](https://omowizard.wordpress.com/2016/03/06/adverse-reaction-risk-the-provenance/) by @heather.leslie.
The Adverse reaction risk archetype was always intended to be used for recording the positive presence of a general propensity to react badly to specific substances or groups of...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [(in)Valid TERMINOLOGY_IDs in templates](https://discourse.openehr.org/t/in-valid-terminology-ids-in-templates/1853)
> Because of HiGHmed there are a lot of new templates out there in German, which includes all sorts of strange characters in template ids and terminology ids.
While doing some tests for EHRBASE, I have found this template https://ckm.highmed.org/ckm/templates/1246.169.620 which uses "§21 KHEntgG" as a terminology_id for coded text constraints.
Looking at the base spec, there is actually a grammar there saying how the terminology_id values should be constructed...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Error While posting composition](https://discourse.openehr.org/t/error-while-posting-composition/1852)
> 
I am receiving this error while posting the composiiton to ehrbase server
I have posted the template first , created a blank ehr with ehr ID from OPT and I put the same EHR ID in the params while posting
**[Roadmap](https://discourse.openehr.org/c/roadmap/74)** - [Conformance roadmap 2021](https://discourse.openehr.org/t/conformance-roadmap-2021/1851)
> [this post is a wiki, you can modify directly if desired]
Discussion thread for approaching formal conformance specifications, tools, test environments etc. **The openEHR board has agreed to formally support a conformance project that will result in some conformance testing capability by Nov/Dec 2021, in order to support increasing procurement activities**. It also wants a roadmap for work in 2022.
Goals
---------
* **enabling procuring orgs to be provided 'standard' (comprehensible)...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Change UI and reflect the change on Backend](https://discourse.openehr.org/t/change-ui-and-reflect-the-change-on-backend/1847)
> I already have a UI made but I want to add :
1) Adhaar Card No.
2) Name
3) Mobile No.
Fields to the form.
How do I reflect the same on the backend
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Revised AQL modular grammar?](https://discourse.openehr.org/t/revised-aql-modular-grammar/1844)
> All,
Please read [this post on new Antlr4 grammars for openEHR](https://discourse.openehr.org/t/new-antlr4-grammars-for-openehr/1843) for background.
This post is for everyone, but particularly for @sebastian.iancu , @Teun , @pieterbos , @christian , @michael.boeckers , as listed on the AQL grammar authors/contribs list.
I have added AQL to the set of grammars, with the idea of making it re-use common lexer and rule sub-grammars from the main set, which includes ADL, CADL, ODIN, EL and...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [New Antlr4 grammars for openEHR](https://discourse.openehr.org/t/new-antlr4-grammars-for-openehr/1843)
> All,
I have been working on a new set of Antlr4 grammars for openEHR, starting with ADL2, CADL, ODIN, Expressions, and now looking at AQL. They are [here in a public repo in my home area for now](https://github.com/wolandscat/openEHR-antlr4), and contain sufficient initial Java code and tests to run syntax tests on any of these languages. You can find the grammars and everything else [right here in Github](https://github.com/wolandscat/openEHR-antlr4/tree/master/combined/src/main).
The aims...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Unable to save composition using EHRBase SDK](https://discourse.openehr.org/t/unable-to-save-composition-using-ehrbase-sdk/1841)
> Hi...I'm new to openEHR implementation. I'm able to work with compositions using Flat format and REST APIs.
Now I'm trying to work with EHRBase SDK.
I'm able to successfully do the following from the OPT file using the SDK's generator:
a) Generate the java entity objects .
b) Create a template (using the REST API Endpoint)
c) Create empty EHR (that returns ehrid)
d) Populate the java entity objects with data from the client application.
However, I'm facing issues while trying to...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Erfarenheter från Open Source produkter för openEHR - t.ex. EHRbase och Medblocks](https://discourse.openehr.org/t/erfarenheter-fran-open-source-produkter-for-openehr-t-ex-ehrbase-och-medblocks/1840)
> Hej!
Det verkar som att det är flera svensk/skandinavisk-talande som testar [EHRbase](https://ehrbase.org/) och andra openEHR-lösningar baserade på öppen källkod. Ni som vill får gärna ge er till känna i denna tråd så kanske vi kan underlätta lite erfarenhetsutbyten, tankar och kanske något lagom tekniknördigt onlinemöte någon gång. Var inte blyga, det är spännande att höra även om initialt utforskande/labbande och tillhörande problem+lösningar.
Själv känner jag till bl.a. att
- @Sebastian...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Clinical Modelling Program - Heather Leslie](https://discourse.openehr.org/t/clinical-modelling-program-heather-leslie/1837)
> Dear openEHR Community
Many of you will know Heather Leslie and the tremendous work she does with openEHR individually and as co-lead of the openEHR Clinical Modelling Program.
After 14 years, Heather has decided to resign as Clinical Modelling Program co-lead, but will remain an advocate of openEHR continuing to give her support as a clinical knowledge administrator.
Silje Ljosland Bakke will become the sole clinical lead for the time being, but the openEHR International Board are looking...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Hypersensitivity examination, Results](https://discourse.openehr.org/t/hypersensitivity-examination-results/1836)
> Is there an existing archetype that expresses Hypersensitivity examination? How are test results, as part of an Hypersensitivity examination, expressed, such as results of elimination test of food, results of provocation test and results of skin prick-test? Is there any specific archetype that expresses information about the results of food elimination test, results of provocation test and results of skin prick?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Radiation therapy, planing and result](https://discourse.openehr.org/t/radiation-therapy-planing-and-result/1835)
> Is there any archetype that expresses information about Microscopic tumor volume, Planned target volume and Clinical target volume for radiation therapy?
**[Resources](https://discourse.openehr.org/c/resources/71)** - [What is an archetype?](https://discourse.openehr.org/t/what-is-an-archetype/1826)
> An archetype is a domain level model of data points and data groups relating to a topic. See the [Archetype specifications page](https://specifications.openehr.org/releases/AM/latest) for a technical description and specifications. The [Archetype Technology Overview](https://specifications.openehr.org/releases/AM/latest/Overview.html) is useful for a business level overview.
If you are clinical and/or a health informatician, you can find hundreds of openEHR archetypes at the [Clinical...
**[Resources](https://discourse.openehr.org/c/resources/71)** - [What is openEHR?](https://discourse.openehr.org/t/what-is-openehr/1825)
> See the [what is openEHR? page ](https://www.openehr.org/about/what_is_openehr) for a short summary of everything .
**[Resources](https://discourse.openehr.org/c/resources/71)** - [About the Resources category](https://discourse.openehr.org/t/about-the-resources-category/1824)
> Resources for those new to openEHR, and those who may have forgotten a few things.
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Is anyone having issues with link sharing on AD](https://discourse.openehr.org/t/is-anyone-having-issues-with-link-sharing-on-ad/1823)
> Hello Everyone
We had created links of some of our templates on AD to share with consultants on our project, however we notice that now when we try to open those links it takes you to the login page of AD and even if you login you are not able to access the templates.
It would take you directly to the templates before.
Update: Spoke with Fabio, AD links expire after 14 days...
so that explains that!
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Scandinavian openEHR Collaboration Meeting Autumn 2021](https://discourse.openehr.org/t/scandinavian-openehr-collaboration-meeting-autumn-2021/1822)
> ***Scandinavian openEHR Collaboration Meeting Autumn 2021***
***Purpose of meeting***
Connect with the Nordic openEHR community to explore ways of collaborating towards common goals related to the use of openEHR.
***When and where***
* Thursday Oct 7th 13.00-15.00 CET
* Online
***How to join***
* Contact Mikael ([mikael.nystrom@cambio.se](mailto:mikael.nystrom@cambio.se)) or Åsa ([asa.skagerhult@regionostergotland.se](mailto:asa.skagerhult@regionostergotland.se))
* Feel free to spread the...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Flatform and Composition](https://discourse.openehr.org/t/flatform-and-composition/1794)
> Hello Forum ,
I am very confused as to what are flat forms , how are they created from a template , how are they different from compositions and what are they used for ?
Thank You
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Process of creating an openEHR system](https://discourse.openehr.org/t/process-of-creating-an-openehr-system/1792)
> Hello Forum , I am very new to openEHR and from my understanding to create a openEHR based website from collection patient data I have created a few steps to follow , but I am not able to understand if this is accurate and I am not able to move beyond it.
Please correct me if I am wrong and suggest steps after the ones I have listed
Step 1 : Create template from achetypes using Archetype Designer
Step 2 : Upload that template to an EHRbase server
Step 3 : Convert the template to a HTML...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Updating archetype of a composition](https://discourse.openehr.org/t/updating-archetype-of-a-composition/1789)
> We are looking into updating existing compositions to use a new version of an archetype.
However the [VERSIONED_COMPOSITION](https://specifications.openehr.org/releases/RM/latest/ehr.html#_versioned_composition_class) class has this invariant:
> *Archetype_node_id_valid*: `for_all v in all_versions | v.archetype_node_id.is_equal (all_versions.first.archetype_node_id)`
And the archetype_node_id [should contain the stringified...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [mCODE based archetypes --initial attempt](https://discourse.openehr.org/t/mcode-based-archetypes-initial-attempt/1788)
> Hi ,
As a Oncology focussed organisation working on data projects we reference mCODE https://mcodeinitiative.org/ as the minimum dataset requirements . We are adopting openEHR for our data storage . With this context we attempted to create mCODE based archetypes using same data elements as in mCODE data profiles which are essentially FHIR. Posting few of archetypes which is very first attempt for the review and comments by community . Kindly give us your valuable inputs.
Thanks
Dr...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Default values in OPT 1.4](https://discourse.openehr.org/t/default-values-in-opt-1-4/1785)
> Several versions of the OPT 1.4 XSD seem to be used. Pablo did a comparison of the different versions in https://discourse.openehr.org/t/opt-version-schema-document/486/34 .
I am currently writing a converter from OPT 1.4 to ADL 2 templates in source form. It now mostly works and can be found in https://github.com/openEHR/archie/pull/261 . It can also be used to parse OPT 1.4 into the AOM 2 directly, without conversion.
However, in the different OPT 1.4 versions, the way to define default...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Missing type id property '_type' Error in Ehrbase](https://discourse.openehr.org/t/missing-type-id-property-type-error-in-ehrbase/1778)
> I am trying to post a composition to ehrbase server but I keep getting this error :
I am not able to detect what the problem is exactly
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Does openEHR recommends to define service APIs using openEHR models as resources/TOs](https://discourse.openehr.org/t/does-openehr-recommends-to-define-service-apis-using-openehr-models-as-resources-tos/1776)
> This is based on https://twitter.com/gaparv/status/1425471884204855297?s=21 which i mentioned i will raised also in this forum.
This is a question that pops in to my mind when thinking about how OpenEHR can be used best with real world solutions. So my question in what is the recommendation on using OpenEHR models such as Archetype, Composition, Careentry models in business service APIs.
When i say business service APIs, they could be
- Micro-service APIs which are written for a certain...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [Is anyone using Marand's web-template project? I doesn't build](https://discourse.openehr.org/t/is-anyone-using-marands-web-template-project-i-doesnt-build/1774)
> I'm trying to build the project https://github.com/better-care/web-template
To generate some test cases for the HiGHmed's compliance test suite.
I have tried many things and failed miserably https://github.com/better-care/web-template/issues/1
Maybe others have better luck with it and can point me in the right direction.
Thanks!
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [When the outcome of an Action can be categorized as an Observation](https://discourse.openehr.org/t/when-the-outcome-of-an-action-can-be-categorized-as-an-observation/1771)
> Hi, I'm a software developer from Brazil working on an EHR system.
This question may be obvious for this community, I'm sorry if that's the case. But I have read a big part of the openEHR specifications and searched across this forum, and I'm still intrigued by this:
Suppose I have a **Instruction** archetype which contains an **Action** that describes an investigation request, requesting a certain test to be performed. The Action describes each step of the test, including the resulting...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Svensk översättning av "Encounter"](https://discourse.openehr.org/t/svensk-oversattning-av-encounter/1767)
> Hej, är helt ny i detta så ber om ursäkt i förväg om jag är i fel forum för denna fråga.
Såg i CKM att "Encounter" i svenska översättningen just nu heter "Vårdtillfälle". Det är nog inte helt korrekt om vi ska följa Socialstyrelsens termbank, där "vårdtillfälle" är "vårdkontakt i sluten vård". Encounters beskrivning är "Interaction, contact or care event between a subject of care and healthcare provider(s)." Den minst dåliga svenska översättning jag kan komma på är "vårdkontakt", som i SoS...
**[News](https://discourse.openehr.org/c/community-news/25)** - [Introducing ALT2MEDCODING. COM-](https://discourse.openehr.org/t/introducing-alt2medcoding-com/1762)
> I have the pleasure of introducing www.ALT2MEDCODING.COM, the new SNOMED AUTOCODING SAAS platform to the openEHR community.
I invite the members to visit us and give valuable suggestions how to integrate the service with openEHR.
We convert the clinical free-text into snomed coded output and also capture the granular data in JSON format for EHR.
A small presentation is available at www.alt2medcoding.com/concept-presentation for understanding the basic workflow.
Looking forward to the...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Catalan Health Service join openEHR as Organisational members](https://discourse.openehr.org/t/catalan-health-service-join-openehr-as-organisational-members/1759)
> We are delighted to announce that Catalan Health Service have joined openEHR as Organisational members. Catalan Health Service will use openEHR for it's [new platform for health records in Catalonia](https://openehr.org/news_events/openehr_news/341).
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [AOM/TOM semantics for cardinality constraints and occurrences in children](https://discourse.openehr.org/t/aom-tom-semantics-for-cardinality-constraints-and-occurrences-in-children/1750)
> Hi all, I'm generating some templates for testing data validation. While checking my code I realized I might be generating invalid OPTs, since my script is updating the cardinality constraints of each multiple attribute in the OPT (content, events, items, etc.), but was not checking the occurrences in the children objects defined for the multiple attribute.
After discussing a little bit with @pieterbos and @yampeku I ended up with a question:
**If there is only ONE child object in the...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Accuracy wrong in Quantified types](https://discourse.openehr.org/t/accuracy-wrong-in-quantified-types/1749)
> There appears to be a BMM reading error in AD, because the inherited accuracy fields are not computed correctly in concrete descendant types:
The `accuracy: ANY` field should have been replaced by the `accuracy:REAL` field, which is inherited from `DV_AMOUNT`.
This is probably occurring for all redefined fields...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Approximate dates](https://discourse.openehr.org/t/approximate-dates/1746)
> Reading the specs at 7.1.1.2. Partial Date/Times:
*"If not even the year is known, then the date is obviously extremely approximate and it would probably be unsafe to represent it computationally. However, if computatable representation was needed in this case, a date interval can be used. A pedantic example which breaks these rules is someone who claims to be born on "a Monday at the start of May in 1934" (i.e. day but not date unknown). Either the clinician determines what date the first...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Accessing the Int'l CKM](https://discourse.openehr.org/t/accessing-the-intl-ckm/1738)
> Good Morning Everyone,
I am trying to access the int'l CKM but am getting a notification about the security certificate being invalid and termsets not being available
is anyone else having this issue?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Person Data archetype draft](https://discourse.openehr.org/t/person-data-archetype-draft/1732)
> Hi Everyone,
I came across an old draft archetype for Person Data to be used with a demographic service. I am not sure I understand how it would fit into a composition.
Was this type of archetype abandoned? since it's not truly clinical data?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Understanding Flat Composition JSON](https://discourse.openehr.org/t/understanding-flat-composition-json/1720)
> Hi,
I am trying to create a Flat JSON using the following Template:
[Web Template (JSON)](https://github.com/venkydeo-philips/openEHR_EHRBase/blob/main/Vital%20Signs%20Encounter%20(Composition).json)
I am using the EHRScape Rest API via Postman and it is successfully creating a JSON.
I am not able to understand a few fields in it.
I have highlighted the fields in the image
These fields are created with all the templates that I...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [First dutch translation ever has been reviewed and published!](https://discourse.openehr.org/t/first-dutch-translation-ever-has-been-reviewed-and-published/1719)
> Crosspost because I think it's a milestone!
https://discourse.openehr.org/t/ckm-review-translations/1316/19?u=joostholslag
https://ckm.openehr.org/ckm/archetypes/1013.1.4218/revisionhistory
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [Region of Catalonia - RFI on technological elements to build an open platform using openEHR](https://discourse.openehr.org/t/region-of-catalonia-rfi-on-technological-elements-to-build-an-open-platform-using-openehr/1712)
> Hello everyone,
The region of Catalonia has launched today a Request for Information (RFI) with the purpose to obtain technical information on the possibilities of supplying the elements of a technological platform for the development of the Electronic Health Record of Catalonia. Given the technical complexity of the technological platform for the development of the Electronic Health Record and the need to finish defining its design and the components of the platform to be tendered, as well...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Automatic openEHR Template Tester](https://discourse.openehr.org/t/automatic-openehr-template-tester/1692)
> So I've come up with a [testing tool](https://github.com/medblocks/triggerfinger) to autogenerate forms for an openEHR template and test it against EHRbase. [The report](https://ci.medblocks.org/job/openEHR%20Template%20Tester/3/HTML_20Report/) includes the template opt, the different FLAT compositions and screenshots from the UI that generated the composition. You can see at a glance which compositions passed and which ones failed. I thought it'll help the community come up with better...
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [Flattened archetype is lacking terminology and language bindings](https://discourse.openehr.org/t/flattened-archetype-is-lacking-terminology-and-language-bindings/1691)
> I've been using [java-libs](https://github.com/openEHR/java-libs) to flatten a template, i.e., apply all of its constraints and print the resulting archetype. This is working wonderfully - but the end result is missing terminology and language bindings - this makes it rather unusable when generating a UI, for instance.
The relevant section in the AOM2 page does not really elaborate on the process (referring to the ADL Workbench for reference). The experimental OPT format mentions the...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Canonical Json / XML example with EHRBase](https://discourse.openehr.org/t/canonical-json-xml-example-with-ehrbase/1683)
> Hello,
I am just starting with openEHR and EHRBase and trying to post a composition using REST-API
(POST /ehr_id/composition) but always get some or the other error. I understand that the api uses canonical json, but I am not able to generate one ( from template) or find any sample. Can someone share a sample template and canonical json or canonical xml, postman collection will be much appreciated. thanks in advance!
Ritika Jain
Philips Healthcare
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [In-person SEC Meeting October, Berlin?](https://discourse.openehr.org/t/in-person-sec-meeting-october-berlin/1679)
> Hi everybody,
while I'm still very occupied with lots of non-technical stuff in several contexts, I would like to get a quick feedback on a possible SEC Meeting in Berlin on October 13. The background is that we will have a HiGHmed Symposium about FHIR and openEHR and we will have some community member gather in Berlin. This might be a good occassion and I think the location in the heart of Europe is also fitting well (and Berlin is relatively easy to travel to).
Please let me know what you...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Media file archetype - ready for publication](https://discourse.openehr.org/t/media-file-archetype-ready-for-publication/1674)
> Hi everyone,
The content description for this 'Media file' archetype is "A media file that is acquired or used as part of the healthcare process, and associated metadata."
Relevant examples include:
- A photo of an injury;
- A diagram of the location of a specific clinical finding;
- A radiological image;
- An audio or video recording of an interview;
- Scanned pathology slide;
- Data output from a clinical device, such as an ECG machine; or
- A scanned image of paper documentation or...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Implementing a solution with EHRbase](https://discourse.openehr.org/t/implementing-a-solution-with-ehrbase/1673)
> Hello!!
I am developing an architecture in which to store data in OpenEHR standard. I have thought about the option of using the EHRbase project as an accelerator to be able to create the service that is capable, among other things, of CRUD operations on the data.
My doubt is if using EHRbase I would already have a CDR composed by a service capable of performing CRUD to a database with OpenEHR standard.
I mean, I make the necessary modifications in the EHRbase project, generate my jar,...
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Updating openEHR terminology format](https://discourse.openehr.org/t/updating-openehr-terminology-format/1668)
> Now we have a full xml file that groups every internal terminology openEHR cares about. This can difficult things like versioning (detecting which subset was changed) and/or translation (now we are translating the full file, with, and the way that is being done makes evolution almost impossible).
IMHO we should try to go to a ValueSet approach, where each one of the current codesets (and their corresponding translations) would be all in one single place. This would also allow to create uris...
**[openEHR & standards](https://discourse.openehr.org/c/standards/69)** - [About the openEHR & standards category](https://discourse.openehr.org/t/about-the-openehr-standards-category/1661)
> Topics on the relationship between openEHR and de jure standards. [Dedicated standards groups here](https://discourse.openehr.org/c/integration/100).
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Participate in the thesis survey](https://discourse.openehr.org/t/participate-in-the-thesis-survey/1657)
> Hi,
I’m not sure if you may have noticed my post on common forums, but let’s raise the issue here now as well.
I would be especially grateful if the representatives of the Swedish openEHR community had the time and interest to respond to the survey, as the development of your health information systems and, in part, the service system are quite close to those in Finland. I have also realized that you have good practical experience in identifying and realizing the benefits of the openEHR...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Doubt XML Composition in Object RM Openehr transformation](https://discourse.openehr.org/t/doubt-xml-composition-in-object-rm-openehr-transformation/1656)
> Hello everyone, I need to transform an XML composition into RM Object, but the examples I find don't work for me.
I need to understand how I can perform this conversion performance.
I found this library
https://github.com/openEHR/java-libs/tree/master/xml-binding/src/test/java/org/openehr/binding
But it doesn't recognize that my XML is a composite, as the tag names are not explicitly stated with the attributes, see...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Versioning problem](https://discourse.openehr.org/t/versioning-problem/1653)
> Hi everybody,
I have a question about versioning.
I am not completely sure.
**Ver 3 of SysA was made from Ver 2 or Ver 2.1.1**
Generally, **users can update the latest version of a specific trunk-branch number** or **have to update the latest version without considering of branch number(the most recently added version)**.
thanks
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Archetype development and governance methodologies for the electronic health record](https://discourse.openehr.org/t/archetype-development-and-governance-methodologies-for-the-electronic-health-record/1651)
> Hello,
The past 15th of February I defended my PhD thesis titled "Archetype development and governance methodologies for the electronic health record".
I forgot to announce it here for the community, I should be ashamed. But better late than never :sweat_smile:
**Summary**
Semantic interoperability of health information is an essential requirement for the sustainability of healthcare, and it is essential to face the new health challenges of a globalized world. This thesis provides new...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Archetype original language and translation policies](https://discourse.openehr.org/t/archetype-original-language-and-translation-policies/1649)
> This comes from other topic, but I think it deserves its own discussion.
Talking about the translation of archetypes, and the requirement of using English as the original language.
[quote="siljelb, post:32, topic:1308"]
[quote="damoca, post:31, topic:1308"]
Off-topic: Is this a policy or a software limitation?
[/quote]
It’s a policy. Translations are always done from the original language to avoid a “telephone game” situation where the semantics diverge between the translations. Having any...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [4th openEHR Asia summit](https://discourse.openehr.org/t/4th-openehr-asia-summit/1647)
> Hi everyone,
The 4th openEHR Asia summit was held on April 29, 2021, hosted by Professor Xudong Lu (@lvxd) from Zhejiang University, Hangzhou. Many thanks to Professor Shinji Kobayashi (JP) for initiating the event and to all of the presenters who shared their knowledge and experience so generously.
I am pleased to be able to make the proceedings from this summit available to the broader openEHR community.
The link to the entire video is here:...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Echocardiography - Change of "Imaging result" CLUSTER archetype? Reuse lab analyte design pattern for nested/repeated clusters?](https://discourse.openehr.org/t/echocardiography-change-of-imaging-result-cluster-archetype-reuse-lab-analyte-design-pattern-for-nested-repeated-clusters/1646)
> HI!
We are developing a template for [echocardiography](https://en.wikipedia.org/wiki/Echocardiography) in Sweden and have had a close look at a template from the German [HiGHmed](https://highmed.org/) project, see: https://ckm.highmed.org/ckm/templates/1246.169.85 (Ping @birger.haarbrandt)
In HiGHmed's template the archetype [openEHR-EHR-CLUSTER.imaging_result.v0](https://ckm.openehr.org/ckm/archetypes/1013.1.2764) is repeated in a nested fashion with an instance for each measurement...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [Demographic model improvements](https://discourse.openehr.org/t/demographic-model-improvements/1645)
> A long-term limitation of the [openEHR demographic model](https://specifications.openehr.org/releases/RM/latest/demographic.html) has been the ability to clearly represent employment and similar relationships, which are commonly needed in healthcare (and are in the FHIR Admin model for example).
A proposal to do this is shown below. It adds the ACCOUNTABILITY concept to the model, which represents a defined requirement or need to be filled for one PARTY by another PARTY, usually playing a...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [Organization of a party within the EHR](https://discourse.openehr.org/t/organization-of-a-party-within-the-ehr/1638)
> Hi everybody,
We need to provide information about the composer and the corresponding organization that was responsible for the treatment of the patient (which can be different from the healthcare facility where the treatment took place). To my understanding, this would require a party_identified for the composer that points to a (demographics or provider) service that stored this information. However, when importing the data, this information can not always be properly put into such...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Recording historical patient reported observational data](https://discourse.openehr.org/t/recording-historical-patient-reported-observational-data/1631)
> We have a use case where a patient reported form for recording information related to bone mineral density scanning, where the patient is asked to record their height "in their youth (about 20 years of age)".
How should this be recorded?
Our first thought was to use the OBSERVATION.height archetype, with the event point in time set to the patient's date of birth + 20 years. But this data isn't really a height recorded at a specific point in time, but at an approximate age which may be 50...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [What is the owner of party(VERSIONED_OBJECT.Owner_Id)](https://discourse.openehr.org/t/what-is-the-owner-of-party-versioned-object-owner-id/1630)
> Hi everyone,
I am trying to implement VERSIONED_PARTY. But I encounter with a problem(owner_id is a mandatory field)
what is the owner of party ??
In my opinion there are not any owners for a party. So, it would be better to be null.
Am I wrong?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRbase DB setup without extensions - flyway migrate problem](https://discourse.openehr.org/t/ehrbase-db-setup-without-extensions-flyway-migrate-problem/1629)
> Hi @birger.haarbrandt @christian @jake.smolka
I am following this tutorial to setup ehrbase DB without extensions https://github.com/ehrbase/ehrbase/tree/develop/base/db-setup
I am trying to do this with postgres running locally in a container and listening on localhost:5432
The db creation works fine with this command
# `sudo psql -h localhost -U postgres < cloud-db-setup.sql`
When I am running #mvn flyway:migrate I get the following error
```
org.flywaydb.core.api.FlywayException:...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [C_ATTRIBUTE.existence clarifications](https://discourse.openehr.org/t/c-attribute-existence-clarifications/1628)
> Cross posting form the SEC Slack to avoid missing the discussion.
While working on data validation openEHR conformance, I've found in the AOM there is a C_ATTRIBUTE.existence attribute that was not supported by the Archetype Editor or the Template Designer, that is actually mandatory in the AOM.
It appears in both AOM 1.4 and AOM...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Loss of some annotations with export](https://discourse.openehr.org/t/loss-of-some-annotations-with-export/1627)
> Hi all,
in a template we are working on for a use case related to a dataset of cancer patients we need to represent :
- the interval (in weeks) passed between the date of first diagnosis and the beginning of the radiation therapy;
- the interval (in weeks) between the date of first diagnosis and the end of radiation therapy.
At the moment, we have modeled it by adding the CLUSTER “Timing - non-daily” in the “Procedure details” SLOT of the ACTION “Procedure” archetype and cloning the...
**[Community](https://discourse.openehr.org/c/community/10)** - [Proposal - sub-categories under New to openEHR category](https://discourse.openehr.org/t/proposal-sub-categories-under-new-to-openehr-category/1625)
> Having a look at the 'New to openEHR' category, it probably is not yet that helpful to true new-comers. I propose to add some sub-categories on major topics like:
* what does openEHR do?
* what are archetypes?
* where are the specifications?
* how do I get involved?
* relationship to standards
and so on.
Thoughts and suggestions from the community?
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Arketyp för ”Obstetrisk National Early Warning Score (ONEWS)”](https://discourse.openehr.org/t/arketyp-for-obstetrisk-national-early-warning-score-onews/1622)
> Inom Cambio har vi fått ett behov av att ganska omgående ha en arketyp för Obstetrisk National Early Warning Score (ONEWS), vilken är en svensk skattningsskala som finns beskriven på sidorna 18-19 i dokumentet [National Early Warning Score 2 NEWS2 - Övervakning och bedömning av vitalparametrar (2018)](https://lof.se/filer/NEWS2-broschyr.pdf). Jag har därför modellerat ett utkast till en sådan arketyp och utkastet finns tillgängligt på sidan [Arketypen Obstetrisk National Early Warning Score...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Systems architecture for data conversion to OpenEHR](https://discourse.openehr.org/t/systems-architecture-for-data-conversion-to-openehr/1619)
> I am trying to implement an architecture to automate Clinical Data transformations to the Openehr standard but I can't find any documentation to support my development.
I was thinking of developing an architecture based on the following elements:
* ETL to extract the original data.
* Open EHR API developed in JAVA that transforms the original data to the OpenEHR standard (I don't know if there is any API that performs these actions). Use the OpenEHR system to do the transformation.
*...
**[Tooling](https://discourse.openehr.org/c/tooling/68)** - [openEHR Conformance / Conformance Levels / Conformance Scopes](https://discourse.openehr.org/t/openehr-conformance-conformance-levels-conformance-scopes/1616)
> Hi all,
I've been working for a while in the CONFORMANCE framework for HiGHmed, and now we are having interest in this area from Solit-Clouds, and having some extended conformance discussions internally. So there are some areas we need to discuss with the community since this will be a CONFORMANCE framework anyone can use to validate their implementations.
# Current conformance framework
The current framework is focused on testing conformance with the Service Model via it's only standard...
**[Community](https://discourse.openehr.org/c/community/10)** - [Master's degree thesis on openEHR-based decision support - Participate in a research survey](https://discourse.openehr.org/t/masters-degree-thesis-on-openehr-based-decision-support-participate-in-a-research-survey/1614)
> Dear openEHR community,
My name is Henri Huttunen, and I am implementing a master's thesis related to openEHR-based decision support. The purpose of the thesis is to examine how an open platform and an openEHR approach could help reform decision support systems in a user-oriented way in Finland and what specific benefits the openEHR approach brings compared to other development models?
To identify areas where the openEHR approach supports the realization of the benefits, implementation,...
**[Tooling](https://discourse.openehr.org/c/tooling/68)** - [About the Tooling category](https://discourse.openehr.org/t/about-the-tooling-category/1613)
> For discussions on implementation of conformance framework and tools.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Tips on archetype/template for "Central venous line/catheter"?](https://discourse.openehr.org/t/tips-on-archetype-template-for-central-venous-line-catheter/1611)
> Can anyone point me towards a suitable archetype/template for documenting insertion of central venous lines/catheters? Ie something that would include things like:
- type of catheter and it's characteristics
- site of insertion and tip
- method of insertion (+/- ultrasound guidance, over guidewire etc)
- prophylactic antibiotics and/or other meds
- post-procedural follow up
Would be very grateful for any tips, it doesn't have to include all of the above :) Apologies in advance if this was...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [ADL2 sample archetypes for testing archetype designer tools](https://discourse.openehr.org/t/adl2-sample-archetypes-for-testing-archetype-designer-tools/1608)
> I need a few specialized ADL2 archetype samples for testing my developing designer tool. I appreciate if anyone can provide me with a few specialized adl2 archetypes that covers most specialization scenarios.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Enabling admin APIs in EHRBase](https://discourse.openehr.org/t/enabling-admin-apis-in-ehrbase/1606)
> I am running the latest EHRbase using docker-compose and am unable to see the admin APIs in swagger. Tried both AUTHUSER & AUTHADMINUSER logins.
Is there any environment variable setting to enable this? @jake.smolka
regards
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Sample folder structure that includes 'details'](https://discourse.openehr.org/t/sample-folder-structure-that-includes-details/1603)
> The sample create folder JSON in EHRBase is as below and does not show the 'details' array that can be used for adding more context information to the folder
"_type": "FOLDER",
"name": {
"_type": "DV_TEXT",
"value": "root"
},
"uid": {
"_type": "OBJECT_VERSION_ID",
"value": "6e13bbdb-893c-4260-b47d-f3585d178667::example.domain.com::1"
},
"folders": [
{
"_type": "FOLDER",
...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Validating stored queries in EHRBase](https://discourse.openehr.org/t/validating-stored-queries-in-ehrbase/1602)
> Does EHRBase do any validations or sanity test when a stored query is saved?
Is the user responsible for ensuring that the query is valid before it is saved?
**[Releases](https://discourse.openehr.org/c/releases/51)** - [Archie 1.0.0 released - OpenEHR Java Library](https://discourse.openehr.org/t/archie-1-0-0-released-openehr-java-library/1599)
> We’re pleased to announce that we have released version 1.0.0 of the Archie library!
Archie is an open source Apache 2 licensed library written in Java that implements several openEHR specifications: the Reference Model version 1.1.0, Archetype Object Model and ADL 2.1.0, BMM and many tools to work with it, including parsers and serialisers to standards compliant JSON, XML, ODIN and ADL 2, Archetype validation, OPT 2 generation and more.
It can and is used as a basis to develop openEHR...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Optimization of stored query execution in EHRBase](https://discourse.openehr.org/t/optimization-of-stored-query-execution-in-ehrbase/1598)
> As per my understanding AQL gets compiled into SQL for execution. In stored queries, are the AQLs being pre-compiled so that it does not have to be done every time it is used?
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Behaviour of logical operators(OR, AND, NOT) in FROM Clause](https://discourse.openehr.org/t/behaviour-of-logical-operators-or-and-not-in-from-clause/1596)
> I am working on aql query to get different composition for an ehr.
Query 1 : "SELECT c1, c2 FROM EHR e[ehr_id/value='3fb5117e-dba9-40d1-b472-d575f0a341ae'] CONTAINS (COMPOSITION c1[openEHR-EHR-COMPOSITION.encounter.v0] AND COMPOSITION c2[openEHR-EHR-COMPOSITION.encounter.v1]) "
I want to know how this above query will execute and in place of AND operator if it is OR then what would be result.
Query 2 : "SELECT c FROM EHR e[ehr_id/value='3fb5117e-dba9-40d1-b472-d575f0a341ae'] CONTAINS...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Arketypen "ASA Physical Status Classification System"](https://discourse.openehr.org/t/arketypen-asa-physical-status-classification-system/1589)
> **ASA Physical Status Classification System**
Klassifikationen “ASA Physical Status Classification System” har använts I över 60 år. I det här arbetet är målsättningen att uppdatera arketypen ”ASA physical status classification”, https://ckm.openehr.org/ckm/archetypes/1013.1.1336 så att den får statusen publicerad och har en svensk översättning och begreppsbindning till Snomed CT. Arketypen skapades ursprungligen 2010-06-25 och har fortfarande statusen utkast.
Arketypen är tänkt att vara en...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [AQL Performance benchmarks in EHRBase](https://discourse.openehr.org/t/aql-performance-benchmarks-in-ehrbase/1588)
> One of the problems that we observed in Ethercis was a rapid deterioration of performance, especially AQL as the number of compositions increased. Has this been addressed in EHRBase?
Has anybody done any performance benchmarks on EHRBase?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Setting custom server node name](https://discourse.openehr.org/t/setting-custom-server-node-name/1586)
> By default EHRBase seems to add local.ehrbase.org to all the URIs that it creates
For example versioned compositionUid - ac760392-f56a-40f0-a4dd-ccd769625ea9::local.ehrbase.org::2
In my understanding the nodename is used in these URIs. I tried changing it by starting the JAR as below
#java -jar application/target/application-0.16.5.jar -server.nodename=local.ehr.network
Though the server starts OK, I do not see any difference to the URIs after that also. Is there any way to check the...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [FLAT composition - EHRBase 0.16.5 - Content values missingin get composition](https://discourse.openehr.org/t/flat-composition-ehrbase-0-16-5-content-values-missingin-get-composition/1585)
> While creating compositions, I am adding the following context value and the composition is created with out any error
"clinical_notes/context/participation:0|function": "Oncologist",
"clinical_notes/context/participation:0|name": "Dr. Marcus Johnson",
"clinical_notes/context/participation:0|identifier": "1345678",
"clinical_notes/context/participation:0|mode": "face-to-face communication::openehr::216",
"clinical_notes/context/end_time": "2021-05-29T13:20:51.451+05:30",
However they are...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [CompositionUid format while using FLAT format for creation](https://discourse.openehr.org/t/compositionuid-format-while-using-flat-format-for-creation/1584)
> EHRBase 0.16.05
When I create a composition using FLAT format, i am getting the following response
{
"meta": {
"href": {
"url": "http://ip6-localhost:8080/ehrbase/rest/ecis/v1/composition25776648-c859-409f-a5a5-b7c811314ca6::1"
}
},
"action": "CREATE",
"compositionUid": "25776648-c859-409f-a5a5-b7c811314ca6::1"
}
In my understanding the compositionUid format should be 25776648-c859-409f-a5a5-b7c811314ca6::local.ehrscape.com::1
Is this an...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - ["archetype_node_id": "openEHR-EHR-EHR_STATUS.generic.v1", in create EHR body](https://discourse.openehr.org/t/archetype-node-id-openehr-ehr-ehr-status-generic-v1-in-create-ehr-body/1581)
> Hi,
In the openEHR REST API specs, I can see this in the EHR_STATUS request body. What does it signify? Can I view and change this archetype anywhere?
regards
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [List of available override the application properties (like database settings) in EHRBase](https://discourse.openehr.org/t/list-of-available-override-the-application-properties-like-database-settings-in-ehrbase/1580)
> Hi,
Is there a documentation on the list of application properties for EHRBase that we can override at startup time? Also is there an application.properties file that I can customize and use at runtime?
regards
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Manually adding external terminology values](https://discourse.openehr.org/t/manually-adding-external-terminology-values/1577)
> When adding external terminology values to a DV_CODED_TEXT element in an archetype, the Archetype Designer apparently only allows adding them using URIs and constraints. In a lot of cases, legacy code sets don't have any of those, but only a name, and at best an OID. We need to be able to add these value sets to the archetype manually. How can we do that?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Compositions involving multiple patients](https://discourse.openehr.org/t/compositions-involving-multiple-patients/1574)
> Hi,
There are multiple use cases when multiple patients are involved in some clinical event. For example many mental health therapies are conducted in a group. What is the recommended approach to handle such compositions that are linked to multiple patients(EHRs)?
The requirements in this situation are
1. The composition should appear in al the EHRs
2. Need for authorized users to know all the patients that were involved in a particular session
3. Maintain privacy of the people...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [AQL through GraphQL](https://discourse.openehr.org/t/aql-through-graphql/1573)
> No openEHR application is built in isolation. There are many services running alongside it and the client usually needs to make multiple requests to obtain different data points like demographics, clinical content, terminology etc. Some views may also require executing multiple AQL queries on the client to get the necessary data.
The Problem: The client application needs to make more HTTP requests than necessary. This becomes especially cumbersome when different services have different...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Use of Draw.io format vs SVG for TP-VML](https://discourse.openehr.org/t/use-of-draw-io-format-vs-svg-for-tp-vml/1568)
> Looking at the work done in the TP-VML specs, we seem to have gone with the proprietary draw.io format for the palette. Is there any specific reason for this choice as we have more open and universal formats such as SVG?
Are there any other opensource tools(Draw.io is free but not opensource) that can be used to build a visual designer using the current palette?
regards
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Lifecycle_state in EHRbase](https://discourse.openehr.org/t/lifecycle-state-in-ehrbase/1567)
> Hi all
We are using EHRbase for our CDR which is going ok albeit we have only a tiny number of EHRs on it (<10), and only for an anticipatory care plan application supporting [ReSPECT](https://www.resus.org.uk/respect).
This is pretty much testing the ground for us as we need to scale up to manage 6 million citizens health and care records, so we need very much to make it work and be solid, safe and meet our requirements!
One recurring requirement is to handle 'drafts', that is...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRBase 0.16.5 - Create EHR error while using Postman](https://discourse.openehr.org/t/ehrbase-0-16-5-create-ehr-error-while-using-postman/1562)
> I am testing the latest dev branch. I have been able to successfully build and run the server. The http://localhost:8080/ehrbase/rest/openehr/v1/ehr works fine from the integrated swagger UI.
However when i am testing this from postman, I get the following error
> {
> "error": "Message at /archetype_node_id (/other_details/archetype_node_id): Attribute archetype_node_id of class ITEM_TREE does not match existence 1..1\nMessage at /name (/other_details/name): Attribute...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Shared blood glucose (+HbA1c) templates?](https://discourse.openehr.org/t/shared-blood-glucose-hba1c-templates/1561)
> Hi!
If I understand things correctly, the old archetypes...
* **Blood glucose**: https://ckm.openehr.org/ckm/archetypes/1013.1.564
* **Blood Glucose Test Result**: https://ckm.openehr.org/ckm/archetypes/1013.1.1402
* **Haemoglobin A1c**: https://ckm.openehr.org/ckm/archetypes/1013.1.551
...have been rejected and replaced by the more generic pattern using terminology e.g. LOINC or SNOMED CT combined with the archetype...
* **Laboratory test result**:...
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [How to create GDL2 guideline based on ADL2 archetypes](https://discourse.openehr.org/t/how-to-create-gdl2-guideline-based-on-adl2-archetypes/1560)
> Hi all,
Does anyone has experience with creating GDL2 files based on ADL2 archetypes. I tried doing this with the GDL2 editor, but it has a hard time interpreting the ADL2 archetypes created with the ADL workbench apps. Wondering if there are any othere tools I could use to achieve this. Or if I should just stick to ADL 1.4 Archetypes for now when wanting to create GDL2 files.
Thanks!
Regards,
Rinke
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR Query Languages (QUERY) Release 1.1.0 published](https://discourse.openehr.org/t/openehr-query-languages-query-release-1-1-0-published/1557)
> The [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) has recently published [QUERY Release 1.1.0](https://specifications.openehr.org/releases/QUERY/Release-1.1.0) specification.
This release brings several additions to the [Archetype Query Language (AQL)](https://specifications.openehr.org/releases/QUERY/Release-1.1.0/AQL.html#_what_is_aql), such as query result pagination, literal values, functions and operators. Most of...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [BMM Schema descriptor class function "is_top_level"](https://discourse.openehr.org/t/bmm-schema-descriptor-class-function-is-top-level/1555)
> The description for the method "is_top_level" breaks the rule for encapsulation. It should determine the state of the class by checking other classes which has no idea about. It should be implemented in the parent class "Model access" that has the access to all its siblings, shouldn't it? Or I misunderstand the concept of the method to show from which class should merging begins.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Creating a composition for EHRBase](https://discourse.openehr.org/t/creating-a-composition-for-ehrbase/1551)
> Hello,
As far as I understand there are two ways to commit a composition into EHRBase:
1- Through the SDK
2- Through the rest api using either the xml or the FLAT format.
According to the [EHRBase documentation](https://ehrbase.readthedocs.io/en/latest/02_getting_started/05_load_data/index.html#flat-format), a flat composition can be created using a web template by concatenating ids and suffixes.
However, I can't figure out how that works in the following example:
This the relevant part...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [What's allowed in FOLDER.items](https://discourse.openehr.org/t/whats-allowed-in-folder-items/1539)
> Currently FOLDER.items is a List, which allows COMPOSITION, EHR_STATUS and FOLDER.
See: https://specifications.openehr.org/releases/RM/Release-1.1.0/common.html#_overview_4
Shouldn't the spec be constrained to List?
I guess what raises red flags for me is that FOLDER already has a List, so having VERSIONED_FOLDER instances in FOLDER.items seems strange.
Also the possibility of having EHR_STATUS in the FOLDERS seems strange, unless there is...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Help needed with openEHR GDL](https://discourse.openehr.org/t/help-needed-with-openehr-gdl/1537)
> Hi all,
I'm a Dutch clinical informatics PDEng student. As part of my studies I am currently designing (and hopefully developing) a decision support tool to be used in a healthcare department.
What I would like to do is to translate a natural language clincal guideline (in the format: if patient had this in the past, then advice this/perform this) into a computer interpretable guideline, which can then be used in a decision support tool. Of course I could just program if-then-else-rules in...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Demographic archetypes for clinical record purposes](https://discourse.openehr.org/t/demographic-archetypes-for-clinical-record-purposes/1534)
> Hi all,
Over the years there's been a proliferation of demographic-related archetypes created using the EHR RM and intended to be used for clinical recording purposes and explicitly designed with a simple, light touch that is adequate for recording in a consult note, a referral or an extract to send to a new GP practice.
We often get pushback from the engineers because it means we don't end up using proper Master Patient Indexes or Healthcare Provider Indexes etc. So, just to be clear, I'm...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Menstruation summary](https://discourse.openehr.org/t/menstruation-summary/1530)
> The archetype has been through 3 review rounds. There seems to be consensus among the reviewers. Unless there are objections this archetype will be published on May 7, 2021.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.1662 ](https://ckm.openehr.org/ckm/archetypes/1013.1.1662)
Please reply to this topic if you have any objections or comments.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Separates Party from Party relationship during loading data](https://discourse.openehr.org/t/separates-party-from-party-relationship-during-loading-data/1528)
> Hi everybody,
According to [I_DEMOGRAPHIC_SERVICE](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_i_demographic_service_interface) party and relationships are two separate root aggregates. But in [I_PARTY](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_i_party_interface) Interface we have to load party( **get_party**) with all relationships(based on party Demographic Rm) which causes performance problems. So, in my opinion it is...
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR XML Schemas (XSDs) Release 2.0.0 published](https://discourse.openehr.org/t/openehr-xml-schemas-xsds-release-2-0-0-published/1522)
> In the end of April, the [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) has published [ITS-XML (XSDs) Release 2.0.0](https://specifications.openehr.org/releases/ITS-XML/Release-2.0.0) specification.
The ITS-XML 2.0.0 brings a number of XML Schema additions, corrections, improvements, a new structure that covers several openEHR component releases, as well as a few breaking changes compared to [ITS-XML Release...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Including FHIR, CIMI or other standard refs in archetypes](https://discourse.openehr.org/t/including-fhir-cimi-or-other-standard-refs-in-archetypes/1519)
> I have noticed quite a few archetypes making mention of particular FHIR resources, 'CIMI', HL7v2, and other data / interop standards. Unless the standard referenced is absolutely immutable, i.e. it is a past release, this is not a good idea. It may not be a good idea anyway, because these standards come and go in time.
Particular issues:
* CIMI is not something we follow, and as far as I know, is not publishing much within HL7. I would suggest these references be removed.
* FHIR resources...
**[openEHR Toolkit](https://discourse.openehr.org/c/openehr-toolkit/92)** - [New openEHR OPT v1.6](https://discourse.openehr.org/t/new-openehr-opt-v1-6/1515)
> This might be useful for some here: https://github.com/ppazos/openEHR-OPT/releases/tag/v1.6
It's basically my toolkit for the terminal to generate test data from OPTs and work with the openEHR formats. Been using this for testing my other systems, like the EHRServer or the openEHR Toolkit. Also used it to work on the conformance validation framework for HiGHMed.
This update is just a sum of fixes, tests and some tools I wanted to build, doing small progress during the weekends.
The new...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [ESAS - pain assessment](https://discourse.openehr.org/t/esas-pain-assessment/1514)
> We are currently working on an application for palliative care. The base is ESAS-R (Edmonton Symptom Assessment System Revised). In addition to this the hospitals use a form for pain evaluation/assessment. A typical solution for this is a paper form presented to the patient to record their pain. The patient is asked to mark on this image:
The original her:...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [openEHR @ Vitalis 2021](https://discourse.openehr.org/t/openehr-vitalis-2021/1512)
> Se [Vitalis information om openEHR-spåret 2021](https://invitepeople.com/public/events/15219/seminars?seminar_category=1931&sort_by=external_id&sort_order=asc) för detaljer, föreläsarpresentationer m.m. Notera att man på Vitalis webbsidor om respektive föredrag i videofönstret kan välja helskärmsläge (ikon med pilar i nedre högra hörnet) samt välja upplösning/kvalitet (kugghjul i övre högra hörnet).
Delar av informationen från vitalis sidor återges även nedan för att finnas kvar längre...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Implementer experiences: Physical properties of a specimen](https://discourse.openehr.org/t/implementer-experiences-physical-properties-of-a-specimen/1511)
> We'd like to hear from implementers and others regarding the 'Physical properties of an object' archetype (https://ckm.openehr.org/ckm/archetypes/1013.1.386).
We've taken it through one review round, but we've found that it tries to incorporate too many concepts, and our only use case that we're sure of is for documenting the volume, mass and physical properties of a specimen removed from the body.
After some discussion we've come to the conclusion that the scope becomes much more...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Semantic versioning of templates](https://discourse.openehr.org/t/semantic-versioning-of-templates/1508)
> Archetype Designer has recently introduced semantic versioning of templates. This is an interesting development which could be very useful, but which may require some fine tuning of the versioning rules.
For archetypes, versioning generally starts with v0.0.1-alpha, and stays that way until the first time it's published as v1.0.0. While the choice to not use v0.0.5 or v0.3.4 can definitely be discussed, I think the use of -alpha is a good idea, to clearly differentiate development versions...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Set references ranges for vital function measurements](https://discourse.openehr.org/t/set-references-ranges-for-vital-function-measurements/1507)
> Hey everyone,
I have a question related to ranges. We are developing a vital function measurements table for clinical purposes in which we would like to mark measurements that are relatively high or low.
In the templates, we can of course set a range but this is only one range. How do we do this if we want to set multiple ranges?
Thanks in advance
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [How to generate an opt 1.4?](https://discourse.openehr.org/t/how-to-generate-an-opt-1-4/1505)
> Hello,
I'm still new to openEHR and I'm trying to figure out how to generate an opt programmatically.
I know that there are some xsd files in the specification repo and that those files should be used to generate an opt (please correct me if I'm wrong). But it's not clear to me how to actually do it.
If anyone can point me in the right direction? I would really appreciate it!
Thanks!
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Phenopackets 2.0 review](https://discourse.openehr.org/t/phenopackets-2-0-review/1503)
> An email from Global Alliance for Genomics and Health ([GA4GH](https://www.ga4gh.org/)) invites to a review of Phenopackets 2.0, see: http://ga4gh-4048059.hs-sites.com/open-for-comment-phenopackets-v2.0 (Deadline May 27)
A lot of new EHR content is represented in v 2.0 so it's likely clever if people with knowledge of openEHR have a look at [the new v 2.0 of the Phenopacket Schema](https://phenopackets-schema.readthedocs.io/en/v2/index.html) to figure out how reasonable alignment can be...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Changes in exported OPT templates](https://discourse.openehr.org/t/changes-in-exported-opt-templates/1501)
> Hi,
As of version 1.20.0 in https://tools.openehr.org/designer/#/ we have noticed a breaking change in the exported OPT temples. It seems that a namespace (ns2) is now added to the XML tags.
ISO_639-1
en
Not...
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR Base Model (BASE) Release 1.2.0 published](https://discourse.openehr.org/t/openehr-base-model-base-release-1-2-0-published/1499)
> In the beginning of April, the [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) has published [BASE Release 1.2.0](https://specifications.openehr.org/releases/BASE/Release-1.2.0) specification.
This release brings a number of improvements to the base model including:
- [SPECBASE-34](https://openehr.atlassian.net/browse/SPECBASE-34): Allow \+14:00 timezone
- [SPECBASE-29](https://openehr.atlassian.net/browse/SPECBASE-29):...
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR REST APIs Release 1.0.2 published](https://discourse.openehr.org/t/openehr-rest-apis-release-1-0-2-published/1498)
> The [openEHR Specifications Editorial Committee (SEC) ](https://www.openehr.org/programs/specification/editorialcommittee) has published [ITS-REST Release 1.0.2 ](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2).
This release contains a number of clarifications and improvements on openEHR REST APIs specifications:
- [SPECITS-59](https://openehr.atlassian.net/browse/SPECITS-59): Specify mimeType used by adl2 template
-...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [DSM-5 archetypes](https://discourse.openehr.org/t/dsm-5-archetypes/1495)
> Does anyone know of any archetypes that model DSM-5 (Diagnostics and statistics manual)?
Ideally a cluster for the additional details slot of EVALUATION.problem/diagnosis.
@sebastian.iancu maybe?
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Web template export](https://discourse.openehr.org/t/web-template-export/1494)
> In the latest version of Archetype Designer (v1.20.0), I am not able to export to Web Template. Here's the error log from the console. Is there another place I can report bugs on the AD?
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [DL vs GDL2 - Purpose and difference](https://discourse.openehr.org/t/dl-vs-gdl2-purpose-and-difference/1485)
> Hi,
I am looking at the new TP & DL specs. I also see GDL and an a bit confused between what DL is for and what GDL is for. If we are building a new CDSS solution in openEHR, should we be using DL or GDL? How will that change if we are developing the decision logic for a TP solution?
regards
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Body temperature - protocol and state](https://discourse.openehr.org/t/body-temperature-protocol-and-state/1484)
> Examing the body temperature archetype for a use-case where I are to add CLUSTER data for both environmental conditions and excertion. These are defined as SLOT in the STATE attribute of the OBSERVATION. So far so good.
State is defined as part of the `state` attribute of the [OBSERVATION](https://specifications.openehr.org/releases/RM/latest/ehr.html#_observation_class):
The RM defines that data and state are separate...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Why is location code only a string?](https://discourse.openehr.org/t/why-is-location-code-only-a-string/1481)
> We're working on patterns for making sure our document meta model is mapped to incoming openEHR compositions. One such element concerns `location` code. An example in structured JSON:
```
"event_context": [
{
"start_time": [
"2021-04-19T14:36:49.691+01:00"
],
"setting": [
{
"|code": "232",
"|value": "secondary medical care",
...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [CKM editorial policies](https://discourse.openehr.org/t/ckm-editorial-policies/1478)
> I’m looking for a place to read up on ckm editorial policies/decisions.
From reviewing medication summary I noticed all summary archetypes (alcohol use, smoking etc) are evaluations, while they mostly/solely describe observed data points (e.g. amount taken of a medication) so I wondered why they are not observations?
I found: https://openehr.atlassian.net/wiki/spaces/healthmod/pages/304742401/CKM+Editorial+Style+Guide
It states: “The Observation class is for recording information that...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Calculating EffectiveOccurrences on RM](https://discourse.openehr.org/t/calculating-effectiveoccurrences-on-rm/1477)
> For the implementation of EffectiveOcurrences method of C_Object (AOM2), the function which calcuates the mutiplicityinterval, gets two string arguments : one is the reference model type name and the other is the path of the attribute. If the method should go through RM to find the cardinality of the attribute why it uses the attribute path instead of its name? Or it should only checks the Archetype definition to find the defined RM type of that attribute ? It is not clear to me in the...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [GDL2 to Drools conversion](https://discourse.openehr.org/t/gdl2-to-drools-conversion/1474)
> Hi.. wanted to find out if there are recommended ways for GDL2 to Drools conversion. The Cambio GDL Editor had a Drools convertor built in, but the GDL2 does not. Please suggest
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Uncertain, unknown and no information](https://discourse.openehr.org/t/uncertain-unknown-and-no-information/1473)
> Clinical data is hard to get right. One problem is to handle the unknown and/or uncertain semantic. I assume you all have met the challenge to model a value list of
* yes
* no
* uncertain
* unknown
* not applicable
Norway is currently implementing a screening program for colorectal cancer. There will be #fhir messages with the data and extensively use of #snomed-ct. DIPS is developing #openehr models (templates and archetypes) to be used within our systems. We need to map these value sets...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Renaming a value in a specialization](https://discourse.openehr.org/t/renaming-a-value-in-a-specialization/1470)
> So currently when redefining/specializing a value set, it is only allowed to limit a larger value set to a smaller one.
The constraint binding strength adds lot of possible things. However, it does not seem to handle the following situation:
a parent archetype, from the CKM, has correct concepts in the value set members. However the terms used do not correspond to the terms used by the intended target audience of this archetypes. Exact matching different terms are available
An example:...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Analytics with OpenEHR](https://discourse.openehr.org/t/analytics-with-openehr/1466)
> What are the OpenEHR compatible visualisation and analytics tools?
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Mayo score - ready for publication](https://discourse.openehr.org/t/mayo-score-ready-for-publication/1462)
> Hi, everyone
The archetype "Mayo score" has been through one review. There were no major issues to solve, only minor changes in wording. The editorial team suggest publishing.
If you have any comments or objections, please note them here, at the latest in time of the planned publication date, April 20th 2021.
Link to the archetype: [Mayo score](https://ckm.openehr.org/ckm/archetypes/1013.1.5078)
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Error in running Ehrbase webservice](https://discourse.openehr.org/t/error-in-running-ehrbase-webservice/1456)
> Hi everyone,
I am trying to run ehrbase on windows 10 (using docker) but unfortunately I encounter the following error during the running of ehrbase webservice(**http://localhost:8080/ehrbase/**):
**Whitelabel Error Page**
**This application has no explicit mapping for /error, so you are seeing this as a fallback.**
**Mon Apr 12 10:02:50 UTC 2021**
**There was an unexpected error (type=Not Found, status=404).**
I was wondering if you could help me to solve this problem.
thanks.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - ["Advance intervention decisions" is ready for publication](https://discourse.openehr.org/t/advance-intervention-decisions-is-ready-for-publication/1452)
> (Formely named: "Ceilings of treatment directive", "Emergency care and treatment", "Limitation of treatment")
The archetype has been through four review rounds. There seems to be consensus among the reviewers. Unless there are objections this archetype wil be published on April 16th, 2021.
Link to the archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.4902
Please reply to this topic if you have any objections or comments.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Housing - access information](https://discourse.openehr.org/t/housing-access-information/1435)
> Hi everyone.
We have a use case in England where we need to record specific information about access to a person's home (e.g. door security code or other access arrangements, for example "neighbour so-and-so has a key"), but that has been specifically excluded from the CLUSTER.dwelling.v0 archetype (https://ckm.openehr.org/ckm/archetypes/1013.1.3285), which states that:
"Not to be used to record information about the dwelling that does not impact on the health or health care needs of an...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [VDFAI Validation interpretation](https://discourse.openehr.org/t/vdfai-validation-interpretation/1433)
> Hi
from https://specifications.openehr.org/releases/AM/latest/AOM2.html#_validity_rules_6 :
> **VDFAI**: archetype identifier validity in definition. Any archetype identifier mentioned in an archetype slot in the definition section must conform to the published openEHR specification for archetype identifiers.
Given that we usually have regexes in the Slots, I can read "conform to" in two ways:
1. The specified regex MUST NOT allow any strings that are no valid archetype ids or
2. It must...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Handling copyright for assessment scales represented as archetypes?](https://discourse.openehr.org/t/handling-copyright-for-assessment-scales-represented-as-archetypes/1429)
> Hi,
Do we have any best practice on how to handle copyright issues for assessment scales when they are represented as archetypes? I have seen the guidance on https://openehr.atlassian.net/wiki/spaces/healthmod/pages/304742407/Archetype+content+style+guide#Content-copyright , but do we also have any guidance about communication with the copyright holder or similar?
Regards
Mikael
**[ITS](https://discourse.openehr.org/c/its/41)** - [JSON/XML data representation considering ADL constraints](https://discourse.openehr.org/t/json-xml-data-representation-considering-adl-constraints/1427)
> Hi all, today we found a case when sharing observations between different systems, for instance Blood Pressure.
In the archetype, systolic and diastolic precision is limited to zero, which means DV_QUANTITY.magnitude is integer.
Due to internal data representation and serialization to JSON or XML, when creating a systolic value of "110", we end up seeing "110.0" in the JSON or XML.
My question is: should precision affect how the RM is serialized to JSON/XML? I mean if precision = 0, should...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Quantitative imaging and Radiomics](https://discourse.openehr.org/t/quantitative-imaging-and-radiomics/1426)
> Dear all,
We are currently working on using openEHR for quantitative imaging and radiomics in the HiGHmed project. Radiomics is the extraction of quantitative information from images. For those of you who are
not familiar with radiomics I recommend these papers that explain the concept of radiomics very well: https://doi.org/10.2967/jnumed.118.222893 and https://doi.org/10.1016/j.ejca.2011.11.036
There is also a video that gives a good introduction: https://vimeo.com/491584563
Radiomics...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Modellering av Swe-PEWS](https://discourse.openehr.org/t/modellering-av-swe-pews/1425)
> Då har jag gjort klart andra versionen av utkast till arketyper för Svensk Pediatric Early Warning Score (Swe-PEWS). Jag vill därför gärna få hjälp att reviewa både dess modellering och den engelska översättningen av dessa arketyper. Kommentarer från reviewn får gärna lämnas på den här sidan.
Själva Swe-PEWS finns beskrivet på sidan [https://lof.se/patientsakerhet/vara-projekt/pews](https://lof.se/patientsakerhet/vara-projekt/pews).
De svenska arketyperna är tänkta att användas inuti...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Use openEHR for DIGA mobile applications](https://discourse.openehr.org/t/use-openehr-for-diga-mobile-applications/1424)
> Medical mobile applications can now be remunerated if they are included in the DiGA directory.
The patient must be able to export the data, in a human-readable form and in a schema for the practitioner.
FHIR should represent the export schema.
Should the user data in the openEHR scheme be saved on the device?
Is a medical mobile application a use case for openEHR?
**[RM](https://discourse.openehr.org/c/rm/42)** - [Proposal: Expanded mode retrieval](https://discourse.openehr.org/t/proposal-expanded-mode-retrieval/1418)
> Currently in openEHR, we retrieve data in the same structures it went in, either:
* as the original COMPOSITION, ENTRY etc, via a direct get from the REST API
* as a list/table of pieces, within an AQL RESULT_SET
Neither of these modes performs two things that would be convenient in many circumstances:
* resolving Links / Citations
* attaching context of matched items
An obvious use case of when we would like this kind of behaviour is the managed list, i.e. Allergy List, Problem List etc....
**[News](https://discourse.openehr.org/c/community-news/25)** - [Industry Partner Solit-Clouds release their flagship openEHR CDR product - EHRDB](https://discourse.openehr.org/t/industry-partner-solit-clouds-release-their-flagship-openehr-cdr-product-ehrdb/1398)
> One of our newer Industry Partners, [Solit-Clouds](https://www.openehr.org/community/industry_partners_detail/solit-clouds), have released their flagship openEHR CDR product - EHRDB.
Solit-Clouds have come a long way from consuming openEHR products to developing their own solutions: proprietary CDR (EHRDB), form building tool (EHR Forms) and others.
We are delighted that so many partners are using openEHR and Solit-Clouds vision is "to share knowledge with the community and make the world...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Best way to handle raw ECG signal data from apple watch](https://discourse.openehr.org/t/best-way-to-handle-raw-ecg-signal-data-from-apple-watch/1395)
> Hey, we are using the ecg of apple watches and would like to store the raw signal data on our openEHR server. We are not sure if a seperation of openEHR data and the raw signal data in a additional DB would make more sense. Does someone have any experience in handling openEHR and raw ecg? Thanks!
**[RM](https://discourse.openehr.org/c/rm/42)** - [Attestation 'Request'](https://discourse.openehr.org/t/attestation-request/1391)
> Hi! We are looking at using Attestations and have a question about the following:
https://specifications.openehr.org/releases/RM/latest/common.html#_attestation
> When an attestation is required, the most common scenario will be that a Composition Version will be committed with a commit_audit of type ATTESTATION, rather than just AUDIT_DETAILS; the is_pending flag will be set to True to indicate that the committed information needs to be signed by another person.
So if I understand this...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR CIC Nomination Call - Election for Directors on openEHR CIC Board April 2021](https://discourse.openehr.org/t/openehr-cic-nomination-call-election-for-directors-on-openehr-cic-board-april-2021/1387)
> We have 3-Director positions due for election to the openEHR International Board this April; one to represent Individual / Professional members, one to represent Industry Partners and one to represent Organisational members.
Nominations open for existing members only.
You can access information and submit nominations by [logging into](https://openehrfoundation26.wildapricot.org/Sys/Login) the members website, where details can be found under the 'Members Only' tab on the Home page.
If you...
**[ITS](https://discourse.openehr.org/c/its/41)** - [JSON Schema and OpenAPI: current state, and how to progress](https://discourse.openehr.org/t/json-schema-and-openapi-current-state-and-how-to-progress/1385)
> We recently had a discussion on the SEC call about JSON Schema. I was asked to write down the current state and to get the discussion going on how to progress. So, here it is:
Several options exist to define a JSON format. Two of the most often used are:
- JSON Schema
- OpenAPI
Tools for working with Json Schema are widespread. It is very suitable for validation purposes, including built-in support in text-editors. However, with OpenEHRs extensive use of polymorphism, it is not suited for...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [Business models for openEHR platforms, tools and services](https://discourse.openehr.org/t/business-models-for-openehr-platforms-tools-and-services/1379)
> It could be interesting to openly discuss possible licensing/payment options of openEHR platforms, tools and services. We've heard it can be a bit tricky to find business models for some things.
The openEHR specifications and models (archetypes etc) are free to use, and are funded/fueled by voluntary donations of time and also by money via membership/sponsorship. This works pretty well now (but was a bit tricky in the beginning) and removes entry barriers to openEHR as such.
But tools,...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [How transform Composition XML to JSONFLAT JAVA 8](https://discourse.openehr.org/t/how-transform-composition-xml-to-jsonflat-java-8/1376)
> Hi,
I would like to know how I can transform an XML composition into a JSONFLAT in the same style as MARAND / Better in JAVA 8, because in one of the OpenehrSDK libraries it seems to contain a method for transformation but it is in JAVA 11, there are alternatives for 8 ?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Participations in Flat format for EHRBase](https://discourse.openehr.org/t/participations-in-flat-format-for-ehrbase/1374)
> I can't retrieve participations that I insert into my EHRBase in Flat format? The composition is accepted but the participations info aren't there. It is something missed, like the ctx support, or am I doing something wrong (syntax, path,..)?
I tried both the path /case/participation (as given by EhrSape example in the Flat format example from template REST call) and the path /case/context/participation (which seems to me more consistent with the template structure). In the webtemplate...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Brøset Violence Checklist (BVC) ready for publication](https://discourse.openehr.org/t/broset-violence-checklist-bvc-ready-for-publication/1371)
> The archetype has been through one reveiw round. There seems to be consensus among the reviewers. Unless there are objections this archetype wil be publisched on March 16, 2021.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.5150](https://ckm.openehr.org/ckm/archetypes/1013.1.5150)
Please reply to this topic if you have any objections or comments.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Renal dialysis?](https://discourse.openehr.org/t/renal-dialysis/1370)
> Has anyone done work on renal disease specific archetypes esp. dialysis? Asking for a friend!!
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Crossposting policy](https://discourse.openehr.org/t/crossposting-policy/1358)
> What are our ideas on crossposting?
I’m posting replies in 3 highly related topics: https://discourse.openehr.org/t/cross-reference-citations-and-a-solution-for-managed-lists/1355
https://discourse.openehr.org/t/linking-in-openehr-goals-and-problems/1032/16?u=joostholslag
https://discourse.openehr.org/t/problem-oriented-medical-record/635/17
I like to keep everyone in those three topics informed. And I myself in other topics, like to dig deeper into linked posts, so I’m crossposting and...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHRBase questions](https://discourse.openehr.org/t/ehrbase-questions/1357)
> Hello!
I'm new to the openEHR world and this is my first time posting!
I've been going through the EHRBase documentation (which has been great) but I have some questions I haven't been able to find the answer for.
1. Regarding https://ehrbase.readthedocs.io/en/latest/02_getting_started/05_load_data/index.html#flat-format . How can the flat format be used in an application? Would the application need to parse the web template and construct the paths which map to a specific field/value?
2....
**[RM](https://discourse.openehr.org/c/rm/42)** - [Cross-reference, citations and a solution for managed lists](https://discourse.openehr.org/t/cross-reference-citations-and-a-solution-for-managed-lists/1355)
> [All: this is a long post on an important topic, so I've made it a wiki post i.e. directly editable by others. Feel free to make inline additions, but please try to retain the general integrity. I suggest to add your initials to any additions. Most likely we should create extra topics on each major question described below.]
We have had a long running need to better solve cross-referencing in the openEHR EHR for managed lists such as the Problem List, Allergies list and so on. We've had many...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Bridging the gap between adl-designer and EHRBase](https://discourse.openehr.org/t/bridging-the-gap-between-adl-designer-and-ehrbase/1354)
> Hello all,
I'm working on integrating [adl-designer](https://github.com/openEHR/adl-designer) with [EHRBase](https://github.com/ehrbase/ehrbase).
EHRbase expects an OPT 1.4 as an input, while adl-designer generates OPT2. One of the features of adl-designer is to export to OPT1.4 but it doesn't work due to a missing dependency (opt-exporter-14.jar).
So my questions are:
- Does anybody have opt-exporter-14.jar or a working copy of adl-designer?
- Is there a library I can use to convert...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [NEWS2 - draft openEHR Decision Logic](https://discourse.openehr.org/t/news2-draft-openehr-decision-logic/1340)
> I created a first draft of the [NEWS2 guideline (RCP, 2017)](https://www.rcplondon.ac.uk/projects/outputs/national-early-warning-score-news-2), as another example to exercise the Task Planning/ Decision Logic Module approach to formulating guidelines ([see here](https://specifications-test.openehr.org/releases/PROC/latest/process_examples.html#_national_early_warning_score_news_2)). I have yet to encode the workflow (Task Planning) part.
In common with other guidelines, NEWS2 has some tricky...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [Update and insert Party with two template](https://discourse.openehr.org/t/update-and-insert-party-with-two-template/1338)
> Hi,
Is it possible to insert a party with an opt, and update the same party with another opt:
For example in the first opt we have information about party, partyIdentity , contact, and on the second opt(for update) we have only party and contact.
Thanks
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [What is the process to publish an Archetype?](https://discourse.openehr.org/t/what-is-the-process-to-publish-an-archetype/1337)
> Hi,
I want to know who can I publish an Archetype?
What is the first step?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Conformance Testing](https://discourse.openehr.org/t/conformance-testing/1335)
> Hi!
I'm responsible for autotestion/testing at EHRDB CDR. We've developed a standart solution of openEHR rest api.
So I was wondering for those how to test our solution for conformance certificate. I have tried to get test exmaple from openEHR specification
but links are not available/
Can you help me to get openEHR conformance certificate tests? Or if you haven't it out team can create them.
Thanks,
Nataliya
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [I_DEMOGRAPHIC_SERVICE Interface UV_PARTY](https://discourse.openehr.org/t/i-demographic-service-interface-uv-party/1333)
> Hi everybody,
I am trying to implement Demographic API based on I_DEMOGRAPHIC_SERVICE, but there is not any related information about **UV_PARTY** that is a parameter for **create_party** service.
Do you have any information about this class or its interface.
Thanks,
**[MedBlocks](https://discourse.openehr.org/c/medblocks/90)** - [Medblocks ui calculation](https://discourse.openehr.org/t/medblocks-ui-calculation/1331)
> Hi @Sidharth_Ramesh,
I love your work on medblocks UI. I saw your tutorial https://youtu.be/GRBIUEA_fc8 and I think a webcomponent as an npm package that automatically renders openEHR artefacts is very valuable for the community! I also think you made the right choice to use webtemplate as input artefact.
At Nedap we created something similar to let a user/customer (people with little to no openEHR knowledge) create (hundreds) of forms for a clinimetrics application. We use:
- A (for now)...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Dynamic archetype in slot based on preconditions](https://discourse.openehr.org/t/dynamic-archetype-in-slot-based-on-preconditions/1329)
> I'm using the Procedure archetype and want to record structured details of the procedure under the "procedure details" slot based on what the procedure is. For eg: CPR procedure cluster if the procedure is CPR, Laryngoscopy procedure cluster if the procedure is laryngoscopy etc.
Is there a way to have multiple archetypes under the same slot in a template and choose between them during runtime?
The question is similar to...
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [Anyone using XML for ADL/AOM 2 Archetypes?](https://discourse.openehr.org/t/anyone-using-xml-for-adl-aom-2-archetypes/1327)
> We recently discovered there is no current single standard XML format for ADL 2 archetypes, but instead there are several around. The Specifications-ITS-XML has a schema, but it is incomplete.
Archie currently has an XML Serialization, which is complete, but has some small mistakes in OPT 2 and other_metadata, and some type names aren't correct.
We are trying to get to a single standard format. Which is mainly possible if people are not already using several at the same time.
So, I would...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Archetype IDs starting with a numeric?](https://discourse.openehr.org/t/archetype-ids-starting-with-a-numeric/1318)
> Hi!
We've noticed a behaviour both in CKM and AD where we're not allowed to assign an identifier (the **domain_concept** part of the ARCHETYPE_ID) with 0-9 as the first character. We can't find where this is stated in the specs, and we don't understand why this limitation exists.
Help please? 😊
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [CKM review translations](https://discourse.openehr.org/t/ckm-review-translations/1316)
> What is the current best practice to ask a (known) reviewer on a translation in CKM?
Only found this
> A official CKM translation review functionality has also been put into place to streamline the review of translations.
on: https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2949125/Translate+Archetypes+Using+CKM
**[News](https://discourse.openehr.org/c/community-news/25)** - [openEHR Industry Partner - recent news](https://discourse.openehr.org/t/openehr-industry-partner-recent-news/1314)
> Sharing some recent postings related to our Industry Partners below. If you have openEHR related ‘news’ you would like us to share with the openEHR community via our LinkedIn, Twitter, website news, events or here; please email [comms@openEHR.org](mailto:comms@openEHR.org) with the detail.
**Code24** welcomed a new customer, Vincent van Gogh, who will be using their mConsole module Lab24, an easy openEHR based application for digital communication with laboratories in their...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Where to store demographic data](https://discourse.openehr.org/t/where-to-store-demographic-data/1312)
> Hi! Apologies for the naive question but was wondering for those who have implemented openEHR as a data model for your database how did you go about storing demographic data? Was it done in a separate database, the same one?
Thanks
Dan
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Sharing Archetypes](https://discourse.openehr.org/t/sharing-archetypes/1309)
> Hello Experts,
How do I share an archetype that I have designed in the archetype designer with few other colleagues (or any one in this forum) for their inputs? I was exploring options to do this in the tool but could not find a way.
Any help is appreciated.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [New Oncology Archetypes](https://discourse.openehr.org/t/new-oncology-archetypes/1308)
> Hello from Dr Anjali Kulkarni , trained Radiation Oncologist based in India . Been associated with many tech ventures as Domain consultant . Currently joined a start-up Karkinos Healthcare based in India and we will be using openEHR platform for our oncology data platform . Been reading all resources and very happy to see the help community provides . Would require direction ,inputs from all experts and not so-experts :) about how best we can design Oncology archeytypes , Will post a example...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [EHR_ACCESS in EHRBase](https://discourse.openehr.org/t/ehr-access-in-ehrbase/1306)
> Hi,
I see that there are REST endpoints in EHRBase to handle Compositions, EHR_STATUS, Directory, EHR, Contributions. What about the EHR ACCESS ? Is it possible to create/update the access control settings for the whole EHR?
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [Difference between data points and archetypes](https://discourse.openehr.org/t/difference-between-data-points-and-archetypes/1301)
> > A [modelling *factory* environment](https://www.openehr.org/ckm/) that builds a library of **data points**, known as *archetypes*, ...
For the [newly updated figure](https://www.openehr.org/media/uploads/2021/02/16/openehr_4pillars.svg) and the [primer](https://www.openehr.org/about/what_is_openehr) , a new reader might find a little bit confusing the difference between data points and archetypes.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Fetal Growth Assessment](https://discourse.openehr.org/t/fetal-growth-assessment/1300)
> Hello! We're working on a Fetal Growth Assessment archetype and we're modelling it based on the Child Growth Indicators archetype.
Could you take a look at this and let us know what you think?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [openEHR and IEEE 1107 (devices) - 2014 paper](https://discourse.openehr.org/t/openehr-and-ieee-1107-devices-2014-paper/1297)
> I just came across this - it appears that it might be of interest to people working on any of the devices archetypes. You probably need to login into http://www.academia.edu and I could not find a convenient direct link, but the full PDF if freely available.
## On the Seamless, Harmonized Use of ISO/IEEE11073 and OpenEHR
Jesus D. Trigo, Christian D. Kohl, Aitor Eguzkiza, Miguel Martınez-Espronceda, Alvaro Alesanco,Luis Serrano, Jose Garcıa, and Petra Knaup
2014, IEEE Journal of Biomedical...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Modelling of Swe-PEWS](https://discourse.openehr.org/t/modelling-of-swe-pews/1294)
> Hi,
We are currently modelling archetypes for our Swedish version of Pediatric Early Warning Score (Swe-PEWS). To get some early feedback on our archetypes, I want to share them here with you so you can comment. I have also added some background information to our archetypes below....
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Bind multiple value sets to an dv_coded_text within a template](https://discourse.openehr.org/t/bind-multiple-value-sets-to-an-dv-coded-text-within-a-template/1293)
> Hi there,
in FHIR it is possible to provide multiple value sets/external codings to an element value:
However, in AD Designer it seems the user is limited to choose only one when further contraining a template:
What would be the correct way to represent this in templates? Asking for our modellers.
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Usage of Aliases in WHERE clause](https://discourse.openehr.org/t/usage-of-aliases-in-where-clause/1291)
> Hi all,
I stumbled upon the following expression:
select
a_a/data[at0002]/events[at0003]/data[at0001]/items[at0004]/value/magnitude as Temperature_magnitude,
e/ehr_id/value,
a_a/data[at0002]/events[at0003]/time/value as Time
from EHR e
contains COMPOSITION a
contains OBSERVATION a_a[openEHR-EHR-OBSERVATION.body_temperature.v1]
where
Temperature_magnitude > 37 and
Time>='2017-10-14T09:35:30+00:00'
In SQL, it is not possible to have...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Decision Logic Modules - move data syntax closer to JSON](https://discourse.openehr.org/t/decision-logic-modules-move-data-syntax-closer-to-json/1289)
> As part of an ongoing effort to finalise the DLM language, I've upgraded its representation of static structures, including descriptive meta-data and terminology (logically the same data structures as in archetypes) to nearly JSON5-compliant (i.e. JSON with a few more things). [See here](https://specifications-test.openehr.org/releases/PROC/latest/process_examples.html#_cha2ds2_vasc).
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Moving on from ODIN & beyond JSON (but staying compatible)](https://discourse.openehr.org/t/moving-on-from-odin-beyond-json-but-staying-compatible/1281)
> I've been thinking about whether we might want to update or replace [ODIN](https://specifications-test.openehr.org/releases/LANG/latest/odin.html), the JSON-like format used for representing the meta-data and terminology in archetypes. For those who don't know, ODIN was invented 20 or so years ago, when there was no JSON to speak of, and we've kept using it because it's regular and includes a) a lot more leaf types than JSON, particularly Intervals and Date/time types, and b) type-markers....
**[IHE](https://discourse.openehr.org/c/ihe/104)** - [IHE and openEHR](https://discourse.openehr.org/t/ihe-and-openehr/1278)
> I had a discussion with a board member of the dutch IHE on the combination of IHE with openEHR. He knew there were some examples and I know that at least better has implemented XDS with openEHR, but we don't know of any concrete examples.
Can anyone share some good examples of IHE and openEHR playing nicely together, perhaps some documentation or presenation on use cases that are being used in practice?
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [New Organisational Member, Swedish Association for Medical Informatics](https://discourse.openehr.org/t/new-organisational-member-swedish-association-for-medical-informatics/1277)
> We are delighted to announce that the Swedish Association for Medical Informatics (SFMI) have joined openEHR as Organisational members, [read more here](https://www.openehr.org/news_events/community_news/332) .
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [I finally don’t feel ‘new to openEHR’ anymore](https://discourse.openehr.org/t/i-finally-don-t-feel-new-to-openehr-anymore/1275)
> Just wanted to share that just now I finished reading the EHR information model and finally I feel some familiarity with the openEHR specifications! What a journey:
I read the architecture overview, the new process overview and various paragraphs of the AQL and common information model specifications;
I watched many event recordings and YouTube instructions;
I build archetypes templates and queries and dabbled a bit with the GDL2 editor;
I reviewed new archetypes and participated in...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Reusability in designing archetypes](https://discourse.openehr.org/t/reusability-in-designing-archetypes/1274)
> I’m really interested in hearing your views on reusing (sub parts) of archetypes when designing archetypes.
I’ve been thinking about this for some time, recently with the design of the advance intervention directive (or whatever it’s called this month :p) but what triggered me right now was this example in the EHR model specs: https://specifications.openehr.org/releases/RM/latest/ehr.html#_glucose_tolerance_test
The example shows a single archetype for modelling a glucose tolerance test....
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Rules in archetypes - getting it right](https://discourse.openehr.org/t/rules-in-archetypes-getting-it-right/1272)
> I've been cogitating on how rules could be written properly in archetypes, a topic I never spent sufficient time on in the past. As usual, @pieterbos has pushed the envelope and forced me to think about this more carefully. @borut.fabjan, @yampeku and @sebastian.garde might want to take a look, since they are close to tools. If @ian.mcnicoll could take a look from the authoring point of view it would also be good. (Obviously I would like everyone to have a look, I'm just pinging those group...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Modelling and behavior of of the data type DV_ORDINAL](https://discourse.openehr.org/t/modelling-and-behavior-of-of-the-data-type-dv-ordinal/1271)
> Hi,
We are currently modelling archetypes for Swedish scores and ran into two problems of how the data type DV_ORDINAL is intended to work. Hopefully someone here are able to answer.
The first problem is how values in DV_ORDINAL is possible to specialize in a specialized archetype.
Let say that archetype A contain the DV_ORDINAL D and archetype B specialize archetype A. Assume also that the DV_ORDINAL D in archetype A contain the value 1 which is defined in the text as “>3 l/min”. Is it...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Financial summary archetype ready for publication](https://discourse.openehr.org/t/financial-summary-archetype-ready-for-publication/1269)
> The archetype has been through 2 review rounds. There seems to be consensus among the reviewers. Unless there are objections this archetype will be published on February 11, 2021.
Link to the archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.2989
Please reply to this topic if you have any objections or comments.
**[News](https://discourse.openehr.org/c/community-news/25)** - [Blog by John Meredith, Digital Health.Wales - What is openEHR and why is it so important](https://discourse.openehr.org/t/blog-by-john-meredith-digital-health-wales-what-is-openehr-and-why-is-it-so-important/1265)
> NHS Wales Informatics Services has been carrying out a technical evaluation into openEHR to test its viability as a repository for structured clinical data. The technology will be rolled out soon to support national projects such as Accelerating Cancer and to provide a shared medications record for NHS Wales.
"Adopting openEHR allows NHS Wales to start the transition from the siloed and document bound approach to the emerging open platform"
[Read...
**[Integration](https://discourse.openehr.org/c/integration/63)** - [Business Intelligence tools with openEHR support](https://discourse.openehr.org/t/business-intelligence-tools-with-openehr-support/1264)
> Does anybody know Business Intelligence (BI) tools that support processing openEHR data?
E.g., to generate reports that contain data from openEHR Compositions combined with data from other sources.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [New CDS Guidelines examples - qRisk3, CHA2DS2-VASc](https://discourse.openehr.org/t/new-cds-guidelines-examples-qrisk3-cha2ds2-vasc/1263)
> I've [published a couple more guidelines](https://specifications-test.openehr.org/releases/PROC/latest/process_examples.html#_cha2ds2_vasc) converted from GDL2 format to the emerging [Decision Language](https://specifications-test.openehr.org/releases/PROC/latest/decision_language.html) format. We are interested in informal feedback from clinical people on whether you consider this representation at least somewhat comprehensible, and what could be improved etc. We will have colourisation...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [How to use exclusion archetypes - does not make it work in a clinical setting](https://discourse.openehr.org/t/how-to-use-exclusion-archetypes-does-not-make-it-work-in-a-clinical-setting/1262)
> Hi.
We often struggle with the use of exclusion archetypes as they do not really work in a clinical setting. The last use case we had is for a solution where to register vaccines. Sometimes we need to register that a vaccine is not given. This should - theoretically be modelled by use with the openEHR-EHR-EVALUATION.exclusion_specific.v1 archetype. But in the application it is necessary not only to register that the vaccine is not given, but also to write a reason why it is not given, and a...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Invalid UCUM units in Archetype Designer](https://discourse.openehr.org/t/invalid-ucum-units-in-archetype-designer/1261)
> In the archetype designer, the g/100ml shows up as an option. I don't think this is a valid UCUM unit. Am I missing something?
**[RM](https://discourse.openehr.org/c/rm/42)** - [Partial attestation](https://discourse.openehr.org/t/partial-attestation/1260)
> https://specifications.openehr.org/releases/RM/latest/ehr.html#_composition_class
“A Composition is... ... the unit of attestation by authorising clinicians”
Architecturally it makes sense to attest the entire composition. But in my experience as a resident, a senior clinician often ‘attests’ (by speech) only part of the data in a composition. E.g. when I would examine an abdomen and the surgeon agreed there is a palpable mass. This does not mean the surgeon attests the blood pressure I...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [The redefinition vs extension question](https://discourse.openehr.org/t/the-redefinition-vs-extension-question/1259)
> Following the extensive discussion in [SPECAM-71](https://openehr.atlassian.net/browse/SPECAM-71), I am posting here, to be more visible.
Technically speaking, i.e. according to the current spec, a single-valued attribute is ‘open’ in the same sense as a multiply-valued attribute, such that a child archetype may add (extend) with new constraint objects, as long as they don’t violate the relevant RM attribute, i.e. `ELEMENT.value: DATA_VALUE`, in this case.
In both cases, some new object...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Representation of ethnicity](https://discourse.openehr.org/t/representation-of-ethnicity/1256)
> A conversation has started on the [CKM Discussion page,](https://ckm.openehr.org/ckm/#showGComment_1013.18.1692) but I'm bringing it here to open it up for broader community involvement...
Aljoscha Kindermann started the thread on 22 Jan:
> In the HiGHmed use case cardiology we need to represent e.g. "caucasian ethnicity" and "black skin color" as anamnesis parameters. The ethnicity has been shown to play a role in different disease characteristics in...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Tool support of DV_DURATION](https://discourse.openehr.org/t/tool-support-of-dv-duration/1255)
> Hi everyone,
We've been confused by how modelling tools support the DV_DURATION class. We've come up with a set of hypotheses about how we think this should work ideally, and would like to discuss it with the community. Some of these are trivial, but I'm mentioning them anyway just to avoid any chance of misunderstandings. Hopefully we can agree on a set of guidelines for UI implementation.
1. It should be possible to allow all time units, or select any combination of allowed units to the...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Layman's translations](https://discourse.openehr.org/t/laymans-translations/1253)
> We are translating an archetype (body temperature, specifically the measurement location) to lay mans terms. I'm struggling where to put the layman's terms: in the archetype or in a template, since some users will prefer more official (latin) names and to me it makes most sense to put those latin words in the archetype, and the layman's terms in the template. But we will run into this a lot, and it feels like a waste not to translate in a scalable way (template will probably remain private,...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Rules in archetypes - a migration path](https://discourse.openehr.org/t/rules-in-archetypes-a-migration-path/1252)
> I've been mulling over the old expression syntax that was defined in the rules section of an archetype a few years ago, and that @pieterbos and @yampeku and I have been discussing. The following is an example.
```
rules
$apgar_breathing_value: Integer := /data[id3]/events[id4]/data[id2]/items[id10]/value[id39]/value
$apgar_heartrate_value: Integer := /data[id3]/events[id4]/data[id2]/items[id6]/value[id40]/value
$apgar_muscle_value: Integer :=...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Version tracking in unpublished archetypes](https://discourse.openehr.org/t/version-tracking-in-unpublished-archetypes/1251)
> I just posted this at https://openehr.atlassian.net/browse/SPECAM-72
When we developed the current archetype versioning rules, based on Semver, the rules around unpublished artefact version tracking in Semver was (and still remains) pretty loose.
We decided to live with that in the context of CKM as it uses MD5 hashing to ensure proper 'hook-up' of versions e.g archetypes in templates, and from the perspective of CKM editors/reviewers, strict version tracking is not that useful.
However,...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Clarification re Medication Archetypes](https://discourse.openehr.org/t/clarification-re-medication-archetypes/1250)
> For a patient encounter in an Accident and Emergency cubicle, which Medication archetype would be the most appropriate for use as immediate treatment within the cubicle? We are torn between Medication Management and Medication order.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Swallowing archetypes](https://discourse.openehr.org/t/swallowing-archetypes/1248)
> Does anyone know archetypes (or other information models) about the ability to swallow? I can’t find anything on ckm or apperta or Google.
The usecase would be to record things like choking, safety of different foods etc.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Contribution in general and how to post them in EHRBase](https://discourse.openehr.org/t/contribution-in-general-and-how-to-post-them-in-ehrbase/1241)
> Hi,
I'd like to learn how/when to use the contributions. Due to my ignorance my questions are very basic and maybe naive.
1)The first thing is that I don't have any example of contribution, to learn from, other than the one in the API openEHR specification [https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#contribution] .
Do you have a meaningful example of a contribution?
2)Then I was wondering what's the difference between posting a composition and posting a...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [2 openEHR Events - 16 Feb openEHR for NHS Wales and 23 Feb openEHR Technical Overview](https://discourse.openehr.org/t/2-openehr-events-16-feb-openehr-for-nhs-wales-and-23-feb-openehr-technical-overview/1239)
> Two openEHR Events that might be of interest during February - for further information visit our [website events page](https://www.openehr.org/news_events/events/) )
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [TP-VML - better repeat loop visual figure](https://discourse.openehr.org/t/tp-vml-better-repeat-loop-visual-figure/1238)
> Improved visual figure for TASK_REPEAT (the for-loop like construct) [here](https://specifications.openehr.org/releases/PROC/latest/tp_vml.html#_task_repeats). Still a work in progress, suggestions welcome.
Peek:
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Nice new feature for templates in Archetype Designer](https://discourse.openehr.org/t/nice-new-feature-for-templates-in-archetype-designer/1232)
> The latest version of Archetype Designer adds a new feature which may not be immediately obvious but I am sure many people will welcome.
Previously you could only add a new archetype to a slot if the slot itself was highlighted - then the list of possible archetypes would appear on the right-hand side.
That's fine but it did mean that if you were working on a complex template adding multiple archetypes to a slot, that you had to navigate back up tothe parent slot each time.
No longer!!...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Felaktigheter i modellbeskrivning](https://discourse.openehr.org/t/felaktigheter-i-modellbeskrivning/1231)
> det finns felaktigheter i texten i modellen för ITEM_TREE Instance Structure
[Data Structures Information Model (openehr.org)](https://specifications.openehr.org/releases/RM/latest/data_structures.html)
MVH
Elham
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Fundal Height how is this data captured ? Archetype?](https://discourse.openehr.org/t/fundal-height-how-is-this-data-captured-archetype/1225)
> So we've also been working on the Antenatal Encounter.
In discussions with Ian we were pointed to the Palpation of Uterus cluster archetype and we wondered if there has been any additional work that would superceded this, or thoughts about capturing fundal height as a standalone data point?
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Contraceptive use summary archetype ready for publication](https://discourse.openehr.org/t/contraceptive-use-summary-archetype-ready-for-publication/1224)
> The archetype has been through 3 review rounds. There seems to be consensus among the reviewers. Unless there are objections this archetype will be published on January 20, 2020.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.3273 ](https://ckm.openehr.org/ckm/archetypes/1013.1.3273)
Please reply to this topic if you have any objections or comments.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Adherence/Compliance Archetype](https://discourse.openehr.org/t/adherence-compliance-archetype/1215)
> Hi Everyone!
Happy New Year from Jamaica!
We hope it has been treating you well so far
We have been thinking about creating an Adherence Archetype that could be used to cover a variety of adherence conditions, and wanted to find out if anyone else in the community had been doing work on anything similar.
For our immediate use case scenarios, we are thinking about Medication, Nutrition and Exercise compliance, particularly in reference to Non Communicable Disease management.
We are...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [openEHR Process/CDS Overview - clinical input sought](https://discourse.openehr.org/t/openehr-process-cds-overview-clinical-input-sought/1214)
> I have been working on an Overview specification to provide a better picture of the multiple specifications in the area of Guidelines, CDS, Task Planning and so on.
It is still work in progress, but since one of the things it tries to do is to summarise clinical requirements in this area, we'd like to get some clinical feedback from those who work with guidelines / CDS etc, or are just interested in them.
The [document is...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Help modelling CPR Procedure Details](https://discourse.openehr.org/t/help-modelling-cpr-procedure-details/1213)
> Hi,
I'm trying to model the details of a Cardio-Pulmonary Resuscitation Procedure like:
- Onset of the collapse of the patient
- What time the CPR team was called (Datetime)
- What time the CPR team arrived (Datetime)
- If Chest compressions were given (Boolean)
- If Defibrillation device was used (Boolean)
- What time CPR was stopped (Datetime)
- Initial Rythm of the heart (CodedText)
How should I model this?
I want to put it under the Procedure details slot of the Procedure archetype...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How identify xml tag in archetype paths?](https://discourse.openehr.org/t/how-identify-xml-tag-in-archetype-paths/1207)
>
I have a problem, I need to make an identification to map the path of the archetype and identify it in XML, because I can create the path`s correctly, but how to identify what I have in my XML for the AT`s path, because in XML that is sent has no specification on how to identify
Is there a way today? or is it necessary to pass this information in XML?
example:
Overall test status timestamp
Hi
I wanted some pointers to any effort that is ongoing in developing oncology specific archetypes in openEHR.
Minimal Common Oncology Data Elements (mCode) has an implementation guide in FHIR, but do not see relevant archetypes on the openEHR side.
I have seen the Cancer Reporting project published archetypes in CKM. Any further work happening in that project or others to cover the breadth of mCode ?
thanks
Sangeeta
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Differential diagnoses archetype ready for publication](https://discourse.openehr.org/t/differential-diagnoses-archetype-ready-for-publication/1200)
> The archetype has been through 3 review rounds. There seems to be consensus among the reviewers. Unless there are objections this archetype will be published on January 12, 2020.
Link to the archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.1670
Please reply to this topic if you have any objections or comments.
**[ITS](https://discourse.openehr.org/c/its/41)** - [Inconsistency in REST API Create EHR implementations -needs spec clarification?](https://discourse.openehr.org/t/inconsistency-in-rest-api-create-ehr-implementations-needs-spec-clarification/1199)
> Hi - I am having a little trouble with the POST /ehr call across the Better and EhrBase implementations
// EhrBase
```
{
"_type": "EHR_STATUS",
"archetype_node_id": "openEHR-EHR-EHR_STATUS.generic.v1",
"name": "ehr status",
"subject": {
"external_ref": {
"id": {
"_type": "HIER_OBJECT_ID",
"value": "{{subjectId}}"
},
"namespace": "{{subjectNamespace}}",
"type": "PERSON"
}
},
"is_modifiable": "true",
"is_queryable":...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How to use null_flavor in the flat format?](https://discourse.openehr.org/t/how-to-use-null-flavor-in-the-flat-format/1196)
> My template uses the Glasgow Coma scale.
The Ordinals in the Glasgow Coma scale archetype have a value and a null_flavor within the ELEMENT.
There seems to be a lot of different paths that are being generated for these, based on the tools used.
Using Better's template designer and the paths generated by concatenating the ids on a webtemplate this was...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Linking and Merging EHR IDs](https://discourse.openehr.org/t/linking-and-merging-ehr-ids/1192)
> How does openEHR handle linking of multiple EHR ids which are generated for the same patient?
Ideally, we would like to have 1 EHR id per patient, but sometimes a temporary EHR ID may have to be generated for things like emergency care. Administrative errors are also another reason why this might happen.
How does one handle merging/linking EHR ids in an openEHR data repository (like EHRBase / EHRServer)?
**[RM](https://discourse.openehr.org/c/rm/42)** - [Contradiction in DvQuantified definition](https://discourse.openehr.org/t/contradiction-in-dvquantified-definition/1191)
> Sorry to bother you the day before Christmas about this tiny issue.
I hope you are all in good health
In DvQuantified class is a little but disturbing error:
**less_than** *alias* "<" (
other: `DV_QUANTIFIED[1]`
): `Boolean`
I thinkt the Post result contradicts with the description
- *Post_result*: `Result = magnitude < other.magnitude`
- True if `other` is less than this Quantified object. Based on comparison of `magnitude`.
Please have a look at that when you have time.
Enjoy your...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [openEHR Process, Task Planning and Guidelines Overview](https://discourse.openehr.org/t/openehr-process-task-planning-and-guidelines-overview/1189)
> For those following Task Planning, Decision Language etc, I have made a [major update to the Overview spec](https://specifications.openehr.org/releases/PROC/latest/overview.html). It is still draft, but is getting toward (I hope) a clearer explanation of the kinds of artefacts we deal with in the real world such as care pathways, guidelines, order sets, and care plans, and executable artefacts that could be used to implement them.
All feedback and fixes welcome.
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Multiple Instances in TP](https://discourse.openehr.org/t/multiple-instances-in-tp/1188)
> In the OpenEHR TP specification, in section 6.2.2.2. Repetition, is stated:
The second attribute, `repeat_spec` of type `TASK_REPEAT` enables a Task or Group to be marked as repeating. This is not intended to replace the use of individual Task instances over time, such as repeated medication administrations, but rather to be used to indicate if larger sections (i.e. Task Groups) of planned Tasks are repeatable.
I'd like to ask the meaning of the phrase "This is not intended to replace the...
**[News](https://discourse.openehr.org/c/community-news/25)** - [OpenEyes on openEHR](https://discourse.openehr.org/t/openeyes-on-openehr/1187)
> openEHR and OpenEyes have been close partners from their inception. We have shared common goals and ways of working and a long-held ambition to align the OpenEyes ophthalmology electronic record on the openEHR platform.
The OpenEyes software is now managed under the auspices of the Apperta Foundation. After many years of effort, led and supported by a determined ophthalmology community, its status in the marketplace is now well-established in the UK. OpenEyes is now able to work...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [How to find and hire openEHR consultants](https://discourse.openehr.org/t/how-to-find-and-hire-openehr-consultants/1181)
> Hi!
Is there any open list of consultants with openEHR expertise and ways to contact them?
1. Regular informatics- and IT-consultants with openEHR knowledge and experience is are of interest. This includes for example designers, software developers and system integration consultants.
2. Global experts at a level similar to members of...
* https://openehr.org/programs/clinicalmodels/members or
* https://openehr.org/programs/specification/editorialcommittee
...regarding...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [How convert tag xml in PATH?](https://discourse.openehr.org/t/how-convert-tag-xml-in-path/1179)
>
How to convert XML tags to a path corresponding to the template?
Example -
FOR
[Archetype ID]/magnitude/value
Java language
**[openEHR.br](https://discourse.openehr.org/c/openehr-brazil/17)** - [Conversão de Tag xml em Path correspondente ao do template](https://discourse.openehr.org/t/conversao-de-tag-xml-em-path-correspondente-ao-do-template/1178)
> Alguém sabe me dizer, se existe alguma biblioteca que consiga converter as TAG XML da composição para o Path correspondente?
para [ComposicaoID]/[Archetype]/magnitude/value
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [The Value of Integration Archetypes](https://discourse.openehr.org/t/the-value-of-integration-archetypes/1177)
> Hi all,
We're currently looking at pulling in an awful blob of HL7 v2.? into openEHR and I have read about integration archetypes in the specification. I'm trying to understand if they have value for our use case where we have already taken the XML input and created a data transfer object that represents the input as a basic JSON structure. We are looking at the appropriate component to do this basic conversion but seeking to represent it in a usable, uniform way. This is then mapped to an...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Some confusion about COMPOSITION](https://discourse.openehr.org/t/some-confusion-about-composition/1172)
> I am learning about OpenEHR specifications but cannot clearly understand about the concept behind COMPOSITION. The specification says that a COMPOSITION is a committal unit (i.e. only COMPOSITION can be committed, but not OBSERVATION etc.).
What about if the clinician take history from a patient and commit that history (using Encounter archetype) and then order a laboratory testing. The laboratory report needs to be in a different COMPOSITION (perhaps a Report archetype) because it isn't...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Resource handling in Task Planning](https://discourse.openehr.org/t/resource-handling-in-task-planning/1170)
> Hello,
Where can I find more information on how resources are allocated/released in TP? I have seen there is a Resource_participation class which is referenced from the Performable_action class. Is there something like a Resource_allocation class, in a similar way as Performers are allocated to a Task Plan?
Thanks in advance!
Natalia
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Why do laboratory results belongs to a template?](https://discourse.openehr.org/t/why-do-laboratory-results-belongs-to-a-template/1163)
> I am a beginner to OpenEHR. I'm viewing this template https://ckm.openehr.org/ckm/templates/1013.26.14 . The structure within this template seems to be counterintuitive to me. I think that some of the sections (e.g. lab results, allergic history) should kept separate from that "lump" of structure and the template should only keep references to these sections. Keeping these sections separately also facilitates the reuse of information for contexts other than heart failure clinic.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [What does this error mean?](https://discourse.openehr.org/t/what-does-this-error-mean/1160)
> I'm trying to upload a composition, but I can't find what I'm doing wrong, what can this mean ??
"validationResourceCode": "composition.element.description.required",
"parameters": [
"openEHR-EHR-ADMIN_ENTRY.admission-ubr.v1",
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Fall 2020 webinar recordings avaialble](https://discourse.openehr.org/t/fall-2020-webinar-recordings-avaialble/1158)
> This fall we had multiple webinars on various subjects, the recordings are all online now:
openEHR.nl webinar - Adoption of openEHR in a EHR system ([https://www.youtube.com/watch?v=ajYKZGo8W-Y&t=490s](https://www.youtube.com/watch?v=ajYKZGo8W-Y&t=490s))
openEHR.nl webinar: Pivot Point for Clinical Systems ([https://www.youtube.com/watch?v=dvtj0a9MbRc](https://www.youtube.com/watch?v=dvtj0a9MbRc))
openEHR nl webinar - Open ecosystem for 9 German university hospitals: The HiGHmed Project...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [How to use LIKE in AQL?](https://discourse.openehr.org/t/how-to-use-like-in-aql/1147)
> hello, I'm trying to use a LIKE in AQL, but it doesn't work ... how do I like to search for any place that has this certain date?
How can I do it?
**[LinkEHR](https://discourse.openehr.org/c/linkehr/38)** - [FHIR Logical models from openEHR templates](https://discourse.openehr.org/t/fhir-logical-models-from-openehr-templates/1144)
> Ok here is something really cool.
Take an openEHR template like [ReSPECT-3](https://tools.openehr.org/designer/#/viewer/shared/Pz9zaGFyZWRJZD0xJGQ0MjcyZmVjMWI1MDQ0YjZhNjlmNThlMzNlYTExM2Vk)
hand it to the wizard that is @yampeku
and 10 seconds later back comes this [FHIR logical model](https://simplifier.net/snippet/ianmcnicoll/4)
Very much a first cut...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Covid-19 vaccination](https://discourse.openehr.org/t/covid-19-vaccination/1143)
> This topic is a starting point of a broad discussion, and perhaps a place to share ideas or already made templates on how to structure Covid-19 vaccinations in openEHR. There are archetypes available in the international CKM, but might need tweeking or spesialization. It is anticipated that there will be national requirements that has to be solved locally, but there is a hope that we at least can share a few general structures.
As per now, there will be no formal lead of the work, any...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Reference to the same observation/entry from different templates](https://discourse.openehr.org/t/reference-to-the-same-observation-entry-from-different-templates/1141)
> I am new to OpenEHR and still learning about its specifications. Sorry for asking question already written in the docs.
Suppose that I have a time-series of plasma glucose values (store as an instance of Laboratory result archetype, which is event-type Observation) within an EHR of a particular patient.
How can I build a template for diabetes follow-up that pulls existing plasma glucose values that is stored in the database into field/entry within the template, without rigidly embedding...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Creating and retrieving flat composition](https://discourse.openehr.org/t/creating-and-retrieving-flat-composition/1135)
> Hi,
I'm trying to create flat composition of a template using docker container. I'm facing issues mentioned below after restarting docker composer.
1. During first try I'm able to create a composition, But after restarting, If I commit a composition I will get an error as mentioned below:
{
"error": "java.lang.IllegalArgumentException: Composition missing mandatory attribute: language",
"status": "Internal Server Error"
}
2. Secondly, I'm able to retrieve a composition using...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How to enable and view logs](https://discourse.openehr.org/t/how-to-enable-and-view-logs/1134)
> Hi,
I am using docker container and creating compositions.After multiple restarts not able to create composition.
Is there anyway to enable logs and check ?
Thanks
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How to export templates in opt or xml formate](https://discourse.openehr.org/t/how-to-export-templates-in-opt-or-xml-formate/1131)
> Hi,
I am new to openEHR system. We are using archetype designer for our research. I have created some template using "https://tools.openehr.org/designer". I would like to export these template in XML or OPT format, so that I can use these templates at "https://toolkit.cabolabs.com/app/free_tools".
I can see opt format option available, but it is giving message like "Cannot export embedded template to OPT."
Could you please help me with exporting template in opt or xml formate?...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Managing interval event data in OBSERVATIONs](https://discourse.openehr.org/t/managing-interval-event-data-in-observations/1127)
> Hi all,
From a modelling perspective there are many data points that only make logical sense to be modelled as an Interval event, for example a travel record which should theoretically have a start and end date (date of departure and date of return. Sometimes the end date has not been completed if they are still travelling. Sometimes we need to record where they travelled to, but don't have dates to set the interval.
I'm sure not having all relevant dates for OBS data IRL is a relatively...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Questions about CONTRIBUTION of VERSION](https://discourse.openehr.org/t/questions-about-contribution-of-version-folder/1126)
> Hi all,
I'm designing some new test cases for the openEHR conformance verification, now for the commit of CONTRIBUTIONS with FOLDERS.
The first question is about modification: could an internal FOLDER be modified by a CONTRIBUTION without the full directory structure in it?
That has the consideration that in order to modify an internal FOLDER (not directory) it's uid should be set, which is optional by the spec.
Second question is about the delete change type, which can be broken into...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Build Image From Dockerfile](https://discourse.openehr.org/t/build-image-from-dockerfile/1124)
> Hi,
I'm trying to build EHRBase image from Docker . Seems to be throwing error when i run " docker run ehrbaseorg/ehrbase".
Errors are mentioned below:
1. org.postgresql.util.PSQLException: The connection attempt failed.
2. Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Support for functions](https://discourse.openehr.org/t/aql-support-for-functions/1122)
> in relation with adding support for more function, we created this https://openehr.atlassian.net/browse/SPECQUERY-28.
One of the first thing I wanted to clarify is the situation of `current-date()` and `now()` function still mentioned, not described in the specs. Does any of the AQL implementation supports anything like this?
Somewhere (forgot where) I saw a comment about function being supported as `current_date()`, as the dash `-` sign might be tricky to be allowed, easily confused with...
**[Covid-19](https://discourse.openehr.org/c/covid19-dev/34)** - [SARS-CoV-2 immunisation](https://discourse.openehr.org/t/sars-cov-2-immunisation/1120)
> We are looking for a way to record SARS-CoV-2 immunisation. I found the following archetypes: https://ckm.openehr.org/ckm/archetypes/1013.1.1389/
https://ckm.openehr.org/ckm/archetypes/1013.1.1424
https://ckm.openehr.org/ckm/archetypes/1013.1.3727
But they are all drafts. We will need archetypes for this urgently, since immunisation may (hopefully) start next month. Is there an interest from the community to do this together? I'm thinking about an accelerated review process for those...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Support for TERMINOLOGY function (improved terminology support - SPECQUERY-12)](https://discourse.openehr.org/t/aql-support-for-terminology-function-improved-terminology-support-specquery-12/1119)
> There is a ticket to improve terminology support https://openehr.atlassian.net/browse/SPECQUERY-12 which I was working on in the last few days. Basically my work was to incorporate proposals and decisions being made half year ago in [Terminology Server Invocation in AQL (SEC proposal)](https://openehr.atlassian.net/wiki/spaces/spec/pages/624754994/Terminology+Server+Invocation+in+AQL+SEC+proposal), which is very shortly about adding a function:
* `TERMINOLOGY(operation, driver,...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Archetype_id_constraint](https://discourse.openehr.org/t/archetype-id-constraint/1118)
> Hi everybody, I am trying to find this ARCHETYPE_ID_CONSTRAINT class which is mentioned in AOM2. Does someone know in which specification it is?
Thanks very much in advance.
Best regards
Bert
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Issues/Questions with CONTRIBUTION of EHR_STATUS](https://discourse.openehr.org/t/issues-questions-with-contribution-of-ehr-status/1116)
> Hi, in EHRBASE it was decided to add support for CONTRIBUTION or EHR_STATUS and FOLDER.
I'm in charge of designing the conformance tests and test cases to verify such service and found a couple of cases I would like to discuss with the community.
1. 'incomplete' EHR_STATUS
When committing CONTRIBUTIONs we will have VERSION inside, and VERSION has lifecycle_state which can be incomplete, complete or deleted.
What would it mean to have an 'incomplete' EHR_STATUS? Is that even...
**[Covid-19](https://discourse.openehr.org/c/clin-models-covid19/35)** - [ACEP Covid19 Risk Assessment guideline modelling and analysis](https://discourse.openehr.org/t/acep-covid19-risk-assessment-guideline-modelling-and-analysis/1115)
> It turns out that our work on [Task Planning](https://specifications.openehr.org/releases/PROC/latest/task_planning.html#_conceptual_basis) and [Decision Logic Modules](https://specifications.openehr.org/releases/PROC/latest/decision_language.html#_dlm_syntax) is bearing unexpected fruit...
As part of consulting work for the US Veterans Affairs, I am encoding the [ACEP/evidence.care Covid19 risk assessment...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [ServiceRequest Due date](https://discourse.openehr.org/t/servicerequest-due-date/1113)
> We have recently spent some time on digging into the different types of dates (timestamps) that are needed for planning various types of services, e.g. surgical procedures.
An area of confusion is around what in the ServiceRequest archetype is called **Service Due**. If we look at its definition, it says:
**Description** = The date/time, or acceptable interval of date/time, for provision of the service
**Comment** = This data element allows for recording of the timing for a single service,...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Subject Proxy Service](https://discourse.openehr.org/t/subject-proxy-service/1112)
> For those interested, [here is a reasonable draft of the Subject Proxy Service](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html#_subject_proxy_service), which provides a way to obtain values for subject variables (e.g. date of birth, diabetic status) from back-end systems.
It corresponds to the blue part (bottom left) of this [conceptual architecture](https://specifications.openehr.org/releases/PROC/latest/overview.html#_conceptual_framework).
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [openEHR Webinar 27 November 14:00](https://discourse.openehr.org/t/openehr-webinar-27-november-14-00/1108)
> Join Birger Haarbrandt, Vita Group and Antje Wulff, Hanover Medical School who will talk about the HiGHmed project, a collaboration of 9 German university hospitals that jointly create a data platform based on open standards. [Register for free and for more information.](https://www.eventbrite.nl/e/tickets-een-open-ecosysteem-voor-duitse-universitaire-ziekenhuizen-highmed-project-125336036459)
**[ITS](https://discourse.openehr.org/c/its/41)** - [Template Data Document and Schema?](https://discourse.openehr.org/t/template-data-document-and-schema/1107)
> I am working on an integration with the national Cancer registry. They have a proprietary xml specification. They will do the mapping from canonical openehr xml themselves. The tool they use for mapping is Altova Map Force. Such mapping solutions doesn't work nicely with openehr xml.
To help them I created a generic xslt to transforn openehr xml into a simpler and more tool friendly format. The xstl is here : https://github.com/bjornna/kremt-examples/tree/main/xslt
After working on this...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL semantics: separating RM semantics from AQL semantics](https://discourse.openehr.org/t/aql-semantics-separating-rm-semantics-from-aql-semantics/1106)
> All,
I am afraid I remain in the dark as to why we are talking about making AQL semantics specifically dependent on openEHR RM - I thought [we already agreed to the opposite on this thread](https://discourse.openehr.org/t/specifying-and-implementing-aql-contains/427/3).
We already have the main RM, Demographics, and TP meta-models published and in use, in BMM, JSON-schema, and XSD formats. The class relations can just be looked up, as described in the above-referenced thread.
Not doing so...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Digital utbildningsserie om openEHR nov 2020 - jan 2021](https://discourse.openehr.org/t/digital-utbildningsserie-om-openehr-nov-2020-jan-2021/1105)
> Svensk Förening för Medicinsk informatik ([SFMI](https://www.sfmi.se/) en av [SLS](https://www.sls.se/) medlemsföreningar) och openEHR arrangerar livesända distansutbildningar i olika smaker.
OpenEHR står som värd för:
* 24 nov [openEHRs digitala event](https://www.digitalhealth.net/events/openehr-2020-digital-event/) (internationellt), se även https://openehr.org/
**Uppdatering**: Inspelningar från den internationella dagen kan nu nås via...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL - what do you expect as results for these example](https://discourse.openehr.org/t/aql-what-do-you-expect-as-results-for-these-example/1104)
> # Topic
The following and quite simple AQL will be evaluated with different datasets (A,B,C,D) using either __AND__ or __OR__ . For each case we have defined alternative and possible resultsets. Look at the examples. Which of the answers do you expect? Are there something missing?
Base AQL to be used for all the examples.
```
select o, e from composition c contains (observation o AND/OR evaluation e)
```
Dataset A
```
composition
o1, o2
e1, e2
```
## Alt A -...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Missing EL_CONSTRAINED](https://discourse.openehr.org/t/missing-el-constrained/1102)
> Hi Thomas, the EL_CONSTRAINED class is missing although called as parent from EL_BOOLEAN_EXPRESSION
I don't know what you are planning to put into it. So I used an empty one.
Maybe you can work this out when you have time.
Thanks very much
Bert
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Demographic Organizations and Groups](https://discourse.openehr.org/t/demographic-organizations-and-groups/1100)
> Hello everyone,
I'm trying modelling templates of organizations and groups, but the following question arose:
Should these templates be built based on demographic archetypes or based, for example, on admin_entry archetypes?
Better Archetype Designer only allow templates from demographic person to be built. Is there an alternative to solve the constraint?
Thank you all,
Daniela Oliveira
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR 2020 Digitial Event 24 November - Book your free place now](https://discourse.openehr.org/t/openehr-2020-digitial-event-24-november-book-your-free-place-now/1098)
> Have you booked to attend the openEHR 2020 Digital - Data for Life event?
This FREE unmissable international virtual one-day conference is for anyone interested in the benefits of open data and open software for healthcare.
Taking place on **24 November, 9:30am - 5:30pm GMT** and hosted by Digital Health, join us to discover the latest developments, insights and best practice openEHR case studies from a variety of international digital health leaders, including **Robert M. Wachter, MD**,...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Upgrade grammar to ANTLR4](https://discourse.openehr.org/t/aql-upgrade-grammar-to-antlr4/1090)
> The AQL grammar is now ANTLR3, but there are a number of other variants (vendor defined grammars) in ANTLR4.
Our published grammar needs to be upgraded to latest format - ANTLR4 (which is allegedly cleaner, easier) and synchronized as much as possible with these other circulating variants.
Therefore I created this https://openehr.atlassian.net/browse/SPECQUERY-30.
Do you have any objection or suggestion or any other things that you can share to get this done?
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Support for XOR](https://discourse.openehr.org/t/aql-support-for-xor/1089)
> It is mentioned in a couple of places that AQL is not yet supporting XOR operator, although is part of the grammar - hence this https://openehr.atlassian.net/browse/SPECQUERY-29.
This needs to be clarify: either support it, or remove it completely from specs (relates then to https://openehr.atlassian.net/browse/SPECQUERY-8)
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [Is openEHR vs FHIR a modern version of HL7x vs 13606?](https://discourse.openehr.org/t/is-openehr-vs-fhir-a-modern-version-of-hl7x-vs-13606/1086)
> Been doing some literature review stuff and hit a few papers from 10 years ago (link below) that are focussing on OWL transforms etc. There's a thread from the below paper that positions 13606 and openEHR differences as;
• openEHR was designed to support construction of EHR systems,
• ISO 13606 was designed for exchanging EHR extracts,
Would it be safe to suggest that the historical difference between 13606 and openEHR (message vs persistence) is manifest in the HL7 opposition that we see...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [ADL and AQL visual studio code extension](https://discourse.openehr.org/t/adl-and-aql-visual-studio-code-extension/1085)
> Nedap Healthcare is pleased to announce our new open source visual studio code extension, for editing, validating and working with OpenEHR ADL and AQL files. It brings full ADL 2 language support to visual studio code, including syntax highlighting, document outlines, hover information, syntax and model validation, OPT 2 generation, example RM Object generation, automated terminology code additions and more.
If you have archetypes present in your workspace, you can then create AQL queries -...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Online webinar about open ecosystems - Friday 6th November](https://discourse.openehr.org/t/online-webinar-about-open-ecosystems-friday-6th-november/1079)
> Free webinars organised by openEHR Netherlands Foundation about openEHR and open platforms. The webinars are free of charge after registration. Due to the foreign guest speakers, webinars will be partly English as the working language.
**open ecosystems webinar on 6th November** will discuss what open ecosystems are and look at opportunities and obstacles from both an international and Dutch perspective, with two experts in this field Rachel Duncombe (NHS / openEHR) and Erik Vermeulen...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [AeHIN hour - Covid 19 Webinars - view on line](https://discourse.openehr.org/t/aehin-hour-covid-19-webinars-view-on-line/1078)
> Just in case you missed these previous webinars they are available to view online:-
AeHIN Hour - [The openEHR Community's Response to COVID 19](https://www.youtube.com/watch?v=oAzjHdiioDY&feature=youtu.be)
AeHIN Hour - [Managing COVID-19: Data and Digital Health Initiatives of Southampton, UK](https://www.youtube.com/watch?v=qWoi_qS0yhU&feature=youtu.be)
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [ADL parser error using both se.acode.openehr.parser.ADLParser and org.openehr.adl.parser.AdlDeserializer](https://discourse.openehr.org/t/adl-parser-error-using-both-se-acode-openehr-parser-adlparser-and-org-openehr-adl-parser-adldeserializer/1071)
> We are trying to deserialize an ADL file (ADMIN-ENTRY), but an error occurs when using both ADLParser and ADLDeserializer.
Using se.acode.openehr.parser.ADLParser return this error message:
se.acode.openehr.parser.ParseException: Encountered " "\"at0108\" "" at line 109, column 112.
Was expecting:
"}" ...
at se.acode.openehr.parser.ADLParser.generateParseException(ADLParser.java:7327)
at...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Apply and interrupt a therapy. Sync between tasks](https://discourse.openehr.org/t/apply-and-interrupt-a-therapy-sync-between-tasks/1069)
> Hello everybody,
Regarding the TP specification, if you need to model two parallel tasks, one is a daily medication and the other some lab tests, and you want to interrupt the medication when the lab tests are ready, would a repeatable task be the right way to represent the medication with a terminate-condition (either a system or manual notification from the lab)? is there any other (better) way to represent that? I have seen that task-waits delay the start of the task, but in this case a...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Do we have conflicting definitions for versioning in archetype node ids?](https://discourse.openehr.org/t/do-we-have-conflicting-definitions-for-versioning-in-archetype-node-ids/1063)
> As per LOCATABLE's archetype_node_id definition:
https://specifications.openehr.org/releases/RM/latest/common.html#_locatable_class
> Always in the form of an at-code, e.g. `at0005`
then we say (a few lines below:)
> At an archetype root point, the value of this attribute is always the stringified form of the `archetype_id` found in the `archetype_details` object
huh? what happened to "always" above?
following type of archetype_details...
**[News](https://discourse.openehr.org/c/community-news/25)** - [Industry Partner Code24 upgrade to Gold Members](https://discourse.openehr.org/t/industry-partner-code24-upgrade-to-gold-members/1062)
> We are delighted to announce that existing Industry Partner Code24 have upgraded their membership. @sebastian.iancu comments: -“as our organisation grows, we upgraded our membership in recognition of the work that openEHR do, the value and the benefits we have gained, and in support of work that is crucial to our continued growth.”
Thank you to all our members for supporting what we do and for helping us to do more.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Boston Bowel Preparation Scale](https://discourse.openehr.org/t/boston-bowel-preparation-scale/1058)
> We are working with a customer with an endoscopy solution. Currently we are making model for the Boston Bowel Preparation Scale : https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2951305/
I did find any archetype for this? Do you have any knowledge of such an archetype?
Want to join a session discussion the modelling of this score?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Save the date - openEHR 2020 Digital Event 24th November](https://discourse.openehr.org/t/save-the-date-openehr-2020-digital-event-24th-november/1057)
> Save the date - [openEHR 2020 Digital Event 24th November](https://www.openehr.org/news_events/events/326).
DATA FOR LIFE - International community event.
Online event via livestream will see healthcare professionals, representatives of public health institutions and digital health representatives sharing experience, opportunities, new ideas and vision of future development of the openEHR approach. More information and agenda available soon.
**[ITS](https://discourse.openehr.org/c/its/41)** - [Return=minimal - 204 no-content is confusing](https://discourse.openehr.org/t/return-minimal-204-no-content-is-confusing/1056)
> Although the current REST behaviour, providing a lto of 204 codes, on successful transactions, is correct, it is pretty confusing for developers, and there seems to be no agreement on minimal responses that might trigger 200 or 201 responses that would be expected by a lot of devs.
Could we agree that return=minimal should (at minimal!!) return the contents of the ETag
e.g.
/composition - the uid
/ ehr - the ehr_id/value
etc.
IMO this will make the API much easier to navigate and use.
**[RM](https://discourse.openehr.org/c/rm/42)** - [EHR_STATUS a locatable?](https://discourse.openehr.org/t/ehr-status-a-locatable/1055)
> I've been playing with EHRbase and the REST AP{I and got an error because I had omitted the archetype_node_id and name. This was a new error - it had not occurred with previous versions but according to the example in RST this is correct - EHR_STATUS is a LOCATABLE but there are no EHR_STATUS archetypes that I know of.
What are others doing here? just putting in a dummy archetype node id??
```
{
"_type": "EHR_STATUS",
"archetype_node_id": "openEHR-EHR-EHR_STATUS.generic.v1",
"name":...
**[Community](https://discourse.openehr.org/c/community/10)** - [New discussion category - Integration](https://discourse.openehr.org/t/new-discussion-category-integration/1054)
> We are continually adding new discussion categories. In the Implementation top-level category, we now have the following:
* [Tools](https://discourse.openehr.org/c/implem/tool-dev/36) - building openEHR modelling and other tools
* [Apps](https://discourse.openehr.org/c/implem/app-dev/8) - developing apps that talk to the openEHR platform
* [Platform](https://discourse.openehr.org/c/implem/platform-implem/7) - implementing the openEHR platform
*...
**[Integration](https://discourse.openehr.org/c/integration/63)** - [About the Integration category](https://discourse.openehr.org/t/about-the-integration-category/1053)
> Discussions about implementation of integration components in openEHR products. See Integration/xx categories to discuss mappings, semantics etc.
**[HL7 v2](https://discourse.openehr.org/c/hl7v2/102)** - [HL7 V2 to OpenEHR](https://discourse.openehr.org/t/hl7-v2-to-openehr/1051)
> Hi,
I am wondering if there has been some work done regarding transformation of HL7v2 to OpenEHR compositions ?
Thanks,
Mateen
**[Community](https://discourse.openehr.org/c/community/10)** - [European Health Data Space - Public Health - European Commission](https://discourse.openehr.org/t/european-health-data-space-public-health-european-commission/1050)
> This might be of interest to have on the radar:
https://ec.europa.eu/health/ehealth/dataspace_en
Probably easier said than done, but likely interesting anyway.
It might not be directly openEHR-connected, but health organisations and system providers that want to send data to the "data space" could collaborate on the conversion and transfer mechanisms form openEHR platforms.
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Language in terminology service](https://discourse.openehr.org/t/language-in-terminology-service/1047)
> Hello,
I want to understand [TERMINOLOGY_SERVICE](https://specifications.openehr.org/releases/RM/latest/support.html#_terminology_service_class) so I can correctly implement it.
From my understanding terminology service does not care about language.
So **CODE_SET_ACCESS** should not care about the language too. In that case how should be implemented **has_lang** method? Does it only indicate translation availability in the database?
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Did anybody use the json schema for code generation?](https://discourse.openehr.org/t/did-anybody-use-the-json-schema-for-code-generation/1046)
> Hi,
After spending hours trying to convince various tools/projects to generate source code from the openehr json schemas, I finally gave up.
The schemas are truly extensive, a huge amount of work must have gone into these, so thanks a lot to Code24 for the initial effort and all the other contributors who brought the schemas to their current state.
Am I the only one who tried to use these in the same way we use XSDs? I'm really fighting the urge to express my feelings about json and its...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Decision Logic Module example (RCHOPS21)](https://discourse.openehr.org/t/decision-logic-module-example-rchops21/1045)
> [Here is the NHS RCHOPS21 example](https://wolandscat.net/2020/10/22/clinical-decision-logic-fun/), colourised for readability, in a recent blog post. Comments welcome here.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Implementing BMM in other languages](https://discourse.openehr.org/t/implementing-bmm-in-other-languages/1043)
> I love the openEHR data modelling idea and I’m relatively new here. As a developer, I find it really hard to understand and implement BMMs in my code. I want to, create a javascript client to create composition instances and doing this is not very straight forward. All I’m concerned about is the structure of the data at this point. And I want to send it to an openEHR API endpoint. My question is, why not use something like protobuf that has well established tolling in almost all languages...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Thanks and Congratulations to Tony Shannon, who leaves the openEHR community for a new appointment](https://discourse.openehr.org/t/thanks-and-congratulations-to-tony-shannon-who-leaves-the-openehr-community-for-a-new-appointment/1040)
> It is a pleasure to record congratulations to our colleague of many years, Tony Shannon @tonyshannon on his appointment as Head of Digital Services in the Office of the Government Chief Information Officer of Ireland.
This completes a return home to Dublin for Tony and his family, after many years at Leeds, in England, as Consultant in Emergency Medicine of the principal hospital of that region.
openEHR could not have had a more dedicated and committed member and supporter, for which we...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Linking in openEHR: goals and problems](https://discourse.openehr.org/t/linking-in-openehr-goals-and-problems/1032)
> I'm diving into the world of treatmen/care plan in elderly care and mental healthcare. Especially in elderly care there is a desire to link a goal to a problem. While translating the [goal archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.5012/): I noticed an element named 'clinical indication' that allows for a DV_TEXT entry. I wonder how does a live system link a goal to an actual problem/diagnosis based on the appropriate archetype. So that the system will be able to show an...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Modelling of Genomics data in VCF format](https://discourse.openehr.org/t/modelling-of-genomics-data-in-vcf-format/1030)
> We have a requirement from a PHR application developer to model genomics data into the EHR of the person. From our research so far we feel that a person's VCF file has all the relevant genetic information that will be required in healthcare and so can be assumed to be part of their EHR. While investigating further, we realized that a typical person's VCF file may have 1000s of variant data sets and if we model the VCF file completely, that can add a large amount of data.
We have a couple of...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Adoption of openEHR and what's the value ... Free Webinar 23 Oct 2020, 10:00 BST](https://discourse.openehr.org/t/adoption-of-openehr-and-whats-the-value-free-webinar-23-oct-2020-10-00-bst/1028)
> **Adoption of openEHR in a EHR system, what is the added value for IT suppliers and care providers?**
Join the free webinar being held [date=2020-10-23 time=10:00:00 timezone="Europe/London"], where openEHR Industry Partners, Cambio (Sweden) and Patient Sky (Norway) will look at answering this question. Both are suppliers of an electronic health record system that uses #openEHR.
Further information and book...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Machine processable specs](https://discourse.openehr.org/t/machine-processable-specs/1026)
> Hi Thomas,
Is it possible to have a machine processable spec for BMM?
I could not find it, and I would like to be productive on this.
Thanks in advance for your answer
Bert
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Require / extensible / preferred - redefinition rules in specialised archetypes](https://discourse.openehr.org/t/require-extensible-preferred-redefinition-rules-in-specialised-archetypes/1018)
> The final part of this change I have not yet specified, is the rules of specialisation of a terminology constraint node in a child archetype.
The default is 'required', and the rules are already described [here in the ADL2 spec](https://specifications.openehr.org/releases/AM/latest/ADL2.html#_terminology_constraint_redefinition).
For the other 3 settings in a parent archetype, we need to determine what is allowed in a child archetype. @pieterbos posted an [example parent archetype...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How to retrieve ehrid in ehrbase](https://discourse.openehr.org/t/how-to-retrieve-ehrid-in-ehrbase/1013)
> Supposedly I created an ehr and posted several compositions how do I retrieve the ehrid ?
From the openehr api I see only the method "get ehr summary from subject_id and subject_namespace " (https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#ehr-ehr-get-1) but I tested it in ehrbase and received:
{"error":"No EHR with supplied subject parameters found","status":"Not Found"}
while In the docker console it's written:
org.ehrbase.dao.access.jooq.EhrAccess : Could not...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [OpenEHR and SMART apps on FHIR](https://discourse.openehr.org/t/openehr-and-smart-apps-on-fhir/1009)
> Hello,
Does openEHR API support SMART on FHIR?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [AQL Optional CONTAINMENT question](https://discourse.openehr.org/t/aql-optional-containment-question/1004)
> Hi all,
I have a case where I need to query something like this:
SELECT a/path1, a/path2, b/path3
FROM EHR e CONTAINS COMPOSITION c CONTAINS ACTION a CONTAINS CLUSTER b
WHERE ....
But the "CLUSTER b" could not occur in the data, on that case I still need the a/path1 and a/path2 and expect b/path3 to be NULL, but I think the CONTAINS CLUSTER b will actually filter that result because there is on CLUSTER instance in the data.
How can that query be expressed in AQL to work properly?
Thanks.
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Toegevoegde vertalingen](https://discourse.openehr.org/t/toegevoegde-vertalingen/1003)
> Afgelopen weken zijn verschillende Nederlandse vertalingen toegevoegd aan de CKM:
* Alcohol consumption summary (openEHR-EHR-EVALUATION.alcohol_consumption_summary.v1) https://ckm.openehr.org/ckm/#showArchetype_1013.1.1521
* Blood pressure (openEHR-EHR-OBSERVATION.blood_pressure.v2) https://ckm.openehr.org/ckm/#showArchetype_1013.1.3574
* Body mass index (openEHR-EHR-OBSERVATION.body_mass_index.v2) https://ckm.openehr.org/ckm/#showArchetype_1013.1.2893
* Body weight...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [An openEHR Decision Logic Module (DLM) in colour](https://discourse.openehr.org/t/an-openehr-decision-logic-module-dlm-in-colour/1001)
> Of course, we're still working on it, but here's a sample of what we think can be a readable syntax for clinical guidelines / CDS authors.
Reactions welcome.
**[Releases](https://discourse.openehr.org/c/releases/51)** - [openEHR Reference Model (RM) Release 1.1.0 published](https://discourse.openehr.org/t/openehr-reference-model-rm-release-1-1-0-published/997)
> The [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) has published [RM Release 1.1.0](https://specifications.openehr.org/releases/RM/Release-1.1.0) today.
[Change-log](https://openehr.atlassian.net/projects/SPECRM/versions/12516/tab/release-report-all-issues) | [Issues fixed](https://specifications.openehr.org/releases/RM/Release-1.1.0/issues)
This release brings a number of important improvements to the reference model...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Choice between data element and SLOT?](https://discourse.openehr.org/t/choice-between-data-element-and-slot/995)
> In some use cases, we need to model elements that can be simple or more complex, within the same model. An example is the body site of a diagnosis, which can be as simple as a free text string or precoordinated terminology term, but could also involve aspects, lines, distances from a landmark in a specified direction, or a circular direction around a landmark. Till now we've handled this by putting in a DV_TEXT plus a SLOT for a CLUSTER archetype, like...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Medication models: Where does "route" belong?](https://discourse.openehr.org/t/medication-models-where-does-route-belong/994)
> Currently, we model the medication route in the [INSTRUCTION.medication_order](https://ckm.openehr.org/ckm/archetypes/1013.1.3124) archetype. FHIR, however, places this element inside their [Dosage](https://www.hl7.org/fhir/dosage.html) resource. I'm struggling to understand why they would place it there, as most orders (I'd say 99% if not 100%) are for a single route or at least the same set of possible routes for all dosages/timings, while there may be a significant number of "Dosage"...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Modelling scores with multiple unit options](https://discourse.openehr.org/t/modelling-scores-with-multiple-unit-options/990)
> When modelling certain scores who depend on particular clinical measurements such as lab values, an issue has been identified where the score in question comes in several different versions where the only difference is the units used.
For example, in SOFA score, the element "Respiration" depends on the calculation of a PaO2/FiO2 ratio, which may be given in either mmHg or kPa. This of course means that the threshold values differ between the different units, although they are equivalent when...
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [PARTY data in EHR space](https://discourse.openehr.org/t/party-data-in-ehr-space/985)
> One of the problem mentioned in the last years is that sometimes is difficult to record/use PARTY data in an optimal and clean way inside a COMPOSITION, inside the EHR space.
Off course, there are dedicated places where PARTY information can be captured, like ENTRY.subject, ENTRY.provider and ENTRY.other_participations (see https://specifications.openehr.org/releases/RM/latest/ehr.html#_entry_class), but it seems that there is a demand for a more 'ad-hoc' solution, see following links:
-...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Physical activity archetypes; exercise, steps etc from apps & devices](https://discourse.openehr.org/t/physical-activity-archetypes-exercise-steps-etc-from-apps-devices/983)
> Work has been done to create physical activity archetypes representing physical exercise, steps etc from (personal) health apps & devices in a vendor neutral openEHR based format.
Backround and models can be found in the readme file at the GitHub project https://github.com/regionostergotland/Physical_activity That also contains subdirectories with mindmaps and archetype proposals
### Mindmaps
The directory...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Original text in ADL?](https://discourse.openehr.org/t/original-text-in-adl/978)
> The requirement is to add an 'original_text' attribute to term definitions to handle very wordy but 'official' questions associated with some scales and scores. THe authors/copyright holders are often anxious that these are faithfully represented.
```
["at0027"] = <
text = <"During the past week had difficulty in concentrating">
description = <"Has the patient had difficulty in concentrating">
comment = <"Ensure original text is used in any user interface">
...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [A case for hierarchical value sets](https://discourse.openehr.org/t/a-case-for-hierarchical-value-sets/977)
> There has been sporadic previous discussion about the addition of hierarchical value sets. This is a much needed addition, which would save us from splitting up concepts that should be one element into several. A good example is "Regularity" from Pulse/heart beat (https://ckm.openehr.org/ckm/archetypes/1013.1.4295):
I'd like to revive the discussion about this issue, hopefully to get this defined and implemented in tools as soon as...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Representing the progression of a condition](https://discourse.openehr.org/t/representing-the-progression-of-a-condition/973)
> Good day everyone :slight_smile:
I am trying to work out the most appropriate way to represent the progression and lifecycle of a condition/diagnosis using OpenEHR.
I'm a developer working on a team with clinicians, but I don't have a medical background myself so please forgive my naivety. Some contrived examples I'm trying to work out how to represent are:
* A skin condition that spreads to new body sites over time.
* A cancer that changes "stage" over time and also spreads to new body...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Specialising value set items?](https://discourse.openehr.org/t/specialising-value-set-items/970)
> I'm working on a specialisation of an archetype. The parent archetype has a DV_CODED_TEXT element with internal codes, with SNOMED CT codes bound to each internal code. The specialisation slightly narrows down the definition of each internal code, which I would like to reflect by specialising each code in terms of textual description and which SNOMED CT code is used. AD isn't letting me do this. Is this a tooling issue or a specifications issue?
**[LinkEHR](https://discourse.openehr.org/c/linkehr/38)** - [LinkEHR add archetype to template](https://discourse.openehr.org/t/linkehr-add-archetype-to-template/967)
> I'm trying to create a template in LinkEHR using an archetype I have defined and some other archetypes taken from the openEHR repository, however I am struggling to work out how to include these in my template. I have tried "Export ADL for openEHR editor/ Template Designer", using a archetype slot and just dragging and dropping but I am having no luck.
Is there something obvious I am missing?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - ['Original text' for scales and scores/ instruments?](https://discourse.openehr.org/t/original-text-for-scales-and-scores-instruments/963)
> I had a chat with @vanessap of Better about the challenges of representing some 'long-winded' questions (and some answers) in some scales and scores or other formal 'instruments'
https://eq-5d-tablet-pda-demo.euroqol.org/usa/demo.html?device=t&app=3
The normal openEHR approach is to say that when we give elements names, we are not trying to define exactly wht should be in the UI - te Element names are more like database column names - we want to accurately reflect the meaning of the...
**[MS VisualStudio](https://discourse.openehr.org/c/visual-studio/96)** - [AQL extension for Visual Code](https://discourse.openehr.org/t/aql-extension-for-visual-code/961)
> Today we released and open sourced an extension for Visual Code support syntax highlighting for AQL.
https://marketplace.visualstudio.com/items?itemName=DIPSAS.aql
I've found it pretty useful my self. Go grab it and use it. Contribute if you want.
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [Region Östergötlands openEHR Platform procurement online presentations](https://discourse.openehr.org/t/region-ostergotlands-openehr-platform-procurement-online-presentations/957)
> Region Östergötland (Swedish healthcare region) recently conducted an openEHR platform procurement.
Online presentations and demo sessions in response to the invitation are available to view online [HERE](https://www.youtube.com/playlist?list=PLhWi0RtmG26UIt0qtzmOLITbu10svShMK).
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Region Östergötlands openEHR Pre-procurement online presentations](https://discourse.openehr.org/t/region-ostergotlands-openehr-pre-procurement-online-presentations/956)
> In response to Region Östergötland’s invitation, the pre-procurement online presentation and demo sessions are available online [HERE](https://www.youtube.com/playlist?list=PLhWi0RtmG26UIt0qtzmOLITbu10svShMK)
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL , DATE(TIME) and WHERE](https://discourse.openehr.org/t/aql-date-time-and-where/955)
> AQL with WHERE , and when you "filter" data on some DATE(TIME) without given a specific timezone. Should the AQL engine (the CDR) assume it to be UTC timezone?
I.e.
`WHERE o//value > "2020-31-08T12:04:10"`
Is this equivalent with:
`WHERE o//value > "2020-31-08T12:04:10.0Z"`
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Missing type in generic class call](https://discourse.openehr.org/t/missing-type-in-generic-class-call/954)
> Hi Thomas,
The BMM_ASSIGNMENT class has a property called "target" of type EL_INSTANTIABLE_REF, I think this this is a generic class and should have a type as parameter.
Best regards
Bert
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [For those interested in guidelines / clinical logic, planning](https://discourse.openehr.org/t/for-those-interested-in-guidelines-clinical-logic-planning/953)
> People here interested in solving the problem of guidelines authoring might be interested in some progress I have reported in [this post](https://discourse.openehr.org/t/a-step-towards-visual-clinical-programming/952) - it relates to how to nicely represent logic structures in a way that is more friendly to clinicians.
We would be very interested to get some feedback.
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [A step towards visual clinical programming](https://discourse.openehr.org/t/a-step-towards-visual-clinical-programming/952)
> I have introduced some new syntax ideas into the evolving Decision Logic Module (DLM) language, which is intended to become the formalism for representing next generation GDL guidelines and also decision logic associated with Task Plans. The particular innovation here is to convert what programmers think of as if/then/else chains and also case statements to a tabular approach:
```
rules
|
| This is a case statement on the variable amniotic_fluid_state
|
amniotic_fluid_risk:...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Constraints on Element names in Templates](https://discourse.openehr.org/t/constraints-on-element-names-in-templates/945)
> We try to put a constraint on the element name within a template to enforce the use of a specific value set. However, this does not seem to be supported in ADL Designer and Template Designer. According to the RM this should be allowed. Any hints on this or should we send a request to Better?
**[ITS](https://discourse.openehr.org/c/its/41)** - [API template version](https://discourse.openehr.org/t/api-template-version/941)
> Hello,
I want to implement POST call `/definition/template/adl2/{?version}`.
As I understand, the template version inside the template file and URL can be different.
The URL version is optional. So what version should be used (saved in DB, used for query this exact template) if no version is provided in URL?
From docs I understand but I'm not sure:
if uploading new template: 0.0.1-alpha.1
if uploading template and previous version was 0.0.1-alpha.1 => 0.0.1-alpha.2
if uploading template and...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Lifetime_event?](https://discourse.openehr.org/t/lifetime-event/940)
> In some cases, it's useful to be able to record that an OBSERVATION is a recording for the lifetime of a patient. Examples of this are lifetime maximum blood pressure, or a questionnaire where the patient reports whether they've ever used prednisone (yes/no/unknown). We can technically express this using an INTERVAL_EVENT, but it's a bit cumbersome to calculate the exact lifetime of the patient expressed as a DV_DURATION, and then applying that to the width of the event. I was wondering...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Philosophy fun - model questionnaires literally or via existing archetypes?](https://discourse.openehr.org/t/philosophy-fun-model-questionnaires-literally-or-via-existing-archetypes/939)
> Just to make all the people who do serious modelling of actual questionnaires crazy, I'd like to a raise a philosophical question: should we model questionnaires as literal tree structures isomorphic to the implied tree structure of the forms they are usually expressed as? Or should we attempt to represent every question / option / field using some existing archetype data point? Let's call this the *literal* versus *semantic* approach.
NB: When I say 'we', I of course mean 'you', the...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Capillary refill time about to be published](https://discourse.openehr.org/t/capillary-refill-time-about-to-be-published/935)
> This archetype has gone through 1 review, and there seems to be no major objections on the design. Final version can be found here: [https://ckm.openehr.org/ckm/archetypes/1013.1.4685](https://ckm.openehr.org/ckm/archetypes/1013.1.4685)
Please have a final look, and reply here if there are any errors.
The archetype will be published August 27th 2020 if no objections.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [PaO2/FiO2 ratio about to be published](https://discourse.openehr.org/t/pao2-fio2-ratio-about-to-be-published/934)
> The archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published on August 27th.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.4537/tabbed](https://ckm.openehr.org/ckm/archetypes/1013.1.4537/tabbed) .
Please reply to this topic if you have any objections or comments.
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Addition of required / extensible / preferred / example terminology constraint to AOM and ADL](https://discourse.openehr.org/t/addition-of-required-extensible-preferred-example-terminology-constraint-to-aom-and-adl/933)
> The openEHR SEC has decided on the addition of the `required | extensible | preferred | example` 'binding strength' constraint modifier, following the [model used in HL7 FHIR](https://www.hl7.org/fhir/terminologies.html#strength). The change is documented in [openEHR CR SPECAM-68](https://openehr.atlassian.net/browse/SPECAM-68).
The change to AOM2 spec looks like this in the UML:
We have yet to determine how it should...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Questionnaire or summary？](https://discourse.openehr.org/t/questionnaire-or-summary/928)
> Hi, everyone!
Is there any existing archetype to express the relationship above, if not, is it necessary to create a new archetype? I've tried *Symptom/sign qustionnaire* and *Problem/diagnosis*, but both cannot conclude medications. I think it is difficult to express the relationship between disease and its medication. :thinking:
I would appreciate it very much if anyone can give me some advice~~
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Ability to model ism_transitions](https://discourse.openehr.org/t/ability-to-model-ism-transitions/927)
> I'm increasingly of the opinion that modelling of the specific ism_transitions is fraught with danger because it is really hard to model these with a universal use case in mind.
Inevitably, no matter how universal we intend to be, we end up being too specific or not specific enough for any given use case. So perhaps these should be added at the template level, rather than fixed (often unusably) at the archetype level. Or maybe archetype the easily universal ones, and allow the list to be...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [ACTIONs in ADesigner](https://discourse.openehr.org/t/actions-in-adesigner/926)
> Just finding a use case where the states required are aligned with the ism_transition grouping ie 'Initial', 'Completed', 'Active', 'Postponed', 'Cancelled', rather than the specific steps.
So it's got me wondering about being able to model at the category level, as well as the option to model the next level of detail with each specific step.
Thoughts?
Heather
**[Community](https://discourse.openehr.org/c/community/10)** - [The Use of SNOMED CT in openEHR data models - video and slides available now](https://discourse.openehr.org/t/the-use-of-snomed-ct-in-openehr-data-models-video-and-slides-available-now/924)
> Ian McNicoll recently presented on The Use of SNOMED CT in openEHR data models. Links to the video and slides are available from https://www.openehr.org/news_events/event_reports/15
**[Community](https://discourse.openehr.org/c/community/10)** - [Free Clinical webinars for clinicians working with SNOMED CT](https://discourse.openehr.org/t/free-clinical-webinars-for-clinicians-working-with-snomed-ct/920)
> Free Clinical Web Series - a collection of monthly 90 minute webinars where clinicians working with SNOMED CT share their real-world experiences. [https://www.snomed.org/news-and-events/events/web-series](https://www.snomed.org/news-and-events/events/web-series)
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Task Planning BMM model issues in AD](https://discourse.openehr.org/t/task-planning-bmm-model-issues-in-ad/917)
> Just used AD today, and the class `CAPTURE_DATASET_SPEC` (which is visible in the editor when you edit a Task) has a field called `archetype_id`, but this should be `template_id`.
Here is the relevant line from the [current Task Planning BMM on Github](https://github.com/openEHR/specifications-ITS-BMM/blob/master/components/PROC/Release-1.6.0/openehr_proc_task_planning_latest.bmm#L952). This is unchanged from v1.5.0, and wasn't present in v1.0.0, so I am not sure which BMM AD is using (maybe...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Simplified JSON data formats for openEHR](https://discourse.openehr.org/t/simplified-json-data-formats-for-openehr/915)
> For those interested, [here is a wiki page](https://openehr.atlassian.net/wiki/spaces/spec/pages/624361477/Simplified+Serial+Formats+-+Data+Types) on which we are refining so-called simplified (JSON) data formats for representing EHR data when talking through openEHR REST APIs, and maybe in other contexts.
This is likely to be relevant if you use EhrScape, EhrBase, EtherCIS among other products.
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Inheritance situation in BmmSchema and PBmmSchema](https://discourse.openehr.org/t/inheritance-situation-in-bmmschema-and-pbmmschema/906)
> PBmmSchema inherits from PBmmPackageContainer and BmmSchema
BmmSchema inherits from PBmmPackageContainer and BmmModelMetaData
This double, because BmmSchema already inherits from PBmmPackageContainer and PBmmSchema inherits from BmmSchema, it is an double that PBmmSchema also inherits PBmmPackageContainer
I think this is an error because it does not add any logical functionality but it causes confusion.
Best regards
Bert Verhees
**[ITS](https://discourse.openehr.org/c/its/41)** - [Simplified Data Template (SDT) - Behavior](https://discourse.openehr.org/t/simplified-data-template-sdt-behavior/905)
> Hi everybody,
we are currently implementing the simSDT format in EHRbase respectively the openEHR SDK. However, we found some behavior that is not defined in the current spec.
For example, in the Better implementation, the ctx/origin is set automatically from ctx/time. If I remember correctly, the composer is also set automatically using the session information of the user.
In my opinion these things have to explicitly described, otherwise clients might not be able to directly work with...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Best practice for updating templates](https://discourse.openehr.org/t/best-practice-for-updating-templates/904)
> Hi all,
I'm new to openEHR and have been playing around with ehrbase. I am wondering what is the best practice for updating a template that has been uploaded to an openEHR server.
I have noticed in the REST spec that there is no DELETE or PUT/PATCH endpoint for templates, and in my experimenting with ehrbase it prohibits me from uploading a template with the same `template_id`. My impression is therefore that templates can not be deleted or updated and the `template_id` must be unique...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Burn injuries and affected body surface estimations (%TBSA etc.)](https://discourse.openehr.org/t/burn-injuries-and-affected-body-surface-estimations-tbsa-etc/902)
> Hi!
We are preparing to partially reimplement/transition an old software system for advanced burn injury care into an openEHR and Snomed CT based system. Is anybody else involved in similar work or interested in modeling of burn related archetypes and templates?
Based on the multitude of methods (and variants of them) used for assessing the relative body surface area affected by burns (and other skin-related conditions) I have made a first go att integrating many of them into two flexible...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [OPT annotations inconsistencies](https://discourse.openehr.org/t/opt-annotations-inconsistencies/901)
> Hi all,
I was checking some OPT samples I have, that were generated using different modeling tools.
Here you can see items contains a text node, while in the second example items contains a value element that contains a text node:
Example 1:
PFA53
...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Querying actions by their ism_transition/current_state](https://discourse.openehr.org/t/querying-actions-by-their-ism-transition-current-state/900)
> Hi all,
While testing EHRBASE and EHRSCAPE trying to get ACTIONs that have a specific ism_transition/current_state, the results are empty.
Context:
We have this action template: https://github.com/ehrbase/ehrbase/blob/develop/tests/robot/_resources/test_data_sets/valid_templates/minimal/minimal_action_2.opt
And generated a JSON instance based on that one, that has:
"ism_transition": {
"current_state": {
"value": "planned",
...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [DV_PROPORTION.is_integral in OPTs and validation rules](https://discourse.openehr.org/t/dv-proportion-is-integral-in-opts-and-validation-rules/899)
> Hi all, I'm working on testing a server, and found for DV_PROPORTION a constraint for "is_integral" ends up in the OPT: https://github.com/ehrbase/ehrbase/blob/develop/tests/robot/_resources/test_data_sets/valid_templates/minimal/minimal_action_2.opt#L247-L273
By the spec, "is_integral" is a function, not a field, so that constraint looks strange there. Is that a bug of the modeling tools?
Looking at the spec definition for is_integral(), the description is a little confusing: "True if the...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [How to call external service](https://discourse.openehr.org/t/how-to-call-external-service/885)
> Hi all,
We have a requirement to call a web service to fill items of a DvCodedText. Besides, we used the Archetype Editor(Ocean) application which we could set terminology for a DvCodedText element that it seems like a web service. But I can not customize this feature.
Now, I want to now how can define external web service in the structure of archetype to load data from external system.
thanks
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Task Planning / GDL3 progress](https://discourse.openehr.org/t/task-planning-gdl3-progress/881)
> I have created a [wiki page](https://openehr.atlassian.net/wiki/spaces/spec/pages/842924037/GDL3+-+reworked+CHOPS-21+Example) with the latest increment of TP / GDL3 syntax and architecture proposals.
Feel free to discuss here, and/or attach comments to that page.
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [How to associate a Composition with a Folder?](https://discourse.openehr.org/t/how-to-associate-a-composition-with-a-folder/876)
> I have never used FOLDERs in anger. Just cannot figure out how to associate a composition/contribution with a FOLDER, either in Better Ehrscape or the openEHR REST API.
Any pointers?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - ['AeHIN hour' online meeting - slides and audio "The openEHR community's response to COVID-19"](https://discourse.openehr.org/t/aehin-hour-online-meeting-slides-and-audio-the-openehr-communitys-response-to-covid-19/875)
> Colleagues from the openEHR community describe how they collaborated and shared information models to respond to the COVID-19 crisis, producing a library within CKM using early work of Industry Partners creating openEHR information models that can be aggregated and mapped.
[Slides with audio are available to view now](https://youtu.be/oAzjHdiioDY).
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Inheritance in Collections in Java](https://discourse.openehr.org/t/inheritance-in-collections-in-java/874)
> There is a problem when doing inheritance on collections in Java. It is about the classes about BmmDecisionGroup, etc.
They all have the property collection branches, and the parametrized class in the collection also has a type which is inheritable from along the same line.
The Java architects decided long ago that this does not work, they always kept it that way. I stumbled on it a few times already in the past, because I forget it and then rediscover it.
This does not work, compiler...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Is a Score an Observation or an Evaluation (philosophy fun)?](https://discourse.openehr.org/t/is-a-score-an-observation-or-an-evaluation-philosophy-fun/871)
> In recently reviewing the various obstetric archetypes from @danielle.santosalves, and many other archetypes over the years, and perusing CKM, I had a thought about whether scores are Observations or Evaluations.
Just to start a little fun controversy, I thought I would suggest how this should be decided and see what modellers think.
Firstly, the interesting thing about a score is that it is intended to generate some level of 'assessment' beyond the phenomena it observes. An Apgar...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Contacts in demographics](https://discourse.openehr.org/t/contacts-in-demographics/870)
> Hi
We had just embraced the difficult task of using OpenEhr demographics, and we are stuck at “contacts”. It seems that “contact class” only allowed address to be referenced. I try specialized, using a slot inside the contact class , but the constrain by default doesn’t allowed to reference other archetype ( like “communication details” ). Any thoughts how to propeller handle this situation
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Task Planning Specification questions](https://discourse.openehr.org/t/task-planning-specification-questions/867)
> Hello,
During an analysis of the [TP specification](https://specifications.openehr.org/releases/PROC/latest/task_planning.html), some questions arose that I would like to discuss:
1) The class CALENDAR_ENTRY has no properties in the specification. I think it would be pertinent to specify these properties since it seems incomplete. What do you think?
2) The class M_CALLBACK is not defined in the specifications despite being defined in...
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [openEHR and Covid-19 deployments](https://discourse.openehr.org/t/openehr-and-covid-19-deployments/864)
> Hi all,
From time to time I have the need to list deployments using or been inspired by openEHR related to Covid-19. Currently Deloitte is about to publish some report on Europeean eHealth, and I was interviewed related to our Covid-19 application.
It would be great to have a concrete list of vendors/hospitals/solutions to be used in such publications.
I open this topic to get some input.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - ["Medication dosage based on..."](https://discourse.openehr.org/t/medication-dosage-based-on/861)
> I've been presented with a medication dosing use case that I haven't seen before, and that I'm not certain how to model. The requirements are as follows:
* A structured dosage and timing is recorded, for example "20 mg three times a day"
* This dosage is based on a mental calculation by the prescriber, based on a parameter of the patient, for example weight, age or body surface.
* We need to be able to record, in a coded element, which parameter the dose is based on, and a free text comment...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [DICOM compliance of OBSERVATION.imaging_exam_result](https://discourse.openehr.org/t/dicom-compliance-of-observation-imaging-exam-result/857)
> Hi all,
Let me please introduce myself. My name is Christian, I am working at the German Cancer Research Center in the HiGHmed project. We are working on Radiomcis image analyses and use the archetype OBSERVATION.imaging_exam_result.
We had the requirement to represent certain DICOM tags with the archetype, which are not covered by the current one. We have found that the existing archetype is difficult to extend. Therefore, we created a specialization of the archetype.
(please see...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Vertaling: Report](https://discourse.openehr.org/t/vertaling-report/851)
> Ik heb een Nederlandse vertaling toegevoegd aan het Report archetype, deze is beschikbaar op https://ckm.openehr.org/ckm/archetypes/1013.1.4856
Feedback is welkom
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Terminologies in the template](https://discourse.openehr.org/t/terminologies-in-the-template/847)
> Hey everybody,
I have one question. I am currently working on a template in Marand and would like to add SNOMED codes for the antibiotic in addition to the LOINC coding. Do you know how to do that? Do you think it works? I want to add a LOINC coding and a SNOMED coding for the same antibiotic.
regards
Sarah Ballout
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Clinical Data Repository step by step guide](https://discourse.openehr.org/t/clinical-data-repository-step-by-step-guide/842)
> From data definition to data query for Clinical Decision Support with #openEHR https://www.cabolabs.com/blog/article/how_to_work_with_an_openehr_clinical_data_repository__step_by_step-5c51bc1c3ac69.html
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Procedure or not procedure?](https://discourse.openehr.org/t/procedure-or-not-procedure/841)
> [ACTION.procedure](https://www.openehr.org/ckm/archetypes/1013.1.204) is a great archetype and it is published a long time ago. I guess all reading this post know the archetype and has some opinions on how to use it.
Surprisingly we discovered that we had really different views on the scope for the archetype. This appeared to my [during this thread](https://www.openehr.org/ckm/#showAComment_1013.18.1628_1013.1.204) with Heather on the openEHR CKM.
This post is an invitation to share...
**[News](https://discourse.openehr.org/c/community-news/25)** - [Better and openEHR International Archetype Designer Launched](https://discourse.openehr.org/t/better-and-openehr-international-archetype-designer-launched/840)
> Industry Partner Better and openEHR International have launched Archetype Designer, a web-based clinical modelling environment for openEHR archetype development. [https://tools.openehr.org/designer](https://t.co/ASUHUF353R?amp=1)
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [Archetype Designer Launched](https://discourse.openehr.org/t/archetype-designer-launched/839)
> Better and openEHR International have launched Archetype Designer, a web-based clinical modelling environment for openEHR archetype development. [https://tools.openehr.org/designer](https://t.co/ASUHUF353R?amp=1)
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR Specifications Editorial Committee (SEC) News](https://discourse.openehr.org/t/openehr-specifications-editorial-committee-sec-news/837)
> In recent months we have made a number of new additions and changes to the openEHR SEC, the international group that manages the [openEHR specifications](https://specifications.openehr.org), which we are very pleased to announce.
Our new members:
* [Pieter Bos](https://www.openehr.org/programs/specification/editorialcommittee#pieter-bos), [Nedap](https://www.openehr.org/community/industry_partners_detail/nedap-nv), Netherlands [April 2020]
* [Birger...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - ['AeHIN hour' online meeting - "The openEHR community's response to COVID-19"](https://discourse.openehr.org/t/aehin-hour-online-meeting-the-openehr-communitys-response-to-covid-19/836)
> Tuesday, July 7, 2020
2100 (GMT+8)
Speakers:
* @ian.mcnicoll (UK) - kickstarting the project & NO implementation; -
* @paolo.anedda (IT) - Italian implementation;
* @heatherleslie (AU) & @siljelb (NO) - Managing evolving archetypes in the COVID-19 incubator and project
* @lvxd (CN) - Dataset for official Chinese guidelines & Wuhan CDS implementation
[Register here](https://zoom.us/meeting/register/uZcrde-orj0v8bwyCSX40TiJ9sN7t8XoVQ)
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Retrospective fix for tagging the form of BMM / P_BMM in use today](https://discourse.openehr.org/t/retrospective-fix-for-tagging-the-form-of-bmm-p-bmm-in-use-today/835)
> A question I originally posed to SEC, but more widely relevant, so moved here...
Due to my lack of proper management of the BMM spec, back in ~2018 when I wasn't sure if it was being used, I failed to ensure that we created a release of the state of BMM corresponding to a) the code in ADL Workbench (which is known working), b) Archetype Designer, which if I am not mistaken uses Better code based on the same version of the spec and c) Archie.
The version that matters is [this one in the BASE...
**[openEHR.cn](https://discourse.openehr.org/c/openehr-china/19)** - [3rd openEHR Asia Summit, 24th July by Zoom Conferencing](https://discourse.openehr.org/t/3rd-openehr-asia-summit-24th-july-by-zoom-conferencing/834)
> * Date: 10:00-12:30, July 24, 2020 [2am - 4.30am UK]
* Online: Zoom access will be available to the registered persons
This is the 3rd openEHR Asia summit. All those interested in openEHR activities in Asia, especially for COVID-19; welcome.
Programme below and book [HERE](https://openehr.connpass.com/event/181317/)
* 10:00-10:05 Opening remarks (Shinji Kobayashi, Japan)
* 10:05-10:35 Perspective/overview on the work behind the openEHR CKM COVID-19 Project (Heather Leslie, Australia)
*...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [3 July ZIBs openEHR online working group meeting](https://discourse.openehr.org/t/3-july-zibs-openehr-online-working-group-meeting/833)
> The next ZIBS openEHR working group meeting (online) is being held on 3 July at 10:00 BST and will look at mapping for Blood Pressure and Contact ZIBs.
More information and register [HERE](https://www.eventbrite.nl/e/werkgroep-zibs-voor-openehr-vrijdag-3-juli-2020-tickets-111197284070)
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [The 3rd openEHR Asia Summit](https://discourse.openehr.org/t/the-3rd-openehr-asia-summit/831)
> ## Date and Venue
* Date: 10:00-12:30, July 24, 2020
* Online: Zoom access will be available to the registered persons
## Summary
This is the 3rd openEHR Asia summit. We welcome the people who are interested in openEHR activities in Asia, especially for COVID-19.
## Programme
* 10:00-10:05 Opening remarks (Shinji Kobayashi, Japan)
* 10:05-10:35 Perspective/overview on the work behind the openEHR CKM COVID-19 Project (Heather Leslie, Australia)
* 10:35-11:05 Modeling works for COVID-19...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Modeling constraints at TP-VML](https://discourse.openehr.org/t/modeling-constraints-at-tp-vml/828)
> Does TP-VML consider to cover also modeling constraints and guidance? Having these set in its metamodel would allow creating only syntactically "legal" models. Examples of such constraints are mandatory values, uniquenesss, legal kind of connections between elements etc.
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [How to avoid multiple inheritance](https://discourse.openehr.org/t/how-to-avoid-multiple-inheritance/826)
> 
This is a part of the inheritance schema from the BMM, the part with the three classes which have multiple inheritance in pink, and on the right and left where they inherit from, left are interfaces because that is a Java-trick to do multiple inheritance.
But the trick is not good enough, especially in Spring, and calling superclasses to return subclasses, there are problems. So this brought me to thinking.
I...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [CURB-65 (OBSERVATION.curb_65)](https://discourse.openehr.org/t/curb-65-observation-curb-65/825)
> This archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published on June 30.
Link to the archetype: https://openehr.org/ckm/archetypes/1013.1.4695
Please reply to this topic if you have any objections or comments.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [CRB-65 (OBSERVATION.crb_65)](https://discourse.openehr.org/t/crb-65-observation-crb-65/824)
> This archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published on June 30.
Link to the archetype: https://openehr.org/ckm/archetypes/1013.1.4694
Please reply to this topic if you have any objections or comments.
**[RM](https://discourse.openehr.org/c/rm/42)** - [Where is the security information model?](https://discourse.openehr.org/t/where-is-the-security-information-model/820)
> The [landing page of specifications](https://specifications.openehr.org/) does not contain the word security.
The EHR information model specifications refer to ACCESS_CONTROL_SETTINGS claiming it is in the Security Information model :
> ...by an instance of a subclass of the abstract class `ACCESS_CONTROL_SETTINGS` , **defined in the Security Information Model**
and [architecture overview](https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html) refers to it...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHRnl free webinar, 26 June - Explore how Covid-19 openEHR models](https://discourse.openehr.org/t/openehrnl-free-webinar-26-june-explore-how-covid-19-openehr-models/813)
> openEHRnl webinar 26 June 1000 - 1100 BST. Explore how Covid-19 openEHR models were developed and used in international use cases. The webinar is in English and open to anyone interested. For more information see [https://www.openehr.org/news_events/events/314](https://www.openehr.org/news_events/events/314)
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Free openEHRnl Webinar 26 June - how Covid-19 openEHR models were developed](https://discourse.openehr.org/t/free-openehrnl-webinar-26-june-how-covid-19-openehr-models-were-developed/811)
> openEHRnl webinar 26 June. Explore how Covid-19 openEHR models were developed and used in international use cases. The webinar is in English and open to anyone interested. For more information see https://www.openehr.org/news_events/events/314
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [BMM statements - initial draft](https://discourse.openehr.org/t/bmm-statements-initial-draft/810)
> Draft simple [meta-model of some basic statement types](https://specifications.openehr.org/releases/LANG/latest/bmm.html#_routine_implementation_2), to serve needs in GDL and TP.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [General question on use of specialisation (particularl in Clusters)](https://discourse.openehr.org/t/general-question-on-use-of-specialisation-particularl-in-clusters/805)
> I was perusing CKM recently looking for archetypes to plug into a slot whose logical definition is 'any kind of physical examination'. This seem doable, since CKM has a specialisation hierarchy:
However, I see no specialisation for some other archetypes where I would expect to see it, e.g. the genetic ones below:
If I wanted to create a slot...
**[Covid-19](https://discourse.openehr.org/c/clin-models-covid19/35)** - [NZ Contact tracing national dataset](https://discourse.openehr.org/t/nz-contact-tracing-national-dataset/804)
> "The purpose of the standard is to ensure that all data collected and used in the contact tracing process is well-defined, properly structured and coded, and supports interoperability. The initial focus is about supporting the consumer registration process and recording consistent information about customers and visitors to business locations."
https://www.health.govt.nz/publication/hiso-100852020-covid-19-contact-tracing-data-standard
Might be useful. Nearly all of it is demographics....
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Will an openEHR implementation provide UI to create and render records based on a template?](https://discourse.openehr.org/t/will-an-openehr-implementation-provide-ui-to-create-and-render-records-based-on-a-template/799)
> Dear community,
I'm working on a medical project and I need to store EHRs in the system. I have some basic questions about the regular flow to store, retrieve, and render records with openEHR.
As I understand an openEHR implementation like EHRServer or EtherCIS provides both frontend and backend solutions. After I install an implementation and upload a template from CKM there, will it provide any UI like a form to create records based on the template? Or I will need to create the records...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Does AQL support Demographic query?](https://discourse.openehr.org/t/does-aql-support-demographic-query/796)
> OpenEHR Demographic is used to represent the party and party relationships. I want to know if AQL spec can support demographic query?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Observation for ISS...or cluster?](https://discourse.openehr.org/t/observation-for-iss-or-cluster/791)
> Hi all,
I stumped @ian.mcnicoll with this one. He had a moment when I flagged it up which is always a nice thing to trigger... but!
Here is a lovely archetype for Myeloma Staging that I have built with a colleague: [Multiple Myeloma Revised International Staging System](https://ckm.apperta.org/ckm/archetypes/1051.32.1058).
Most cancer based staging archetypes have been Clusters, however our requirement is to attribute a Date that the stage was agreed. Therefore it strikes me more of an...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Software Development Kit for app development](https://discourse.openehr.org/t/software-development-kit-for-app-development/790)
> Hi everybody,
as you might know, we are working on an open source SDK (https://github.com/ehrbase/openEHR_SDK) with the aim to make application developers love to work with openEHR. As this is developed against the official openEHR REST API and aims to be 100% vendor-neutral, this is something that should be of general interest to the community, including other vendors. From my point of view, it is absolutely crucial that people who are new to openEHR are able to get their first application...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Form creation from OpenEHR Templates](https://discourse.openehr.org/t/form-creation-from-openehr-templates/780)
> Hi,
I am wondering if there is a tool to create PDF forms from OpenEHR Templates. I used Ocean Template Designer to create OFD form and got it compiled and running (attached) but export somehow doesn't work. I tried exporting in VB code as well as in C#. In addition, I also tried with XML but couldn't figure out a way to create a full featured PDF form which can be shown to clinicians before further steps.
I also had a quick look at Better Studio and LinkEHR but couldn't find any option. I...
**[Covid-19](https://discourse.openehr.org/c/clin-models-covid19/35)** - [Paper about COVID-19 data set collaboration?](https://discourse.openehr.org/t/paper-about-covid-19-data-set-collaboration/771)
> Hi all,
In response to yesterday's publication of the paper on the [Chinese COVID19 data set](https://www.jmir.org/2020/6/e20239/) and the [EY report](https://www.ey.com/en_gl/health/how-will-you-design-information-architecture-to-unlock-the-power) highlighting the need for common semantics, I've been thinking that it would be a great opportunity to gather together information/insights/experiences/case studies about all openEHR data sets developed in response to Coronavirus.
Ideas include...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Renaming in Templates with coded text constraint](https://discourse.openehr.org/t/renaming-in-templates-with-coded-text-constraint/767)
> Hi everybody,
I hope you can help me with this n00b question. When using the Template Designer or Archetype Designer, I'm not able to find a function to use a contraint on a coded text field for names. For example, I would like to rename an adhoc section and only allow a coded text which is encoded by a specific loinc code (for example "Plan of Care Synopsis" with code 57197-6 (https://loinc.org/57197-6)).
From the RM perspective, I think this should be possible.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [References on modelling styles?](https://discourse.openehr.org/t/references-on-modelling-styles/766)
> I've had a question from a colleague about scientific basis for modelling styles, which I had to say I don't know of. The specific example was how to model a diagnosis with qualifiers, for example the diagnosis "renal tubular atrophy" with modifiers "not detected, light, moderate, pronounced, not classified".
We may have our professional opinions about how this should be modeled for the greatest possible expressivity, scalability and safety, but does anyone know of any published works that...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Query API possible issue](https://discourse.openehr.org/t/query-api-possible-issue/765)
> Checking the Queyr API iI found we have:
Execute stored query: `POST /query/{qualified_query_name}/{version}`
with optional {version}
https://specifications.openehr.org/releases/ITS-REST/latest/query.html#query-execute-query-post-1
And Execute ad-hoc query: `POST /query/aql`
https://specifications.openehr.org/releases/ITS-REST/latest/query.html#query-execute-query-post
The issue is: the second is a special case of the first one, when the {quelified_name} is `aql` and {version} is not...
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [ElTypeRef implementation eval_type from ElExpression missing](https://discourse.openehr.org/t/eltyperef-implementation-eval-type-from-elexpression-missing/761)
> ElTypeRef is in that inheritance-line the last class and not an abstract class.
Same for ElConstraintExpression, ElUnaryOperator and ElBinaryOperator
My editor complains not having done this.
;-)
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Datetimes in AQL and API](https://discourse.openehr.org/t/datetimes-in-aql-and-api/760)
> We were discussing in HiGHmed / EHRBASE about the accepted formats for dates, times and specially datetimes in AQL.
The spec [https://specifications.openehr.org/releases/QUERY/latest/AQL.html#_dates_and_times] says those datatypes should comply with ISO 8601 which allows to:
a. use dots or commas for the fraction seconds marker
b. avoid the time separator if "mutually agreed", that is the 'T' in aaaammddThhmmssZ
Currently EHRBASE doesn't support using commas for the fraction seconds marker...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [The Specifications link is dead](https://discourse.openehr.org/t/the-specifications-link-is-dead/755)
> 
points to https://discourse.openehr.org/c/site-feedback/vdo - which doesn't allow access to me. Is that intentional?
It may be better suited to being a published page - see:
https://meta.discourse.org/t/page-publishing/151971
**[News](https://discourse.openehr.org/c/community-news/25)** - [Rachel Dunscombe appointed to openEHR International Board](https://discourse.openehr.org/t/rachel-dunscombe-appointed-to-openehr-international-board/747)
> We are delighted to announce that Rachel Dunscombe has been appointed to the openEHR International Board. Rachel has a wealth of experience within digital health education, is an advocate for EHR usability and best practice with a passion for improving health and care; read more at https://www.openehr.org/news_events/openehr_news/312
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Possible inconsistency in class-scheme](https://discourse.openehr.org/t/possible-inconsistency-in-class-scheme/745)
> In BmmClass we have to abstract functions: isPrimitive and isAbstract. They are declared optional, but in BmmEntity, where they are derived from, they are declared as mandatory.
I think this is not allowed and also unclear what is meant here, I think it would be better to make the functions mandatory too.
This is also in BmmType, where isAbstract is missing, but isPrimitive is mandatory. The missing isAbstract is not an error because it can be implemented in derived classes from BmmType (I...
**[Text Editors](https://discourse.openehr.org/c/editors/91)** - [ADL support for IDEs](https://discourse.openehr.org/t/adl-support-for-ides/743)
> Hi all, I would like ADL support in Sublime. Especially color support, syntax checking and auto complete. Came across this: https://microsoft.github.io/language-server-protocol/implementors/servers/ this would make a potential implementation availabe to lots of IDE's.
Do other people have the same wish? I can't build it myself unfortunately (lack of dev skills). Would anybody be interested in building this? @pieterbos maybe?
Since you've built something like this for our custom...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How to add a Snomed CT code to each value in a list of ordinals?](https://discourse.openehr.org/t/how-to-add-a-snomed-ct-code-to-each-value-in-a-list-of-ordinals/742)
> Looking at "Air or oxygen" in the archetype NEWS2. If I would like to add a Snomed CT code to each of the values in the ordinal - is that possible in Archetype designer? If so, where can I read about how to do that?
/Sanna
**[RM](https://discourse.openehr.org/c/rm/42)** - [DV_SCALE modelling discussions](https://discourse.openehr.org/t/dv-scale-modelling-discussions/738)
> There is a lively discussion ongoing in the clinical community around requirments fo scales, which the recent changes on relaxing the unique value raule and introduction of DV_SCALE largely resolve.
There are 3 other requirements that have emerged..
1. 'Description' on an internal term linked to a DV_SCALE should be optional. This is universally agreed and makes a lot of sense. Quite often, especially with scores and scales, the term Description is redundant and just adds an overhead of...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Mapping: Blooddruk-v3.2](https://discourse.openehr.org/t/mapping-blooddruk-v3-2/737)
> Dit ondewerp is voor de discussie over de mapping in de werkgroep ZIBs voor OpenEHR van openehr NL.
De mapping website vind u hier: https://openehr-nl.github.io/ZIBs-on-openEHR/zibs/bloeddruk.html
** Voor alle mappings waar aan actief aangewerkt wordt komt hier een topic **
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [SPO2 + exercise challenge for COVID-19](https://discourse.openehr.org/t/spo2-exercise-challenge-for-covid-19/735)
> Interesting modelling challenge for someone - [SPO2 + exercise challenge for COVID-19](https://www.cebm.net/covid-19/what-is-the-efficacy-and-safety-of-rapid-exercise-tests-for-exertional-desaturation-in-covid-19/).
Is this worth working up as embedded template? Good exemplar for events, filled slots etc.
**[ITS](https://discourse.openehr.org/c/its/41)** - [JSON schema format, is attribute order considered for validating JSON?](https://discourse.openehr.org/t/json-schema-format-is-attribute-order-considered-for-validating-json/731)
> Hi,
I'm working on generating the canonical JSON format, and I'm not sure if the attribute order should be the same as the one declared in the JSON Schemas, or if for JSON the order is not important.
I know for XML XSD order is important, and an attribute in the wrong order will return a validation error.
Thanks.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Body segment family of archetypes](https://discourse.openehr.org/t/body-segment-family-of-archetypes/727)
> This family of archetypes have just completed review - 2 review rounds for Body segment length and 1 for Body segment area and Body segment circumference. There seems to be consensus among the reviewers on the body segment pattern. The archetypes will be published on June 3.
Link to the archetypes:
* [Body segment area ](https://ckm.openehr.org/ckm/archetypes/1013.1.3670)
* [Body segment circumference](https://ckm.openehr.org/ckm/archetypes/1013.1.3790)
* [Body segment...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Text, descriptions and comments for value set items - mandatory or optional?](https://discourse.openehr.org/t/text-descriptions-and-comments-for-value-set-items-mandatory-or-optional/728)
> > We need a data type that allows:
>
> * data element names for all
> * descriptions for some, but not all
I checked and I was wrong. the Description attribute on a term is mandatory.
> * ordering for some, but not all and not always sequential or unique
We have that now with DV_ORDINAL and the same will apply to DV_SCALE
[quote="heather.leslie, post:11, topic:709"]
scores associated with some, but not all
[/quote]
So we are left with 2 issues, I think.
1. Mandatory descriptions- I...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Task Planning Specifications possible flaws](https://discourse.openehr.org/t/task-planning-specifications-possible-flaws/726)
> Hello,
I may have found some issues in the Task Planning specifications that should potentially be corrected, namely the use of *start_window* in the TASK_WAIT Class description, since this was replaced by PLAN_ITEM.reminders and the existence of an incomplete phrase in the *override_type* meaning in CHOICE_GROUP Class.
What do you think?
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Clinical Frailty Scale (OBSERVATION.clinical_frailty_scale)](https://discourse.openehr.org/t/clinical-frailty-scale-observation-clinical-frailty-scale/725)
> This archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published soon.
Link to the archetype: [https://openehr.org/ckm/archetypes/1013.1.4691](https://openehr.org/ckm/archetypes/1013.1.4691).
Please reply to this topic if you have any objections or comments.
P.S: There is an ongoing discussion about the use of ordinals vs coded text in clinical scales, https://discourse.openehr.org/t/clinical-scales-ordinal-or-coded-text/709/5
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Svenskt original namespace](https://discourse.openehr.org/t/svenskt-original-namespace/723)
> Tittar lite på hur vi unikt kan identifiera arketyper som kodsystem (name space som omfattar arketypens at-koder). Har även tidigare funderat över vad som händer när olika implementatörer gör egna varianter av samma kliniska koncept, eller använder samma arketyp-id för olika skärningar på ett liknande begrepp. T.ex. så finns/lär det finnas olika arketyper på PEWS, och det är väl inte osannolikt att de har liknande arketyp-id:n.
Såg då här att man kan kombinera **original namespace** med...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Timing in the real world, openEHR and FHIR](https://discourse.openehr.org/t/timing-in-the-real-world-openehr-and-fhir/721)
> As part of my work with the US VA, I have done [an analysis of the HL7 FHIR 'choice' construct](https://openehr.atlassian.net/wiki/spaces/stds/pages/441581569/HL7+FHIR+choice+x+analysis) - choice is the little '[x]' you see in a FHIR resource where there is a choice of data types (example: look for [onset in AllergyIntolerance](http://hl7.org/fhir/R4/allergyintolerance.html#resource)). There are various problems with choice in general ([my discussion of...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Reports following postponement of openEHR Day Helsinki March 2020](https://discourse.openehr.org/t/reports-following-postponement-of-openehr-day-helsinki-march-2020/718)
> Following postponement of the openEHR Day Helsinki Finland earlier in March, the organisers have provided useful content to the openEHR community.
[The first report](https://www.openehr.org/news_events/event_reports/10) from PhD Hanna Pohjonen, openEHR Ambassador Finland and a Healthcare Management Consultant from Rosaldo Oy gives her perspective approaching open platform, modular software development in healthcare around the world.
[The second and most recent...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Editing existing data from another template](https://discourse.openehr.org/t/editing-existing-data-from-another-template/714)
> Hello
doctor created diagnosis record using template f.e. admission template. Patient is in hospital, he is recovering. Doctor want set this state to diagnosis, using doctor's ward template. Do we should copy existing diagnosis to this template so he can edit it and create new instance of diagnosis, or we can somehow edit diagnosis from admission template inside ward template?
Thank you.
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Data from more template](https://discourse.openehr.org/t/data-from-more-template/713)
> Hello,
assume i have more templates for diagnosis archetype - it can be templates for various medical specializations, or situations, sometime diagnose can be nested deeper in template, not just in root.
I want create report for health insurance company and i need get all diagnose code. Do i have to known every template that is including diagnosis archetype?
Let assume i have query to get all diagnosis code, but then we add new type of template using diagnosis archetype, do we need update...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Local SNOMED CT terms in international archetypes?](https://discourse.openehr.org/t/local-snomed-ct-terms-in-international-archetypes/710)
> Lately we've had archetypes proposed containing bindings to SNOMED CT terms that are not in the international edition, but only in a country specific one. According to the information I've received, these may be made into international terms with the same SNOMED CT IDs, but they may also not.
Should terms that are not (yet) in the international SNOMED CT edition be included in international archetypes?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Clinical scales - ordinal or coded text?](https://discourse.openehr.org/t/clinical-scales-ordinal-or-coded-text/709)
> Starting with some definitions. These are not universal, but I'm using the words this way in this post:
* Clinical score: A multi-component clinical assessment tool that involves summing up the numerical values of a set of more than one component. Example: NEWS2
* Clinical scale: A clinical assessment tool consisting of one or more components with a value set, which are *not* summed into a total score. The component value set items may or may not have numerical values associated with them....
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [TNM classification (CLUSTER.tnm and CLUSTER.tnm-pathological)](https://discourse.openehr.org/t/tnm-classification-cluster-tnm-and-cluster-tnm-pathological/706)
> These archetype have been through 2 review rounds. There seems to be consensus among the reviewers. The archetypes will be published on May 27.
Link to the archetypes:
* [TNM clinical classification](https://ckm.openehr.org/ckm/archetypes/1013.1.2413)
* [TNM pathological classification](https://ckm.openehr.org/ckm/archetypes/1013.1.4191)
Please reply to this topic if you have any objections or comments.
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [Fixing your Discourse notifications for Implemenation categories](https://discourse.openehr.org/t/fixing-your-discourse-notifications-for-implemenation-categories/704)
> all,
we recently created various sub-categories under the Implementation top-level category to make it easier to navigate to particular topics. This had the unintended effect that you are not automatically subscribed to those new sub-categories, i.e. you are not watching them. That means that posts you may be interested in will not by default generate an email to you.
**Please visit the Implementation category and make sure you are watching / tracking etc each sub-category according to your...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Notifications on sub-categories issue](https://discourse.openehr.org/t/notifications-on-sub-categories-issue/703)
> all,
We recently created various sub-categories under the Clinical top-level category to make it easier to navigate to particular topics. This had the unintended effect that you are not automatically subscribed to those new sub-categories, i.e. you are not watching them. That means that posts you may be interested in will not by default generate an email to you.
**Please visit the Clinical category and make sure you are watching / tracking etc each sub-category according to your actual...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Fixing your Discourse notifications for Specifications topics](https://discourse.openehr.org/t/fixing-your-discourse-notifications-for-specifications-topics/702)
> all,
we recently created various sub-categories under the Specifications top-level category to make it easier to navigate to particular topics. This had the unintended effect that you are not automatically subscribed to those new sub-categories, i.e. you are not watching them. That means that posts you may be interested in will not by default generate an email to you.
**Please visit the specifications category and make sure you are watching / tracking etc each sub-category according to your...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Evolution of openEHR Discourse forums](https://discourse.openehr.org/t/evolution-of-openehr-discourse-forums/693)
> A quick update to the openEHR community subscribed here on using Discourse. Over the last few months, the user base and set of categories (aka 'discussion lists' in old-school speak) has grown substantially. If you [visit the site](https://discourse.openehr.org), you will now see a very rich set of groups and discussions:
If you want to follow a category, don't forget to:
* 'watch' the category - this will result in...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Handling CVCs and PVCs](https://discourse.openehr.org/t/handling-cvcs-and-pvcs/685)
> Hi all
A common use case is that healthcare professional want to get a quick overview of a needles and things put into the patient, like CVCs (https://en.wikipedia.org/wiki/Central_venous_catheter) and PVCs (https://en.wikipedia.org/wiki/Peripheral_venous_catheter).
**Assumption 1**
These should be recorded using the openEHR-EHR-ACTION.procedure.v1, both for *inseration* and *removal*
**Assumption 2**
It is a good idea to create a template "Catheter procedure" or similar using the...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Anatomical location](https://discourse.openehr.org/t/anatomical-location/677)
> Dear informatics colleagues,
A tricky semantic conundrum for you.
The Anatomical location archetype was published initially in 2015 and then republished in 2017 as 1.1.0 - https://ckm.openehr.org/ckm/archetypes/1013.1.587/18. The intent was to be able to identify a specific place on the body, at a surface anatomy/macroscopic level, where we observed tenderness or a lump, lesion, burn, laceration, bruise or similar as part of physical examination. In that context it only made sense that a...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Obstetric summary (EVALUATION.obstetric_summary)](https://discourse.openehr.org/t/obstetric-summary-evaluation-obstetric-summary/676)
> This archetype has been through 5 review rounds. There seems to be consensus among the reviewers. The archetype will be published on May 15.
Link to the archetype: [https://openehr.org/ckm/archetypes/1013.1.1093 ](https://openehr.org/ckm/archetypes/1013.1.1093).
Please reply to this topic if you have any objections or comments.
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [About the BMM/Expressions category](https://discourse.openehr.org/t/about-the-bmm-expressions-category/675)
> Discussions on [BMM](https://specifications.openehr.org/releases/LANG/latest/bmm.html) and [EL](https://specifications.openehr.org/releases/LANG/latest/expression_language.html) specifications.
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [About the Terminology category](https://discourse.openehr.org/t/about-the-terminology-category/674)
> Discussions on terminology use / interface / bindings in openEHR.
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Possible Problem in BMM class-scheme](https://discourse.openehr.org/t/possible-problem-in-bmm-class-scheme/672)
> Hi,
I think there is a problem in the class-scheme of BMM, latest version.
It is about BMM_MODULE, it is not yet defined in the class-descriptions, but it found its way in some UML-drawings in the documents. Especially the one in paragraph 4.1 and 7.1
In these drawings is BMM_MODULE just between BMM_CLASS and BMM-DECLARATION, and BMM_DECLARATION is derived from BMM_DEFINITIONS.
There is also another route from BMM_DEFINITIONS to BMM_CLASS, that is over BMM_ENTITY that, according the...
**[Affiliates](https://discourse.openehr.org/c/affiliates/58)** - [About the Affiliates category](https://discourse.openehr.org/t/about-the-affiliates-category/671)
> News about openEHR Affiliates around the world.
**[RM](https://discourse.openehr.org/c/rm/42)** - [How to represent "other" for coded values](https://discourse.openehr.org/t/how-to-represent-other-for-coded-values/669)
> Dear All,
being from the Swedish SNOMED CT NRC we need to advice our users on how to represent the notion of "other" in coded value sets (mainly because wo do not want to add "other" SNOMED concepts due to semantic volatility etc). I find that openEHR have null_flavor on the ELEMENT level, but there will still be a need to provide e.g. a DV_CODED_TEXT.value even though there is no DV_CODED_TEXT.defining_code. Further, the null flavors available seem to me not to meet the needs of this not...
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [Why is the email address for a new account limited to Google and Microsoft?](https://discourse.openehr.org/t/why-is-the-email-address-for-a-new-account-limited-to-google-and-microsoft/667)
> Why is the email address for a new account limited to Google and Microsoft?
Google and its email are not available in my country.
I have no Microsoft email account yet. :sweat_smile:
For example, Roadmap for Process Model (PROC) Component:
https://specifications.openehr.org/components/PROC/roadmap
**[Releases](https://discourse.openehr.org/c/releases/57)** - [About the Releases category](https://discourse.openehr.org/t/about-the-releases-category/666)
> Release announcements for products, tools and models from openEHR vendors, research groups, providers and jurisdictions.
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Nordic collaboration call](https://discourse.openehr.org/t/nordic-collaboration-call/658)
> In our previous Swedish collaboration meeting we agreed that it would be useful and interesting to listen to what our Nordic friends are working on in the openEHR space and how they are doing work on a national level (if there is such an initiative).
I have created a Doodle for a first meeting, initially with the intention to get to know each other, share knowledge and experience and maybe find ways of future collaboration :slight_smile:
This is also a follow up to the discussion...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Pattern for modelling of scores (and PEWS)](https://discourse.openehr.org/t/pattern-for-modelling-of-scores-and-pews/655)
> We have recently been looking into the requirements around PEWS based on requirements in Sweden.
I am by no means an expert on the topic, but PEWS seems to be interpreted differently based on country and other contexts. There does not seem to be any consensus on how to calculate a PEWS score. There is no PEWS archetype in the international ckm either.
I hade a brief discussion with @siljelb who mentioned the Norwegian PEWS archetype (https://arketyper.no/ckm/#showarchetype_1078.36.1402)....
**[Releases](https://discourse.openehr.org/c/releases/51)** - [Task Planning Release 1.5.0](https://discourse.openehr.org/t/task-planning-release-1-5-0/654)
> The Specifications PROC component group is pleased to publish [Release 1.5.0 of the Task Planning specification](https://specifications.openehr.org/releases/PROC/Release-1.5.0/), which includes:
* improved explanatory material;
* improved Events model;
* Order tracking;
* Guideline references.
The [full change-log may be found on Jira](https://openehr.atlassian.net/projects/SPECPROC/versions/12505/tab/release-report-all-issues).
We are now working on Release 2.0.0, which will support...
**[openEHR days](https://discourse.openehr.org/c/openehr-days/52)** - [About the openEHR days category](https://discourse.openehr.org/t/about-the-openehr-days-category/653)
> Announcement of openEHR days.
**[Releases](https://discourse.openehr.org/c/releases/51)** - [About the Releases category](https://discourse.openehr.org/t/about-the-releases-category/652)
> News on releases of [openEHR specifications](https://specifications.openehr.org) and software.
(CKM releases in [clinical category](https://discourse.openehr.org/c/clinical/ckmpublication/23)).
**[openEHR.pt](https://discourse.openehr.org/c/openehr-portugal/44)** - [Comunidade Portuguesa do OpenEHR](https://discourse.openehr.org/t/comunidade-portuguesa-do-openehr/648)
> Olá
Um pequeno grupo de pessoas têm reunido com alguma regularidade com o objetivo de alavancar a comunidade portuguesa com interesse na norma OpenEHR. O Ricardo Correia têm carregado este fardo ao longo destes anos todos, e chegamos a um ponto em que precisamos de nos unir em torno de um objetivo comum, demonstrando as vantagens do OpenEHR e torná-lo um standard de eleição no panorama nacional. Nesse sentido este *post* espera ser um ponto de partida e serve para identificar que estará...
**[openEHR.pt](https://discourse.openehr.org/c/openehr-portugal/44)** - [About the openEHR.pt category](https://discourse.openehr.org/t/about-the-openehr-pt-category/638)
> Forum for discussions about openEHR in Portugal / discussões sobre o openEHR em Portugal. **To find out more visit their [website](https://www.e-mais.pt/openehr)**
**[Community](https://discourse.openehr.org/c/community/10)** - [Portugal OpenEHR Community](https://discourse.openehr.org/t/portugal-openehr-community/637)
> This pandemic has underlined the need to have good quality data, and the importance of a united community in bringing reusable clinical models to the field, and sharing their knowledge with the world.
In Portugal, the EHR landscape is dominated by a monolithic, standard-less information system. But I hope openEHR will be a reference in a near future. With that goal in mind, we have recently put together a small group of local openEHR enthusiasts, and have already had a few informal...
**[openEHR Toolkit](https://discourse.openehr.org/c/openehr-toolkit/92)** - [New capabilities for the openEHR Toolkit](https://discourse.openehr.org/t/new-capabilities-for-the-openehr-toolkit/636)
> After receiving many requests from users wanting this, the openEHR Toolkit will soon be used to store and manage templates, archetypes and generate artifacts from them https://server001.cloudehrserver.com/cot/
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Problem Oriented Medical Record](https://discourse.openehr.org/t/problem-oriented-medical-record/635)
> Dear all,
First, my apologies if this post is a bit too long. I've been trying to get some orientation from the community concerning openEHR modeling of a problem oriented medical record (POMR). I thank Ian for his previous replies, both in the forum and in the seminar Erik recently organized (sorry for the long question I sent; I guess it's a pattern). I must say, though, that I am not satisfied with the answers 🙂 My bad: I couldn't accurately picture the use case.
Second, a bit of...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [About the AQL category](https://discourse.openehr.org/t/about-the-aql-category/632)
> For discussions on the openEHR [Archetype Query Language (AQL) specification](https://specifications.openehr.org/releases/QUERY/latest/AQL.html). Please FORMAT your queries as MULTI-LINE!
**[RM](https://discourse.openehr.org/c/rm/42)** - [About the RM category](https://discourse.openehr.org/t/about-the-rm-category/631)
> Discussions on the [Reference Model (RM) specifications](https://specifications.openehr.org/releases/RM/latest/index), including EHR model, Demographics, data types.
**[ITS](https://discourse.openehr.org/c/its/41)** - [About the ITS category](https://discourse.openehr.org/t/about-the-its-category/630)
> Discussions on any of the [Implementation Technology Specifications](https://specifications.openehr.org/releases/ITS/latest/index), i.e. derivatives from the abstract specs, including REST APIs, XSD, JSON, and HL7 FHIR interfaces.
**[ADL](https://discourse.openehr.org/c/adl/40)** - [About the ADL category](https://discourse.openehr.org/t/about-the-adl-category/629)
> Discussions on the [openEHR 'AM' component, i.e. any of the Archetype or Template specifications](https://specifications.openehr.org/releases/AM/latest/index).
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Task planning and ACTION archetypes](https://discourse.openehr.org/t/task-planning-and-action-archetypes/625)
> Recently @heather.leslie and I have been discussing the limitations of ACTION archetypes and how they relate to Task planning, and we'd really like to know more about this topic. We feel that the intricacies of task planning is a bit opaque at the moment, and we need to know more about it to be able to make good modelling choices. This is particularly important for the ACTION archetypes, where we think we could be in danger of trying to replicate structures/functions that would fit better...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [ADL2 valuesets - extend beyond 'local' terms](https://discourse.openehr.org/t/adl2-valuesets-extend-beyond-local-terms/624)
> Currently, the last main blockers in getting ADL2 over the line, are various issues around DV_CODED_TEXT constraints that are required and variably supported in .oet.
One of the options in .oet is to be able to define an inline external terminology valueset e.g.
https://ckm.apperta.org/ckm/templates/1051.57.253
SNOMED-CT::49727002::Cough
...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Option to record free text as choice against DV_CODED_TEXT - do we need DV_PLAIN_TEXT](https://discourse.openehr.org/t/option-to-record-free-text-as-choice-against-dv-coded-text-do-we-need-dv-plain-text/623)
> There is an established use of the DV_TEXT/DV_CODED_TEXT choice pattern to allow
1. extension/replacement of internal code lists (better solved by the proposed changes to allow for 'extensible' etc.
2. To allow a free text to be used in place of a coded text, where none is available.
As an example, the Adverse reaction archetype is intended to be used in the UK with a very strict SNOMED valueset, so that it can power decision support across systems . So in this case the valueset is...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Constraining/ documenting mappings](https://discourse.openehr.org/t/constraining-documenting-mappings/622)
> One of the gaps that I am experiencing is not being able to constrain/enforce mappings at template-level.
e.g. I may have an internal code list which needs to be mapped to a set of SNOMED terms ( The bindings may or may not be available in the underlying archetype) but either way, I have no means of 'forcing' the mappings to be carried at run-time.
We also need to be able to constrain a mapping to be expressed against a text value or default text value.
I don't think we can rely on...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Duration data type](https://discourse.openehr.org/t/duration-data-type/621)
> Hi all,
We have always expressed the clinical notion 'age' as DV_DURATION. It was one of the first things I remember Sam telling me... ie the duration of time since birth.
BUT there is a clinical situation where you can have a negative 'adjusted age' where there is a premature infant, now chronologically 2 months old but born 3 months premature - they are said to have an adjusted, or corrected, age of -1 month. Clinically this is important when related to expected...
**[Implementation](https://discourse.openehr.org/c/implem/39)** - [About the Implementation category](https://discourse.openehr.org/t/about-the-implementation-category/617)
> For discussions on *development* of openEHR implementations. **ESSENTIAL**: *watch* sub-categories to get notifications.
**[LinkEHR](https://discourse.openehr.org/c/linkehr/38)** - [Findings: "Transform openEHR to FHIR Questionnaire"](https://discourse.openehr.org/t/findings-transform-openehr-to-fhir-questionnaire/614)
> Here are some of my findings from playing with the "Transform openEHR to FHIR Questionnaire" feature in LinkEHR:
* enableBehaviour should be enableBehavior
* item.linkId is not always unique
* DV_QUANTITY is not properly transformed. item.type is missing
* DV_QUANTITY missing unit
* For quantity data types I have been using an extension (STU3), that might have been moved to code in R4 version, but I can't confirm that
* All text fields are converted to item.type = "text", for some of them...
**[LinkEHR](https://discourse.openehr.org/c/linkehr/38)** - [About the LinkEHR category](https://discourse.openehr.org/t/about-the-linkehr-category/612)
> This category is for the user community of the [LinkEHR tool provided by VeraTech](https://linkehr.veratech.es/).
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [Italian COVID-19 related template building](https://discourse.openehr.org/t/italian-covid-19-related-template-building/606)
> Good morning everybody,
I would like to report below our experience, in Italy and in particular in Sardinia:
After receiving the report from Tomaz Gornik of Better, that the entire OpenEHR community was mobilizing to provide support in the fight against covid19, we decided to contribute to the overall effort.
Together with CRS4 we started the translation of the created archetypes into Italian and in parallel, we at Inpeco started the development of a demonstration application, using Better's...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Capillary refill archetype](https://discourse.openehr.org/t/capillary-refill-archetype/605)
> Hi!
The archetype openEHR-EHR-CLUSTER.capillary_refill_time.v0 is in draft state, but we'd like to translate it to Swedish and use in a project. However it seems to belong to another CKM (uk.org.clinicalmodels) so we can't start translation in the international CKM (see image below).
How would you suggest that we go on in order to translate it in a way that can be shared via the CKM? Or can capillary refill be recorded in any other existing archetype that we have missed?
@ian.mcnicoll is...
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [Pan-European Hackathon](https://discourse.openehr.org/t/pan-european-hackathon/608)
> This weekend there is a hackathon where new or tweaks to the existing openEHR COVID solutions could be a part:
https://euvsvirus.org/
(One of many possible ideas: https://discourse.openehr.org/t/complete-open-source-tele-health-solution-w-openehr-as-core/551)
**[ITS](https://discourse.openehr.org/c/its/41)** - [JSON - howto serialise enumerations?](https://discourse.openehr.org/t/json-howto-serialise-enumerations/596)
> When serialising openEHR types to JSON should we use the numbered code or the name of the type?
I.e. when serialising [VALIDITY_KIND enumeration](https://specifications.openehr.org/releases/BASE/latest/base_types.html#_validity_kind_enumeration)
I know we discussed this sometime ago, but I wasn't able to find the resource.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Service direction (CLUSTER.service_direction)](https://discourse.openehr.org/t/service-direction-cluster-service-direction/595)
> This archetype has been through 2 review rounds. There seems to be consensus among the reviewers. The archetype will be published on April 28.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.3181](https://ckm.openehr.org/ckm/archetypes/1013.1.3181).
Please reply to this topic if you have any objections or comments.
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [Thoughts about federation of CKMs and the future](https://discourse.openehr.org/t/thoughts-about-federation-of-ckms-and-the-future/587)
> This text is a copy from a Slack post I made in September 2019, about a possible way to make the international and local CKMs work better together in the future. I'm posting it here partly to archive it for the future before it disappears from Slack, partly to get more input.
> I just had an epiphany of sorts about this problem of federation: Maybe we should rather look towards having a single CKM, which can have "Localisation domains" or similar, kind of like the existing subdomains but...
**[Community](https://discourse.openehr.org/c/community/10)** - [Industry Partner activity](https://discourse.openehr.org/t/industry-partner-activity/584)
> **Digia**: [Implementation of the openEHR-based UNA Kernel is progressing well in Finland](https://digia.com/ajankohtaista/uutiset/una-ytimen-toteutus-etenee--tiedonkulku-sote-sektorilla-digitalisoituu/?utm_content=126445207&utm_medium=social&utm_source=twitter&hss_channel=tw-86915332)
**DIPS**: [when building their #COVID19 app DIPS collaborated closely with the #openEHR...
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [How to translate the universal attributes of archetypes?](https://discourse.openehr.org/t/how-to-translate-the-universal-attributes-of-archetypes/581)
> As the Tab "Reference Model" of each archetype‘s Tabbed View shows, *the underlying openEHR reference model 'class' provides a small number of universal attributes which will always be available as if they were part of the archetype itself.*
My question:
How to translate these universal attributes and publish such a translation in order to show them in other non-English language(s) in the same way as other tabs show their content?
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [How to log in Better's Archetype Designer?](https://discourse.openehr.org/t/how-to-log-in-betters-archetype-designer/578)
> Today I know that the web site of Better's Archetype Designer is moved to https://www.openehr.org/archetypedesigner/#/ from https://ehrscape.marand.si/designerv2/#/.
In the previous site test account was provided, but now is not and there is no registration menu.
Is it under construction or does it need other process?
Best regards
Seung-Jong Yu
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [About the Ask IEB category](https://discourse.openehr.org/t/about-the-ask-ieb-category/577)
> Category for discussions about archetype governance and editorial tasks on the CKM and questions to the International Editorial Board.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Advance care directive archetype](https://discourse.openehr.org/t/advance-care-directive-archetype/570)
> This archetype has been through 2 review rounds. There seems to be consensus among the reviewers. The archetype will be published on April 21st.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.4274 ](https://ckm.openehr.org/ckm/archetypes/1013.1.4274).
Please reply to this topic if you have any objections or comments.
**[Template Designer](https://discourse.openehr.org/c/template-designer/93)** - [Using the openEHR Template Designer to create Clinical Document Definitions](https://discourse.openehr.org/t/using-the-openehr-template-designer-to-create-clinical-document-definitions/569)
> Quick overview of what you need to know about the Template Designer to create Clinical Document Definitions (Operational Templates) that can be used in software.
I have created this video some time ago, might be helpful for people starting with templates and operational templates https://www.youtube.com/watch?v=B-W5c3qwpFE
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [How to use the rm attribute of the entry archetype in the template form?](https://discourse.openehr.org/t/how-to-use-the-rm-attribute-of-the-entry-archetype-in-the-template-form/568)
> Hi，every one:
I have a question for help and answers:How to use the rm attribute of the entry archetype in the template form? Could template support this function?
For example, we need to fill in the 'Start Date / Time' of an observation archetype , or the 'Information Provider' of an Action archetype in the ocean template designer?
In other words, can it be achieved by developing and adding functions in other template editors?
Best wishes！
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Path+Archetype ID in RESULT_SET.columns](https://discourse.openehr.org/t/aql-path-archetype-id-in-result-set-columns/559)
> Hi all,
I have mentioned in the last SEC meeting the need of adding some archetype_id information in the columns because the paths alone are not enough info to know what the data in the row columns are.
So for instance, in EHRBASE we have something like:
```
{
"q": "SELECT o, eval, i FROM EHR e[...] contains composition c contains observation o[...]
OR evaluation eval[...] OR instruction i[...]",
"columns": [
{
"path": "/",
"name": "#0"
...
**[Template Designer](https://discourse.openehr.org/c/template-designer/93)** - [Different Languages in Template Designer](https://discourse.openehr.org/t/different-languages-in-template-designer/557)
> Hello,
I am currently creating templates in Template Designer from Ocean Informatics. The archetypes I use will eventually be translated into another language. Is it possible to indicate in which language you want to load the archetypes in Template Designer?
**[RM](https://discourse.openehr.org/c/rm/42)** - [Instruction State Machine](https://discourse.openehr.org/t/instruction-state-machine/553)
> From Figure 25. in the specifications about the ISM, it appears that an activity is always in state initial as long as there is no associated action for it. In order to transfer it e.g. into planned state, it seems that at least one action is required. In order to reach the completed state, at least two actions seem to be required. Is that correct? If so, should the initial action to transfer into state planned be in the archetype containing the instruction, or should it be submitted separately?
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [Complete open source tele-health solution w/openEHR as core?](https://discourse.openehr.org/t/complete-open-source-tele-health-solution-w-openehr-as-core/551)
> Just an idea that I won't have time to pursue myself:
Could a complete open source tele-health solution for scalable handling of remote (home based) Covid patients be built with openEHR as core using "Task Planning" etc. A flexible setup where some patients can do all follow-up/reporting by themselves (forms+bots), some can chat (with human care staff + bots) and some can use videoconferencing where needed.
If somebody would combine open source:
* Video conferencing: https://meet.jit.si/...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL ORDER BY doesn't specify the columns should appear in the projection](https://discourse.openehr.org/t/aql-order-by-doesnt-specify-the-columns-should-appear-in-the-projection/550)
> Reading about SQL ORDER BY, detected it is mandatory that a projection is done over the column that appears in the ORDER BY which makes sense because without that projection the client won't see any order.
But we don't have anything in the AQL spec mentioning this constraint.
I think we need to add some note about that. What do others think?
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Det finns inga dumma frågor!](https://discourse.openehr.org/t/det-finns-inga-dumma-fragor/549)
> Om du inte klurar ut hur man startar en ny tråd eller tycker det verkar läskigt/onödigt bara för din lilla fråga så kan du haka på din fråga i denna tråd.
Letar du nybörjarintroduktioner till openEHR, kolla då även länkarna i https://discourse.openehr.org/t/openehr-se-borja-lasa-har/391
**[RM](https://discourse.openehr.org/c/rm/42)** - [Tags: Initial thoughts on RM representation](https://discourse.openehr.org/t/tags-initial-thoughts-on-rm-representation/547)
> Starting from [this wiki page put together by Better/Code24/DIPS](https://openehr.atlassian.net/wiki/spaces/spec/pages/424706234/Current+State+of+Data+Tagging+Overview), we have some ideas about what tags look like in 3 current systems.
The job is to decide what to try to standardise on. We could just standardised on the API and a representation of a 'tag', and ignore where they are stored. However... if we do that, and some site decides to move some EHRs from say Better or DIPS to EhrBase,...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Kommentarer om openEHR.se (flyttad diskussionstråd)](https://discourse.openehr.org/t/kommentarer-om-openehr-se-flyttad-diskussionstrad/1121)
> Den som är nyfiken på Region Östergötlands förberedelser kring upphandlings av openEHR-baserat system kan hitta mer info om dem under:
* https://discourse.openehr.org/t/swedish-openehr-platform-procurement-q1-2020/247
* och på wiki-sidan: https://openehr.atlassian.net/wiki/spaces/resources/pages/416514052/Procurement+of+openEHR-related+systems+and+services
Regionen är i upphandlingen även nyfiken på process- och beslutsstöd i stil med de som presenterades i...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Simplified Data Template (SDT) - data types](https://discourse.openehr.org/t/simplified-data-template-sdt-data-types/546)
> Following our decision to provide a more basic specification of the Simplified Data Template (SDT), I thought I would start at the 'easy' end, i.e. data types and various low level RM types. [Here is a wiki page that I am starting to populate on this](https://openehr.atlassian.net/wiki/spaces/spec/pages/624361477/Simplified+Serial+Formats+-+Data+Types).
One question I thought I would pose is this. For primitive, types, the representation is generally obvious and non-controversial (i.e. it's...
**[Community](https://discourse.openehr.org/c/community/10)** - [Blog by Hannah Pohjonen openEHR Ambassador Finland](https://discourse.openehr.org/t/blog-by-hannah-pohjonen-openehr-ambassador-finland/543)
> The openEHR Day Nordics and openEHR Workshop for Social Care, which were scheduled for 25th March in Helsinki, had to be cancelled due to the current global situation but will be held at a later date. In the meantime we will be posting a couple of openEHR blogs written by knowledgeable experts.
Hanna Pohjonen PhD, opens up one perspective approaching open platform, modular software development in healthcare around the world. Hanna is openEHR Ambassador Finland and a Healthcare Management...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Where should claim related artefacts go?](https://discourse.openehr.org/t/where-should-claim-related-artefacts-go/541)
> As the tile said, I've been wondering where claim related artefacts should be placed in the CKM? Similarily, discussion topics on such artefacts might also need a separate category in the forum.
In addition, this question reminds me of the counterparts/modules in the FHIR Specification, such as Financial Module and Administration Module.
Thanks
Cheers,
Lin Zhang
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [COVID-19 project](https://discourse.openehr.org/t/covid-19-project/537)
> Hi everyone,
The [COVID-19 project](https://ckm.openehr.org/ckm/projects/1013.30.81) is slowly growing, especially with archetypes that have been developed in response to the project requirements related to the virus. Inspired by some of the common requirements identified in the [COVID-19 incubator](https://ckm.openehr.org/ckm/incubators/1013.30.80), [NT (AU) requirements](https://ckm.openehr.org/ckm/templates/1013.26.273) and [Chinese...
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [About the Tools category](https://discourse.openehr.org/t/about-the-tools-category/536)
> Discuss **development** aspects of tool-building, e.g. tools for building archetypes, templates, guidelines, task plans and more.
For tool support, please use the top-level category Tool Support.
**[Tools](https://discourse.openehr.org/c/tool-dev/36)** - [Blockly for openEHR projects](https://discourse.openehr.org/t/blockly-for-openehr-projects/535)
> [Blockly](https://developers.google.com/blockly) is a javascript library that provides block-based editors to any given app.
I've used it personally to define a first version of a Snomed expression syntax editor in less than a week (and most of the time came from integrating an autocomplete widget with it) and I'm no javascript expert :smiley:
It's a quite rewarding little piece of technology, because you get results quite fast.
I can see several use cases in the openEHR world:
* AQL...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL - the simplest possible question?](https://discourse.openehr.org/t/aql-the-simplest-possible-question/533)
> Given a CDR with only two compositions and one EHR.
Composition 1 (C1) has one OBSERVATIONS.
Composition 2 (C2) has two OBSERVATIONS.
And you query with the following AQL:
SELECT c FROM COMPOSITION c CONTAINS OBSERVATION o
What is the expected result?
Alternative 1:
--------
| c |
--------
| C1 |
--------
| C2 |
--------
Alternative 2:
--------
| c |
--------
| C1 |
--------
| C2 |
--------
| C2 |
...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Online-seminarium om besluts- och processtöd arrangerat av KI, tre regioner och openEHR](https://discourse.openehr.org/t/online-seminarium-om-besluts-och-processtod-arrangerat-av-ki-tre-regioner-och-openehr/527)
> I inlägget...
https://discourse.openehr.org/t/march-26-online-seminar-practical-tools-and-methods-for-clinical-decision-and-process-support/376
...finns information om ett online-seminarium om besluts- och processtöd arrangerat av KI, tre regioner och openEHR som hålls 26:e mars 2020 kl 16:15-17:15.
* Anslutning: https://nedap.zoom.us/j/281953142
* Agenda/program inkl. presentationer och referenser:...
**[ADL Workbench](https://discourse.openehr.org/c/adl-workbench/94)** - [Archetype Workbench Setup RM Schema Configuration - No archetypes found](https://discourse.openehr.org/t/archetype-workbench-setup-rm-schema-configuration-no-archetypes-found/526)
> Hello, I'm trying to set up the Archetype Workbench. I installed the openEHR-reference repository by cloning the GitHub repository on my local machine. In the RM Schema Configuration, all schemas are checked by default. But I still get the error message "No archetypes found; may need to enable appropriate RM schema; See RM Schemas > Configure Menu". Can you please tell me what is missing? Thanks a lot!
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Svenskt intresse för openEHR-baserade COVID-19 applikationer?](https://discourse.openehr.org/t/svenskt-intresse-for-openehr-baserade-covid-19-applikationer/524)
> Se det internationella: https://discourse.openehr.org/t/openehr-covid-19-project/448
Finns det vårdgivare som har intresse för för openEHR-baserade COVID-19 applikationer? I så fall kan vi t.ex. behöva översätta eller uppdatera/granska översättning av vissa arketyper.
VI undersöker litet om möjlighet för en sådan applikation i Region Östergötland men har inte fattat några beslut om det än.
Företaget Better har erbjudit att man får använda deras plattform (Think!EHR) gratis för...
**[REQUESTS](https://discourse.openehr.org/c/tool-requests/95)** - [Data set visualisation of templates](https://discourse.openehr.org/t/data-set-visualisation-of-templates/521)
> I'm coordinating a COVID-19 related modelling effort in Norway, and publishing the models as openEHR templates is on the table. To make this feasible for the vendors and other interested parties that don't implement their solutions on an openEHR CDR, we'd like to be able to visualise templates more fully and in a more readable way than what the CKM currently does. For example showing the full value sets, including codes, in a "printable" format.
Ocean's Template Designer has a [HTML...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Ventilator settings](https://discourse.openehr.org/t/ventilator-settings/520)
> HI everyone. We are trying to create a template to help intensive care prescribe ventilator settings.We search CKM and Apperta and we didn´t find any. Is there any archetype already build to use?
**[Covid-19](https://discourse.openehr.org/c/covid19-dev/34)** - [Chinese COVID-19 Diagnosis and Treatment Decision Support: openEHR Templates and Rules](https://discourse.openehr.org/t/chinese-covid-19-diagnosis-and-treatment-decision-support-openehr-templates-and-rules/516)
> Dear Colleagues,
On behalf of all the members of Xudong's @lvxd team, I'm pleased to share our GDL rules and related archetypes regarding the Chinese COVID-19 Guideline. The files are now available on GitHub ([https://github.com/ZJU-BME-VICO/openEHR-COVID-19](https://github.com/ZJU-BME-VICO/openEHR-COVID-19)). Everyone is encouraged to test, use, fork, and feedback on the rules and archetypes freely.
In China, COVID-19 broke out in December 2019 and has been under control for a couple of...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Jira-projekt för prioritering av ärenden](https://discourse.openehr.org/t/jira-projekt-for-prioritering-av-arenden/513)
> Idag har vi en wiki med prioritering av ärenden: https://openehr.atlassian.net/wiki/spaces/healthmod/pages/91768271/Prioritering+och+intresseinventering
Vi skulle gärna se en modell liknande den i Norge där vi använder Jira: https://openehr.atlassian.net/projects/OENO/issues
Vad tror ni om det? Skönt med strukturerad backlog, brädor, assignees, processtöd osv.
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [Cambio ser fram emot utökat nationellt samarbete inom openEHR!](https://discourse.openehr.org/t/cambio-ser-fram-emot-utokat-nationellt-samarbete-inom-openehr/512)
> Cambio har sedan länge arbetet med openEHR i olika sammanhang, och välkomnar nu både det här nya diskussionsforumet och ett fortsatt produktivt arbete tillsammans med vårdgivare i Sverige (oavsett om de är kunder till Cambio eller inte), samt andra leverantörer i de [nationella samverkansmötena](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/561676784/M+ten) som har dragits igång!
Cambio arbetar långsiktigt med openEHR, både inom ramen för vårt journalsystem COSMIC, Cambio CDS,...
**[RM](https://discourse.openehr.org/c/rm/42)** - [How to use Persistent Compositions?](https://discourse.openehr.org/t/how-to-use-persistent-compositions/508)
> My openEHR experience is still on a high level, so please excuse if this is a trivial question!
We were looking at how to set up a strategy for persistent archetypes versus a folder structure for keeping various types of aggregated lists. We also discussed why we cannot just query for what is in the lists, without the persistent compositions.
What is the reason for having a persistent composition as opposed to just query for a list of something?
Should persistent compositions be used only...
**[Covid-19](https://discourse.openehr.org/c/clin-models-covid19/35)** - [About the Covid-19 category](https://discourse.openehr.org/t/about-the-covid-19-category/504)
> For openEHR Covid-19 clinical models.
**[Covid-19](https://discourse.openehr.org/c/covid19-dev/34)** - [About the Covid-19 category](https://discourse.openehr.org/t/about-the-covid-19-category/503)
> For openEHR Covid-19 application development.
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [About the Covid-19 category](https://discourse.openehr.org/t/about-the-covid-19-category/501)
> For openEHR Covid-19 work - see other sub-categories; use this category if no sub-category applies. See also the main [Clinical modelling category](https://discourse.openehr.org/c/clinical/).
**[Terminology](https://discourse.openehr.org/c/terminology/59)** - [Handling SNOMED CT synonyms](https://discourse.openehr.org/t/handling-snomed-ct-synonyms/500)
> This is an issue which has emerged in the COVID-19 work but is familiar to me from UK GP systems.
In theory the inferencing and relationships in SNOMED-CT should allow us to use any synonym in place of the defining concept.
e.g in the current COVID symptoms
'Sore throat' is actually a synonym `2164213014` for the fully-specified name`162397003 | Pain in throat (finding) |` is the
as it should be possible for the underlying system to query for `162397003`... and get any of the codes which...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Validation of coded_text values esp. with external terminology](https://discourse.openehr.org/t/validation-of-coded-text-values-esp-with-external-terminology/499)
> I am seeing a difference in interpretation of if and how a coded_text/value should be validated
e.g. ehrBase does full validation on
terminology
defining_code
value
Better does only
terminology
defining_code
but NOT value
Full validation, particularly against a default value can be problematic in international templates because we generally want to add the coded value (rubric) for human meaning ubt international settings this text may well be translated or not!!).
Thoughts?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Episode of care - institution](https://discourse.openehr.org/t/episode-of-care-institution/495)
> Hi @heather.leslie (and everybody),
I just saw that the archetype has been made visible. I'm currently working on the representation of episodes of care and encounters for HiGHmed/Nephro Digital and a case management software. I was wondering what has been the sources for the modelling. In general, I would see an encounter as the information object being created on an admission inside a particular organization and episode of care as something that exists one level above an encounter. I think...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [OPT 2 templates in ckm](https://discourse.openehr.org/t/opt-2-templates-in-ckm/494)
> The specification website clearly details out about ADL 2 and Operational Templates with ADL 2 artifacts. But I could not find example templates to fiddle with. Where can I find OPT 2 format of templates?
Thanks! :slightly_smiling_face:
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [About the Archetype Designer category](https://discourse.openehr.org/t/about-the-archetype-designer-category/490)
> This category is for the user community of the Archetype Designer clinical modelling tool provided by [Better](https://www.better.care/) and openEHR International at [openEHR Archetype Designer](https://openEHR.org/archetypedesigner). Experts and developers monitor this group.
Please tag all posts, with tags such as: `archetype`, `template`, `task-plan`, `ui`, `ux` etc.
**[Tool Support](https://discourse.openehr.org/c/tool-support/29)** - [About the Tool Support category](https://discourse.openehr.org/t/about-the-tool-support-category/489)
> For user community support for clinical modelling and other tools. **ESSENTIAL**: *watch* sub-category of tools you use to get notifications.
Tool maintainers *usually* monitor and help.
Please come here first with your problem, so as to avoid reporting problems already known, and for which fixes or workarounds may already be published.
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [URI and GI symptoms recording](https://discourse.openehr.org/t/uri-and-gi-symptoms-recording/609)
> The Covid-19 one-pager gives the following symptoms:
How do we record the following symptoms ?
* URI symptoms
* GI symptoms
My idea was to find some SNOMED-CT codes to expand the current set with _fever_, _cough_ and _short of breath_ .
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL type predicate](https://discourse.openehr.org/t/aql-type-predicate/487)
> Our EHR Server end-user consultants report that sometimes filtering by object type would be useful in AQL. As an example they point out laboratory results where archetypes and templates allow for many data-value types at the leaf level, and sometimes a query might want to only include DV_QUANTITYs and DV_SCALEs. They propose a solution in a sense of adding an implicit attribute `@class` which could be used like this: `myResult/@class MATCHES {"DV_QUANTITY","DV_SCALE"}`.
I must say I prefer a...
**[Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)** - [OPT version, schema & document](https://discourse.openehr.org/t/opt-version-schema-document/486)
> Hi.
Many thanks to great contributors !
I'm Seung-Jong Yu and not a newbie but kind of lurker :slight_smile:
I can't categorize my topic, so post here.
I have some OPT-related questions while I'm making some templates and export it in OPT using Better's Archetype Designer.
Here are questions.
1) OPT of Better's Archetype Designer has some unknown attributes and omits those (via Cabolabs' Operational Template XML Validator). For example, the former are "**matches_negated**" ,...
**[News](https://discourse.openehr.org/c/community-news/25)** - [ECHAlliance shares direct Member to Member offers targeting the COVID-19](https://discourse.openehr.org/t/echalliance-shares-direct-member-to-member-offers-targeting-the-covid-19/485)
> openEHR are a member of ECHAlliance and several of their members have developed and can offer a number of relevant services or products to support efforts to combat the spread of the COVID-19 virus and or mitigate against its impact.
ECHAlliance are encouraging those members with solutions to contact them so that they can include the detail in the next edition of their ‘Member to Member - COVID-19’, scheduled for 24 March 2020.
For more information see:...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [NEWS2 Score (OBSERVATION.news2)](https://discourse.openehr.org/t/news2-score-observation-news2/479)
> The archetype has been through 2 review rounds. There seems to be consensus among the reviewers. The archetype will be published on March 24th.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.3342 ](https://ckm.openehr.org/ckm/archetypes/1013.1.3342).
Please reply to this topic if you have any objections or comments.
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [Dutch COVID-19 template for elderly care](https://discourse.openehr.org/t/dutch-covid-19-template-for-elderly-care/607)
> @ian.mcnicoll there are plans coming up to use this by the association off Dutch elderly care doctors(Verenso);)
Do you need any help from a medical perspective?
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [BMJ article -"Better use of data and digital offer rapid opportunities to address covid-19"](https://discourse.openehr.org/t/bmj-article-better-use-of-data-and-digital-offer-rapid-opportunities-to-address-covid-19/468)
> This is a very interesting paper in the [latest online BMJ](https://blogs.bmj.com/bmj/2020/03/13/better-use-of-data-and-digital-offer-rapid-opportunities-to-address-covid-19/) arguing for better use of data and digital in response to Covid-19.
Amongst its authors are Ben Goldacre, Rachel Dunscombe and Amir Mehrkar who are highly respected in the UK digital space and at least some of what they are suggesting - better computable and 'open' documentation of data models, guidance and pathways...
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [AQL issues and the Health risk archetype](https://discourse.openehr.org/t/aql-issues-and-the-health-risk-archetype/611)
> Our work in India
Inspired by the work of OpenEHR community lead by Ian, we have teamed up with E-Health Research Center @IIITB to create something that can be used in India. We have proposed the concept to Karnataka state as we are based out of Bangalore and are waiting for their response.
While we wait for their response, we have decided to invest a week's effort to see what we can come up with so that we do not waste time till we hear from the state health authorities. We had a hackathon...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Have a problem starting Ocean's Template Designer](https://discourse.openehr.org/t/have-a-problem-starting-oceans-template-designer/463)
> Hi everyone,
I'm trying to create an openEHR template with Ocean's Template Designer. I think most people also use this tool too. I'm using Mac. However, I can't start the program no matter which method I tried. It's like the program is loading, then it crashed.
* I tried to run it on Parallels virtual machine and Azure's Windows 10 pro virtual machine.
* I tried every compatibility setting available and also run as administrator.
The Windows version I'm using is Windows 10 Pro version...
**[Covid-19](https://discourse.openehr.org/c/covid19/32)** - [Archetype specialisation and tooling issues](https://discourse.openehr.org/t/archetype-specialisation-and-tooling-issues/610)
> Hi Ian,
As of now we are just curious about what is happening. However along with EHRC ([https://ehrc.iiitb.ac.in/](https://ehrc.iiitb.ac.in/)) we are planning to pitch a monitoring/tracking solution to the karnataka government for use across the state public health system. If they show interest we may go further.
Just to build on my earlier mail openEHR-EHR-CLUSTER.symptom_sign-cvid.v0 seems to have been specialized from openEHR-EHR-CLUSTER.symptom_sign.v0 (not v1), in which this node is a...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Press Release: openEHR Community Rises to the Challenge of Coronavirus](https://discourse.openehr.org/t/press-release-openehr-community-rises-to-the-challenge-of-coronavirus/454)
> The global openEHR community led by the major openEHR vendors DIPS (Norway) and Better (Slovenia) have today released open source components to assist software developers creating applications and services to help those fighting the global Coronavirus (COVID-19) pandemic... meanwhile UK based OpusVL are developing an open-source screening assessment app. [Read full Press Release](https://www.openehr.org/news_events/openehr_news/311)
**[Covid-19](https://discourse.openehr.org/c/covid19-dev/34)** - [openEHR COVID-19 Project](https://discourse.openehr.org/t/openehr-covid-19-project/448)
> Some of you may have become gently aware of a project that a small number of openEHR folks (mostly from vendors) have been quietly working on for the past few days. This came from an idea that @Bna of DIPS and his team had discussed of the need for some kind of app to help hospitals screen patients for risk of Covid-19.
Basically this is the primary use case (good old fashioned paper form) from the...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [How to share a template about covid-19 to ckm？](https://discourse.openehr.org/t/how-to-share-a-template-about-covid-19-to-ckm/439)
> Hello, everyone!!!
we have developed an openEHR template based on China ’s "Diagnosis and Treatment Protocol for Novel Coronavirus Pneumonia (Trial Version 6)", the main purpose is to use for the interoperability of patient diagnosis and treatment data and as the basis for GDL We hope to make it public to ckm's incubator for your review. I know that Covid-19 project already exists in incubator, who should we contact?
**[Community](https://discourse.openehr.org/c/community/10)** - [Time to light the FHIR](https://discourse.openehr.org/t/time-to-light-the-fhir/438)
> Hi All,
You may have seen [my piece on Digital Health Intelligence](https://www.digitalhealth.net/2020/03/time-to-light-the-fhir-and-get-to-grips-with-standards/) It's generated quite a few comments. Including one from Richard Kavanagh which describes openEHR as futile. I will respond in due course, but would be good if others from our community added their thoughts.
Ewan
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Specimen (CLUSTER.specimen)](https://discourse.openehr.org/t/specimen-cluster-specimen/436)
> The archetype has been through 3 review rounds. There seems to be consensus among the reviewers. The archetype will be published on March 16th.
Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.331 ](https://ckm.openehr.org/ckm/archetypes/1013.1.331).
Please reply to this topic if you have any objections or comments.
**[ITS](https://discourse.openehr.org/c/its/41)** - [REST: POST EHR directory twice, what happens?](https://discourse.openehr.org/t/rest-post-ehr-directory-twice-what-happens/432)
> What should happen in the EHR directory is created (POST) twice? PUT is used for updates and requires `If-Match` to prevent conflicting concurrent updates. POST should probably return 409 Conflict if EHR already has a directory?
https://specifications.openehr.org/releases/ITS-REST/latest/ehr.html#directory-directory-post
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Specifying and implementing AQL CONTAINS](https://discourse.openehr.org/t/specifying-and-implementing-aql-contains/427)
> In the interests of clarifying what became a far more contentious issue than I would have ever imagined, let me describe briefly why I thought we should retain AQL's independence at the spec level from any particular model.
Let's say we have two models, openEHR RM and Acme RM, a model of some company structures. To let an AQL processor know where the logical CONTAINment relations are, the processor needs some model information. It could interrogate a meta-model, but let's say we don't want...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Special treatment of "incomplete" VERSIONs](https://discourse.openehr.org/t/special-treatment-of-incomplete-versions/420)
> At Better we have requests from multiple customers to implement the following change of behaviour for `VERSION`s that have `lifecycle_state` set to `incomplete`:
* When committing incomplete data, the validation should be somewhat relaxed. At the moment we think it is sufficient to skip validation of cardinality lower bounds, in other words, to allow missing data. All other validation (cardinality upper bounds and constraints on values) would be performed normally.
* When querying, data from...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [What is an AQL projection?](https://discourse.openehr.org/t/what-is-an-aql-projection/418)
> Based on the discussions in the 'teaser' posts, I have thought a bit more about the way we can formally define the notion of 'projection' in AQL. The confusing thing is that in 'normal' DB theory, the FROM part of a query specifies the logical database (tables or virtual join) on which the row-filtering (WHERE clause) should operate, before the SELECT columns are selected to generate the result. You can't mention columns in the SELECT that don't exist in the FROM part. Here, the WHERE clause...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Template-based validation on other_details](https://discourse.openehr.org/t/template-based-validation-on-other-details/416)
> Hi everybody,
for EHRbase, we would like to support validation of other_details like in Folders or EHR_STATUS. I was wondering if there are any existing approaches used by any vendor/project and what is the experience so far. We will need to make some decisions (attaching the template, likely based on a cluster) to a single EHR, all EHRs and the CDR also needs to know on which context (is other_details part of a feeder_audit, EHR_STATUS, a particular FOLDER or all folders...).
Would be...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Representation of variation in pregnancy](https://discourse.openehr.org/t/representation-of-variation-in-pregnancy/442)
> @SEC - there is maybe a related use case with pregnancy, where we need to describe a due date as a Duration data type expressed in weeks but with a variation of x days eg 34 weeks +/- 7 days.
I'm wondering if there is a need to add an attribute to the Duration and Count data types that allows us to express the variation - Silje's example of ‘87+1’ or ‘88-3’ or the pregnancy 34 **wks** +/- 7 **days**. So we need 3 components to express the pregnancy date and most of the genomics example:
1....
**[RM](https://discourse.openehr.org/c/rm/42)** - [Integration Information Model revamp](https://discourse.openehr.org/t/integration-information-model-revamp/410)
> I've always been a fan of this part of the model, as it can really allow for quick integrations, but from chatting with everyone else, seems like I'm in the minority here :slight_smile:
So I would like to propose a revamp for the model, not only in the model itself, but also in the use cases presented in the specification. Here is the tasks I proposed in the past to enhance the model:
[SPECRM-18](https://openehr.atlassian.net/browse/SPECRM-18): Change GENERIC_ENTRY data attribute type from...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Representation of genetic positions](https://discourse.openehr.org/t/representation-of-genetic-positions/407)
> Hi everyone!
We're working on the Genetic variant archetypes, and have run into an issue with how to represent the more complex positions within a gene. On the genomic level this is easy, a simple positive number starting from the left side of the genome and ending on the right side. For the coding sequence (a single gene), this gets more complicated because positions in the exons are numbered with positive numbers. Positions in the introns are however numbered with a combination of the...
**[ITS](https://discourse.openehr.org/c/its/41)** - [Does ETag in composition response header really need quotes?](https://discourse.openehr.org/t/does-etag-in-composition-response-header-really-need-quotes/404)
> It's all in the title but I note that the compositionUID comes back within quotes e.g. `"acf0a908-71b0-4e17-9d77-005cca119672::local.ehrbase.org::1"`. What's the reason behind the quotes as this obviously puts another step into converting this into a variable for further use.
**[ADL](https://discourse.openehr.org/c/adl/40)** - [DV_CODED_TEXT with open/extensible set of codes (value set)](https://discourse.openehr.org/t/dv-coded-text-with-open-extensible-set-of-codes-value-set/403)
> I would like to pick up a discusssion we started in the ADL2 meeting last year in Braunschweig:
We had another request (this time from HiGHmed) to support open/extensible set of codes in a DV_CODED_TEXT.
In this case, the reason is that they cannot standardise all codes across the various sites, but wherever it is possible they want to use the available codes as defined. You will probably have seen various variations of such a request (e.g.: we cannot use Snomed, but need to use another...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL (and related) documentation](https://discourse.openehr.org/t/aql-and-related-documentation/402)
> As we have started to get into the detail of tidying-up the AQL specification and related issues like datatype ordering and comparison rules, there has been a pretty lively discussion [here]( https://discourse.openehr.org/t/aql-formal-definition-of-from-clause/322/63) about the best way of documenting the required behaviour of AQL **in the context of the openEHR Reference models**.
I think we now have to make a decision so that we can make tangible progress. Broadly speaking two approaches...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Aql teaser 4 for implementers](https://discourse.openehr.org/t/aql-teaser-4-for-implementers/401)
> Dear implementers:
@bna @matijap @ian.mcnicoll
Given the composition on the left, and the AQL query after that, what should the result set for the select clause on the right be? Same as before: think on it whenever you have some free time
SELECT
c,s,i_1,i_2
FROM
COMPOSITION C c
CONTAINS
SECTION s
CONTAINS
(INSTRUCTION i_1 OR INSTRUCTION i_2)
on the...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL question about predicates](https://discourse.openehr.org/t/aql-question-about-predicates/398)
> Could path predicates be used to filter on other attributes than archetype ids and node ids? For instance, is this valid?
`SELECT c FROM COMPOSITION c [uid/value='_this_is_a_version_id_']`
> Note: testing that on EHRScape, I get 400 Bad Request with no error message, and on Ethercis/EHRBASE I get 400 and an antlr exception “Could not process query, reason:org.antlr.v4.runtime.misc.ParseCancellationException: AQL Parse exception: line 1: char 29 mismatched input ‘uid’ expecting...
**[openEHR.se](https://discourse.openehr.org/c/openehr-sweden/28)** - [openEHR.se (Börja läsa här)](https://discourse.openehr.org/t/openehr-se-borja-lasa-har/391)
> *Forum category for those working with, or interested in openEHR in Sweden or openEHR things in Swedish. It's OK to post in Swedish here.*
Forum för dig som jobbar med, eller är nyfiken på, openEHR i Sverige eller som arbetar med openEHR-relaterade saker på svenska. Det går bra att skriva på svenska i denna kategori av openEHRs diskussionsforum.
## Länkar och tips
* [Wiki-sida om arbetet med arketyper på...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Aql teaser 3 for implementers](https://discourse.openehr.org/t/aql-teaser-3-for-implementers/389)
> Dear implementers:
@bna @matijap @ian.mcnicoll
Given the composition on the left, and the AQL query after that, what should the result set for the select clause on the right be? Same as before: think on it whenever you have some free time
SELECT
c,s,i_1,i_2
FROM
COMPOSITION C c
CONTAINS
SECTION s
CONTAINS
(INSTRUCTION i_1 OR INSTRUCTION i_2)
(i) on the...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL teaser 2 for implementers](https://discourse.openehr.org/t/aql-teaser-2-for-implementers/388)
> Dear implementers:
@bna @matijap @ian.mcnicoll
Given the composition on the left, and the AQL query after that, what should the result set for the select clause on the right be? Same as before: think on it whenever you have some free time
SELECT
c,s,i_1,i_2
FROM
COMPOSITION C c
CONTAINS
SECTION s
CONTAINS
(INSTRUCTION i_1 AND INSTRUCTION i_2)
(i) on...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [QEWD.js great video on VM-style DBs](https://discourse.openehr.org/t/qewd-js-great-video-on-vm-style-dbs/379)
> Rob Tweed had made a masterful video ([here on YouTube](https://youtu.be/1TlAKTw167s)), very nicely produced on his QEWD.js framework and its seamless DB back-end. I've posted it here, because although it's about DBs, it's really the back-end of a framework that he (and Ripple) has used to make building openEHR applications fast.
It's 37 mins and very nicely presented.
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [March 26 online seminar: Practical tools and methods for clinical decision- and process-support](https://discourse.openehr.org/t/march-26-online-seminar-practical-tools-and-methods-for-clinical-decision-and-process-support/376)
> # Practical tools and methods for clinical decision- and process-support
*Update March 12: This seminar was previously planned as a physical event in Stockholm and has now been changed to an online event.*
*Update March 30: The [video recording is now available](https://discourse.openehr.org/t/march-26-online-seminar-practical-tools-and-methods-for-clinical-decision-and-process-support/376/39)
## What
Public seminar demonstrating and...
**[Covid-19](https://discourse.openehr.org/c/covid19-dev/34)** - [Project Covfefe](https://discourse.openehr.org/t/project-covfefe/375)
> Develop the openEHR dataset to support efforts to contain and manage COVID-19
Aims
- assist professional assessment of individual risk/ liklihood of symptoms/signs being due to COVID-19
- assist personal/non-professional assessment of individual risk/ liklihood of symptoms/signs being due to COVID-19
https://www.hps.scot.nhs.uk/web-resources-container/novel-coronavirus-2019-ncov-guidance-for-primary-care/
https://www.cdc.gov/coronavirus/2019-ncov/php/risk-assessment.html
This relies on...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Aql teaser 1 for implementers](https://discourse.openehr.org/t/aql-teaser-1-for-implementers/373)
> Here is a little something for aql implementers that I know of (where Ian counts for EhrBase)
@bna @matijap @ian.mcnicoll
Given the composition on the left, and the AQL query after that, what should the result set for the select clause on the right be? Take this as a tease between me and you in a light hearted way please ;) think on it whenever you have some free time.
SELECT
c,s,i,o,e
FROM
COMPOSITION C...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Genetic inversion variant](https://discourse.openehr.org/t/genetic-inversion-variant/370)
> The archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published on March 4th. Link to the archetype: [https://ckm.openehr.org/ckm/archetypes/1013.1.3755](https://ckm.openehr.org/ckm/archetypes/1013.1.3755). Please reply to this topic if you have any objections or comments.
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [FHIR RDF and openEHR](https://discourse.openehr.org/t/fhir-rdf-and-openehr/369)
> Just came across FHIR RDF and read through the [documentation page](https://www.hl7.org/fhir/rdf.html). It looks like a shared common and generic way of describing FHIR resources. What would be the analogy for openEHR archetypes?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Financial summary archetype](https://discourse.openehr.org/t/financial-summary-archetype/368)
> After the pushback we received in the first review round of [the "Income summary" archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.2989), we're considering changing the concept to "Financial summary". It's got some of the same content as the Income summary archetype had, but the elements related to specific income have been removed, and a "Financial security" element has been added.
We've also renamed the "Primary income source" to "Source of money", and made it repeatable. The...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Revision of the clinical 'demographic archetypes'](https://discourse.openehr.org/t/revision-of-the-clinical-demographic-archetypes/367)
> There is a need to be able to detail/describe people/caregivers/roles within the clinical record or documents to be exchanged eg cc'd clinicians to a record or a list of caregivers in a referral. The current clinical archetypes were built over a decade ago and never had any formal review process.
Given the momentum of FHIR, logically it makes some sense to align the content with the FHIR models, to minimise need for mappings etc.
Are there any strong feelings against exploring this...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL - same logical AQL with different syntax](https://discourse.openehr.org/t/aql-same-logical-aql-with-different-syntax/366)
> What do you think about the following logic related to AQL?
The following AQLs will be intepreted as **logical equals for the AQL engine**. The first AQL 1.0 is a short hand query for the full AQL defined as AQL 1.3.
The examples is given here: https://github.com/bjornna/openehr-conformance/blob/master/aql/index.adoc#case-1
>AQL 1.0
select o from OBSERVATION o[openEHR-EHR-OBSERVATION.lab_test-result.v1]
> AQL 1.1
select o from COMPOSITION c
CONTAINS OBSERVATION...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Binding archetypes to SNOMED as an ontology?](https://discourse.openehr.org/t/binding-archetypes-to-snomed-as-an-ontology/364)
> The Norwegian archetype governance is working with the Norwegian SNOMED CT NRC to bind a set of vital signs archetypes to SNOMED CT. Initially we were both thinking the same way with regard to how this should be done, with Observable entitiy and Attribute SNOMED terms beng bound to data elements, and other concept types such as Finding, Physical object, Body structure for value sets. We didn't have an agreement on how or if the archetype top level nodes should be bound.
Lately though,...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Announcing openEHR Ambassador to Finland](https://discourse.openehr.org/t/announcing-openehr-ambassador-to-finland/360)
> openEHR International is delighted to announce the appointment of Hanna Pohjonen PhD as openEHR Ambassador to Finland. Read more [HERE](https://www.openehr.org/news_events/community_news/309)
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [PROMS archetypes: EQ-5D](https://discourse.openehr.org/t/proms-archetypes-eq-5d/357)
> Does anyone know of any archetypes that have been created for recording EQ-5D?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR Netherlands Working Group, 3rd March, Leiden Netherlands](https://discourse.openehr.org/t/openehr-netherlands-working-group-3rd-march-leiden-netherlands/356)
> openEHR Netherlands is organising another introduction workshop for the ZIBs working group for openEHR. This working group hope to accelerate the acceptance of openEHR in the Netherlands by making a reference implementation of ZIBs available in openEHR. More information and sign up to attend [HERE](https://www.eventbrite.nl/e/herhaling-werkgroep-zibs-voor-openehr-tickets-95244792739)
**[openEHR days](https://discourse.openehr.org/c/openehr-days/52)** - [Invite to openEHR Day, Finland, 25th March 2020](https://discourse.openehr.org/t/invite-to-openehr-day-finland-25th-march-2020/351)
> We would like to invite you to the next openEHR Day being held in Helsinki Finland on 25th March. For full information and to register see [HERE](https://www.eventbrite.com/e/openehr-day-tickets-93884702673).
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [POSTPONED: openEHR Day, Helsinki Finland, 25 March 2020](https://discourse.openehr.org/t/postponed-openehr-day-helsinki-finland-25-march-2020/349)
> For that last two weeks we have been closely following the situation with COVID-19 globally and as the virus continues to spread more rapidly, it is clearly necessary to cancel the openEHR day and openEHR social care workshop in Helsinki planned for 25th March.
UNA Oy and openEHR leaderships held a meeting last Friday and decided to cancel the events, with the idea of organising again sometime in the autumn.
Consideration to holding the event remotely had been given, but after input from...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Coding archetype concepts and nodes using terminology](https://discourse.openehr.org/t/coding-archetype-concepts-and-nodes-using-terminology/347)
> Many of the archetypes in CKM (for example Blood pressure - https://openehr.org/ckm/archetypes/1013.1.3574) have their concepts and nodes coded using SNOMED CT. I have the following queries regarding this
1. What tools can be used to do this? Can we use archetype editor and template designer for this? BTW, I am also not able to view these coding in template designer and archetype editor.
2. Once such coding is done, do the do they become part of every instance of the template?
3. Can we...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Product Forge Edinburgh Hack 20th-23rd Feb 2020](https://discourse.openehr.org/t/product-forge-edinburgh-hack-20th-23rd-feb-2020/342)
> I am going to this event next week, representing [Apperta](https://apperta.org.uk)
[Digital Health Product Forge 2020](https://productforge.io/events/digital-health-product-forge-2020)
with a small crew of volunteers, aiming to do an openEHR-based hack around something like this
https://www.nweurope.eu/media/8649/7-chal-chute-dhi-chance-hospital-at-home-v1-191119.pdf
openEHR CDR(s) , Alexa, Wearables, Smart scales, loads of fun (and beer). Maybe even a bit of FHIR and GraphQL
All welcome...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Clarify use of parameters in AQL queries](https://discourse.openehr.org/t/aql-clarify-use-of-parameters-in-aql-queries/341)
> Going over the section of 3.5 of the spec, based on Pablo's comments re the need to clarify how quotes are to be applied, I realised that we need to do more than that.
Reading Section 3.5.3 (where and how parameters are resolved), I can see that the spec is implying that some parameters can be recognised by the backends by default and their value would be provided during query execution. One such example is ehrUid.
I suggest we remove this particular feature of parameters. The example of...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [OpenEHR in Peri-Operative Medicine](https://discourse.openehr.org/t/openehr-in-peri-operative-medicine/340)
> I'm organising a meeting at Queen's Uni Belfast on 1-2 June 2020. I'm hoping to do a session on Tuesday on aspects of OpenEHR relevant to peri-operative medicine.
As a rough guide, the areas of clinical practice under consideration are :
* Pre-assessment/Pre-habilitation
* Surgical and Anaesthetic Digital Care Records
* Specialist Anaesthetic Care Records (e.g. Obs, Paeds, Dental, ECT)
* Continuous Physiological Monitoring - basic (e.g. ECG, Blood Pressure, SpO2 etc) or advanced (e.g....
**[BMM/Expressions](https://discourse.openehr.org/c/bmm-el/60)** - [Expression Language syntax](https://discourse.openehr.org/t/expression-language-syntax/335)
> Hello,
I'd like to know if there exists a syntax/grammar specification for the Expression Language (EL) since I will probably make use of this language in order to create constraints on archetypes (including conditional value set bindings) as a part of my research work.
Thanks.
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Multiple instantiations of templates](https://discourse.openehr.org/t/multiple-instantiations-of-templates/333)
> Hallo,
I don't know if it is mentioned somewhere in the specs, but is there a restriction on the amount of instances that may be instantiated for the same template in the the same EHR ? Is it possible to enforce e.g. that an anamnesis template may only exist one time, but the echocardiography template may exist in an unrestricted amount of times ?
Greetings
Georg
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Implementation of Instructions vs Actions in exchange](https://discourse.openehr.org/t/implementation-of-instructions-vs-actions-in-exchange/331)
> Hi everyone,
I'd love some advice that I can pass on to other modellers...
Many times it is clear where an INSTRUCTION or ACTION should be modelled in a template ie an order vs something that has been done.
In the clinical scenario where we want to extract and share a list of medications that a patient is currently taking I'm faced with two options...
1. Include the list of INSTRUCTIONs that make up the current Medication list, package it up and send to the receiving EHR, with the added...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Clarify types to be supported by ORDER BY](https://discourse.openehr.org/t/aql-clarify-types-to-be-supported-by-order-by/329)
> Raised by @bna on slack. I'd suggest basing this on https://discourse.openehr.org/t/aql-clarify-types-supported-by-relational-operators/321 Copying my response from slack:
ORDER BY is closely related to this since we can define it as based on the result of the relational operator x < y. So the RM types within the scope of ORDER by would be defined by the underlying relational operator < This would be a consistent way to define which types ORDER by would work on, based which types relational...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Nephrology and Transplant Medicine](https://discourse.openehr.org/t/nephrology-and-transplant-medicine/328)
> Hi everybody,
as announced last year, we started with the Nephro-Digital project in Germany. The project is about manged care of young patients with kidney transplants. Through a previous project (Screen Reject), we are lucky to already have some initital archetypes:
https://ckm.highmed.org/ckm/projects/1246.152.8
Although many of them are still German, I would like to figure out if there is international interest in this topic (e.g. I would like to hear from @wouterzanen if there is also...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Archetype specialization vs new archetypes](https://discourse.openehr.org/t/archetype-specialization-vs-new-archetypes/327)
> Hi,
What are the reason why we should specialize as opposed to creating new archetypes? Does it bring any advantages in querying? Can we use wild cards in aql to represent all specializations?
In understand that they help keep the closely related clinical concepts together and make it easy to manage them. But does it also offer any advantage in app development and run time as well?
regards
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [AQL to query the same node across multiple versions of any archetype](https://discourse.openehr.org/t/aql-to-query-the-same-node-across-multiple-versions-of-any-archetype/325)
> Hi,
What is the way to write an aql to query the same node in multiple versions of the same archetype? Is there a way to use a wild card or regex to include all versions of an archetype in the contains section of an archetype?
If that is not possible, can we include multiple versions as below and point the data nodes to the same key?
select
b_b/data[at0002]/events[at0003]/data[at0001]/items[at0004]/value/magnitude as weight, ...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Missing NodeId Elements](https://discourse.openehr.org/t/missing-nodeid-elements/324)
> Hi
I have been using the openEhr client library class to generate a composition based upon a couple of templates that I have been working with. However in order for the compositions to be generated without error, I have had to manually add elements to each element with a tag of "Children" e.g. , as the template I am using only has nodeId fields where there is a set value. I am just wondering if this perhaps an issue with the client library that I am using, and that nodeId's should...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: Formal definition of FROM clause](https://discourse.openehr.org/t/aql-formal-definition-of-from-clause/322)
> Here is the content I'd like to suggest for addition to AQL spec. The spec becomes a a bit repetitive if this is replaces 3.10.2 but I need to explain various things to expand the argument so I can live with it. Comments are welcome.
**3.10.2 FROM**
The `FROM` clause defines the scope of the query in terms of reference model (RM) types of data to be retrieved along with additional constraints that further narrow down the matching instances of data. These constraints can be constraints on...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Aql: clarify types supported by relational operators](https://discourse.openehr.org/t/aql-clarify-types-supported-by-relational-operators/321)
> I'd suggest the following clarifications to the specification regarding the use of relational operators:
Let's add a list of types supported by the relational operators > >= = != <= < and define expected behaviour.
We can later extend this list, but I think the ones below from the quantity package have high priority due to being used frequently. Type of value attribute in parenthesis.
DV_ORDINAL(Integer)
DV_SCALE(Real)
DV_PROPORTION(Real,Real)
DV_QUANTITY(Real,Int)...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL- New feature suggestion: descendant paths](https://discourse.openehr.org/t/aql-new-feature-suggestion-descendant-paths/320)
> @ian.mcnicoll @pablo can you please clarify the use case you have in mind for descendant paths and the suggested changes to current syntax? (i.e. under which clauses this should be available)
jira issue: https://openehr.atlassian.net/browse/SPECQUERY-18
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Fixing the 'end-block' problem](https://discourse.openehr.org/t/fixing-the-end-block-problem/315)
> Here's a typical example of the 'end-block' problem we get in current [Task Planning visual modelling language (VML)](https://specifications.openehr.org/releases/PROC/latest/tp_vml.html):
In the current version of things, every end-block has a visual node, as shown above. This makes for a 'long-tail' problem visually. If we were programming, it would be like a series of end -'}', finally getting to the outermost level.
So to fix...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [About the Task Planning/GDL category](https://discourse.openehr.org/t/about-the-task-planning-gdl-category/314)
> Use this category for discussing the [Task Planning and related specifications](https://specifications.openehr.org/releases/PROC/latest/index), as well as the [Guideline Definition Language (GDL)](https://specifications.openehr.org/releases/CDS/latest/index).
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [First editorial review of 'Living will' archetype](https://discourse.openehr.org/t/first-editorial-review-of-living-will-archetype/311)
> The [Living will archetype](https://openehr.org/ckm/archetypes/1013.1.4274/mindmap)
has been through a first review and we have setup a [Doodle poll](https://doodle.com/poll/ax9vkzqhvnvh58dn) for the first editorial review of the comments made. with a few critical invitees but others are welcome to join, if you'd like to participate or just get a feel for how the editorial process works.
Ian
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Any experiences of synthetich openEHR data, e.g. using Synthea?](https://discourse.openehr.org/t/any-experiences-of-synthetich-openehr-data-e-g-using-synthea/309)
> Hi!
Are you aware of any experiences of synthetich (fake) openEHR conformant data, generated e.g. using Synthea https://synthetichealth.github.io/synthea/ or similar?
Are there any openEHR based generation-source-code or datasets publicly available?
//Erik
P.s. I do know that the [ORBDA](https://journals.plos.org/plosone/article/comments?id=10.1371/journal.pone.0190028) dataset can be used for tests, but since it is based on real patient data it only contains the kind of data that was...
**[Community](https://discourse.openehr.org/c/community/10)** - [How to advertise the 2020 modelling program](https://discourse.openehr.org/t/how-to-advertise-the-2020-modelling-program/316)
> [quote="heather.leslie, post:1, topic:298"]
In order to kickstart the 2020 modelling program I’d like to offer everyone in the community the opportunity to contribute to the modelling priorities for this coming year.
[/quote]
I think we should consider how to advertise this new 'modelling campaign' much more widely at some point, both in specific countries and also across the openEHR community with some general news announcements.
thoughts?
**[OHDSI OMOP](https://discourse.openehr.org/c/omop/103)** - [OHDSI - and openEHR](https://discourse.openehr.org/t/ohdsi-and-openehr/308)
> Hi
Do anyone have any experiences with OHDSI - https://www.ohdsi.org/ ?
I was asked if it has any correlation/similarities/overlap with openEHR. Reading through the web page it seems more like a dataware house solution/spec.
I found this blog with a comment from @ian.mcnicoll : http://blog.thehyve.nl/blog/omop-ohdsi-health-informatics-environment
Appreciate any feedback!
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Extra data elements in archetypes representing clinical scores and scales](https://discourse.openehr.org/t/extra-data-elements-in-archetypes-representing-clinical-scores-and-scales/299)
> In the recent review of the ACVPU scale archetype (https://ckm.openehr.org/ckm/archetypes/1013.1.3317), a question has arisen about whether we should add any extra data elements to this archetype or any other archetypes that represent clinical scores or scales. Other examples of these are Glasgow Coma Scale (https://ckm.openehr.org/ckm/archetypes/1013.1.137), qSOFA score (https://ckm.openehr.org/ckm/archetypes/1013.1.3813) and ECOG performance status...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Setting clinical modelling priorities for 2020](https://discourse.openehr.org/t/setting-clinical-modelling-priorities-for-2020/298)
> Dear colleagues,
In the early days, 2009-ish, we voted on '[10 archetypes to save a life](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/2949124/Poll+Results+-+Top+10+archetypes+for+use+in+an+Emergency)'.
Then this segued into the infamous archetype sprint, which had great effect, although it became more of a marathon with extraordinarily complex models like Medications and Laboratory tests - you can view the current status...
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Public health archetypes](https://discourse.openehr.org/t/public-health-archetypes/297)
> From the latest coronavirus outbreak I kept wondering if anyone has developed some kind of public health archetypes (or more in general, some data aggregation archetypes)
Maybe a related question is if this kind of population-wide data can be easily represented with current RM
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [How to create a RMObject model for a given archetype or template using archie](https://discourse.openehr.org/t/how-to-create-a-rmobject-model-for-a-given-archetype-or-template-using-archie/296)
> I working on a small App where i need to present a archetype or a template for data input. i want to create a RMObject model so that i can set values into different data attributes by using this empty model. How can i create a RMObject model for a given archetype using Archie ?
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [OpenEHR with SNOMED,LOINC,HL-7 Support](https://discourse.openehr.org/t/openehr-with-snomed-loinc-hl-7-support/291)
> Hi,
We are a new startup and trying to implement a small EHR project by adopting an OpenEHR framework. Just wondering if most of the OpenEHR frameworks have the interfaces with SNOMED,LOINC and HL-7/FHIR by default or one has to build them?
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Rare Disease model in OpenEHR](https://discourse.openehr.org/t/rare-disease-model-in-openehr/287)
> Dear all,
We in Slovenia are planning the rare disease registry. Regarding cross border interoperability, I am asking if there are any OpenEHR models for rare diseases.
Thank you for the answer.
**[CKM](https://discourse.openehr.org/c/ckm/89)** - [What is the storage backed by CKM?](https://discourse.openehr.org/t/what-is-the-storage-backed-by-ckm/282)
> Is CKM storage is backed by a git repository ?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [About the Confs & Events category](https://discourse.openehr.org/t/about-the-confs-events-category/279)
> Category for posting about conferences and events featuring openEHR presentations, speakers, or other relevant content of interest more generally in health informatics.
**[News](https://discourse.openehr.org/c/community-news/25)** - [About the News category](https://discourse.openehr.org/t/about-the-news-category/278)
> openEHR community news items.
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Maybe consider a new category related to external events](https://discourse.openehr.org/t/maybe-consider-a-new-category-related-to-external-events/277)
> For example the current posts: coordinating attandance at MIE (or Medinfo) etc. Or external events where we should try to have openEHR representation like the WHO event...?
**[ADL](https://discourse.openehr.org/c/adl/40)** - [How to export opts in other languages](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274)
> Hello,
How can I export opts to have them containing another language (or just in that other language) using Template Designer? The archetypes used in those templates are already translated. I have tried adding additional language when exporting but nothing has changed, is there some other setting I am missing?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [export opt in other languages](https://discourse.openehr.org/t/export-opt-in-other-languages/16540)
> Hello,
How can I export opts to have them containing another language (or just in that other language) using Template Designer? The archetypes used in those templates are already translated. I have tried adding additional language when exporting but nothing has changed, is there some other setting I am missing?
Thank you.
Joyce
**[Ask IEB](https://discourse.openehr.org/c/ask-ieb/37)** - [Right archetype for new EHR app?](https://discourse.openehr.org/t/right-archetype-for-new-ehr-app/268)
> [We](https://nedap-healthcare.com/oplossingen/ons/) are building a new EHR app based on openEHR ADL2 to extend and replace our legacy EHR app.
Is [this](https://ckm.openehr.org/ckm/archetypes/1013.1.339) the right archetype to implement if we want to offer SOAP style medical notes?
How much can change since it's in concept status?
Where do I view what needs to be done to get it to an accepted status?
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Anyone presenting at/going to MIE2020 Geneva?](https://discourse.openehr.org/t/anyone-presenting-at-going-to-mie2020-geneva/266)
> Just wondering who is going to this or better still has a paper to present.
http://mie2020.org/en/programme/programme/
I am still deciding whether to go or not .. persuade me!!
Ian
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Consequences of bad modelling and lessons learned?](https://discourse.openehr.org/t/consequences-of-bad-modelling-and-lessons-learned/261)
> Hi everyone,
I would like to have a discussion about the consequences of bad modelling.
Usually if the modelling is good we know how beautiful that can be, but what happens if it's not? What are the further issues? What are the lessons learn? What was done to avoid these situations?
For me openEHR it's really great and has an awesome proposition to address many issues on current healthcare IT situation - which it's why I decided to go further on working with this technology, although it's...
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Proposed new specifications site home page](https://discourse.openehr.org/t/proposed-new-specifications-site-home-page/260)
> A new look for the specifications home page is [proposed here](https://specifications.openehr.org/index3). We aim to add more linking and some icons, but I would like to get feedback from specifications users to know if people feel it is generally better than [the current home page](https://specifications.openehr.org).
thanks
- thomas
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [How to handle Defining multiple roles without creating new archetypes](https://discourse.openehr.org/t/how-to-handle-defining-multiple-roles-without-creating-new-archetypes/258)
> Hi everyone,
I tried to design archetypes for many roles with different names and same item structure in demography.
should I create an archetype for each role name or there is other way?
I asked this question because I think role name comes from "name property in locatable"
if I use only one archetype how can I set the many **roles name**
thanks
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [OpenEHR. How to get started!?](https://discourse.openehr.org/t/openehr-how-to-get-started/254)
> Hi!
I'm a GP in Thailand who interested in IT things and just get interested by the idea of openEHR.
Since I'm really new to this community and may be replicate this topic so I would like to apologize beforehand.
I just wondering how to get start OpenEHR and want to confirm something.
1.We don't have to change database of EMR software that we already used.
Just mapping it with the library(or archetype) that already existed then we can use openEHR query(or AQL) to query the data in our...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL: 3. Rules for parameter substitution on AQL: which types will add or not quotes](https://discourse.openehr.org/t/aql-3-rules-for-parameter-substitution-on-aql-which-types-will-add-or-not-quotes/251)
> According to the current grammar:
```
DATE: '\'' DIGIT DIGIT DIGIT DIGIT DIGIT DIGIT DIGIT DIGIT 'T' DIGIT DIGIT DIGIT DIGIT DIGIT DIGIT '.' DIGIT DIGIT DIGIT '+' DIGIT DIGIT DIGIT DIGIT '\'';
STRING: '\'' ( ESC_SEQ | ~('\\'|'\'') )* '\''
| '"' ( ESC_SEQ | ~('\\'|'"') )* '"'
;
```
So this means that:
* ISO 8601 date/times are currently the non-expanded form, i.e. without dashes / colon (and are all full date/times, with TZ included), and require single quotes;
* Strings are...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [Swedish openEHR procurements & RFIs](https://discourse.openehr.org/t/swedish-openehr-procurements-rfis/247)
> Hi! Just a heads up that Region Östergötland (RÖ), a Swedish healthcare region serving approx. 500 000 inhabitants and providing some nation-wide Swedish services, will be conducting an openEHR platform procurement during the first quarter of 2020. It will likely at earliest open around mid-February and likely be open during approximately one month.
During 2019 RÖ has been testing how an openEHR platform fits our use cases, organization and workflows and now RÖ wants to procure a permanent...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [CDS / GDL support](https://discourse.openehr.org/t/cds-gdl-support/244)
> Hi,
New to this forum and have been looking at OpenEHR open source implementations for a while. I can’t see any CDS (/GDL) implementations. Is there anything out there or are all the implementations closed source?
Thanks,
Dave
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [BP terminology bindings](https://discourse.openehr.org/t/bp-terminology-bindings/241)
> HI all
Having a debate with some colleagues about the SNOMED CT binding in a proprietary UK GP system with respect to blood pressure, which uses:
163020007 |On examination - blood pressure reading (finding)|
Which is a finding.
To be terminologically correct my understanding is that values should be observable entities.
So I went to check our openEHR Blood Pressure archetype and it seems it too is using:
163030003 |On examination - Systolic blood pressure reading...
**[HL7 FHIR](https://discourse.openehr.org/c/fhir/101)** - [Relationship between FHIR and openEHR](https://discourse.openehr.org/t/relationship-between-fhir-and-openehr/236)
> I am new to openEHR ( and Health informatics in general ) space but find myself stuck with this question.
How do HL7 FHIR and openEHR relate ? I understand that HL7 v2 etc is basic messaging for interoperability. But FHIR seems to add some Clinical Data Modeling to this in the form of resources - A Visit with a Patient with an Observation is to my mind a Clinical Model no ? And when you add in a FHIR server concept are we not verging on the CDR ?
So then openEHR models the same Clinical...
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Pulse/Heart beat](https://discourse.openehr.org/t/pulse-heart-beat/233)
> The archetype has had breaking changes applied after first publication (see https://discourse.openehr.org/t/pulse-heart-beat-archetype-new-review-needed/), and is scheduled for republication as v2 on December 17.
Link to the archetype: https://ckm.openehr.org/ckm/archetypes/1013.1.170. Please reply to this topic if you have any objections or comments.
**[Entity/demographics](https://discourse.openehr.org/c/entity/112)** - [PARTY as 'regular' datatype](https://discourse.openehr.org/t/party-as-regular-datatype/231)
> Hi everybody,
I come across some cases where I think it would be beneficial if we could put an item of type Party into an Archetype. For example, the multimedia resource archetype has a field "author" that allows to capture information about the creator of a resource. Just using a URI instead of a DV_TEXT might be insufficient. Of course we might build an internal cluster and put a string and an URI together to build our own PARTY subtitute. Though, this does not seem to be an elegant...
**[RM](https://discourse.openehr.org/c/rm/42)** - [Representation of Episodes of Care and Encounters in folders](https://discourse.openehr.org/t/representation-of-episodes-of-care-and-encounters-in-folders/226)
> Hi everybody,
for HiGHmed, we explore the use of the newly introduced other_details field to represent above mentioned concepts. We aim to concurrently allow the mapping to corresponding FHIR resources. For me this appears to be a natural fit, as the care episodes and encounters have a hierarchical relationship and encounters on hospital level can be nested with clinic encounters (I refer to encounter as defined by FHIR: https://www.hl7.org/fhir/encounter.html). Furthermore, this is a nice...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [Modeling case question: quantity units depending on the element name coded value](https://discourse.openehr.org/t/modeling-case-question-quantity-units-depending-on-the-element-name-coded-value/225)
> Hi all, I have a question about clinical modeling: in a use case, which is similar to the current generic modeling for laboratory results, but for fluid replacement (solutions and blood products), I'm trying to model the recording of each solution or blood product administered to a patient by using a quantity as the value of the amount of fluid administered, and to say which was the fluid (saline solution, ringer, colloids, plasma, red cells, etc), I'm trying to use the ELEMENT.name as a...
**[ISO 13606](https://discourse.openehr.org/c/iso13606/105)** - [openEHR and ISO/CEN 13606 - what is the relationship?](https://discourse.openehr.org/t/openehr-and-iso-cen-13606-what-is-the-relationship/224)
> The relationship between openEHR and ISO/CEN 13606 is a common question for newcomers, and sometimes a source of confusion.
As an overview...
1. openEHR and 13606 share a common heritage and make use of two-level domain modelling, based on the Archetype Object Model, which though developed by openEHR, is itself part of the ISO13606 specification. Both use archetypes to define their clinical content but openEHR and 13606 archetypes are quite different and are not compatible.
2. Their...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Pulse/Heart beat archetype - new review needed?](https://discourse.openehr.org/t/pulse-heart-beat-archetype-new-review-needed/223)
> Recently, the Pulse/Heart beat archetype (https://ckm.openehr.org/ckm/archetypes/1013.1.170) had breaking changes applied to it, and its status set to "Reassess". The breaking change consists of the removal of two runtime name constraints, which fixes a problem discussed in this discussion thread: https://ckm.openehr.org/ckm/#showAComment_1013.18.1515_1013.1.170
I'm particularly looking for viewpoints from application developers, but others can of course voice their opinion too: Does this...
**[openEHR.br](https://discourse.openehr.org/c/openehr-brazil/17)** - [Considerações sobre o arquétipo 'Obstetric Summary' (Sumário Obstétrico)](https://discourse.openehr.org/t/consideracoes-sobre-o-arquetipo-obstetric-summary-sumario-obstetrico/216)
> Olá a todos,
Nas últimas duas semanas, revisamos o arquétipo 'Obstetric Summary'. Não apenas o conteúdo, mas também os conceitos e até o nome.
Removemos alguns dados e adicionamos outros. Você pode ver o resultado do rascunho neste link:
(https://ckm.openehr.org/ckm/archetypes/1013.1.4258)
O objetivo deste arquétipo é registrar informações resumidas ou persistentes sobre a história obstétrica de uma mulher, incluindo uma visão geral de todas as gestações e os resultados ou intervenções...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [Making openEHR Discourse work for you](https://discourse.openehr.org/t/making-openehr-discourse-work-for-you/212)
> New members of the openEHR Discourse forums site...
you may be wondering how to get Discourse to push new messages to you when people post to categories you are interested in, in the way that the old mailing lists did. It's easy: you can do it when you are visiting a Category by clicking on the circular icon at the right and choosing 'Watching':
Or in the your profile view (click top right avatar icon), choose :gear:...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Considerations on the Obstetric Summary archetype](https://discourse.openehr.org/t/considerations-on-the-obstetric-summary-archetype/209)
> Hi everyone,
For the past two weeks we've been reviewing the 'Obstetric summary' archetypes. Not only the content, but also the concepts and even the name.
We removed some data points and added others. You can see the draft result in this link:
https://ckm.openehr.org/ckm/archetypes/1013.1.4258
The purpose of this archetype is to record summary or persistent information about the obstetric history of a woman, including an overview of all pregnancies and the associated outcomes or...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Extracted CKM FHIR ValueSets](https://discourse.openehr.org/t/extracted-ckm-fhir-valuesets/204)
> I've extracted all possible subsets from CKM and put them online as FHIR ValueSets. ValueSets have been generated from DV_CodedTexts, DV_Ordinals and DV_Quantities (when they contain units subsets defined). 1024 ValueSets have been generated this way. This should be useful both for reuse and reviewing purposes.
List of available ValueSets can be accessed [here](https://linkehr.veratech.es/fhir/openehr_valuesets.html) or [downloaded in a...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Create native JSON composition format from OPT](https://discourse.openehr.org/t/create-native-json-composition-format-from-opt/198)
> Hi,
I am trying to test the EHRBase APIs and have been able to create EHR and sample templates(did not return success though the template was created) . The next is to create compositions.
Here I am stuck as the API expects the native JSON format for the composition. How can I create the JSON composition format from OPT? Is there any tool that I can use? In Ethercis, I used the template example format API to get a sample that I can use for compositions, but could not find something similar...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [New Procurements news sub-category](https://discourse.openehr.org/t/new-procurements-news-sub-category/196)
> We have created a new [Procurement sub-category](https://discourse.openehr.org/c/community-news/procurements) of the Community new category.
Please follow if you:
* work with procuring bodies such as MoHs, DoHs, etc, and want to post procurements for open platform solutions including openEHR;
* are a vendor or other implementer and want to be able to respond to procurement calls.
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [MoHW Jamaica RFI for national EHR system](https://discourse.openehr.org/t/mohw-jamaica-rfi-for-national-ehr-system/195)
> The *Government of Jamaica has received* financing from the Inter-American Development Bank (IDB) toward the cost of the Support for the Health Systems Strengthening for the Prevention and Care Management of Non- Communicable Diseases Programme, and intends to apply part of the proceeds for the procurement of an Electronic Health Record (EHR) Management System.
The Ministry of Health and Wellness now invites potential suppliers to provide general information about their company and product...
**[Procurements](https://discourse.openehr.org/c/procurements/24)** - [About the Procurements category](https://discourse.openehr.org/t/about-the-procurements-category/194)
> Please post here and/or follow this category if you:
~ work with **procuring authorities** such as MoHs, DoHs, etc, and want to post procurements for HIT solutions that include openEHR;
~ work with **healthcare provider institutions** issuing tenders;
~ are a **vendor or other implementer** and want to see tenders, RFIs etc.
The openEHR wikipage [Procurement of openEHR-related systems and...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [Aankondiging: werkgroep "ZIBs voor openEHR"](https://discourse.openehr.org/t/aankondiging-werkgroep-zibs-voor-openehr/188)
> De werkgroep ZIBs gaat op basis van bestaande en nieuw te creëren openEHR bouwblokken (archetypes) een referentie implementatie voor ZIBs binnen openEHR realiseren.
Deze werkgroep is bedoelt voor Iedereen die zich bezighoudt met informatiemodellen in de Zorg of daar interesse in heeft. Na een korte introductie gaan we aan de slag om de Basisgegevenset Zorg (BzG) te mappen op openEHR archetypes en templates.
Datum: **dinsdag 10 december 2019**
Tijd: **15:00 uur -18:00 uur,** inloop vanaf...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Duplicating data for reports, or some smarter solution?osen](https://discourse.openehr.org/t/duplicating-data-for-reports-or-some-smarter-solution-osen/178)
> Sorry for late response here. Days are too short!
With "ugly" and "monster-archetypes" I mean separate archetypes made for one purpose only, even though the data points are clinically valid and stored in their correct archetypes. One report form = One archetype and (at least some of the) data is duplicated.
For example the "Sick leave note", which is a big form - approx. 100 elements - and consists of a variety of information: Date the individual got sick, the ability to work, reason for...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [One page getting started guide](https://discourse.openehr.org/t/one-page-getting-started-guide/177)
> We (openEHRnl) get a lot of requests from people we speak to on what they should read/watch to get a good rounded first impression of different aspects of openEHR, I have setup a concept of this one page (I don't want to go larger).
https://docs.google.com/document/d/1E6tOzYfs9Aj-x1SVA8nJxnXr81VlLDUBLUYbaMvfyTk/edit?usp=sharing
I will be happy to receives comments on the resources I have quoted. The document is in dutch, but it should still be easily understandable ..
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [Edmonton Symptom Assessment System Revised (ESAS-r)](https://discourse.openehr.org/t/edmonton-symptom-assessment-system-revised-esas-r/176)
> The archetype has been through 1 review round. There seems to be consensus among the reviewers. The archetype will be published on the 25th of November. Link to the archetype: https://www.openehr.org/ckm/archetypes/1013.1.3819. Please reply to this topic if you have any objections or comments.
**[CKM publication](https://discourse.openehr.org/c/ckmpublication/23)** - [About the CKM publication category](https://discourse.openehr.org/t/about-the-ckm-publication-category/175)
> Category for announcing planned publication of archetypes on https://ckm.openehr.org.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Recommended use of RM Attributes while recording data](https://discourse.openehr.org/t/recommended-use-of-rm-attributes-while-recording-data/172)
> Hi,
The standard RM attributes for composition and entry classes include the subject and participations in all of them. When we model templates(for 1.4 OPTs), the entry archetypes always goes inside a composition(such as encounter). In a template with more than one entry archetypes, while the participations could be different for the encounter and the entries, the subject is always the same.
What is the recommended practice in recording the subject? do we do it at the composition level or...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Proposed Ethercis MKII and EHRBase. Are they the same project](https://discourse.openehr.org/t/proposed-ethercis-mkii-and-ehrbase-are-they-the-same-project/171)
> Hi,
I recall a Dec 2018 meeting in London where a proposal for Ethercis MKII was discussed and circulated to the community. Just wondering if EHRBase is a fallout of that or an independent initiative.
As I understand EHRBase builds on Ethercis, but uses the Archie library. Does it mean that the databases of Ethercis and EHRBase are compatible?
In light of the EHRBase imitative, will Ethercis continue it's development independently? Is EHRBase planning to offer data migration from...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Ordering vital sign measurements etc](https://discourse.openehr.org/t/ordering-vital-sign-measurements-etc/167)
> Hi everybody,
I got a question regarding instructions and actions. My understanding is, that we can use clusters to provide a formal description of the order, i.e. in the case of medication, we can provide clusters with details about the dosage. However, if we want to order the measurement using the blood pressure archetype and with defined details (position, pulse pressure), this does not work because of the entry class. It would be great to learn how you are dealing with this in practice....
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR: Modelling and Persisting Vendor-neutral Healthcare Data - 13 December Cardiff Wales UK](https://discourse.openehr.org/t/openehr-modelling-and-persisting-vendor-neutral-healthcare-data-13-december-cardiff-wales-uk/16625)
> *Event information posted also to the new [Discourse forums server](https://discourse.openehr.org) (Community News), which provides a more modern community experience than the current lists. We encourage you to create an account on the new server.*
**openEHR: Modelling and Persisting Vendor-neutral Healthcare Data - 13 December Cardiff Wales UK**
Over the past few years, openEHR based solutions within a multivendor environment have proven to be a successful approach to managing electronic...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR: Modelling and Persisting Vendor-neutral Healthcare Data - 13 December Cardiff Wales UK](https://discourse.openehr.org/t/openehr-modelling-and-persisting-vendor-neutral-healthcare-data-13-december-cardiff-wales-uk/163)
> Over the past few years, openEHR based solutions within a multivendor environment have proven to be a successful approach to managing electronic healthcare records at any scale. The technology is based upon an open and agile architecture, supporting multiple electronic health records (EHR) use cases with validated clinical models. These are stored in a vendor-neutral repository and underpin the principles of commoditising healthcare data management and maximising data fluidity.
This event is...
**[Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)** - [Missing interface definition in Task Planning Specification](https://discourse.openehr.org/t/missing-interface-definition-in-task-planning-specification/158)
>
The [Global Class Index](https://specifications.openehr.org/releases/AA_GLOBAL/latest/index.html) contains a link to the interface `I_TASK_PLAN_DEFINITION` which doesn't exist in the HTML page of the [ Task Planning Specification](https://specifications.openehr.org/releases/PROC/latest/task_planning.html#_i_task_plan_definition_interface).
Here is the ADOC file for this...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Mark topics as solved](https://discourse.openehr.org/t/mark-topics-as-solved/155)
> Hi,
From my point of view the greatest feature of Discourse is to be able to mark topics as solved.
Maybe you could consider to activate this plugin:
* https://discourse.openehr.org/admin/plugins
* https://github.com/discourse/discourse-solved
Kind regards,
Jan
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Great Medium article on openEHR and FHIR](https://discourse.openehr.org/t/great-medium-article-on-openehr-and-fhir/153)
> From Alastair Allan, CTO at Kainos Software.
> I recently presented at an openEHR event in London where I talked about my experience of working with #FHIR and #openEHR.
>
> Read more about it here [https://medium.com/@alastairallen/fhir-openehr-bef21694f76b](https://medium.com/@alastairallen/fhir-openehr-bef21694f76b) with credits to @wolands_cat, @ukpenguin, @rtweed and @JohnMeredith
https://twitter.com/alastairallen/status/1195375750347677697
Alastair also gave a great [presentation...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Duplicating data for reports, or some smarter solution?](https://discourse.openehr.org/t/duplicating-data-for-reports-or-some-smarter-solution/152)
> Reposting my post in Specifications (https://discourse.openehr.org/t/safety-features-in-aql-subject/137/42?u=varntzen):
When it comes to data that are exclusively registered for reporting (research, financial, sick leave formulas to authorities dealing with sickness benefit, etc) purposes, we’ve for now abandoned the report flag on compositions, and instead making , ugly, local archetypes to be used to duplicate data born in “real” archetypes made for primary documentation. Example:...
**[Releases](https://discourse.openehr.org/c/releases/57)** - [New LinkEHR version available with improved openEHR2FHIR transformation](https://discourse.openehr.org/t/new-linkehr-version-available-with-improved-openehr2fhir-transformation/151)
> (v2019115)
This version includes the following improvements:
* Improved openEHR2FHIR process
* OPT paths should be more readable now
* It is possible to generate several Observation profiles from a single archetype by changing the 'Group' (to group which Elements should end in the same Observation profile)
* Bundle profile generation from the generated Observation profiles
* Composition profile generation from the generated Observation profiles (only available if archetype is a...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Adding support to .adl/adls/opt/oet... as allowed file extensions in upload attachments](https://discourse.openehr.org/t/adding-support-to-adl-adls-opt-oet-as-allowed-file-extensions-in-upload-attachments/147)
> Sending little archetype snippets seems something we will end doing. I assume these file extensions (at least) should be added
**[RM](https://discourse.openehr.org/c/rm/42)** - [Links between data elements in different archetypes](https://discourse.openehr.org/t/links-between-data-elements-in-different-archetypes/146)
> I note the commentary in the specs on Links - [https://specifications.openehr.org/releases/RM/latest/common.html#_link_class](https://specifications.openehr.org/releases/RM/latest/common.html#_link_class).
However, despite feeling judged by the commentary :slight_smile:, I have what appears to be a non-sensible use case where we are curious about the possibility of establishing a link between source clinical data (ie captured using the CKM archetypes designed for clinical recording) and...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Hyperlinks barely visible in current config](https://discourse.openehr.org/t/hyperlinks-barely-visible-in-current-config/145)
> I've just added this topic and included a couple of hyperlinks (outlined in red) in the screenshot but even though I know they are there, I can barely discern them. I suspect others will not notice the link. Can hyper links be made more obvious please?
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [Service direction archetype review](https://discourse.openehr.org/t/service-direction-archetype-review/144)
> We have a review for the [Service direction CLUSTER archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.3181) active at present and we need some more reviewers.
It is intended to support complex requests that have varying patterns within a single day or over time, so we really need the input of implementers and technical people who might not ordinarily get involved in reviews.
The intent is that for a simple request, all data elements are already available within the...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Safety features in AQL: subject](https://discourse.openehr.org/t/safety-features-in-aql-subject/137)
> Hi everybody,
we recently discussed topics regarding use-cases in transplant medicine. This is a domain where the subject in entries is quite important to distinguish between donors and receivers. For example, lab values may need to be compared to create a banff classification. However, within AQL, values from donor and receiver cannot be easily distinguished as this would require an explicit statement about the subject of care within the AQL statement.
Hence, I would like to re-open the...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [openEHR Day held 28 Oct 2019 - links to presentations and other information](https://discourse.openehr.org/t/openehr-day-held-28-oct-2019-links-to-presentations-and-other-information/135)
> Following the recent openEHR Day held in London on 28th October, please find below links to presentations and other event materials for information.
Video Link: [https://www.youtube.com/playlist?list=PLhWi0RtmG26VgPo5SrYejhEJi0XXzUFfd](https://www.youtube.com/playlist?list=PLhWi0RtmG26VgPo5SrYejhEJi0XXzUFfd)
Presentations link: [https://www.dropbox.com/sh/j4xy0tjvzba2ci9/AACkYm7ZA5lx5kJewExbzWHka?dl=0](https://www.dropbox.com/sh/j4xy0tjvzba2ci9/AACkYm7ZA5lx5kJewExbzWHka?dl=0)
Photos of the...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Day held 28 Oct - presentations +](https://discourse.openehr.org/t/openehr-day-held-28-oct-presentations/16624)
> Following the recent openEHR Day, please find below links to presentations and other event materials for information.
Video Link: [https://www.youtube.com/playlist?list=PLhWi0RtmG26VgPo5SrYejhEJi0XXzUFfd](https://www.youtube.com/playlist?list=PLhWi0RtmG26VgPo5SrYejhEJi0XXzUFfd)
Presentations link: [https://www.dropbox.com/sh/j4xy0tjvzba2ci9/AACkYm7ZA5lx5kJewExbzWHka?dl=0](https://www.dropbox.com/sh/j4xy0tjvzba2ci9/AACkYm7ZA5lx5kJewExbzWHka?dl=0)
Photos of the event:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Event: Develop in the Open (DITO) - 3rd December Coventry UK](https://discourse.openehr.org/t/event-develop-in-the-open-dito-3rd-december-coventry-uk/14433)
> *Event information posted also to the new [Discourse forums server](https://discourse.openehr.org) (Community News), which provides a more modern community experience than the current lists. We encourage you to create an account on the new server.*
**Develop in the Open (DITO) Event – 6pm, 3rd December, Coventry University UK.**
The DITO project seeks to improve patient outcomes and reduce staff administration time when developing digital systems to enable their constant...
**[Confs & Events](https://discourse.openehr.org/c/conferences-events/26)** - [Develop in the Open (DITO) - Event - 3 Dec Coventry Univ UK](https://discourse.openehr.org/t/develop-in-the-open-dito-event-3-dec-coventry-univ-uk/133)
> The DITO project seeks to improve patient outcomes and reduce staff administration time when developing digital systems to enable their constant improvement and remove vendor lock-in. Solution based on openEHR, built upon the existing Ripple stack, is a good exemplar for openEHR members and supports the clinical modelling group of the Apperta Foundation.
Funded by Innovate UK, the DITO project looks at implementing an open approach to the full digital application life-cycle, developing an...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [AQL spec review for stabilization, formalization and cleanup](https://discourse.openehr.org/t/aql-spec-review-for-stabilization-formalization-and-cleanup/131)
> Hi all, I've reviewed the current AQL spec and the open tickets related to AQL in JIRA. Please check the comments/questions/suggestions to see if you agree (mainly for SEC members but general opinion would be good feedback) https://docs.google.com/document/d/1g8zOh06LhSNi1yFZWKuBzUX0bJN88r7mKpAFqDNi2JI/edit?usp=sharing
I'll start making some changes to the spec this week, reordering sections and adding missing information without changing the semantics of the operators and clauses.
We need...
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [Proper way of discerning between siblings that are instances of the same archetype in COMPOSITION](https://discourse.openehr.org/t/proper-way-of-discerning-between-siblings-that-are-instances-of-the-same-archetype-in-composition/127)
> Hi everyone, we're currently running a scenario here in Brazil in which modelers create the COMPOSITION in Ocean's Template Designer, export the OPT and TDS and deploy them to be distributed to external/public implementers. Since most of them have zero to little knowledge about openEHR, they use the TDS to create TDDs, and internally we have some transformation logic to turn them into canonical XML instances and commit (we're refactoring from EtherCIS to EHRbase).
A major issue we're dealing...
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [Best Database for openEHR](https://discourse.openehr.org/t/best-database-for-openehr/117)
> Which database would you advise for OpenEhr, and is there documentation about more details for that choice?
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [Process for typographical corrections in openEHR specifications](https://discourse.openehr.org/t/process-for-typographical-corrections-in-openehr-specifications/113)
> Hi,
I occasionally read through the various openEHR specifications for the sake of learning about the health IT domain. While doing so I sometimes find typographical mistakes, Asciidoc syntax problems, or broken links.
Since one pull request fixing typos was merged but others don't receive feedback on GitHub (since [13 Aug](https://github.com/openEHR/specifications-RM/pull/5) and [21 Sep](https://github.com/openEHR/specifications-RM/pull/8)) and I am wondering whether it's worth the time...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [DENWIS - Dutch Early Nurse Worry Indicator Score](https://discourse.openehr.org/t/denwis-dutch-early-nurse-worry-indicator-score/14432)
> We have been trying to find out more about use of the DENWIS score, and how it is practically implemented - do others have any experience? In particular we are not clear about what data is actually recorded...
Please join the discussion at our new Discourse forums at [https://discourse.openehr.org/t/denwis-dutch-early-nurse-worry-indicator-score/96](https://discourse.openehr.org/t/denwis-dutch-early-nurse-worry-indicator-score/96)
It is a free sign-up. I have been using Discourse for the UK...
**[AQL](https://discourse.openehr.org/c/aql/43)** - [Filtering signed documents in AQL](https://discourse.openehr.org/t/filtering-signed-documents-in-aql/106)
> Hi everyone,
we are having a question regarding AQL, and it would be great to have some input from the community. When querying our data, we need to be able to filter out non-signed entries (without ATTESTATION) . We are looking at different solutions, but all seem quite cumbersome. It becomes even harder when you have different signers for different parts of the composition. It seems like a common use case, but we were not able to find any info about it. Has anyone thought on how to solve...
**[ADL](https://discourse.openehr.org/c/adl/40)** - [OPT 1.4 Specification](https://discourse.openehr.org/t/opt-1-4-specification/105)
> Does anybody know about the whereabouts of the OPT1.4 specification? When I click the link on [https://specifications.openehr.org/](https://specifications.openehr.org/),I always get directed back to the same page.
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [openEHR REST APIs 1.0.1 Released](https://discourse.openehr.org/t/openehr-rest-apis-1-0-1-released/101)
> The [openEHR REST APIs Release 1.0.1](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.1/) is now out!
[Release notes - 14 Change Requests](https://openehr.atlassian.net/projects/SPECITS/versions/12528/tab/release-report-all-issues).
Thanks to the [SEC](https://www.openehr.org/programs/specification/editorialcommittee) and particularly @sebastian.iancu of Code24 who worked very hard to put this release together.
Although this is a so-called 'patch' release, it includes a...
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [New openEHR Discourse site replacing mailing lists](https://discourse.openehr.org/t/new-openehr-discourse-site-replacing-mailing-lists/97)
> As of today, **openEHR discussions will move** to our new [Discourse forums server](https://discourse.openehr.org), which provides a more modern community experience than the current lists. **We encourage you to create an account on the new server** .
## The new Discourse Facility
[[site code of conduct](https://discourse.openehr.org/faq) - please read]
The home page you will initially see looks [like this](https://discourse.openehr.org).
Some of the categories currently defined...
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [DENWIS - Dutch Early Nurse Worry Indicator Score](https://discourse.openehr.org/t/denwis-dutch-early-nurse-worry-indicator-score/96)
> 
We have been trying to find out more about use of this score, and how it is practically implemented - do others have any experience? In particular we are not clear about what data is actually recorded.
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [More Lab challenges](https://discourse.openehr.org/t/more-lab-challenges/86)
> My colleague Debora Farage at Core Consulting has done some excellent work on analysing lab results and she has put together a number of use cases that are interesting challenges for the current lab archetypes.
I have pasted these use cases into the [Lab Tests in openEHR wiki page](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/91139266/Implementing+Laboratory+Tests+in+openEHR).
The question is: how should each of these be met with the current lab archetypes? I continue to think...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Difficulty with signing up](https://discourse.openehr.org/t/difficulty-with-signing-up/81)
> I made it!
Could not get the sign in with google link to work last night.
Used my nes.scot.nhs.uk e-mail but no confirmation e-mail arrived. In inbox at 01:00 notification it had been quarantined by exchange, so released that this morning and seems to have worked.
Thanks for setting this up Marcus :slight_smile:
Does not like my initial topic title "Signing up issues" and keeps asking if it is a complete sentence.
I'll add a full stop.
Nope.
Change it to: "Difficulty with signing up"
Paul
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [More errors on site heading](https://discourse.openehr.org/t/more-errors-on-site-heading/65)
> 
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR Discourse site replacing mailing lists](https://discourse.openehr.org/t/new-openehr-discourse-site-replacing-mailing-lists/14431)
> As of today, **openEHR discussions will move** to our new [Discourse forums server](https://discourse.openehr.org), which provides a more modern community experience than the current lists. **We encourage you to create an account on the new server**.
## The new Discourse Facility
[[site code of conduct](https://discourse.openehr.org/faq) - please read]
The home page you will initially see looks like this:
![]()
See the [CR here](https://openehr.atlassian.net/browse/SPECRM-89).
The main changes are in [this section of the EHR IM](https://specifications.openehr.org/releases/RM/latest/ehr.html#_compositions).
Please have a read and consider whether we need more precision about when to use the 'episodic' category, and what it is used for, e.g. querying, grouping things in Folders etc.
**[openEHR.uk](https://discourse.openehr.org/c/openehr-uk/22)** - [About the openEHR.uk category](https://discourse.openehr.org/t/about-the-openehr-uk-category/46)
> Forum for those working with openEHR in the UK.
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Announcing openEHR International re-elected Board Members](https://discourse.openehr.org/t/announcing-openehr-international-re-elected-board-members/16622)
> Following the recent call for candidates to be nominated for 2 openEHR International Board positions, we had 2 people put themselves forward and therefore there is no need for voting to take place as both candidates will automatically be elected to the Board.
**The candidates re-elected are:-**
Individual Members: **Ian McNicoll**
Industry Partners: **Tomaž Gornik**
We would like to take this opportunity of thanking them both for standing for a further term – both have worked extremely...
**[openEHR.es](https://discourse.openehr.org/c/openehr-spain/21)** - [About the openEHR.es category](https://discourse.openehr.org/t/about-the-openehr-es-category/45)
> Forum for those working with openEHR in Spain. Spanish language welcome.
Foro para todos aquellos trabajando con openEHR en España y todos los países hispanohablantes. Son todos bienvenidos!
[openEHR.org.es site](http://openEHR.org.es).
**[openEHR.si](https://discourse.openehr.org/c/openehr-slovenia/20)** - [About the openEHR.si category](https://discourse.openehr.org/t/about-the-openehr-si-category/44)
> Forum for those working with openEHR in Slovenia. Slovenian language welcome.
**[openEHR.cn](https://discourse.openehr.org/c/openehr-china/19)** - [About the openEHR.cn category](https://discourse.openehr.org/t/about-the-openehr-cn-category/43)
> Forum for those working with openEHR in China.
Chinese language welcome.
[openEHR.org.cn site](http://openEHR.org.cn).
**[openEHR.jp](https://discourse.openehr.org/c/openehr-japan/18)** - [About the openEHR.jp category](https://discourse.openehr.org/t/about-the-openehr-jp-category/42)
> Forum for those working with openEHR in Japan.
Japanese language welcome.
[openEHR.jp site](http://openehr.jp).
**[openEHR.br](https://discourse.openehr.org/c/openehr-brazil/17)** - [About the openEHR.br category](https://discourse.openehr.org/t/about-the-openehr-br-category/41)
> Forum for those working with openEHR in Brazil.
Portuguese language welcome.
[openEHR.org.br site](http://openEHR.org.br).
**[openEHR.de](https://discourse.openehr.org/c/openehr-germany/16)** - [About the openEHR.de category](https://discourse.openehr.org/t/about-the-openehr-de-category/37)
> Forum for discussions about openEHR in Germany.
German language welcome.
[openEHR.de site](http://openehr.de).
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [Wrong logo on discourse site](https://discourse.openehr.org/t/wrong-logo-on-discourse-site/31)
> The discourse site logo uses the wrong colours. Suggest replacing it with https://openehr.org/media/uploads/2019/03/08/openehr_logo_rgb.svg.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [access on items in a cluster](https://discourse.openehr.org/t/access-on-items-in-a-cluster/15561)
> Hello,
I would like to typecheck AQL queries and have some problems doing that:
The items in a CLUSTER are of type ITEM\. If I access myCluster/items\[at0001\]/value, is there any possibility to type\-check the validity of this path without having the concrete archetype definition at hand? Just using the reference model isn't enough for this task, because ITEMs do not have a value\-field\.
How can \(from an object oriented point of view\) the values of the ITEMs be accessed without...
**[New to openEHR?](https://discourse.openehr.org/c/new-to-openehr/13)** - [About the New to openEHR? category](https://discourse.openehr.org/t/about-the-new-to-openehr-category/26)
> Just starting in openEHR? Ask questions here!
Some useful resources:
* [what is openEHR? (short summary of everything )](https://www.openehr.org/about/what_is_openehr)
* where do I find archetypes? [Clinical Knowledge Manager (CKM)](https://www.openehr.org/ckm/)
* [Online Archetype Designer](https://tools.openehr.org/designer/#/)
* [specifications home](https://specifications.openehr.org/)
* [openEHR for HL7 FHIR...
**[openEHR.nl](https://discourse.openehr.org/c/openehr-netherlands/12)** - [About the openEHR.nl category](https://discourse.openehr.org/t/about-the-openehr-nl-category/25)
> Discussion area for openEHR.nl Netherlands Affiliate members.
Dutch language welcome.
[openEHR.nl site](http://openehr.nl).
**[openEHR Affiliates](https://discourse.openehr.org/c/openehr-affiliates/11)** - [About the openEHR Affiliates category](https://discourse.openehr.org/t/about-the-openehr-affiliates-category/24)
> Forum for general issues relating to all openEHR Affiliates. See geography level sub-categories for your region.
**[Community](https://discourse.openehr.org/c/community/10)** - [About the Community category](https://discourse.openehr.org/t/about-the-community-category/22)
> News from the community, including:
* New academic projects
* New and updated vendor product releases
* Forthcoming training courses
**[openEHR news](https://discourse.openehr.org/c/openehr-news/9)** - [About the openEHR news category](https://discourse.openehr.org/t/about-the-openehr-news-category/21)
> Announcements from [openEHR International](https://www.openehr.org/governance/organisational_structure)
[Web archive of openehr-announce mailing list](https://www.mail-archive.com/openehr-announce@lists.openehr.org/).
**[Apps](https://discourse.openehr.org/c/app-dev/8)** - [About the Apps category](https://discourse.openehr.org/t/about-the-apps-category/19)
> Discuss app(lications) development, typically using [openEHR APIs](https://specifications.openehr.org/releases/ITS-REST/latest/index.html) and [AQL](https://specifications.openehr.org/releases/QUERY/latest/AQL.html).
**[Platform](https://discourse.openehr.org/c/platform-implem/7)** - [About the Platform category](https://discourse.openehr.org/t/about-the-platform-category/18)
> Discussions on openEHR platform (back-end, services) implementation.
[REST APIs spec](https://specifications.openehr.org/releases/ITS-REST/latest/overview.html);
[Abstract platform spec (PIM)](https://specifications.openehr.org/releases/SM/latest/openehr_platform.html)
[Web archive of openehr-implementers mailing list](https://www.mail-archive.com/openehr-implementers@lists.openehr.org/).
**[Specifications](https://discourse.openehr.org/c/specifications/6)** - [About the Specifications category](https://discourse.openehr.org/t/about-the-specifications-category/17)
> Discussions about the [openEHR specifications](https://specifications.openehr.org) | [Global UML website](https://specifications.openehr.org/releases/UML/latest/index.html). **ESSENTIAL**: *watch* sub-categories to get notifications.
[Web archives of openehr-technical mailing list](https://www.mail-archive.com/openehr-technical@lists.openehr.org/) .
**[Clinical](https://discourse.openehr.org/c/clinical/5)** - [About the Clinical category](https://discourse.openehr.org/t/about-the-clinical-category/16)
> Discuss healthcare use cases, clinical models, [CKM archetypes](https://ckm.openehr.org/). **ESSENTIAL**: *watch* sub-categories to get notifications.
[Web archive of openehr-clinical mailing list](https://www.mail-archive.com/openehr-clinical@lists.openehr.org/).
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR ADL2 published as ISO 13606-2:2019](https://discourse.openehr.org/t/openehr-adl2-published-as-iso-13606-2-2019/16620)
> In 2008, ADL 1.4 was adopted as the basis of ISO 13606-2.
A few years ago, the renewal process started for this standard, and as part of that, openEHR Foundation was asked to allow the ADL2 version of the Archetype Formalism (specifically, [the AOM2 specification](https://specifications.openehr.org/releases/AM/latest/AOM2.html)) to be used as the basis for the new version of 13606-2. The latter has now been published as ISO 13606-2:2019 ([ISO home...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Latest agenda for openEHR Day, 28th October, London.](https://discourse.openehr.org/t/latest-agenda-for-openehr-day-28th-october-london/16619)
> **Latest agenda for openEHR Day, 28th October, London.**
Please find below the latest agenda for the openEHR Day being held on Monday 28th October 2019 at SkillsMatter London, United Kingdom. If you’ve not booked your free place already and wish to attend you can still book online at [https://www.eventbrite.com/e/openehr-day-tickets-66842753475](https://www.eventbrite.com/e/openehr-day-tickets-66842753475)
08:30 – 09:00 Registration
09:00 – 09:20 Welcome, Ian McNicol...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Day London October 28th 2019](https://discourse.openehr.org/t/openehr-day-london-october-28th-2019/15730)
>
|
Dear friend,
Join us on the 28th of October, 2019, at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [name of language to define OPTs ?](https://discourse.openehr.org/t/name-of-language-to-define-opts/16621)
> Hello,
What is the language name in which templates \(OPT and OPT2\) are defined ?
Greetings
Georg
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [difference in expressability for archetype and template definitions](https://discourse.openehr.org/t/difference-in-expressability-for-archetype-and-template-definitions/15559)
> Hello,
In what extends does the specification language for defining archetypes and the language for defining templates differ ?
Both take existing data models \(RM types and archetypes\) and constrain them as needed\.
It is often said, that archetypes are used to recombine RM types and templates are used to recombine archetypes\. But the slot mechanism within the archetype definition does as well allow archetypes recombination within archetypes\. And the constraining that is done within...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Comments on "Terminologies in Information models", anyone?](https://discourse.openehr.org/t/comments-on-terminologies-in-information-models-anyone/14430)
> My thoughts:
- The picture is not wrong
- It needs more detail:
- Codes from codings systems are used in structures
- Ontologies are the ‘best’ coding systems, derived classifications are ‘good’ as well
- In structures codes are used in two ways: to give meaning to nodes in the structure, as
And to give meaning to the data fields in the structure.
-Since both codes and structures can give (i) meaning to concepts problems can occir (the Boundary Problem)
Additional rules how to use the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [information gain by "cardinality" ?](https://discourse.openehr.org/t/information-gain-by-cardinality/16623)
> Hello,
Constrained Container RM\-Types can define a "cardinality" for their list/array fields and the contained types can define "occurrences" for themselves inside the array\.
The summed max\-"occurrences" may never surpass the max\-"cardinality and the summed min\-"occurrences" may never be less than the min\-"cardinality"\.
The min\-max\-"occurrences" could perhaps even be calculated from the "occurrences"\.
What...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [data element type from the RM](https://discourse.openehr.org/t/data-element-type-from-the-rm/15557)
> Hello,
Which is the field that stores the RM\-model\-type of data elements ? When I use the ocean instance generator the json contains a field called "@xsi:type", which contains this information\. Where in the RM\-model itself is this type\-field defined ?
Greetings
Georg
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [definition of custom fields in archetypes](https://discourse.openehr.org/t/definition-of-custom-fields-in-archetypes/14429)
> Hallo,
I have a question about the degree of freedom in defining archetypes:
Archetypes are not composed but rather specified by constraining the base classes from the reference model\. Hence no new/custom field members can be definied in the definition of a new archetype but only the field members already existing in the base classes have to be used\. So there will never be a path like
a/myField/myProperty/value
but always just something like
a/data/events/items/value
The same applies...
**[Site Feedback](https://discourse.openehr.org/c/site-feedback/2)** - [About the Site Feedback category](https://discourse.openehr.org/t/about-the-site-feedback-category/1)
> Discussion about this site and how we can improve it.
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Board Nomination Call - Election for Director on openEHR International Board October 2019](https://discourse.openehr.org/t/openehr-board-nomination-call-election-for-director-on-openehr-international-board-october-2019/14425)
> Following the recent announcement regarding the new openEHR International (CIC), we now have 2 Director positions due for election to the openEHR International Board, with voting open only to existing paid Individual and Industry Partner members.
If you are not currently a paid-up member and wish to vote, you will need to ensure that your current membership is paid.
**The [Call for...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [International recognition for openEHR innovators](https://discourse.openehr.org/t/international-recognition-for-openehr-innovators/14434)
> We would like to record our huge pleasure in the international recognition of several people who have played key roles in the creation and development of openEHR to this point.
Sam Heard has been awarded the prestigious Order of Australia for his many services to that country, both nationally and internationally.
And Dipak Kalra and Heather Leslie have been made Fellows of the International Medical Informatics Association.
Each of these in their own way, has made invaluable contributions...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [API for adding data to an EHR](https://discourse.openehr.org/t/api-for-adding-data-to-an-ehr/14428)
> Hello,
In which part of the openEHR API is the definition of how to add an instance of a template to an existing EHR ?
Something like "add <serialized 'Health risk assessment'> to <id of EHR>" ?
Greetings
Georg
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Announcement from the openEHR Foundation and openEHR Community Interest Company](https://discourse.openehr.org/t/announcement-from-the-openehr-foundation-and-openehr-community-interest-company/14424)
> It is a great pleasure to record and announce recent seminal events in the evolution of openEHR.
First of these is to announce that the new openEHR Community Interest Company (CIC) is up and running. It has taken some months to complete the necessary organisational and legal arrangements but these are now complete.
The official legal name is ‘openEHR CIC’ but we will only use this inside legal and technical documents, and will use the ‘trading name’ of ‘openEHR International’ in most...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [schema of .oet xml templates](https://discourse.openehr.org/t/schema-of-oet-xml-templates/14427)
> Hello,
In the international CKM in the template "Demo with hide\-on\-form\.oet" there is a tag named "activityDescription"\. I thought that only a fixed set of tags \(e\.g\. "Content", "Item", "Rule"\) are allowed in template definitions\. This tag looks like is a field name of the archetypes "openEHR\-EHR\-INSTRUCTION\.imaging\.v1"\. If arbitrary field names are allowed in template definitions, can there be at all a fixed template...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Better DevDays - openEHR workshop](https://discourse.openehr.org/t/better-devdays-openehr-workshop/14418)
> Don't miss a two\-day workshop which will provide hands\-on development sessions on the Better Platform™\.
Dear member of openEHR tech community,
I'm kindly inviting you to our two\-day workshop which will provide hands\-on development sessions on the Better Platform™\. So please, mark your calendars for 1 and 2 October 2019 and join our experts for the event at the Skills Matter venue in London\. The workshop is designed to enable partners and implementation specialists to gain...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [usage of templates in AQL](https://discourse.openehr.org/t/usage-of-templates-in-aql/14426)
> Hello,
I have some question related to the coupling of AQL and templates:
Imagine I want to write an AQL query containing a certain archetype and that archetype is used in multiple templates in the openEHR system\.
What do I need to know about the data model structures of the templates potentially containing this archetype ?
When there are multiple templates that contain this archetypes, will they all be found by this query, no matter where the archetype is contained in their structure?
How...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openehr template specification questions](https://discourse.openehr.org/t/openehr-template-specification-questions/15728)
> Hello,
I am currently trying to learn the openEHR template format specification\.
The first thing I did was looking at the specification page \(https://specifications.openehr.org/), to see what template formats exist\. On this page OPT1\.4, OPT2 and AOM2 are listed as description laguages that somehow are related to templates\. \.oet is not listed on this page and I did not find a a formal definition of the xml\-specification for \.oet\.
Is there somewhere a formal \.oet specification ?
I...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Improving FHIR - the admin resources](https://discourse.openehr.org/t/improving-fhir-the-admin-resources/15727)
> For people trying to work with FHIR, [this post on how some of its Resources could be improved](https://wolandscat.net/2019/09/11/fixes-for-fhir-the-admin-resources/) may be of interest.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [templates in .oet and .opt](https://discourse.openehr.org/t/templates-in-oet-and-opt/16538)
> Hi,
I am not yet very familiar with templates and I only recently started digging into the documentation\.
One thing I encountered is the distiguishment between template \(\.oet\) and operational templates \(\.opt\)\.
I played a bit using the oceans\-toolbox and transformed some \.oets into \.opts\.
Although the oceans\-toolbox seems not capable to reimport the exported \.opts, it looks like both representations can be transformed into the other without loss of information\. E\.g\. in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [usage of references to archetype instances in templates ?](https://discourse.openehr.org/t/usage-of-references-to-archetype-instances-in-templates/16616)
> Hi,
Does openEHR contain the paradigm to reference instances of archetypes in template instances ? When I want to use an archetype instance in two different templates I have two possibilities, 1\. to duplicate the data and store it in the serialized objects of both template instances or 2\. to store the archetype instance once and reference it from within the template instances\. The 2nd option would have the advantage that I could change the data of the archetype instance and both template...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Medinfo 2019 program](https://discourse.openehr.org/t/openehr-medinfo-2019-program/14417)
> openEHR participation:
- **Aug 26** (Mo)
- 13:00 - 16:10 - Room: Gratte Ciel
- **Tutorial**: openEHR clinical modelling 101
- H Leslie, JT Valand, SL Bakke, V Arntzen
- **Aug 27 (Tu)**
- 11:50 - 12:10 - Room: Tête d'or 2
- **Paper**: Can openEHR represent the clinical concepts of an obstetric-specific EHR — ObsCare software?
- Danielle Santos Alves, Priscila A. Maranhão, Ana Margarida Pereira, Gustavo M. Bacelar-Silva, Tiago Silva-Costa, Thomas...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Help list openEHR procurements, related documents and things to think of!](https://discourse.openehr.org/t/help-list-openehr-procurements-related-documents-and-things-to-think-of/16618)
> Hi!
I have started a wikipage about "Procurement of openEHR-related systems":
[https://openehr.atlassian.net/wiki/spaces/resources/pages/416514052/Procurement+of+openEHR-related+systems](https://openehr.atlassian.net/wiki/spaces/resources/pages/416514052/Procurement+of+openEHR-related+systems)
(As a preparation for an upcoming, not yet started procurement)
Please help me list things there, it may help many others in similar situations now and in the future.
Hope to see some of you at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Modeling tool: current version and latest release date](https://discourse.openehr.org/t/modeling-tool-current-version-and-latest-release-date/14416)
> Hi all, when looking at the modeling tools page, I think it would be good to add more information like:
1. current version number
2. latest release date (we have very old tools there and some that are currently being updated)
3. RM versions supported (also different tools support different RM versions and some only one version, like the AE)
This information will be useful to pick the right tool for each project, and if we have tools that are not longer being maintained, it is also good to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [MEDINFO presentations.](https://discourse.openehr.org/t/medinfo-presentations/16617)
> Hi folks,
I updated openEHR related presentations in MEDINFO2019 at Wikipage\.
There are so many interesting topics\.
https://openehr.atlassian.net/wiki/spaces/resources/pages/320634886/MEDINFO2019?atlOrigin=eyJpIjoiOTdkY2U2ZGQwYjAzNDY0OThkMDYyMmUxYmNjYzMzNDQiLCJwIjoiYyJ9
If you find something wrong on this topic, please feel free to fix by
yourself or let me know\.
I am looking forward to meet you soon in Lyon, and have much
expectation for social events\.
Best regards,
Shinji Kobayashi
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [State of the clinical modelling program and international CKM](https://discourse.openehr.org/t/state-of-the-clinical-modelling-program-and-international-ckm/14415)
> Dear colleagues,
*Apologies for cross posting – just wanted to ensure that we share these insights broadly…*
We recently passed the eleven-year anniversary for the first upload to the international CKM – the body temperature archetype. As Europe readies itself for summer holidays and the clinical review season slows down, it is a good time to review the progress of the openEHR clinical modelling program.
Roughly 6 weeks ago I created and downloaded a number of reports from CKM. I’ve spent...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Template for Surgical Pre-Assessment](https://discourse.openehr.org/t/template-for-surgical-pre-assessment/15563)
> Hello All, been doing a bit of work (with help from Ian McNicoll) on an OpenEHR template for surgical pre-operative assessment.
You can view the results of my efforts (and Ian's) here :
[https://github.com/johngrant4est/surgical_preassessment](https://github.com/johngrant4est/surgical_preassessment)
and I'm not sure how this works in terms of sharing but the working repo is here...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR modeling for physical activity data etc. from personal health platforms (like Google Fitness, Apple Health, Samsung Health, Withings, Garmin, Polar, Strava, MyFitnessPal etc.)](https://discourse.openehr.org/t/openehr-modeling-for-physical-activity-data-etc-from-personal-health-platforms-like-google-fitness-apple-health-samsung-health-withings-garmin-polar-strava-myfitnesspal-etc/14323)
> Hi!
Those of you interested in openEHR modeling for physical activity data etc. from personal health platforms (like Google Fitness, Apple Health, Samsung Health, Withings, Garmin, Polar, Strava, MyFitnessPal etc.) may want to take a look at some of the info, links, mindmaps etc at [https://github.com/regionostergotland/openehr_definitions/tree/master/mindmaps](https://github.com/regionostergotland/openehr_definitions/tree/master/mindmaps)
Feel free to join the discussion and experimentation.
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archie 0.7.0 - ADL 1.4 to ADL 2 conversion](https://discourse.openehr.org/t/archie-0-7-0-adl-1-4-to-adl-2-conversion/14414)
> I’m pleased to announced the release of Archie version 0.7.0. This version brings the ability to import ADL 1.4 files to AOM 2, and to convert them to ADL 2.
This makes it possible to generate ADL 2 archetypes directly from within java-based ADL 1.4 tools. Note that there are some things you need to be aware of if you’re planning to do this, see the Archie readme for more information.
In addition, compliance to the XML and JSON schemas and to the RM specification has been improved, it is...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Problem orientation in OpenEHR](https://discourse.openehr.org/t/problem-orientation-in-openehr/15567)
> How would we do this?
There is a method of implementation in problem oriented records whereby a header, generally the ‘problem’, is linked to other record entries or elements that are to do with that problem.
So ‘chest pain’ as a problem may be linked to blood tests, clinical notes, ECG, CXR and medications that were ordered or reported as part of the work up of that condition.
In interfaces this allows for views of the record showing the Problem and all linked events/entries/data. It’s...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Significance of UID, template_id & concept in templates](https://discourse.openehr.org/t/significance-of-uid-template-id-concept-in-templates/16520)
> Hi,
Please see a snippet from an OPT that we have. I see that there are 3 different pieces of identification - UID, template_id & concept. Template_id seems to have been picked up automatically from the template file name and UID automatically generated by the template designer.
The concept is something that the person creating the template can optionally give and can be different from the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Choosing appropriate composition archetypes for recording smoking and drinking summary](https://discourse.openehr.org/t/choosing-appropriate-composition-archetypes-for-recording-smoking-and-drinking-summary/16515)
> Hi,
What would be the composition archetype recommended for a template to record summaries such as Smoking & drinking? The best that I could think of is the encounter composition. Do let me know if any other is better suited.
On a related note, are there any rules or best practices in choosing the appropriate composition archetype to use for building templates? Are we planning to have more composition archetypes such as Medication list & problem list for use with all kinds of different...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Mandatory fields in service_request.v1](https://discourse.openehr.org/t/mandatory-fields-in-service-request-v1/14413)
> Hi,
I am using [openEHR-EHR-INSTRUCTION.service_request.v1] in a template and notice that it has two mandatory nodes - narrative & current_activity:0/timing.
Narrative expects a human readable narrative of the request (mandatory for all instructions). But I am not sure what the 'timing' node expects. It takes any text value, but I am not sure what to put there.
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL for all specializations of an archetype](https://discourse.openehr.org/t/aql-for-all-specializations-of-an-archetype/14412)
> Hi,
Does AQL allow defining containment so that the basic archetype and all it's specializations can be included in the query? f yes can somebody share the syntax?
regards
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Downloading previous versions of archetypes from CKM](https://discourse.openehr.org/t/downloading-previous-versions-of-archetypes-from-ckm/15634)
> Hi,
I had used some archetypes from CKM in my templates some time back. Now when I am revising & reviewing them I notice that some of the archetypes have newer versions an so my templates give error as they are unable to locate the older versions that they use. So I have a few questions on the best practices for using CMK resources
1. Can I access older versions of archetypes from CKM? and how?
1. Should I maintain a copy of the archetype versions that are used in my templates...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Retrieving healthcare facility ID details using aql](https://discourse.openehr.org/t/retrieving-healthcare-facility-id-details-using-aql/14410)
> Hi,
I am committing the heatcare facility id context details n my compositions as below
"clinical_notes/context/health_care_facility|id": "123456-123",
"clinical_notes/context/health_care_facility|id_scheme": "UUID",
"clinical_notes/context/health_care_facility|id_namespace": "EHR.NETWORK",
"clinical_notes/context/health_care_facility|name": "HealtheLife",
Trying to retrieve this in aql using
c/context/health_care_facility/id/value as orgID...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with Pulse/Heart beat archetype](https://discourse.openehr.org/t/problem-with-pulse-heart-beat-archetype/14411)
> Hi,
The Pulse/Heart beat archetype from CKM,([https://www.openehr.org/ckm/archetypes/1013.1.170](https://www.openehr.org/ckm/archetypes/1013.1.170) ) when inserted into any template is giving error in Template designer (Node ID must not be null). Has any body faced this problem?
I think the problemis with the newer updates as I had used the same a year back with out any problem.
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL access of fields of potential subclasses or derived archetypes](https://discourse.openehr.org/t/aql-access-of-fields-of-potential-subclasses-or-derived-archetypes/15562)
> Hello,
I have a question the is a bit related to the discussion about the constraining of the ELEMENT type in the laboratory\_analytes\.
The current specification defines the field "ehr\_status" of the class EHR with the type OBJECT\_REF\. In the AQL specification there is an example \(chapter 3\.7\.2\.3\. NOT\) that accesses this field with the assumption that the field is of type EHR\_STATUS\.
I have written a type checker for AQL queries, so I am now stumbling across queries that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [constraining of laboratory_test_analyte Analyte result](https://discourse.openehr.org/t/constraining-of-laboratory-test-analyte-analyte-result/15552)
> Hello,
How do I constrain the Analyte result of a laboratory\_test\_analyte\.v1 ?
The Analyte result are defined as an ELEMENT that is only constrained by a node predicate \(i\.e\. ELEMENT\[at0001\]\)\. Therefore the results cannot be bound with a specialized type and an alias within the FROM part, as in the FROM part only archetypeID\-predicates are allowed and no node predicates\. As the result is defined with the abstract ELEMENT type, which has an abstract DATA\_VALUE as its content, no...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL query for blood pressure from the AQL documentation](https://discourse.openehr.org/t/aql-query-for-blood-pressure-from-the-aql-documentation/14420)
> Hello,
I have a problem with the interpretation of an AQL query from the AQL documentation\. In section 6\.3 the path to the value of the systolic blood pressure is
/data\[at0001\]/events\[at0006\]/data\[at0003\]/items\[at0004\]/value/value
The first part until
/data\[at0001\]/events\[at0006\]/data\[at0003\]/items\[at0004\]/value
denotes a DV\_QUANTITY\.
Where is the additional field 'value' of the type DV\_QUANTITY defined ?
The class itself defines the fields 'magnitude',...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [automatic demotion of lists in AQL ?](https://discourse.openehr.org/t/automatic-demotion-of-lists-in-aql/14419)
> Hello,
Is it allowed to use an element that is allowed to appear multiple times within a path ?
For example in the query
SELECT a/items\[at0001\]/value
FROM EHR e
CONTAINS CLUSTER a\[openEHR\-EHR\-CLUSTER\.laboratory\_test\_analyte\.v1\]
the field items\[at0001\] may appear 0\.\.\* times\. Thus the access to the value field is not properly defined from a type checking point of view\.
Does the AQL specification allow such constructs and how is this situation interpreted...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Genomics archetype reviews kick off today!](https://discourse.openehr.org/t/genomics-archetype-reviews-kick-off-today/15724)
> Dear colleagues,
I’d like to draw your attention to some exciting work just commencing on CKM – today we sent out our first genomics archetype for review. More will come over the next few weeks.
It has taken a small collaboration of subject matter experts nearly 8 months to design a coherent suite of archetypes to support how to record genetic test results.
The archetypes can now be seen in the Genomic Project on CKM -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL questions](https://discourse.openehr.org/t/aql-questions/16615)
> Hello,
I have some problems concerning the formulation of an AQL query\.
I would like to check a laboratory analyte within a laboratory test\. The analyte should have "Calcium" as analyte name and I would like to receive all EHRs that contain the analyte as the query result\.
The SELECT part seems easy, as I just want the EHRs, so this looks like this:
SELECT e
A problem I now have is about the nesting of the Archetypes\. As the test is an OBSERVATION and an EHR contains only...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [FHIR-like terminology 'binding strengths'?](https://discourse.openehr.org/t/fhir-like-terminology-binding-strengths/15609)
> Last week, we had a workshop on ADL2 in Germany, to try to sort out a few issues on the way to making ADL2 mainstream in openEHR implementations. [See here for the wiki page](https://openehr.atlassian.net/wiki/spaces/ADL/pages/382599192/ADL2%2BTooling%2BWorkshop%2B2019).
One of the issues discussed was on what basis terminology code constraints (value sets, generally) in archetypes (or templates) could be considered optional, recommended etc ([discussion page...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [GDL2 Guideline Language v2 released](https://discourse.openehr.org/t/gdl2-guideline-language-v2-released/14407)
> We are proud to announce the publication of the version 2 of the [Guideline Definition Language (GDL2) design specification](https://specifications.openehr.org/releases/CDS/latest/GDL2.html).
Exactly six years has passed since the first version of GDL was published by the openEHR Foundation, GDL-based CDS applications have been deployed to improve healthcare in Swedish regions, e.g. the stroke prevention app, clinically validated by a [large scale randomized clinical trial led by the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [How to write Github commit messages to connect to openEHR Jira issues](https://discourse.openehr.org/t/how-to-write-github-commit-messages-to-connect-to-openehr-jira-issues/16614)
> We have been doing this for a few years now, but we have installed the new Jira connector for Github projects under openEHR\. Here is a refresher on the instructions for writing commit messages if you are trying to connect to a Jira issue\.
https://openehr.atlassian.net/plugins/servlet/ac/com.github.integration.production/github-post-install-page
\- thomas
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Appropriate archetype for pulse recording in vitals](https://discourse.openehr.org/t/appropriate-archetype-for-pulse-recording-in-vitals/15568)
> Hi,
CKM includes two archetypes -
|
|
openEHR-EHR-OBSERVATION.pulse.v1 &
|
|
openEHR-EHR-OBSERVATION.respiration.v1, Both of which seem to be capturing very similar data.
Which is recommended for general vitals recording of pulse rate? What is the reason why we have 2 very similar archetypes?
regards
|
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Class of archetype 'Gender'](https://discourse.openehr.org/t/class-of-archetype-gender/14408)
> The only thing I can think of is that it would prevent that ENTRY archetype to be used within the details of a Demographic Actor (Patient/Agent), which could have a big impact
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Identity matching](https://discourse.openehr.org/t/identity-matching/14405)
> Among openEHR standard compliant platforms, what is the common strategy to handle patient identity management when sharing medical records in order to reduce mismatch, duplication, clinical trial candidate matching, …
What is the current most logical standard practices for (openEHR) administrators/community to handle patient matching issues if it involves sharing patient records between openEHR platforms and propriety EMR platforms?
Is there a role EMPI can play to assist this process...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Automation with openEHR & SNOMED-CT ontology reasoning](https://discourse.openehr.org/t/automation-with-openehr-snomed-ct-ontology-reasoning/14404)
> Hi all openEHR+Snomed CT hackers!
Doing the inference described below using a reasoner and openEHR with AQL+api calls as a bridge to EHR content would be pedagogical.
Who in the openEHR community will get a demo video out first?
Good luck with this little challenge!
Best regards,
Erik Sundvall
I am pleased to announce a short hands-on tutorial on using FHIR/RDF with the SNOMED-CT ontology: http://tinyurl.com/fhir-rdf-snomed-tut Try it out! A 90-second video also demonstrates the steps:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New SEC member Matija Polajnar](https://discourse.openehr.org/t/new-sec-member-matija-polajnar/14403)
> openEHR Specification Editorial Committee (SEC) news.
This month we see the departure of Boštjan Lah (from Marand) from the SEC, after having actively participated for 4 years, and as a result, improved the specifications development in that time. The Foundation and SEC greatly appreciate his involvement.
To replace him, we have a new member [Matija Polajnar](https://www.openehr.org/programs/specification/editorialcommittee#matija-polajnar), also from Marand, via election by the SEC. Matija...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Moving towards the use of SNOMED CT in place of local codes for better interoperability](https://discourse.openehr.org/t/moving-towards-the-use-of-snomed-ct-in-place-of-local-codes-for-better-interoperability/16407)
> Hi,
Many of the archetypes in the CKM use local codes extensively (Diagnosis certainty in problem diagnosis, severity category in symptom sign etc.). SNOMED CT seems to include reasonable replacements for a large number of these already.
Will it not make sense for reducing the use of local codes in archetypes as that will improve interoperability of OpenEHR modeled data beyond the OpenEHR ecosystem and also reduce management overhead for the modelling community?
Do we have any specific...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Task Planning Visual Modelling Language TP-VML](https://discourse.openehr.org/t/task-planning-visual-modelling-language-tp-vml/15721)
> For those interested in clinical workflow, Task Planning, etc, the [Task Planning Visual Modelling Language (TP-VML)](https://specifications.openehr.org/releases/PROC/latest/tp_vml.html) is taking shape, initially as a draw.io mode.
Hi everyone,
The CKM editors have been gradually refining our views on how to model Physical examination findings for many years now. There have been many hours wasted exploring options that have had dead ends. We’d like to prevent others having the same experience by sharing and publishing an agreed pattern and we feel that we have one ready for broader consumption.
We clearly needed to find a solution that works from a modelling point of view ensuring that the clinically diverse...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [serialization syntax of openEHR instance data](https://discourse.openehr.org/t/serialization-syntax-of-openehr-instance-data/16403)
> Hello,
Is there a documentation of the syntax how openEHR EHR data is serialized ? I would be interested in a concrete example of an EHR\-API\-GET\-call and the returned String in XML or JSON which can be used as transfer medium between applications or as a storage format\. It would be beneficial if the example EHR would contain some commonly used archetypes and some usual demographics data\.
I have taken a look at https://openehr.github.io/specifications-ITS-REST/ehr.html and at the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [JSON for definitions-notation](https://discourse.openehr.org/t/json-for-definitions-notation/15543)
> I always admired OpenEhr for its ability to notate archetype\-definitions and now also BMM definitions in any type\.
I saw experiments in XML, but the official endorsed notation language is ADL\.
I wonder, would it also be possible to write archetypes and reference\-models in JSON?
If so, it would save us tons of code, no grammars needed, no parsers needed\. Many programming languages support JSON out of the box, with only some annotations needed\. NoSQL Databases often support JSON, and...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EtherCIS update: growing the open source community effort in openEHR](https://discourse.openehr.org/t/ethercis-update-growing-the-open-source-community-effort-in-openehr/15720)
> Dear colleagues,
We are pleased to update the openEHR community on the outcome of our EtherCIS camp held over 3 days in London in December 2018.
A group of 12 individuals, representing 8 nationalities, from academia, commercial and non-profit sectors came together to explore, discuss and plan the growth of EtherCIS and the open source openEHR community via an EtherCIS MkII plan. See here for the related roadmap that was agreed by the group as the way forward....
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archie version 0.6.0 released](https://discourse.openehr.org/t/archie-version-0-6-0-released/15551)
> Today I’m pleased to announce another major release of the Archie library. This release brings a number of new features and improvements:
- A tool that constructs valid json example instances of RM Objects, based on an operational template. Can be parsed to RM Objects.
- Native ODIN serialization of arbitrary java objects using the Jackson library, now used in Archetype and P_BMM serialization
- The library is now supported on Android, Android 8.0/API level 26 and higher, including faster...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Rules in archetypes - what are the requirements?](https://discourse.openehr.org/t/rules-in-archetypes-what-are-the-requirements/15354)
> For many years, there has been a little-used capability in ADL which enables basic expressions to be stated such as the following in the Apgar Observation archetype:
**`rules`**
`*score_sum*: /data[id3]/events[id4]/data[id2]/items[id26]/value[id44]/magnitude = /data[id3]/events[id4]/data[id2]/items[id6]/value[id40]/value + /data[id3]/events[id4]/data[id2]/items[id10]/value[id39]/value + /data[id3]/events[id4]/data[id2]/items[id14]/value[id41]/value +...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Useful openEHR terminology Links on specifications page](https://discourse.openehr.org/t/useful-openehr-terminology-links-on-specifications-page/14402)
> There are now some useful links to get to any openEHR terminology group on the [specifications home page ](https://specifications.openehr.org)(scroll down) in one click.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [BASE Component 1.1.0 Release published](https://discourse.openehr.org/t/base-component-1-1-0-release-published/16613)
> BASE component Release 1.1.0 [has been published](https://specifications.openehr.org/releases/BASE/Release-1.1.0/) by the [openEHR SEC](https://www.openehr.org/programs/specification/editorialcommittee).
It contains a number of improvements to the [Architecture Overview](https://specifications.openehr.org/releases/BASE/Release-1.1.0/architecture_overview.html), and formalises the [Foundation](https://specifications.openehr.org/releases/BASE/Release-1.1.0/foundation_types.html) and [Base...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New openEHR XML schemas](https://discourse.openehr.org/t/new-openehr-xml-schemas/16612)
> Hi all,
I've been working in the last 2 months on a new release for XML Schemas (XSDs). We had several discussions inside the SEC group and we also had several issues recorded in our JIRA environment, all about what needs to be changed and how. We reached a point where most of the intentions and planned actions are performed, but now we would like to have (some) more feedback from you, the community. It will help us proceed to final steps towards releasing these new schemas.
If you did not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Error in website](https://discourse.openehr.org/t/error-in-website/15717)
> Don't know where to tell this, but there is something not okay on:
https://specifications.openehr.org/releases/ITS/latest/index
Many links don't work
Bert
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR RM Release 1.0.4 published](https://discourse.openehr.org/t/openehr-rm-release-1-0-4-published/16611)
> The openEHR [Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) is proud to announce **[Release 1.0.4 of the Reference Model (RM)](https://specifications.openehr.org/releases/RM/Release-1.0.4/)** component of openEHR.
This release implements [25 Change Requests](https://openehr.atlassian.net/projects/SPECRM/versions/11074/tab/release-report-all-issues) (CRs), including:
- support Markdown in DV_TEXT / DvText;
- allow context data...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [DV_PROPORTION vs DV_QUANTITY for %](https://discourse.openehr.org/t/dv-proportion-vs-dv-quantity-for/15555)
> I would have guessed it would be the other way around. If you know at design time that this value will be a percentage, use the DV_PROPORTION data type with the ‘type’ attribute set to 2 (percent, denominator fixed to 100). On the other hand if you don’t know for sure (such as for some lab results or medication strengths which could be for example mg/ml or % interchangeably), you would use DV_QUANTITY.
Regards,
**Silje**
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_PROPORTION vs DV_QUANTITY for %](https://discourse.openehr.org/t/dv-proportion-vs-dv-quantity-for/14421)
> Hi everyone, happy new year!
We’ve just hit a question about modelling choices, how to represent percentages. We have a data type DV_PROPORTION, which can be used to represent any proportion such as a fraction or a percentage, and we have the DV_QUANTITY data type which can have % as the unit. In most existing archetypes such as the OBSERVATION.pulse_oximetry archetype, we’ve used the DV_PROPORTION data type for the percent elements, while for some reason in the draft...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Future Governance for openEHR](https://discourse.openehr.org/t/future-governance-for-openehr/14400)
> **Future Governance for openEHR**
We are pleased to announce that Articles of Association for the new openEHR Community Interest Company (‘openEHR CIC’) and revised articles for the existing openEHR Foundation were adopted at the Foundation Annual General Meeting at UCL, in London, on October 16th.
There has been extensive discussion about these changes within our community, over several years. The gestation period has been prolonged but there has been benefit from allowing ideas to be...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Christmas greetings from the CKM team](https://discourse.openehr.org/t/christmas-greetings-from-the-ckm-team/14401)
> Hi everyone,
What a year it has been, and great to be able to reflect back on achievements and the gathering momentum.
Silje Ljosland Bakke and myself, as clinical program leads would like to thank everyone for their contributions and efforts over the year.
Some stats to provide some insight into the ‘state of the CKM’ and activity over the year:
- Archetypes
- 443 archetypes available, distributed over 35 projects; and a further 102 ungoverned ones evolving in incubators
- In...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Coding the DV_IDENTIFIER 'type'](https://discourse.openehr.org/t/coding-the-dv-identifier-type/16610)
> Hi,
In the documentation for the DV_IDENTIFIER data type ([https://specifications.openehr.org/releases/RM/Release-1.0.3/data_types.html#_dv_identifier_class](https://specifications.openehr.org/releases/RM/Release-1.0.3/data_types.html#_dv_identifier_class)), the attribute ‘type’ is described as “Optional identifier type, such as prescription , or Social Security Number . **One day a controlled vocabulary might be possible for this.**” (my emphasis). Is it possible to code this at the moment,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Christmas cleaning of the openEHR wiki...](https://discourse.openehr.org/t/christmas-cleaning-of-the-openehr-wiki/15664)
> Hi everyone,
Sorry for the crossposting, but I thought this would concern everyone.
I believe the openEHR wiki is an important documentation tool that has probably been a bit neglected(?). The default Confluence theme isn’t super pretty, and the site is difficult to navigate, in my opinion because of the large number of spaces and the lack of a proper front page for the site as a whole.
I’d like to suggest reducing the number of spaces by removing/merging/archiving the spaces that are...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR REST API version 1.0.0 released](https://discourse.openehr.org/t/openehr-rest-api-version-1-0-0-released/16607)
> The [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) is pleased to announce the release of the [openEHR REST API version 1.0.0](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.0/). It contains three APIs:
- [EHR API](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.0/ehr.html)
- [Definitions API](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.0/definitions.html) -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Syntax for including archetypes in SLOTs, regardless of version](https://discourse.openehr.org/t/syntax-for-including-archetypes-in-slots-regardless-of-version/16725)
> Hi,
Sebastian Garde and I had a brainstorm a while ago about how to handle inclusion of archetypes in SLOTs (either CLUSTERs within ENTRY archetypes, or ENTRY archetypes within COMPOSITIONs or SECTIONs). At the moment this has to be noted explicitly (whether because of tooling or the specifications, I don’t know), so that in order to include for example all historical versions and specialisations of the Body Mass Index archetype in a COMPOSITION or SECTION, I have to include both...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Foundation AGM, Oct 2018 - Report from the Chair – Professor David Ingram](https://discourse.openehr.org/t/openehr-foundation-agm-oct-2018-report-from-the-chair-professor-david-ingram/16606)
> openEHR Foundation
Annual General Meeting at UCLB, October 22nd, 2018
Report from the Chair – Professor David Ingram
[[website link to report]](https://www.openehr.org/news_events/foundation_news.php?id=253)
Today’s AGM brings openEHR to an exciting new juncture in its evolution.
In this final report to UCL, as the sole member organisation of the Foundation, I would like to recognise and record thanks to many colleagues and groups, without whose efforts and staying power, over many...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR on FHIR and vice versa](https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548)
> Hello,
I have just read the paper "Combining Archetypes with Fast Health Interoperability Resources in Future\-proof Health Information Systems", in which the representation of openEHR archetypes as FHIR profiles is presented\. As I am also trying to use this approach and I wonder if there are working and publicly available applications \(possibly emerged from the above mentioned research\) that use that approach ? I am especially interested in:
\- transforming openEHR archetypes...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Use of LinkEHR to create OPTs like we do with Template designer](https://discourse.openehr.org/t/use-of-linkehr-to-create-opts-like-we-do-with-template-designer/15549)
> HI,
I have been using Archetype editor and Template designer so far and am experimenting with LinkEHR studio. I have managed to import, visualize and edit OpenEHR archetypes(1.4).
However I am not able to understand how to combine archetypes into a template (like we do in Template designer) and export OPTs.I am importing these OPTs into an EtherCIS server. Is this possible? if yes can somebody point to the documentation for this(the documentation from LinkEGR only talks about...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [use_node semantics](https://discourse.openehr.org/t/use-node-semantics/16608)
> Hello,
I am unsure about the semantics of the use\_node keyword\. Can the archetype branch that is attached at the place where use\_node is mentioned be seen like when a preprocessor would paste the part of the referenced branch into the place where use\_node is used ? In practice this could create problems when a recursive insertion of the referenced branch is inserted, but from a logical point of view is that interpretation correct ?
Is an archetype using use\_node\-branches equivalent to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ID namespace for composer and healthcare facility](https://discourse.openehr.org/t/id-namespace-for-composer-and-healthcare-facility/14053)
> Hi,
Compositions require id_namespace for composer and healthcare facility, along with id & id_scheme, to uniquely identify them. How do we ensure universal uniqueness for such name spaces? Is there any central registry where EHR systems are supposed to register their namespaces?
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reference Model as Archetypes ?](https://discourse.openehr.org/t/reference-model-as-archetypes/15546)
> Hello,
Is there somewere a machine readable definition available which describes the content of the openEHR Reference Model as Archetypes ?
The Reference Model classes should be expressable as Archetypes, shouldn't they ? At least concerning their logical data model\. The methods they also possibly provide can hardly be expressed using Archetypes\.
Greetings
Georg
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL specification question](https://discourse.openehr.org/t/adl-specification-question/14397)
> Hello,
I have an archetype with a complex object derived of CLUSTER with
"items cardinality matches \{2\.\.\*; ordered\}"
and those two items are also defined inside the complex object\.
I understand the semantics of this definition that both items always have to appear together inside the cluster but the package of those two items may appear any number of times\.
Is it allowed for instances of this archetype to have an uneven number of items > 2 inside this cluster, because that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Two-level modelling diagram](https://discourse.openehr.org/t/two-level-modelling-diagram/15716)
> [This diagram ](https://www.openehr.org/releases/BASE/latest/docs/architecture_overview/diagrams/two_level_engineering.svg)(SVG) is a replacement for an old one used in a lot of papers. People who want a better diagram might like this one, from a more recent version of the Architecture Overview.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Better definition of 'system_id' attribute in openEHR sytems](https://discourse.openehr.org/t/better-definition-of-system-id-attribute-in-openehr-sytems/16609)
> Following [SPECPR-99](https://openehr.atlassian.net/browse/SPECPR-99) and [this email string](http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2014-August/008468.html) from 2014, the imminent RM 1.0.4 release will include [SPECRM-80](https://openehr.atlassian.net/browse/SPECRM-80), which improves the documentation about *system_id*, which is recorded in the EHR and also in AUDIT_DETAILS, i.e. on each committed version.
In response to this, I have added the following...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 80, Issue 12](https://discourse.openehr.org/t/openehr-technical-digest-vol-80-issue-12/15254)
> Hi all,
It's been a while since I've seen it but I think Pablo Pazos has some quite good work for that topic on EHRServer, at least for subsumption [[https://ppazos.github.io/cabolabs-ehrserver/](https://ppazos.github.io/cabolabs-ehrserver/) mentions "Support of SNOMED CT Expressions on openEHR queries (simplifies complex queries)"]. There is also a demonstration video on YouTube. With regards to binding to the model, though, things might be tricky.
Cheers,
Ricardo Gonçalves.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR BMM files have moved to new specifications-ITS-BMM repository](https://discourse.openehr.org/t/openehr-bmm-files-have-moved-to-new-specifications-its-bmm-repository/15715)
> **Attention all users of the openEHR BMM files**:
these used to be in the [Github repo reference-models](https://github.com/openEHR/reference-models), but have now moved to [specifications-ITS-BMM Github repo](https://github.com/openEHR/specifications-ITS-BMM). They have also had numerous small errors fixed by Kristoffer Lundberg, Chief architect at Cambio Health Systems, for which we are very grateful.
The files are laid out in a different way, with the directory structure reflecting the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Postcoordinated terminology expressions in openEHR](https://discourse.openehr.org/t/postcoordinated-terminology-expressions-in-openehr/15554)
> Hi everyone,
We’ve recently started an informal and practically oriented regular contact with the Norwegian SNOMED CT NRC. One of the things they were interested in discussing was how to use postcoordinated SNOMED CT (expression constraint language) expressions with openEHR, which I know nothing about. Does anyone have any knowledge about or experience with this?
Kind regards,
**Silje Ljosland Bakke**
Information Architect, RN
Coordinator, National Editorial Board for Archetypes
Nasjonal...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Oslo SEC meeting news](https://discourse.openehr.org/t/oslo-sec-meeting-news/16603)
> 
The recent Specifications Editorial Committee (SEC) meeting in Oslo ([meeting page](https://openehr.atlassian.net/wiki/spaces/spec/pages/352157702/2018-11-05+openEHR+SEC+Meeting+Oslo)), generously hosted and provided for at the offices of [DIPS](https://www.openehr.org/industry_partners/dips), made great progress, including:
- The [REST APIs...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes for consent, end-of-life planning and advance decision to refuse treatment](https://discourse.openehr.org/t/archetypes-for-consent-end-of-life-planning-and-advance-decision-to-refuse-treatment/16605)
> Dear Ian,
We are in discussions with a state government in India for the use of our EHR.Network platform for implementing a public Mental Health Management System(MHMS) in line with the Indian National mental healthcare act 2017(MHA).
Some of the requirements of this system are registration of advance directives, consent and designated persons. As the MHA defines mental healthcare as a right, these directives hold a very critical role in care related decisions.
While exploring options and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parsing of Archetypes/Templates](https://discourse.openehr.org/t/parsing-of-archetypes-templates/15547)
> Hello,
For a project we want to create a generic mechanism to transform archetypes into FHIR Logical Models, so we can store, retrieve and query archetype instance with FHIR tools \(CQL, FHIR\-REST\-API\-query\)\. At the moment we just want to read/write archetypes and not archetype instances\. We are looking for existing components to parse and process archetypes\. I have some questions I encountered related to these issues:
\- I have found several projects that store openEHR\-data...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GDPR and consent - Sitra's IHAN blueprint](https://discourse.openehr.org/t/gdpr-and-consent-sitras-ihan-blueprint/15713)
> Finland's Sitra institute (something like Fraunhoffer in Germany) has published a very interesting [paper on a GDPR-compliant architecture for consent](https://media.sitra.fi/2018/09/25133347/180925-ihan-blueprint.pdf).
I have not fully digested yet, but I thought I would share here.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL on versioned compositions](https://discourse.openehr.org/t/aql-on-versioned-compositions/14394)
> Hi,
We are implementing virtual folders to organize compositions as per episodes of care and encounters. The plan is to keep track of versioned compositions in encounters to capture the change of information(Complaints and diagnosis getting resolved across encounters inside an episode).This will allow us to view the compositions as they were in any encounter and not the latest version always.
For this we need to be able to query specific versions of compositions using aql. Can some body...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question about: openEHR-EHR-CLUSTER.microscopy_breast_carcinoma.v1](https://discourse.openehr.org/t/question-about-openehr-ehr-cluster-microscopy-breast-carcinoma-v1/14395)
> Hi,
I'm a master student at Linköpings University and are writing my master thesis as a part of the Biomedical engineering program. The thesis is about investigating the possibility to create a dynamic template for breast specimen, with openEHR and SNOMED CT, in the pathology lab to replace four static locally created templates.
I've found the archetype *openEHR-EHR-CLUSTER.microscopy_breast_carcinoma.v1* and I was wondering if someone has done anything similar?
If someone has created a...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [on the passing of Hildegard McNicoll 1959 - 2018](https://discourse.openehr.org/t/on-the-passing-of-hildegard-mcnicoll-1959-2018/16602)
> Hildegard McNicoll, one of our key community members and the wife of Ian McNicoll passed away on Sunday 21 October after a short episode of pneumonia related to her breast cancer recurrence. In fact she had many happy months since her latest diagnosis and commencement of chemotherapy, which performed well.
Those of you who knew her will remember a wonderful woman with a discerning mind, endless drive and an impish sense of humour, who wasted no time in 'getting on with life'. Her presence in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [e-health services landscape - initial proposal, open forum](https://discourse.openehr.org/t/e-health-services-landscape-initial-proposal-open-forum/14393)
> Every so often I get bored of what I am doing and start trying to draw one of those 'services roadmap' kind of diagrams. These often pretty pictures appear in slide presentations, in standards, whitepapers etc, but are not often used as a tool to help map out the road ahead. We do however need some sort of vision of the future for staking out new services. I like my latest version enough that I thought it would be worth putting up publicly to get reactions and input.
Please comment and/or...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Unique paths for slots problem if slots are filled with same archetype](https://discourse.openehr.org/t/unique-paths-for-slots-problem-if-slots-are-filled-with-same-archetype/15545)
> Hi all,
We have encountered an interesting issue with how to construct unique paths for slots when there is more than one slot on the same level, and both slots are filled with the same archetype.
In this case, the resulting paths for both seem to be the same in OPT and thus in the data. (The at/id code of the slot are not part of the path for a filled slot.)
Likewise, you cannot apply an annotation to only one of them, because they share the same path.
This seems to be a general problem,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SEC f2f meeting Oslo 5-7 Nov - agenda items welcome](https://discourse.openehr.org/t/sec-f2f-meeting-oslo-5-7-nov-agenda-items-welcome/15712)
> The [openEHR Specifications Editorial Committee (SEC)](https://www.openehr.org/programs/specification/editorialcommittee) will be having a face to face meeting in Oslo, 5-7 Nov 2018, hosted courtesy of [DIPS](https://www.openehr.org/industry_partners/dips). The agenda is being [put together here](https://openehr.atlassian.net/wiki/spaces/spec/pages/352157702/2018-11-05+openEHR+SEC+Meeting+Oslo). Feel free to add items under 'Agenda Items'.
We will be aiming to complete new releases of the RM...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [query writing question 2 (Seref Arikan)](https://discourse.openehr.org/t/query-writing-question-2-seref-arikan/15714)
> Oh, sorry\. I have indeed used the wrong alias in the example\. I intended to write
SELECT a/data\[at0001\]/items\[at0004\]/value
FROM EHR e CONTAINS COMPOSITION a\[openEHR\-EHR\-COMPOSITION\.encounter\.v1\]
WHERE a/data\[at0001\]/items\[at0004\]/value/value >= 140
What ensures that the identified path in the SELECT section references
the same data instances that are contrained with the same identified
path in the WHERE section ?
Greetings
Georg
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [query writing question 2](https://discourse.openehr.org/t/query-writing-question-2/15550)
> Hello,
I have another question concerning the semantics of AQL queries:
In the documentation there are queries of the form
SELECT a/data\[at0001\]/items\[at0004\]/value
FROM EHR e CONTAINS COMPOSITION a\[openEHR\-EHR\-COMPOSITION\.encounter\.v1\]
WHERE b/data\[at0001\]/items\[at0004\]/value/value >= 140
What ensures that the identified path in the SELECT section references the same data instances that are contrained with the same identified path in the WHERE section ? It could be argued...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Seeking clarification regarding Assumed value](https://discourse.openehr.org/t/seeking-clarification-regarding-assumed-value/15544)
> Hi everyone,
Assumed value - [https://www.openehr.org/releases/AM/latest/docs/AOM1.4/AOM1.4.html#_assumed_value](https://www.openehr.org/releases/AM/latest/docs/AOM1.4/AOM1.4.html#_assumed_value)
I’ve spoken to Sam Heard on many occasions and I have understood him to say that the intent for an assumed value to only be relevant for ‘State’ in an OBSERVATION. But never in ‘Data’. This is what I’ve always taught modellers.
The original Ocean Archetype Editor, had this implemented. In more...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [AQL query writing question](https://discourse.openehr.org/t/aql-query-writing-question/16601)
> Hello,
In the AQL documentation there is a query
SELECT c/uid/value, instruction
FROM EHR e\[ehr\_id/value=$ehrid\]
CONTAINS COMPOSITION c
CONTAINS INSTRUCTION instruction\[openEHR\-EHR\-INSTRUCTION\.referral\.v1\]
WHERE EXISTS instruction/links\[target='ehr://327000002/87284370\-2D4B\-4e3d\-A3F3\-F303D2F4F34B@latest\_trunk\_version'\]
When I reduce this query to
SELECT e FROM EHR e\[ehr\_id/value=$ehrid\]
why is the constraint on the ehr\_id done in the FROM section and not in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SHRINE for openEHR ?](https://discourse.openehr.org/t/shrine-for-openehr/16604)
> Hello,
Is there an equivalent to i2b2's SHRINE in the openEHR world ? SHRINE is a system that distributed an i2b2 query to a network of i2b2 installations and aggregates the returned results\.
Greetings
Georg
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_DURATION and magnitude_status?](https://discourse.openehr.org/t/dv-duration-and-magnitude-status/15553)
> Hi,
I’ve got a use case where we need to represent a time duration (of a symptom), which can be for example <24H or >3M. Is it possible to represent this using the DV_DURATION data type, like you can do with DV_QUANTITY and magnitude_status? If not, what should we do?
Kind regards,
**Silje Ljosland Bakke**
Information Architect, RN
Coordinator, National Editorial Board for Archetypes
Nasjonal IKT HF, Norway
Tel. +47 40203298
Web: [http://arketyper.no](http://arketyper.no/) / Twitter:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [formal openEHR guidelines, GDL, expressions, Task Planning: who will author them?](https://discourse.openehr.org/t/formal-openehr-guidelines-gdl-expressions-task-planning-who-will-author-them/16600)
> I've put up a wiki page with a [draft of what a real world guideline](https://openehr.atlassian.net/wiki/spaces/spec/pages/344621059/openEHR+Expression+Language+EL) (for choosing breast cancer therapy, based on various input variables) might look like in the emerging [openEHR Expression language](https://www.openehr.org/releases/BASE/latest/expression.html).
The example on the page shows the guideline in two forms: the first is a more natural-language style syntax, and the second is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Generic modeling and issues for querying](https://discourse.openehr.org/t/generic-modeling-and-issues-for-querying/14399)
> Hi all,
Lately I've been working a lot with lab test reports. Current CKM modeling for this relies on a generic model that applies to any kind and structure of result in this way:
- COMPO.report-result // any result document
- OBSERVATION.laboratory_test_result // results container, can be used as a panel
- CLUSTER.laboratory_test_analyte // single result
This kind of generic model relies on specific structures to be set at runtime, and also to use specific codes to know which type of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [What's the correct XML in an OPT for multiple terminology references?](https://discourse.openehr.org/t/whats-the-correct-xml-in-an-opt-for-multiple-terminology-references/16599)
> Hi,
I'm having trouble generating OPTs (1.4) from archetypes that reference multiple terminologies from a DV_CODED_TEXT.
For instance, I have a coded node that will be coded by LOINC or SNOMED-CT, that can be set in the archetype. But when exporting the OPT from the Template Designer, only LOINC appears in this way:
Hi all, lately I've been modeling different types of lab results.
Now I'm modeling cervical cytology, and there is a kind of result that is "inconclusive or not clear", for other results I've found SNOMED CT codes but not for this one. That is the only one that I can't code right now, maybe others with more experience on this area can help me find a code.
This is what I have right now, sorry rubrics are in spanish (but is easy to just put the codes in the SNOMED browser to see the concept...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Identifying archetype nodes in AQL via terminology code](https://discourse.openehr.org/t/identifying-archetype-nodes-in-aql-via-terminology-code/13791)
> Hello,
In AQL it is possible to constrain the value of a node to one of the codes that are allowed for that value (as specified in the respective archetype).
To find patients with gender (snomed-ct:248153007) male (snomed-ct:248153007) I could write something like this:
SELECT e FROM EHR e CONTAINS DEMOGRAPHICS d
WHERE d.items[at0017].value = 'snomed-ct:248153007'
Is it possible to identify the node of an archetype instead of its path parts (e.g. d.gender or d.items[at0017]) also with a...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ECG archetype advice required](https://discourse.openehr.org/t/ecg-archetype-advice-required/15541)
> Hi everyone,
I’ve just been facilitating the most recent reviews on the ECG archetype and would appreciate some advice on two issues.
The current atrial and ventricular rates are modelled as a Quantity (frequency) ie 1/min. However UCUM is unclear and there seems to be a few options, including {Beats}/min, {beats}/min and {H.B} is represented in another context, so maybe {H.B}/min is valid as well. Note that if we decide that it is appropriate to modify to one of these specific UCUM units,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Recommended versioning strategy for Templates](https://discourse.openehr.org/t/recommended-versioning-strategy-for-templates/15710)
> Hi,
As an EHR solution evolves, the templates also tend to evolve to an acceptable level, especially since the archetypes themselves are evolving. However, all the data recorded using different versions of the OPT should remain consistently and easily query-able with out the AQL becoming overly complex and difficult to manage.
So is there any best practices in versioning the templates as they evolve so that the incremental evolution does not break the AQLs. The question is do we use the OPT...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GDPR and OpenEhr.](https://discourse.openehr.org/t/gdpr-and-openehr/15711)
> OpenEhr does not really allow to delete data, only logical deletion (mark as deleted), but GDPR demands the right of the patient to be forgotten.
Is there some change expected in the specs for compliance to GDPR, or was this already implemented?
We had this discussion, slightly different, about ten months ago but no conclusion if I recall well
Sorry if I missed a message about this.
Thanks
Bert Verhees
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL support for an array of ehr_id](https://discourse.openehr.org/t/aql-support-for-an-array-of-ehr-id/15532)
> Hi,
I am not sure if this has been asked before. I am asking again since I could not find an answer
Does AQL support an array of EHRs? In AQL specs i can see examples to query any a single EHR and across all EHRs in the system. If I want to limit my query to a set of EHRs is it possible using AQL?
Use case - As part of a dynamic consent management framework, we keep a dynamic mapping of EHRs to organizations. This is kept updated based on patient consent. So at any time a query is run by...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archie version 0.5.0 released](https://discourse.openehr.org/t/archie-version-0-5-0-released/16597)
> Today I’m pleased to announce the release of Archie version 0\.5\.0\. Archie is an open source OpenEHR library for archetype modelling and implementing EHRs, based on ADL 2, written in Java\. This release brings two new features, one for modeling and one of EHR implementations: Archetype diffing and validating RM Objects against archetypes\.
The diff operation extends the set of archetype modeling tools already available in Archie\. It makes editing specialized archetypes much easier by...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Missing classes in EtherCIS VirtualEhr](https://discourse.openehr.org/t/missing-classes-in-ethercis-virtualehr/16598)
> Hello,
I try to compile the EtherCIS project\. I managed to compile the openehr\-java\-libs as well as the ehrservice projects\. But I have a problem with the VirtualEhr:
In the project ecis\-vehr\-service there is a class FileDispatchMapper that uses the two classes com\.ethercis\.ehrserver\.servicemap\.Action and com\.ethercis\.ehrserver\.servicemap\.MapperDociument\. However, there is no namespace com\.ethercis\.ehrserver and so those two classes also do not exist\.
What am I missing ? Did...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [completeness of tagging of archetpyes with snomed terminology IDs](https://discourse.openehr.org/t/completeness-of-tagging-of-archetpyes-with-snomed-terminology-ids/15537)
> Hello,
When looking at the published archetypes in the international CKM I see a lot of archetype members that do not have a terminology binding, but which could possibly have one\. The "Body Surface Area" for example has a member "Body Surface Area" which has no bound code but could have the Snomed Code 128178001\. Or "Blood Pressure" has terminology bindings for its members "Systolic" and "Diastolic", but not for the "Mean arterial...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [MEDINFO 2019, Lyon, France.](https://discourse.openehr.org/t/medinfo-2019-lyon-france/15539)
> Dear openEHR colleagues,
In the next year, MEDINFO 2019 will be in Lyon, France, from 26th to
30th August, 2019\.
The application for paper/poster/workshop/tutorial deadline is Nov 12\.
This is important, ONLY less than TWO MONTH left for the deadline\.
I already launched wiki page for MEDINFO 2019\.
https://openehr.atlassian.net/wiki/spaces/resources/pages/320634886/MEDINFO2019
If you have some plan for proposal related with openEHR, please give
us comments on the wiki or mail\.
I will...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Strange behavior in Template designer 2.8.94 Beta](https://discourse.openehr.org/t/strange-behavior-in-template-designer-2-8-94-beta/15534)
> Hi,
I am observing a strange behavior in the template designer and whated to check if this is the expected behavior and if not how to manage it.
In any template, when ever I rename any archetypes, their occurrence gets set to [0..1] automatically (single occurrence). The options for selecting multiple occurrences is no more available.
Have anybody else noticed this problem? Is there any way to work around this as some of these archetypes need to be multiple occurrences
Please see...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL on specific list of compositions](https://discourse.openehr.org/t/aql-on-specific-list-of-compositions/14923)
> Hi,
Can you write an AQL to query only on a list of specific compositions? Is there any sample for reference?
I am trying to create the concept of clinical encounters and maintain a collection of compositions per encounter. I am using AQL to retrieve data per encounter and need to pass the corresponding set of compositions.
Thanks in advance
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Drug dispense entry class question](https://discourse.openehr.org/t/drug-dispense-entry-class-question/15538)
> Hi all,
How would you map a "pharmacy drug dispense" task, where the patient comes with a prescription and a clerk delivers the medication packages?
I was thinking this is clearly and ACTION, but also seems to be an ADMIN_ENTRY, since it is just a delivery of some product.
I'm inclined to think it as an ACTION if this task alters the state of the prescription INSTRUCTION ISM. On this case, as a parallel question, I'm not sure if the dispense ACTION should be a final "COMPLETED" state, what...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [post-coordination in openEHR](https://discourse.openehr.org/t/post-coordination-in-openehr/16596)
> Hello,
Using terminology bindings it is posssible to bind terminology IDs of specific terminologies to archetypes as well as to their members\. In the openEHR documentation it is written that there is no concept of post\-coordination outside the terminology environment\. What does that exactly mean ? When I have a post\-coordinated expression, how do I use it within openEHR ? The linkage of an openEHR system to a potential terminology server is something that I do not yet unterstand very...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is description = <"*"> mandatory?](https://discourse.openehr.org/t/is-description-mandatory/15536)
> Hi everyone,
In modelling cases, particularly where we’re modelling scores and scales, the description element of text or ordinal values are unnecessary, because the value defined in the score only contain a single string of text. A good example of this is the ECOG Performance Status archetype, where editors (both Ocean’s AE and Marand’s AD) add a ‘*’ in the empty description element, like this:
["at0005"] = <
text = <"Fully active, able to carry on all pre-disease performance without...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Sports and Wellness](https://discourse.openehr.org/t/sports-and-wellness/15709)
> Is this subject clinical? Not really \(maybe another mailing\-list would be in place, I explain it\)
A few weeks ago I discussed that OpenEhr should also focus on sports and wellness, because it is a growing market, it is very much related to health, and it has about the same software requirements as EHR has\.
One of my favourite jokes I make last weeks when I talk with healthcare professionals:
Health and Healthcare should also be about Health\. It is a bit Orwellian New Speak to name...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [The openEHR Asia summit succeeded.](https://discourse.openehr.org/t/the-openehr-asia-summit-succeeded/14501)
> Dear openEHR colleagues,
We completed all the schedule for the first openEHR Asia summit, and
the second general assembly of Japan\.
We also celebrated the new board member, Xudong Lu with many kampais\.
Congratulations\.
In Asia, openEHR activities are supported with ground roots, and
growing steadily\.
Dr Ryan Bannez showed his beautiful EMR system based on Marand
EhrScape in Philippines, and 40 clinics adopted that\.
Prof Xudong Lu showed 5 big projects plan in China\.
I presented openEHR...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Management Board Election results](https://discourse.openehr.org/t/management-board-election-results/16595)
> The individual members and industry partners have voted for 2 positions on the openEHR Management Board and we now have two new elected members, confirmed by our returning officers, Thomas Beale and Jill Riley.
The candidates elected are:
Individual Members:
Xu Dong Lu, China
Industry Partners:
Bjorn Naess, DIPS, Norway
Many congratulations to the successful candidates and many thanks to those who were unsuccessful on this occasion. It was heartening to see a healthy contested election...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Welcoming 2 new members to the Specifications Editorial Committee (SEC)](https://discourse.openehr.org/t/welcoming-2-new-members-to-the-specifications-editorial-committee-sec/15708)
> We announce the addition of two new members to the [openEHR SEC](https://www.openehr.org/programs/specification/editorialcommittee), the group that manages the specifications in openEHR, by majority vote of the SEC. They are both 'old hands' at openEHR, and bring long experience which will be of great value. Those new to openEHR might also be interested to know the governance and change management process we use for the specifications,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [The first openEHR Asia Summit will be broadcast](https://discourse.openehr.org/t/the-first-openehr-asia-summit-will-be-broadcast/14391)
> Dear openEHR members,
We will broadcast our openEHR Asia summit via our youtube channel from
10:00\(JST\), on the 28th July, 2018\.
We also welcome your comments via youtube\.
https://www.youtube.com/watch?v=DSyOlTp8pwY
Programme:
10:00\-10:15 Overview of openEHR movement and its localisation
programme, Shinji Kobayashi\(Japan\), English session
10:15\-10:45 openEHR Activity in Philippines, Ryan Banez\(Philippines\),
English session
10:45\-11:15 openEHR Activity in China, Xudong...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Education Program](https://discourse.openehr.org/t/openehr-education-program/15533)
> [Although this is a transversal topic to openEHR, I send it to the technical list, as it is the most active]
Hello,
Some time ago (I think it was in 2015), there was some movement towards formalizing an Education Program about openEHR. I thing Evelyn Hovenga and Pablo Pazos were involved.
There have not been news about this, so I'm curious if it is still active. If not, I think it is more important than ever, and we should retake it.
In the past I was responsible of (trying to) develop a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [UCUM/SNOMED/custom units](https://discourse.openehr.org/t/ucum-snomed-custom-units/15535)
> I wonder if it is possible to use other units then UCUM units in DV\_QUANTITY\. I read from Pablo in Stackoverflow that the SEC is considering custom units\. I think this is great, but I see some problems coming up\. I have some questions about this,
I wonder how you can do that without changing the DV\_QUANTITY\-definition, because it has a units\-attribute, it says it must be expressed in UCUM syntax\. It does not say anything about the unit itself, only about the notation\.
Must we...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Getting to know openEHR](https://discourse.openehr.org/t/getting-to-know-openehr/15528)
> Hello All,
I’m relatively new to this topic so wondered if anyone had any pointers for me to get started. Currently working on some integration projects for an NHS trust and this looks like it could be the ideal route for us to go down in terms of structuring data etc.
If anyone has any good ‘beginners-guides’ they could point me to, it would be very welcomed!
Also, I notice the C#/.Net mailing list doesn’t seem to work, has this been disbanded now?
Many thanks,
Alex Hitchins
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Last few days to vote in openEHR Foundation Management Board Elections - Voting ends 20th July](https://discourse.openehr.org/t/last-few-days-to-vote-in-openehr-foundation-management-board-elections-voting-ends-20th-july/14390)
> Voting for elections for two openEHR Foundation Management Board positions to Individual and Industry Partner members closes on 20th July, so if you’ve not voted yet please do so soon.
Nominee information and link to vote available [HERE](http://members.openehr.org/mbvoting)
To vote you must:
- be signed up as an Individual Member of the Foundation to vote for the Industry Member Nominees.
- be an existing employee of a current Industry Partner to vote for the Industry Partner...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Basic Meta-Model (BMM) and syntax major upgrade](https://discourse.openehr.org/t/openehr-basic-meta-model-bmm-and-syntax-major-upgrade/14389)
> I have created a [new blog post](https://wolandscat.net/2018/07/16/openehr-basic-meta-model-bmm-and-syntax-major-upgrade/) on the latest BMM upgrade. From the post:
The openEHR [Basic Meta-Model (BMM)](https://www.openehr.org/releases/BASE/latest/docs/bmm/bmm.html) that has been in use in some form for nearly 10 years now was recently upgraded to version 3.0.0 (from 2.x), with the [persistence format (now called...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [API's](https://discourse.openehr.org/t/apis/14392)
> Today I looked at the OpenEhr API:
[https://www.openehr.org/releases/ITS/latest/ehr_restapi.html#top](https://www.openehr.org/releases/ITS/latest/ehr_restapi.html#top)
I live sometime in the OpenEhr world, so I am not surprised that it is a rather low level API. In fact it is a bit hard to recognize quick what it is about. And it fits perfectly to the philosophy of OpenEhr. The API is not semantically rich. It are the archetypes which are semantically rich, the API IS GENERIC. So it is fine....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Does anyone know if the Template Designer is being maintained?](https://discourse.openehr.org/t/does-anyone-know-if-the-template-designer-is-being-maintained/15706)
> Bug reports been there for 3 years and no new versions seem to be released: [https://openehr.atlassian.net/projects/TDPR/issues/TDPR-16?filter=allopenissues](https://openehr.atlassian.net/projects/TDPR/issues/TDPR-16?filter=allopenissues)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Unique paths for nodes in multiple instances of one archetype in the same OPT](https://discourse.openehr.org/t/unique-paths-for-nodes-in-multiple-instances-of-one-archetype-in-the-same-opt/15526)
> Hi,
We are trying to create a service request template using the following structure
[openEHR-EHR-COMPOSITION.request.v1]
[openEHR-EHR-INSTRUCTION.request.v0]
[openEHR-EHR-CLUSTER.organisation.v0]
[openEHR-EHR-CLUSTER.person_name.v1]
[openEHR-EHR-CLUSTER.organisation.v0]
[openEHR-EHR-CLUSTER.person_name.v1]
The first set of organization & person name archetypes are for the requester and the second set for the receiver.
However in the template editor, the paths for the nodes of both...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Topics of the openehr-clinical list](https://discourse.openehr.org/t/topics-of-the-openehr-clinical-list/16594)
> Hi everyone,
I’ve seen a tendency lately that topics that at least to me seem to be of a technical nature are posted to the clinical list. These topics often generate a lot of discussion, which drowns out much of the discussion about the clinical aspects of openEHR. I realise that a lot of discussions will be borderline technical/clinical, but I still think a lot of them would better belong in the technical or even implementers list. If you’re unsure where to post something, may I suggest...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Empty COMPOSITION.content is valid?](https://discourse.openehr.org/t/empty-composition-content-is-valid/15527)
> Hi all,
Recently a client committed COMPOSITIONS with empty content to the EHRServer, because in the OPT all the structure was associated to context.other_context.
After reviewing the specs, I found this invariant on the COMPOSITION spec:
Content_valid: content /= Void implies not content.is_empty
That means that content can actually be null/void, since on that case, the "implies" is true.
Also checked the COMPOSITION XSD, and the minOccurs for content is 0.
Does it make sense to have...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Foundation Management Board Elections - VOTE NOW UNTIL 20th JULY](https://discourse.openehr.org/t/openehr-foundation-management-board-elections-vote-now-until-20th-july/15705)
> Voting is now open for elections for two openEHR Foundation Management Board positions to Individual and Industry Partner members.
Nominee information and link to vote available [HERE](http://members.openehr.org/mbvoting)
To vote you must:
- be signed up as an Individual Member of the Foundation to vote for the Industry Member Nominees.
- be an existing employee of a current Industry Partner to vote for the Industry Partner Nominees.
Non-members wishing to vote will need to [join...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Non existing constraints: closed or open interpretation?](https://discourse.openehr.org/t/non-existing-constraints-closed-or-open-interpretation/14372)
> Hi all,
I'm adding some extra checks on the EHRServer, and found cases where users were committing compositions with nodes that are not defined in the referenced OPT.
That made me think of the interpretation of non existing constraints. For instance, the extreme case of can empty COMPOSITION OPT (no constraints defined for the COMPOSITION.content), how that should be interpreted?
1. open: any structure is allowed on the COMPOSITON.content
2. closed: structures not defined in the OPT are...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [A clinical modelling conversation...](https://discourse.openehr.org/t/a-clinical-modelling-conversation/13418)
> Dear Colleagues,
This email is jointly sent by the openEHR Clinical Knowledge Administrators, Silje and Heather.
Following recent email threads, we would like to establish some common understanding and expectations about the current clinical modelling effort and effect that we hope might stimulate a constructive and innovative conversation within the openEHR community about moving the clinical modelling work forward.
Let’s say that publication of a typical archetype takes four review...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [DV_TEXT vs. DV_PARSABLE with formalism "text/plain"](https://discourse.openehr.org/t/dv-text-vs-dv-parsable-with-formalism-text-plain/15524)
> Hi,
I'm playing around with the AE and have a question about the semantics in the differences between specifying an ELEMENT.value as DV_TEXT or a DV_PARSABLE with formalism = "text/plain".
Since text/plain MIME type is used for narrative text and DV_TEXT is just for that, why text/plain is allowed on the constraints for DV_PARSABLE.formalism?
Is there any use case specific for DV_PARSABLE text/plain that can't be modeled as DV_TEXT?
Thanks!
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is the proportion kind "integer fraction" correct?](https://discourse.openehr.org/t/is-the-proportion-kind-integer-fraction-correct/15525)
> Hi, I'm checking the datatypes specs doing some modeling tests on the archetype editor.
In the specs, the "integer fraction" proportion kind means the representation of the fraction 3/2 should be 1 1/2.
[http://www.openehr.org/releases/RM/Release-1.0.3/docs/data_types/data_types.html#_proportion_kind_class](http://www.openehr.org/releases/RM/Release-1.0.3/docs/data_types/data_types.html#_proportion_kind_class)
Semantically I think this is not on the same level as the other "proportion...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [wellness, lifestyle, sports archetypes ... or templates?](https://discourse.openehr.org/t/wellness-lifestyle-sports-archetypes-or-templates/16593)
> To the extent that I have thought about this area \(not deeply\), I suspect that clinical models for these types of use probably should take the form of templates that 'mix in' multiple bits and pieces from existing clinical archetypes\.
A complex of data elements that you might expect from a \(say\) person on a rowing machine will be some typical vital signs \(breathing, heart rate, O2 sat, real time blood analytes?, maybe some computed derivatives, vO2 etc\) \- which will mostly...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [How to define transitions in the ISM](https://discourse.openehr.org/t/how-to-define-transitions-in-the-ism/15518)
> Hi all,
I'm testing the AE for a new workshop, and designed a simple state machine for and order so my students can use it as basic for more complex state machines.
I have: NEW (maps to ISM PLANNED), ASSIGNED (maps to ISM PLANNED), STARTED (maps to ISM ACTIVE) and FINISHED (maps to ISM COMPLETED).
What the AE is not allowing is to specify the ISM_TRANSITION.transition : DV_CODED_TEXT.
The problem is if I have two states mapped to ASSIGNED, how a software knows which one is the state to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AE constraints offset for POINT_EVENTs](https://discourse.openehr.org/t/ae-constraints-offset-for-point-events/16591)
> Hi all,
Testing the Archetype Editor for OBSERVATION, found that defining a POINT_EVENT structure, allows to create a constraint for EVENT.offset, while that is a function by the v1.0.2 spec.
Another weird thing is that defining a POINT_EVENT, and saying the HISTORY is periodic, makes the panel for the offset definition disappear, but the offset is still on the generated ADL.
I believe this is a bug. Will test with LinkEHR.
Anyone had problems with this...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Interval events - "change" math function semantics](https://discourse.openehr.org/t/interval-events-change-math-function-semantics/16592)
> Hi, another question about interval events.
I'm having issues understanding how to use the "change" math functions. From the spec [http://www.openehr.org/releases/RM/Release-1.0.2/docs/data_structures/data_structures.html#_change_data](http://www.openehr.org/releases/RM/Release-1.0.2/docs/data_structures/data_structures.html#_change_data)
- "change": this means that the value recorded is the difference between the value now and the value some time previously. It can be positive or...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about periodic interval events](https://discourse.openehr.org/t/question-about-periodic-interval-events/15523)
> Hi all,
As usual I'm reading the specs and have a question about periodic interval events.
I'm not sure how the period is calculated in a series. Let's say we have interval events on a time line:
---E1.start___________E1.end----------E2.start____E2.end-------...
Note: interval events can have different durations.
Is the period calculated from E1.start to E2.start or from E1.end to E2.start?
This is of course to know when E3 should start.
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Machine Learning , some thoughts](https://discourse.openehr.org/t/machine-learning-some-thoughts/15520)
> Today my wife showed me Plantnet\.
https://plantnet.org/en/
It recognizes over 6000 plants from showing a flower or a leaf to your phone\. It has learned from machine\-learning 700\.000 pictures, and its knowledge every day grows stronger, because it keeps on learning\. And not only the looks of a flower, but if it takes location \(biotope\) and date in consideration, the certainty of recognizing gets stronger\.
Now you can imagine that it must be hard to recognize a plant from a picture,...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Foundation Management Board Nominations DATE EXTENDED TO 30TH June 2018](https://discourse.openehr.org/t/openehr-foundation-management-board-nominations-date-extended-to-30th-june-2018/16590)
> **openEHR Management Board Election June 2018 – DATE EXTENDED TO 30TH JUNE**
As agreed with the openEHR Board of Governors, **two** of the existing openEHR Management Board positions are now up for election with voting open to all paid Individual and Industry Partner members.
The call for nominations is for **two** Management Board positions; one to represent Individual Members, one to represent Industry Partners.
**Nominations can be made [HERE...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical question on stackoverflow](https://discourse.openehr.org/t/clinical-question-on-stackoverflow/16089)
> Someone wants to answer it? Makes your account on stackoverflow shine
[https://stackoverflow.com/questions/50918982/medication-order-vs-prescription-in-openehr](https://stackoverflow.com/questions/50918982/medication-order-vs-prescription-in-openehr)
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR - how to define this concept? - Work concepts + how people spend their day](https://discourse.openehr.org/t/openehr-how-to-define-this-concept-work-concepts-how-people-spend-their-day/14388)
> Some additional feedback from the team here; CDC/NIOSH;
The Occupational Data for Health \(ODH\) model that has been shared with some openEHR folks and reflected in comments on the Occupation Record \(formerly Occupation Episode\) and Occupation Summary archetypes provides a way to collect information about many of the concepts that have been raised, including being unemployed \(not employed and seeking work\) and both paid and unpaid work\. It does not preclude modeling for a person who is...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 70, Issue 5](https://discourse.openehr.org/t/openehr-clinical-digest-vol-70-issue-5/15703)
> Everyone \- I work with CDC/NIOSH and have forwarded this thread on to the Occupational Data for Health team\. We may have some input to provide next week in regard to work and health information and how we recommend it be collected\. We've commented on the Occupation archetype and are due for another review since the last round of comments\.
Thanks,
Angela C\. Crovetti
Sr\. Consultant, Attain/CDC/NIOSH
Office: 513\-841\-4498 Cell: 513\-520\-8031
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [What to call this concept?](https://discourse.openehr.org/t/what-to-call-this-concept/15511)
> Hi everyone,
We’ve been struggling for a while to define and delineate a concept about the activities an individual does during their day – do they do paid work, unpaid work, are they a student, are they unemployed and seeking work, unemployed and not seeking work, retired, carer, are they a young child or infant, or something else? There may be multiple, like both studying and working.
A lot of feedback has been that we should constrain this to just employment, ie paid work. That would...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Management Board Election June 2018](https://discourse.openehr.org/t/openehr-management-board-election-june-2018/14387)
> **openEHR Management Board Election June 2018**
As agreed with the openEHR Board of Governors, **two** of the existing openEHR Management Board positions are now up for election with voting open to all paid Individual and Industry Partner members.
The [call for nominations](http://members.openehr.org/page-18074) is for **two** Management Board positions; one to represent Individual Members, one to represent Industry Partners.
The Board of Governors and Management Board would like to warmly...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Events](https://discourse.openehr.org/t/openehr-events/14383)
> Want to know more about openEHR events – see [http://openehr.org/news_events/events](http://openehr.org/news_events/events)
Involved in an event supported by openEHR Foundation and members, but not promoted on our webpage – please email [comms@openehr.org](mailto:comms@openehr.org) with more information.
Upcoming events:-
6th & 7th June – Clinical Modelling Workshop, Plymouth
18th June - openEHR open data platforms in medical informatics,...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Event Notification: openEHR Asia Summit and NPO Japan general assembly July](https://discourse.openehr.org/t/event-notification-openehr-asia-summit-and-npo-japan-general-assembly-july/14381)
> Event Notification: The 1st openEHR Asia Summit and 2nd NPO openEHR Japan general assembly is being held on 27th & 28th July, Japan.
Early booking for this event is advised, and further information is available on the website at [https://www.openehr.org/news_events/events.php?id=234](https://www.openehr.org/news_events/events.php?id=234)
Kindest regards
**Jill Riley**
on behalf of [openEHR](http://www.openehr.org/) Foundation Management...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org server upgrade 15/05/2018 20:00CEST / 19:00 BST](https://discourse.openehr.org/t/openehr-org-server-upgrade-15-05-2018-20-00cest-19-00-bst/14380)
> The openEHR.org main server will be switched over to a new one tomorrow evening:
Tuesday 15 May 2018
20:00: CEST / 19:00 BST
We expect about 1 hour during which openEHR.org email addresses will not be able to send email, but an otherwise smooth changeover.
Any problems, please report via email to [webmaster@openehr.org](mailto:webmaster@openehr.org)
- Andraž Hvalica
- Thomas Beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Future governance arrangements for openEHR](https://discourse.openehr.org/t/future-governance-arrangements-for-openehr/14379)
> Due to very serious illnesses affecting our two families over the past six months, there has been unavoidable delay in completing arrangements to establish the planned openEHR Community Interest Company (CIC) that will take full legal and financial responsibility for openEHR operations in future. The Articles of the openEHR Foundation will, at the same time, be changed to reflect its new role, solely as the owner and protector of the openEHR Intellectual Property.
Fortunately, we are now...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ECG test result archetype review](https://discourse.openehr.org/t/ecg-test-result-archetype-review/14378)
> Hi everyone,
I am also going to restart the ECG test result archetype review – see [http://www.openehr.org/ckm/#showArchetype_1013.1.276](http://www.openehr.org/ckm/#showArchetype_1013.1.276)
This is also something started a long, long time ago but not completed. It will likely need some revision to update before we send out for the next review, and some expert input to ensure that we can use the archetype to capture device data.
If you would like to participate as a reviewer, please adopt...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Visual acuity test result archetype](https://discourse.openehr.org/t/visual-acuity-test-result-archetype/15702)
> Hi everyone,
There is a review round for Visual acuity test result that commenced in 2013 but hasn’t completed the review process - [http://www.openehr.org/ckm/#showArchetype_1013.1.1291](http://www.openehr.org/ckm/#showArchetype_1013.1.1291)
I would like to re-start the review process and progress it to publication.
If you would like to participate as a reviewer, please adopt the archetype so that we can invite you to the next review round.
If you have some clinical expertise in this...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SMART on FHIR integration](https://discourse.openehr.org/t/smart-on-fhir-integration/15508)
> I see you have had discussions on FHIR and SMART on FHIR. Is it on the roadmap for openEHR to support SMART on FHIR launch sequence ([http://docs.smarthealthit.org/authorization/](http://docs.smarthealthit.org/authorization/)) for single sign on? I know many customers who would like this seemless integration.
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR within a mature NHS Ecosystem event - Plymouth, UK, 18 April 2018](https://discourse.openehr.org/t/openehr-within-a-mature-nhs-ecosystem-event-plymouth-uk-18-april-2018/15701)
> >
|
> - |
|
|
|
|
**Dear** openEHR community member,
Learn more about the opportunities and challenges of openEHR!
University Hospitals Plymouth NHS Trust and Plymouth University are hosting an event where you will learn more about:
- OpenEHR from a national and international perspective
- the local perspective, we want to showcase the incredible progress made in the South West, as well as...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SEC meeting 18-20 April; community issues solicited](https://discourse.openehr.org/t/sec-meeting-18-20-april-community-issues-solicited/14382)
> We have a [Specifications Editorial Committee](https://www.openehr.org/programs/specification/editorialcommittee) meeting in Ljubljana 18-20 April, during which we will be processing as many of the outstanding [Problem Reports (PRs)](https://openehr.atlassian.net/issues/?jql=project%20%3D%20SPECPR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC%2C%20updated%20DESC) as possible.
The agenda is posted on the [meeting...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Toolkit](https://discourse.openehr.org/t/openehr-toolkit/15517)
> Hi all,
I have released a humble pack of tools to help developers working with openEHR and the EHRServer.
This is a pre-alpha version, I'm looking for feedback. Any service idea, improvements, comments, etc. are very welcome!
Please give it a try: [http://server001.cloudehrserver.com/cot/](http://server001.cloudehrserver.com/cot/)
We have many areas of improvements :)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 73, Issue 86](https://discourse.openehr.org/t/openehr-technical-digest-vol-73-issue-86/12819)
> Creating subsets is the case in the Netherlands.
However they are published in different fashions:
- As national extensions in SnomedCT online
- On Nictiz art decor for projects as perinatology (varied sets for data and for valuesets)
- On zorginformatiebouwstenen
- On the FHIR publication sites
- On project sites
- On github Detailed Clinical Models in individual DCMs
- And probably more.
Dr William Goossen
Directeur
Results 4 Care bv
Tel +31654614458
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Should Duration class used in AOM 1.0.2 be ISO8601_DURATION from support specs?](https://discourse.openehr.org/t/should-duration-class-used-in-aom-1-0-2-be-iso8601-duration-from-support-specs/15512)
> Hi,
Looking at CDuration [http://www.openehr.org/releases/1.0.2/architecture/am/aom.pdf](http://www.openehr.org/releases/1.0.2/architecture/am/aom.pdf) page 46, the range constraint is defined with a Duration class.
On the support specs [http://www.openehr.org/releases/1.0.2/architecture/rm/support_im.pdf](http://www.openehr.org/releases/1.0.2/architecture/rm/support_im.pdf) page 30 we have the ISO8601_DURATION class.
Should AOM reference that class or we have another Duration class...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Is partial datetime pattern (yyyy-mm-ddTHH:??:??) equivalent to "any allowed"?](https://discourse.openehr.org/t/is-partial-datetime-pattern-yyyy-mm-ddthh-equivalent-to-any-allowed/14377)
> Hi,
I'm digging into the specs again, and testing the modeling tools to produce different constraints for DV_DATE_TIME.
When I analyzed the partial datetime pattern yyyy-mm-ddTHH:??:?? that allows optional minutes and seconds, and the constraints that would correspond to "any allowed" it seems both are the same. I'll explain.
"any allowed" for DV_DATE_TIME would be any value that actually is a datetime. For instance "1999-01-01" is not a datetime, so "any allowed should check for datetime...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Don’t miss the future of healthcare IT - openEHR Day in Helsinki and Stockholm, 20 & 21 March 2018](https://discourse.openehr.org/t/don-t-miss-the-future-of-healthcare-it-openehr-day-in-helsinki-and-stockholm-20-21-march-2018/16588)
> \*Dear \*\*openEHR community member\*,
Learn more about the opportunities and challenges of openEHR\!
The openEHR Foundation <https://www.openehr.org/home> is hosting two events exploring the opportunities and challenges of openEHR\. The events will take place:
\* Helsinki on Tuesday, March 20th, Kilta\-sali, Lapinrinne 1 \-
MAP<http://go.marand.com/e/149541/3d60-16712644d24-9274629-dcr-0/3k6knk/201605402>
\* Stockholm on...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Export via CDISC ODM or FHIR](https://discourse.openehr.org/t/export-via-cdisc-odm-or-fhir/16589)
> Hello,
Are there already ideas about a future export API of AQL queries that support an export in CDISC ODM or FHIR ? It would be nice to have an export format that could be immediately consumed by other systems supporting the same specifications\. I am not yet that much into either topic \(ODM as well as FHIR\), therefore I do not yet see if the desire itself makes not sense or if there are serious problems that would hinder such exports\.
Greetings
Georg
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Improving the specification for DV_PARSABLE, specially for ACTIVITY.timing](https://discourse.openehr.org/t/improving-the-specification-for-dv-parsable-specially-for-activity-timing/14376)
> Hi all,
The specs have a very loose definition of DV_PARSABLE that makes it hard for developers to know how to use it correctly.
The first issue is on the DV_PARSABLE.formalism attribute.
**1) In the data_types spec there is no clear terminology associated with the formalism.**
Current: "Name of the formalism, e.g. GLIF 1.0 , Proforma etc." [1]
Expected: An internal terminology, or references to acceptable external terminologies, like IANA Media Types [2], or subsets of such external...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Setting thresholds](https://discourse.openehr.org/t/setting-thresholds/15515)
> We are developing a completely openEHR based Personal Health Environment (PHR). For this we would like to show measured data in a graph containing "good" or "bad". Mostly one would see some traffic light system, our approach is different but comes to the same principle.
So for this we need to set thresholds that also could be changed afterwards. In the most common BP archetype (and Template) no thresholds are defined, so at what level would we do that?
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype Modeling Methodology](https://discourse.openehr.org/t/archetype-modeling-methodology/15699)
> Dear community,
We have just published a new paper describing a formal Archetype Modeling Methodology (AMM). The aim of this paper is to provide archetype designers (especially those who are new to this methodology) with clear guidelines on how to face an archetype development project.
D. Moner, J.A. Maldonado, M. Robles, Archetype modeling methodology, Journal of Biomedical Informatics. 79 (2018) 71–81. doi:10.1016/j.jbi.2018.02.003.
You can find the published paper...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR REST APIs: any plans for Contribution semantics?](https://discourse.openehr.org/t/openehr-rest-apis-any-plans-for-contribution-semantics/15700)
> Greetings,
I cannot see any resources that represent Contributions in the current REST API specs. Is this on the roadmap for REST API specifications?
All the best
Seref
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Creating a terminology](https://discourse.openehr.org/t/creating-a-terminology/15510)
> Dear All,
I've been looking for some time for ways of injecting knowledge into the ecosystem so that it is available to an EHR, but also to other systems that might want to use it\.
I currently think I need to create a terminology \(or maybe more than one\), but I've found vanishingly few open tools and little guidance on what I could use to do this, and experiment to see if it does what I need\.
I'd be grateful for any advice\.\.\.
Yours,
Matthew
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [LOINC Groups](https://discourse.openehr.org/t/loinc-groups/14374)
> This may be interesting for those using LOINC\.
Help us improve LOINC Groups We need your feedback on the new LOINC Groups\. There are a number of ways you can contribute\.
<https://loinc.us8.list-manage.com/track/click?u=2bc346eeceafd92b045a21bfd&id=913e871039&e=8273cc8e53>
Do you know about the new \*LOINC Groups <https://loinc.us8.list-manage.com/track/click?u=2bc346eeceafd92b045a21bfd&id=e127ed7782&e=8273cc8e53>\*? This project aims to give you a computable way to to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [repository of AQL queries ?](https://discourse.openehr.org/t/repository-of-aql-queries/14373)
> Hallo,
Is there somewhere a repository of archived AQL queries ?
I could imagine that to be a bit problematic because the queries are always bound to their corresponding repository of archetypes\.
An AQL\-query\-repository would be great as a source for examples when trying to learn AQL\. It would also be a good resource for experiments and testcases, because real life queries often include aspects that other developers would never have thought of\.
Greetings
Georg
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes for Ayurveda and yoga](https://discourse.openehr.org/t/archetypes-for-ayurveda-and-yoga/14375)
> Hi,
We are working on a OpenEHR based EHR solution for Ayurveda and Yoga practices. As the fundamental tenets of Ayurveda are different from the allopathy, we are in the process of creating a different set of archetypes as per their practice requirements. We would like to make them available to anybody else who may find them useful.
What is the best way to do this? Is it appropriate to add them to the OpenEHR CKM? or is that only for Allopathy specific archetypes? What should be the general...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADLParsers for ADL 1.4/2.0](https://discourse.openehr.org/t/adlparsers-for-adl-1-4-2-0/12216)
> Hello,
I am currently trying to get a feeling for using the Java utilities that exist for openEHR and startet with the tools that exist as Maven repositories at https://mvnrepository.com.
I am currently experimenting with the ADLParser 1\.0\.71\. As a test example I downloaded from the Clinical Knowledge Manager the archetype "openEHR\-EHR\-OBSERVATION\.blood\_pressure\.v1" and exported it as an \.adl\-file\. When parsing this file I receive an archetype instance but when invoking...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Modeling family members / next of kin participants and "other clinicians"](https://discourse.openehr.org/t/modeling-family-members-next-of-kin-participants-and-other-clinicians/12310)
> Hi,
I'm checking on the RM 1.0.2 how to add information about family members (if the patient is a child or an elder), and maybe other clinicians that participate of an emergency care event (composition).
In 1.0.2 the extra participations appear at the ENTRY level as PARTICIPATION [http://openehr.org/releases/RM/Release-1.0.2/docs/ehr/ehr.html#_entry_and_its_subtypes](http://openehr.org/releases/RM/Release-1.0.2/docs/ehr/ehr.html#_entry_and_its_subtypes)
But it is not possible to add that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templates for application form development - should probably explain our EtherCIS/QEWDjs/PulseTile stack here](https://discourse.openehr.org/t/templates-for-application-form-development-should-probably-explain-our-ethercis-qewdjs-pulsetile-stack-here/12342)
> Hi all,
This might be a useful time to briefly explain why we are supporting 3 open source components in our "showcase" stack
EtherCIS - open source implementation of openEHR Clinical Data Repository [http://ethercis.org/](http://ethercis.org/)
QewdJS - nodeJS based middleware for varied purposes - inc microservices between UI & CDR
PulseTile- frontend UX/UI framework for healthcare
A few comments;
Point 1
We know that structured data in an EHR is essential for lots of reasons, inc...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templates for application form development](https://discourse.openehr.org/t/templates-for-application-form-development/15509)
> I've been recently messing around with ADL-designer, and thinking more about how to do application building with templates. A few things are becoming clearer to me. Firstly, templates based on COMPOSITION (or PARTY, PERSON etc, for demographics) are potentially good for data capture, but don't in general make sense for data retrieval.
For a retrieval data set, e.g. a screen containing a combination of demographics, EHR clinical, other info, we need another kind of container. Let's call this...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Optmizing AQL](https://discourse.openehr.org/t/optmizing-aql/15507)
> The discussion Pablo has makes me think it could be good to have in an AQL-engine an entry to have external query languages executed like SNOMED expressions which can treat result data as hierarchies of data and so add an extra functionality layer
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype pattern](https://discourse.openehr.org/t/archetype-pattern/15516)
> An interesting wiki from Heather Leslie
https://openehr.atlassian.net/wiki/spaces/healthmod/pages/90507705/Archetype+Design+Patterns
She concludes that pattern are necessary, I agree with that, and she also concludes that clinicians are better modelers then technicians\.
Well, that depends, of course it is very important to have domain\-knowledge when modeling data, and clinicians have the best domain\-knowledge\. So from that point of view, she is right\.
But what we have seen until now...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL Parser](https://discourse.openehr.org/t/aql-parser/14370)
> Hello,
What is the best \(comfortable, easiest to use, most often used, most interoperable, etc\.\) implementation of an AQL parser currently available ?
After some googleling I found a Git repository of JacSoyYo\. Alternatively I could cut the parser from the EtherCIS\-Server\.
Currently I am only interested in a runtime object model of AQL queries so I do not need an interpreter engine\.
Greetings
Georg
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Seeking Modeling Assistance for openEHR](https://discourse.openehr.org/t/seeking-modeling-assistance-for-openehr/14371)
> Hello team – I’m at CDC/NIOSH; & looking for some help with getting Occupational Data for Health modeled in openEHR. I’m unfortunately not able to download the archetype editor tool to submit for proposed new archetype (due to restrictions on what we can run on our workstations here); and hoping someone may be able to help me with this.
Thanks so much in advance for any assistance you can provide -
**Angela C. Crovetti**
Sr. Consultant, Attain
1600 Tysons Boulevard, Suite 1400 | McLean,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 72, Issue 4](https://discourse.openehr.org/t/openehr-technical-digest-vol-72-issue-4/12144)
> On the "putting together a web frontend and a Java backend" topic, it may be interesting to look at Vaadin, which is an open source framework to build web applications using Java (you code everything in Java, an equivalent GUI is generated and all behavior that comes from user interaction is actually triggered on the backend through a protocol like RPC; pretty much like the old GWT but smarter and with less boilerplate code). They also have a dev preview on something called Flow, which is...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Announcing Archie version 0.4](https://discourse.openehr.org/t/announcing-archie-version-0-4/15513)
> Hi,
We’re pleased to announce Archie version 0\.4\! For those of you unfamiliar with Archie, it’s an Apache 2 licensed OpenEHR java library, suitable as a basis for archetype modelling and EHR implementations with ADL 2\.
Version 0\.4 is a big change from version 0\.3\. Many features have been added that make Archie suitable as a library for modelling archetypes, and the existing functionality has been improved\.
It includes a BMM implementation contributed by Claude Nanjo, Joey Coyle and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR REST APIs - Release 0.9.0 / invitation for comments](https://discourse.openehr.org/t/openehr-rest-apis-release-0-9-0-invitation-for-comments/12200)
> The REST API Team (Bostjan Lah, Erik Sundvall, Sebastian Iancu, Heath Frankel, Pablo Pazos, and others on the [SEC](https://www.openehr.org/programs/specification/editorialcommittee) and elsewhere) have made a 0.9.0 Release of the ITS (Implementation Technology Specifications) component, in order to make a pre-1.0.0 release of the REST APIs available for wider comment.
The key point about this current release is that it is meant to be a 'core basics' foundation of APIs to build on, and some...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Quantities of arbitrary units in openEHR](https://discourse.openehr.org/t/quantities-of-arbitrary-units-in-openehr/15514)
> Hi all,
I’m working on representing medication strengths in archetypes at the moment. Most medications are thankfully measured in SI units such as mg/ml or mg/{dose unit}, but others use arbitrary units that are not derived from any other physical dimensional units. Examples of these are standardized quality units (SQ-U), focus forming units (FFU), European and American pharmacopoeia units, anti factor Xa units, or international units (IU). There are seemingly an unlimited number of these...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Are there any tutorial on ADL 2.0](https://discourse.openehr.org/t/are-there-any-tutorial-on-adl-2-0/12019)
> Hi,
So far I have been using the template designer and archetype editor to create templates. But I want to explore using ADL 2.0 going forward.
Since the graphical tools available are limited, I am considering hand coding in ADL 2.0. However I am unable to find any documentation other than the OpenEHR specification ([http://openehr.org/releases/AM/latest/docs/ADL2/ADL2.html](http://openehr.org/releases/AM/latest/docs/ADL2/ADL2.html)). Is there any help, documentation or guide that explains...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [How do you identify OPTs in your implementation?](https://discourse.openehr.org/t/how-do-you-identify-opts-in-your-implementation/14369)
> Hi openEHR implementers!
I have a question about how do you identify operational templates in your systems, since the Template Designer doesn't enforce any template ID format, but we have a format defined in v1.0.2 of the specs ([http://www.openehr.org/releases/RM/Release-1.0.2/docs/support/support.html#_template_identifiers](http://www.openehr.org/releases/RM/Release-1.0.2/docs/support/support.html#_template_identifiers)).
In the current version of the specs, the template ID format is to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Process to follow for coding using Terminology server](https://discourse.openehr.org/t/process-to-follow-for-coding-using-terminology-server/14368)
> Hi,
We are in the process of adding a terminology server to code the composition date. However many of the nodes that can be coded are text fields (Eg. Symptom/sign name in Symptom/sign archetype that we have used in Complaints template). As we understand, the data type has to be changed to CODED-TEXT before we can store coded data.
What is the best practice to do this? Shall we go ahead and edit the archetypes, in which case our archetypes will no longer be same as the ones in CKM? Are...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Announcelist](https://discourse.openehr.org/t/announcelist/14366)
> Hi everybody,
In the beginning of the year we had the idea of having an announce list for implementers, hosted by the OpenEhr foundation\.
The discussion starts here:
https://www.mail-archive.com/openehr-technical@lists.openehr.org/msg09912.html
The occasion was that Pablo announced a new version of his Cloud EHRServer to this list\. It was on Christmas day 2016\.
That discussion starts here
https://www.mail-archive.com/openehr-technical@lists.openehr.org/msg09902.html
Isn't that a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with creating medication order with Template designer](https://discourse.openehr.org/t/problem-with-creating-medication-order-with-template-designer/15697)
> Hi,
I am trying to create a medication order template using Template designer and am getting an error while trying to add openEHR-EHR-CLUSTER.timing_daily.v0 and openEHR-EHR-CLUSTER.timing_repetition.v0. More details along with the screenshot of the error in the attached file. I am also attaching the template file set for reference.
I looked at the offending Archetypes, but could not find any problem. If any of you have faced similar problems before, pls point me in the right direction to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Using the openEHR Problem Reports tracker - voting, search, comments.](https://discourse.openehr.org/t/using-the-openehr-problem-reports-tracker-voting-search-comments/16585)
> openEHR 'issues', aka Problem Reports (PRs) are [located here](https://openehr.atlassian.net/projects/SPECPR/issues/SPECPR-168?filter=allopenissues). There are two features which the community can use on issues which can help you to help us improve the specifications more quickly. The first is that you can use 'advanced search' to look at issues in convenient ways, to find what you care about for example.
The second is to 'vote' for issues, which means you want this issue to be addressed....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Extract archetypes](https://discourse.openehr.org/t/extract-archetypes/15505)
> Hi,
Since that it is so that some extract\-classes derive from Locatable, they can be used to use them as RM\-class for an archetype\-definition\.
But how would the ArchetypeId look like, special the rmName\. Would it be something like openEHR\-Extract\-Extract\.\.\.\.\.\.\.\. ?
Thanks in advance for answering
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updates to UML, package paths; new global class index.](https://discourse.openehr.org/t/updates-to-uml-package-paths-new-global-class-index/14367)
> A few improvements for users and implementers of the specifications.
**class indexes**: I've improved the UML extractor that generates the UML diagrams and tables used in the specifications, to generate better class index lists, including a [global one for the whole of openEHR](http://www.openehr.org/releases/BASE/latest/docs/global/index.html). You can use these indexes to search for a class name in a normal browser; the link you find will drop you into the relevant class definition in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [information about allowable data in a openEHR format](https://discourse.openehr.org/t/information-about-allowable-data-in-a-openehr-format/16587)
> Hey all,
Apologies for asking what is probably a simple question but I’m just starting out in this space now.
My question is:
If I have a patient record with ICD-9 and ICD-10 codes, Pharmacy codes, procedure codes, patient data such as age, sex, height, weight etc. and also free form clinical notes. Can I store all this kinda of data in a openEHR format? And if so could you provide me with a sample json of what that kind of patient record would look like?
Or point me in the right...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [SV AW: Versioning of archetypes: Minor or major changes?](https://discourse.openehr.org/t/sv-aw-versioning-of-archetypes-minor-or-major-changes/16586)
> Hi everyone!
This spreadsheet Sebastian mentioned, " spread sheet with some cases to decide what is a major, minor, patch change…", is that available? We're in the making of such a list in Norwegian, and experienced difficulties to differ among the severity of implications of the changes.
This is definitely a interesting topic to examine more – synchronized version updates of archetypes among all EHRs will never happen for sure…
Kind regards,
**Vebjørn Arntzen**
Enterprise Architect,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Versioning of archetypes: Minor or major changes?](https://discourse.openehr.org/t/versioning-of-archetypes-minor-or-major-changes/16695)
> Another crosspost between the Clinical and the Implementers lists.
In versioning archetypes, we’ve defaulted to SemVer’s three version levels MAJOR.MINOR.PATCH. When discussing with DIPS what should be considered MINOR or MAJOR changes, we’ve come to the preliminary conclusion that many more changes than we previously thought may require a MAJOR version change. This is exemplified below mostly with exchange of information between systems, but may also be relevant within a system when adding...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Blockchain](https://discourse.openehr.org/t/blockchain/14384)
> How are the plans about blockchain for OpenEhr? Is there any plan to incorporate it in the standard, or is it regarded as a technical implementers business?
Bert
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Day - Free event London 22nd November 2017](https://discourse.openehr.org/t/openehr-day-free-event-london-22nd-november-2017/15695)
> The openEHR Foundation and Marand are hosting an event on 22nd November at SkillsMatter in London.
The event will explore the opportunities and challenges of openEHR.
Speaking sessions and a panel discussion will provide an introduction to openEHR for novices, along with guests talking about their experiences with openEHR, its implementation, scale of the opportunity, and vision for its capabilities to facilitate interoperability in health IT.
Speakers will shed light on the context and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Stackoverflow tag: openehr](https://discourse.openehr.org/t/stackoverflow-tag-openehr/15506)
> Hi all,
Today I created a tag on Stackoverflow for openEHR
https://stackoverflow.com/questions/tagged/openehr
For it to persist over time there needs to be sufficent level of activity involving openehr tagged questions\.
enjoy\!
Gavin Brelstaff
CRS4 Sardinia
https://stackoverflow.com/users/3507061/gavinbrelstaff
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Mandatory elements in archetypes, and user interfaces](https://discourse.openehr.org/t/mandatory-elements-in-archetypes-and-user-interfaces/15497)
> Crossposting this between the clinical and implementers lists, since it belongs in both:
In some archetypes, one or more elements are set as mandatory (typically occurrences 1..1 or 1..*), because the rest of the concept makes no sense without this particular element recorded. Examples are Problem/diagnosis name in Problem/diagnosis, and Temperature in Body temperature. This is not intended to mean that it’s mandatory to enter data into the element in a UI, but that this particular element...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to use ACTION.procedure for Surgery Reports](https://discourse.openehr.org/t/how-to-use-action-procedure-for-surgery-reports/14363)
> I have written a note on how we will use ACTION.procedure to document what happened during surgery.
Have a look at the notes here: [https://github.com/bjornna/openehr-discussion/blob/master/surgery/index.adoc](https://github.com/bjornna/openehr-discussion/blob/master/surgery/index.adoc)
There is also some discussions on #slack: [https://openehrclinical.slack.com/messages/C7U9JD1EK](https://openehrclinical.slack.com/messages/C7U9JD1EK)
Sincerely
Bjørn Næss
Product Owner openEHR...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Occurrences on Top level element](https://discourse.openehr.org/t/occurrences-on-top-level-element/14362)
> Hello, my name is Leonardo Ornelas, this is my first message for this mail list. Maybe somebody could take my doubts. I'm working on a project that follows some parts of openEHR. I did an adl-core implementation on nodejs. This version makes the parser from adl to json, supports flattener of archetypes and generation of operational templates, as well as the generation of a hierarchical model of RM from Archetype / OPT. There is a person in the team in charge of creating some templates and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [This topic needs a title](https://discourse.openehr.org/t/this-topic-needs-a-title/15493)
> An implementation focused evaluation of openEHR and its integration with Bayesian Belief Networks for clinical decision support
One of my most persistent PhD students, Seref Arikan, has published his ground-breaking PhD thesis on the UCL online repository.
A fuller announcement and link has been posted in the News Section of the openEHR web site at:
[http://openehr.org/news_events/community_news](http://openehr.org/news_events/community_news)
We hope it will make a useful contribution to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Does aql support multiple ehrids?](https://discourse.openehr.org/t/does-aql-support-multiple-ehrids/14364)
> Hi,
I have tested aql with single ehr and across all ehrs(without any ehrid). Can we pass an array of ehrids in an aql to limit the query to selected ehrs?
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL for multi-occurrence nodes](https://discourse.openehr.org/t/aql-for-multi-occurrence-nodes/14365)
> Hi,
What is the expected response to AQL on a node with multiple occurrences? Does it return all the occurrences or only the first one?
If it is expected to return all occurrences, what is the structure of the response? will the occurrences be returned as an array?
If only the first one is returned, how do we get all the occurrences? Adding multiple select lines in aql may not be practical as the number of occurrences can vary.
Can nay body give a select statement syntax for this?
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Scenarios for change type "deleted"](https://discourse.openehr.org/t/scenarios-for-change-type-deleted/15494)
> Hi I'm trying to define a set of rules for a logical delete commit and have some gray areas that I'm not sure of.
**1. commit after delete flow**
[creation v1] => [modification v2] => [deleted v3] => ?
Can a modification/amendment v4 happen after a delete?
This is one of those cases that forks in the version tree can happen, since v2 is deleted by v3, but v1 can be forked and a commit of modification or amendment can happen on that branch.
I'm considering the delete only affects a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 68, Issue 11](https://discourse.openehr.org/t/openehr-technical-digest-vol-68-issue-11/14357)
> Yes yes, we understand that it is not exactly correct to say "template filled", just as it would not be exactly correct to say "filled class" in the object orientation paradigm. But we imagine if we spoke only "Composition" would not be clear what we meant and we use the term "Filled Template" knowing that it was not the most appropriate. Now we understand that it is sufficient to use the term "Composition Instance", or would there be a more adequate term?
Sim sim, entendemos que não é...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Entitlements](https://discourse.openehr.org/t/entitlements/14361)
> Dear Sam,
I remind you of your legal obligations to pay me my proper entitlements on leaving Ocean's employment. As you know, I was not paid for the last 4 weeks of my employment with the company, nor have I been paid owing leave entitlements or long service leave entitlements.
I will expect full payment of these entitlements by the end of this week or I will need to take further action.
Yours sincerely
Hugh Leslie
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 68, Issue 8](https://discourse.openehr.org/t/openehr-technical-digest-vol-68-issue-8/14356)
> Hi!
We were able to import openEHR-OPT.jar into our JAVA project and we were also able to instantiate the classes XmlInstanceGenerator, OperationalTemplate, OperationalTemplateParser, etc. However, we have a question regarding the template in OPT format. We understand that this format has a template metadata structure, but it does not carry clinical data within it (eg blood pressure: 120 mmHg), in other words, it is not an instance of the template. Is this understanding correct? If yes, how...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Using Other Constraints in Slots](https://discourse.openehr.org/t/using-other-constraints-in-slots/16584)
> Hi there,
I stumpled upon the "Using Other Constraints in Slots" section in the spec ([http://www.openehr.org/releases/AM/latest/docs/ADL1.4/ADL1.4.html#_using_other_constraints_in_slots](http://www.openehr.org/releases/AM/latest/docs/ADL1.4/ADL1.4.html#_using_other_constraints_in_slots)). When taking a look at the tools (ADL Editor, LinkEHR, ADL Designer), there does not seem to be real support for this expressions. Therefore, I tried to create it by hand but have not been able to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 68, Issue 7](https://discourse.openehr.org/t/openehr-technical-digest-vol-68-issue-7/14355)
> We understand Pablo, we will test.
Thank you very much.
[]´s
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 68, Issue 6](https://discourse.openehr.org/t/openehr-technical-digest-vol-68-issue-6/15725)
> Good afternoon.
Yes, we did. Until we know the repository, but unfortunately we do not dominate Groovy. So we asked if there was anything in JAVA. We know there is a relationship between Groovy and JAVA, but we do not know how to do this integration.
Pablo, do you have a tutorial on how to use your library in JAVA?
Thank you very much for the kind attention and prompt return of this community.
/* Original in portuguese:
Boa tarde.
Sim, vimos. Até conhecemos o repositório, mas...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [COMPOSITION (TEMPLATE FILLED) TO XML](https://discourse.openehr.org/t/composition-template-filled-to-xml/15722)
> Good Morning!
Is there any library in JAVA or any tutorial about serialize a composition (template filled with data) in XML?
Bom dia!
Existe alguma biblioteca em JAVA ou algum tutorial para serializar uma composition (template preenchido com dados) em XML ?
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Welcome to our new openEHR Ambassador - Philippines](https://discourse.openehr.org/t/welcome-to-our-new-openehr-ambassador-philippines/16583)
> It is with great pleasure that we announce the appointment of our new openEHR Ambassador- Philippines.
[http://www.openehr.org/about/ambassadors](http://www.openehr.org/about/ambassadors)
Ryan Julius A. Bañnez, MD (Philippines)
Ryan obtained his Doctor of Medicine degree at the University of the Philippines, Manila, and pursued a fellowship track in Medical Informatics at the National Library of Medicine, National Institutes of Health, Bethesda, Maryland. His areas of interest include...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[openEHR SEC] AQL FROM & CONTAINS with many entries](https://discourse.openehr.org/t/openehr-sec-aql-from-contains-with-many-entries/15498)
> Hi all, another question about AQL and CONTAINS.
Most of the AQL samples use just one branch in the FROM clause, like:
EHR CONTAINS COMPOSITION CONTAINS OBSERVATION.
I'm wondering what would be the correct FROM notation when more than one ENTRY is needed. Some examples below.
SELECT o1/data[...]/.../value, o2/..., ....
FROM
COMPOSITION c [archid] CONTAINS OBSERVATION o1 [archid2],
COMPOSITION c [archid] CONTAINS OBSERVATION o2 [archid3],
COMPOSITION c [archid] CONTAINS OBSERVATION o3...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[openEHR SEC] CONTAINS in AQL](https://discourse.openehr.org/t/openehr-sec-contains-in-aql/16580)
> Hi all,
I'm reading through the AQL specs, on this section [http://openehr.org/releases/QUERY/latest/docs/AQL/AQL.html#_containment](http://openehr.org/releases/QUERY/latest/docs/AQL/AQL.html#_containment) it is mentioned that CONTAINS is from parent to child.
Most examples there show COMPOSITION CONTAINS ENTRY. In a case that there is a SECTION in the middle, should AQL be always COMPOSITION CONTAINS SECTION CONTAINS ENTRY?
Before reading this specific point I was thinking that CONTAINS...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Suitable data type to record frequency of something happening](https://discourse.openehr.org/t/suitable-data-type-to-record-frequency-of-something-happening/15503)
> Hi,
I need to record the frequency of occurrence of an event.Typical readings will be like 2/day, 5/week, 1/month etc.In archetype editor I could not find a suitable property to use under quantity. The count also does not work as it does not have a unit associated. Please advise the best approach.
Also what is the difference between Duration and Quantity with time property? Both seem to be doing the same.
regards
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Info request about openEHR implementations for a presentation](https://discourse.openehr.org/t/info-request-about-openehr-implementations-for-a-presentation/16581)
> Hi all,
I'm giving a talk about openEHR next month in Argentina and the organization asked me to mention something about openEHR implementations especially in Latin America. You know the typical stuff, where it was implemented, why openEHR, for what it is used, challenges, benefits, lessons learned, etc.
Since I don't have much info I ask for your help to gather some info. I know Thomas, Jussara and people from Marand know more than me about openEHR in Brazil, if you can assist me with some...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Modeling generic concepts, considerations for querying](https://discourse.openehr.org/t/modeling-generic-concepts-considerations-for-querying/15499)
> Hi all,
I'm working with the clinical synopsis archetype, using it to model very open psychotherapy notes. The difference of that archetype from, for instance, blood pressure, triage, problem/diagnosis, is these archetypes are more or less very specific concepts, while synopsis might be used in many contexts, by different specialties, to save different kinds of data. The synopsis itself is a very generic concept.
Considering querying for a synopsis, I think queries should consider the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is 'Choice' datatype available in Archetype editor an OpenEHR standard](https://discourse.openehr.org/t/is-choice-datatype-available-in-archetype-editor-an-openehr-standard/15496)
> Hi,
Archetype editor includes a datatype called "Choice'. This allows more than one data type(text & coded text for example) for the same node. Is this OpenEHR standard?
regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New Visa Cards was card request](https://discourse.openehr.org/t/new-visa-cards-was-card-request/16579)
> I have applied for a debit card against our CBA business transaction A/c. Will take abou 1/52+ after which we can auto pay licences and the like via the card.
David
[details="(attachments)"]
[/details]
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New interim release of ADL Workbench.](https://discourse.openehr.org/t/new-interim-release-of-adl-workbench/15495)
> I have released a new version of the ADL Workbench ([build 2.0.6.2934](https://openehr.atlassian.net/browse/AWBPR-64)) which fixes various problems, including start-up problems ([AWBPR-64](https://openehr.atlassian.net/browse/AWBPR-64)) caused by a bad BMM schema that was included in the previous build.
The above link is a 64-bit build for Windows (7, 8, 10 etc). We'll post a Mac version as soon as possible.
- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer v1.0 milestone reached!](https://discourse.openehr.org/t/ehrserver-v1-0-milestone-reached/16578)
> Hi all,
I'm glad to announce we have reached v1.0, a feature complete and production ready version.
Mre info about the release: [https://github.com/ppazos/cabolabs-ehrserver/releases/tag/v1.0](https://github.com/ppazos/cabolabs-ehrserver/releases/tag/v1.0)
Useful info:
+ clients and resources: [https://cloudehrserver.com/community](https://cloudehrserver.com/community)
+ documentation: [https://www.cabolabs.com/en/projects](https://www.cabolabs.com/en/projects)
+ cloud staging server for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR in North Americas](https://discourse.openehr.org/t/openehr-in-north-americas/16582)
> Hello,
Are there any openEHR projects or efforts that are either planned or in progress in Canada, USA and/or Mexico?
Ramayya
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openeHR Specifications Editorial Meeting Aug 28/31 - RFI](https://discourse.openehr.org/t/openehr-specifications-editorial-meeting-aug-28-31-rfi/16577)
> The [openEHR SEC](http://www.openehr.org/programs/specification/editorialcommittee) is having a 3-day meeting in Alkmaar at the end of August at which we will undertake various routine SEC work (PR and CR-processing), as well as consider various design issues, new specifications and create baselines for some existing artefacts that are not yet properly official.
The details of the meeting are [here on the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [standalone .opt parser open source](https://discourse.openehr.org/t/standalone-opt-parser-open-source/15698)
> I am working with some UCL computer science students who are exploring the use of an operational template to generate mappings.
Can anyone point me to a reasonably standalone .opt parser, preferably jajva-based?
Ian
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR related News: Ripple Foundation launches EtherCIS to the world of Healthcare](https://discourse.openehr.org/t/openehr-related-news-ripple-foundation-launches-ethercis-to-the-world-of-healthcare/14129)
> Dear openEHR Colleagues,
At long last I'm pleased to announce some news to the openEHR community, which I hope you will find of interest/value to you.
Those of you who know me, know I have been championing openEHR for quite some time, I believe it is key to the future of healthcare.
You may also know that I have been an advocate for an open source implementation of openEHR in action for quite some time too.
In my opinion if we want openEHR to truly transform the world of healthIT and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Terminology bindings ... again](https://discourse.openehr.org/t/terminology-bindings-again/15500)
> Recently we discussed terminology bindings. We probably still have not got them right, but we don't have a model of what we think they should be. I posted a quick idea of a possible more structured version:
```
term_bindings = <
["snomed_ct"] = <
["/data[id3]/events[id4]/data[id2]/items[id26]"] = (SIMPLE_BINDING) <
target = <[http://snomedct.info/id/169895004](http://snomedct.info/id/169895004)> -- Apgar score at 1 minute
notes = <"some notes">
min_version =...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Q: design description of lab archetypes](https://discourse.openehr.org/t/q-design-description-of-lab-archetypes/15501)
> Clinical modellers,
I'm trying to work out the latest design of Lab archetypes. A Lab result seems to now be a structure like the following:
- openEHR-EHR-**OBSERVATION**.**laboratory_test_result**
- + at0097|Test findings|: openEHR-EHR-**CLUSTER**.**laboratory_test_panel** [*]
- +at0002 |Laboratory Result|: **CLUSTER** [*]
- +at0004 |Reference range guidance|
- +at0005 |Result status|
- +at0014 |Result Detail|: [open slot] - ? openEHR-EHR-**CLUSTER**.**laboratory_test_analyte** [*]
-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Task Planning update](https://discourse.openehr.org/t/openehr-task-planning-update/16574)
> For those interested in a short update, [see here (blog post)](https://wolandscat.net/2017/07/06/openehr-task-planning-progress-update/).
The latest [spec draft is here](http://www.openehr.org/releases/RM/latest/task_planning.html).
- thomas
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Some persistent compos are event in the CKM](https://discourse.openehr.org/t/some-persistent-compos-are-event-in-the-ckm/15502)
> Doing testing for the EHRServer with persistent compositions found problem list and medication list have category 433 (event) instead of 431 (persistent).
Maybe other compositions have the same issue.
This might affect many people.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Using aql for data set in DV_CODED_TEXT](https://discourse.openehr.org/t/using-aql-for-data-set-in-dv-coded-text/15488)
> HI,
I am just wondering if it is possible to embed an AQL into the archetype so that the data set for a DV_CODED_TEXT is formed out of existing compositions.
For example, a hospital registration form that asks for a person's allergies. Instead of an empty field, it can be populated from existing data through a query so that the front desk can just validate the data. Can this be modeled into the archetype? Or should it be an implementation detail?
regards
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Versioning implementations](https://discourse.openehr.org/t/versioning-implementations/15484)
> Hi all,
I had this questions in mind for a long time: did someone implemented the distributed versioning of openEHR?
The specs define a great distributed versioning mechanism but it is a little trickier to implement. Also there is no clear who will do the work of managing that, and how that structure will be queried. It is very difficult to me to think of an amendment sent to an EHR and that not being available for all the parties looking at the EHR of the patient.
In the case of the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 64, Issue 21](https://discourse.openehr.org/t/openehr-technical-digest-vol-64-issue-21/16572)
> Thank you Thomas,
The use of URI's is well known, but just not fitting with the billions of HL7 v3 implementations\. As long as identification is correct each variant of ids is fine\.
I partly agree to your point here:
codeSystem="2\.16\.840\.1\.113883\.6\.96
This is not how it normally appears in an DCM or HL7 v3 message and i suggest should not appear in an archetype\.
Normally it reads like
<codeSystem="2\.16\.840\.1\.113883\.6\.96"...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 64, Issue 19](https://discourse.openehr.org/t/openehr-technical-digest-vol-64-issue-19/16575)
> Dear all,
If openEHR wants to be really interoperable, it must have a mechanism to handle OIDs\. Billions of specifications and standards in health informatics are deploying OIDS\.
Comparing them with the plague, probably in analogy with viruses and worms, does not help to solve issues\.
How for instance would you be able to exchange SNOMEDCT based coded data e\.g\. In an HL7 v3 CDA that is populated with archetypes and requires SNOMEDCT being identified with its OID\. Here in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM 1.4 - Archetype.uid a UUID or OID?](https://discourse.openehr.org/t/aom-1-4-archetype-uid-a-uuid-or-oid/15482)
> Bert picked up an anomaly [in this PR](https://openehr.atlassian.net/browse/SPECPR-219) that I think should probably be fixed. ARCHETYPE.uid is of type UUID in the AOM2 spec, but of type HIER_OBJECT_ID in the AOM1.4 spec (the latter type is the openEHR type for OIDs). However it appears that all ADL1.4 archetypes that have a uid have it as a Guid (i.e. UUID), and I assume the various tools do as well. We avoid Oids like the plague in openEHR, and I am not aware of them being used...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR UML website updated to latest](https://discourse.openehr.org/t/openehr-uml-website-updated-to-latest/16573)
> The 'UML' link on the home page was pointing to an out of date copy of the [openEHR UML web portal](http://www.openehr.org/releases/trunk/UML/). This has now been updated to the latest, and includes AM, RM, BMM and BASE components.
Click on the Diagrams link and you will see this.
The diagrams are all from MagicDraw, and are the same as those in the specifications. MagicDraw files (which contain orthodox XMI 2.x files) are all...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New Gartner report on openEHR](https://discourse.openehr.org/t/new-gartner-report-on-openehr/16570)
> Courtesy of Marand, we are pleased to be able to provide complimentary access to the new Gartner report:
Gartner - Evaluate openEHR Standards for Managing Clinical Content Across the Care Continuum, Mike Jones, Henrik Hallenberg, 7 April 2017.
which describes how to reduce the risk of vendor lock-in and create the right conditions for innovation by persisting structured clinical content from proprietary care delivery applications outside the EHR.
A link to the full report is available on...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [SV: openEHR-technical Digest, Vol 64, Issue 6](https://discourse.openehr.org/t/sv-openehr-technical-digest-vol-64-issue-6/15487)
> Hi all
To me a "questionnaire" is a vague notion. There can be a lot of different "questionnaires" in health. From the GP's in Thomas's example to a Apgar score, to a clinical guideline and even a checklist. Those are all a set of "questions and answers", but the scope and use is totally different. In paper questionnaires we will find a mix of many, maybe all, of those, crammed into what the local practice have found to be useful (= "Frankenforms"). To try to put all of them into a generic...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 64, Issue 6](https://discourse.openehr.org/t/openehr-technical-digest-vol-64-issue-6/15481)
> Hi Heather,
the key difference is that the assessment scales have a scientific validation, leading to clinimetric data, often for populations, but e\.g\. Apgar and Barthell are also reliable for individual follow up measures\.
a simple question, answer, even with some total score, does usually not have such evidence base\. I agree that in the data / semantic code representation in a detailed clinical model it is not different\.
Hence, also Grahame's nonsense comment on the value of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 64, Issue 4](https://discourse.openehr.org/t/openehr-technical-digest-vol-64-issue-4/15491)
> The examples given as Glasgow Coma Scale and Barthel index are definitely NOT questionnaires\. These are assessment scales and require quite a different approach than the also extremely useful questions and answers\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Questionnaires](https://discourse.openehr.org/t/questionnaires/15490)
> Following Thomas’ suggestion re a separate thread:
I wrote a blog post in 2014 which still reflects our current thinking re questionnaires: [https://omowizard.wordpress.com/2014/02/21/the-questionnaire-challenge/](https://omowizard.wordpress.com/2014/02/21/the-questionnaire-challenge/)
Our experience is that the data is the priority and so we want to focus on questionnaires to support capture of good quality data.
If you want to try to capture data from the majority of existing...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Little sync problem in Java-code regarding ResourceItem](https://discourse.openehr.org/t/little-sync-problem-in-java-code-regarding-resourceitem/16571)
> Hi,
A short notification for there is a small but disturbing problem in Java\-lib code, which I was studying for some project purpose\.
In the code in java\-libs is in conflict with the specifications \(the specifications are right, also conform the many examples on CKM\)\. It is not a big thing, but can be confusing for someone new in OpenEHR\.
I did not find a Jira\-project to post it, so I do it here\.
Thx
Bert
The explanation, for if some wants to repair it\.
It is about these...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Major update to openEHR Task Planning (workflow) draft specification](https://discourse.openehr.org/t/major-update-to-openehr-task-planning-workflow-draft-specification/15489)
> I have published a major update to the [Task Planning draft specification](http://www.openehr.org/releases/RM/latest/docs/task_planning/task_planning.html). It now includes sequential and parallel groups, conditional pathways, and a new model of execution time structures. It's still very rough in places, but in the interests of 'publish early publish often'...
The main thing to be obtained from this version is that the general model structure I think is about right, i.e. the separation of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reports - a new openEHR RM type?](https://discourse.openehr.org/t/reports-a-new-openehr-rm-type/15483)
> some of us have been looking at the idea that a 'report' should be a new content type in openEHR, that can include other content of different types, and in different ways.
We have [published a wiki page](https://openehr.atlassian.net/wiki/display/spec/Reports) with the initial notes on the idea, and a (possibly) novel approach to solving the quoting/inclusion problem, which is to serialise included content into the report. We think the report type (the name may need to be reconsidered) would...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer v0.9.5 was released!](https://discourse.openehr.org/t/ehrserver-v0-9-5-was-released/14352)
> Dear friends,
The EHRServer openEHR Clinical Data Repository, Open Source, Designed for the Cloud v0.9.5 was released!
Release: [https://github.com/ppazos/cabolabs-ehrserver/releases/tag/v0.9.5](https://www.linkedin.com/redir/redirect?url=https%3A%2F%2Fgithub%2Ecom%2Fppazos%2Fcabolabs-ehrserver%2Freleases%2Ftag%2Fv0%2E9%2E5&urlhash=NVBW&_t=tracking_anet)
EHRServer overview:...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [A little community coordination](https://discourse.openehr.org/t/a-little-community-coordination/15485)
> Hi all,
We were discussing on other threads about the need to improve the tools, ref impls and frameworks we use for openEHR stuff. We are few in the community working on those areas, and sometimes doing duplicated work and overlapping solutions.
I believe if we know who is working on what, we can make a better use of our collective time as a community, and reuse others work, or even help on their projects.
Modeling tools are getting behind the specs progress, tool chain is broken and...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Please help answer this question on StackOverflow](https://discourse.openehr.org/t/please-help-answer-this-question-on-stackoverflow/14351)
> [http://stackoverflow.com/questions/43922257/how-to-write-a-compliance-statement-for-the-openehr-standard](http://stackoverflow.com/questions/43922257/how-to-write-a-compliance-statement-for-the-openehr-standard)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 63, Issue 9](https://discourse.openehr.org/t/openehr-technical-digest-vol-63-issue-9/16567)
> Actually it not just a local terminology expression library we need. I think we also need context / artefact specific synonyms for search.
The RCPA have done a lot of work trying to subset evaluation procedures/lab procedures in SNOMED CT in the context of Lab ordering (e.g. GP/FP/Specialist to Lab, Aged Care facility to Lab). If we arranged for the Australian NRC to add all of these synonyms it would certainly `pollute` the reference terminology. An example might be 'AA' for Amino Acids. I'm...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 59, Issue 20](https://discourse.openehr.org/t/openehr-clinical-digest-vol-59-issue-20/14353)
> Many questions are in SNOMEDCT eg observable entities
Many answers are in LOINC, in particular the answers to questions for assessment scales\.
ISO TS 13972 gives careful guidelines to choose the precise code from any code system for both questions and answers\.
The blunt this does A and that does B will prove impossible for many concepts and I see no move to 100% redo SnomedCT nor LOINC \(because it is unnecessary\)\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [SNOMEDCT - correct representation](https://discourse.openehr.org/t/snomedct-correct-representation/15486)
> Norway just became a SNOMED country.
One simple question – what is the correct terminologyId to use for SNOMED-CT.
Currently we use ‘SNOMEDCT’ like below. Is this correct?
Høyre øye
SNOMEDCT
18944008
Vennlig hilsen
Bjørn Næss
Produktansvarlig
DIPS ASA
Mobil +47 93 43 29 10
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [AQL: Expected result with repeating structures](https://discourse.openehr.org/t/aql-expected-result-with-repeating-structures/16576)
> Hi
We have created a GIT repo with some issues from our experiences with AQL.
The repo was created to expose one issue with repeating items. You will find it here – and some feedback is welcome:
Folder with all files: [https://github.com/bjornna/openehr-conformance/tree/master/aql/case1-permutations](https://github.com/bjornna/openehr-conformance/tree/master/aql/case1-permutations)
README with the problem:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Add SNOMED codes to values in Internal code set](https://discourse.openehr.org/t/add-snomed-codes-to-values-in-internal-code-set/15614)
> Hi,
I am trying to model some archetypes using coded text. The option values should ideally come from SNOMED. Currently we do not have access to a terminology service and so we are using Internal codes to achieve what we want.
However we would like recorded values to also include their SNOMED codes for backward compatibility when we start using terminology service in the future. How can we include a terminology code with the option values in internal code set.
Regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Random / Synthetic Data Generation over Templates](https://discourse.openehr.org/t/random-synthetic-data-generation-over-templates/15473)
> Hello everyone
I remember some time ago, there was a tool that given a detailed template description, it would populate it with random data taking
into account only knowledge about the datatype.
I vaguely remember Heather Leslie mentioningit but I may be wrong.
Is that functionality available from one of Ocean’s tools? (e.g. the Template Designer)
Is similar functionality available through other tools? (e.g. LinkEHR, other).
Looking forward to hearing from you
Athanasios Anastasiou
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Including reference range in archetypes](https://discourse.openehr.org/t/including-reference-range-in-archetypes/15610)
> Hi,
I am trying to create an archetype that screens for health risks. All the questions have ordinal data. Based on the values selected for the questions, the consolidate risk value is calculated.
I want the UIi to display appropriate warnings (coloring the risk value etc) based on a reference range for the value. How can I include the reference range in the archetype so that the UI can read that and display the warnings?
thanks for the help
regards
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [SNOMED in CKM](https://discourse.openehr.org/t/snomed-in-ckm/15472)
> Hi,
I needed to clean up archetypes from SNOMED bindings because of license\-reasons, I "grepped" the local directory from CKM\.
To my surprise I found there SNOMED bindings in over 50 archetypes\.
This can, I think, be a problem for countries which have no SNOMED license\.
Or is the opinion that SNOMED is allowed in archetypes even in non\-member\-countries\.
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [BMI archetype](https://discourse.openehr.org/t/bmi-archetype/15476)
> Hi,
Shouldn't the BMI archetype on CKM be of type Evaluation? One does not observe BMI, it is a calculation.
openEHR-EHR-OBSERVATION.body_mass_index.v1
Thanks for your comments.
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template specs](https://discourse.openehr.org/t/template-specs/15680)
> Hi all,
We are looking for the opt and oet XML format for the Templates, is it somewhere in the specs?
Many thanks, Jan-Marc
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Z scores](https://discourse.openehr.org/t/z-scores/15477)
> Hi everyone,
We’ve got an archetype proposal for Z scores ([https://en.wikipedia.org/wiki/Standard_score](https://en.wikipedia.org/wiki/Standard_score)).
The way we understand these, they’re statistical calculations for specific values such as height or weight, based on a population average, similar to percentiles. We’re not sure how to model this in archetypes, and were wondering if anyone else have solved this already? We’ve got an archetype that’s related to child growth charts that will...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 58, Issue 10](https://discourse.openehr.org/t/openehr-clinical-digest-vol-58-issue-10/16565)
> Hi everyone,
Bert, here in Brazil we are facing the same situation. We are supposed to bind the openEHR-EHR-EVALUATION.problem_diagnosis.v1 problem/diagnosis name element to both ICD10 and ICPC2 code systems, so at runtime the professional can use the locally preferred terminology. Since it doesn't seem to be possible through Template Designer, we tried to implement it on the archetype just like you. So far we are not working with ADL, but when exporting the operational template and XML...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Problem with constraint_binding](https://discourse.openehr.org/t/problem-with-constraint-binding/15469)
> Dear readers,
I have a problem and I want to ask your advise.
The problem is that I want to use openEHR-EHR-EVALUATION.problem_diagnosis.v1 which is in CKM.
In that archetype is the item "Problem/Diagnosis name", which is of type DV_TEXT. We want to use it as DV_CODED_TEXT, because we want to add code to the entered name.
In this situation where I work, the customer wants to use 2 different codes, one company crerated internal codelist, and ICD10.
It seems easy to arrange in the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical Knowledge Manager (CKM) - New Release with new Dashboard](https://discourse.openehr.org/t/clinical-knowledge-manager-ckm-new-release-with-new-dashboard/16569)
> Dear all,
We have just updated the openEHR Clinical Knowledge Manager.
This CKM release adds a new Dashboard for new or not logged-in users. It also completely revamps the current Dashboards for logged-in users, editors and clinical knowledge administrators. In addition, we have finetuned many details around the review process, statistics, various grid tooltips, the UCUM unit validation and the general CKM look & feel.
You can view the detailed RELEASE NOTES here:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR in China 2016](https://discourse.openehr.org/t/openehr-in-china-2016/16564)
> After the successful "First Workshop on Using and Promoting openEHR in China in 2016" in April, more and more domain experts, hospitals and vendors in China are interested in openEHR.
To make more people know openEHR in China, OpenEHR technical committee had developed an official website, including contents of news, notification, forum, cases and program. And several other organizations and companies has joined in the working groups led by Zhejiang University (ZJU) to start localization of...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New Clinical Knowledge Manager user interface](https://discourse.openehr.org/t/new-clinical-knowledge-manager-user-interface/16568)
> Dear colleagues,
Ocean is in the final stages of preparing a major new release for the openEHR Clinical Knowledge Manager – featuring a new Dashboard as the default view, and which is configured differently depending on the viewer’s role. I wanted to share this with you a little earlier so that when the update occurs, it will not be a total shock to everyone!
I have created a new wiki page that has some screenshots of the upgrade from our test server – showing some example Dashboards for :
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [is change type "merge" needed?](https://discourse.openehr.org/t/is-change-type-merge-needed/14350)
> Hi all,
Going through the specs again for a new course, I was checking the version control. Since "merge" of two branched versions is possible, shouldn't the openEHR terminology include a "merge" value for change_type?
Or a merge is considered to be a "creation" change type with "is_merged" = true?
Ref: page 13 [http://www.openehr.org/releases/1.0.2/architecture/terminology.pdf](http://www.openehr.org/releases/1.0.2/architecture/terminology.pdf)
Thanks!
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer v0.9 was released!](https://discourse.openehr.org/t/ehrserver-v0-9-was-released/15478)
> Dear friends and colleagues,
I'm glad to let you know that the new version of the EHRServer is ready. You can find the code of the release here: [https://github.com/ppazos/cabolabs-ehrserver/releases](https://github.com/ppazos/cabolabs-ehrserver/releases)
The EHRServer is an open source, service oriented, cloud-ready, openEHR compliant, clinical data repository. You can find more about he project, here: [http://cabolabs.com/en/projects](http://cabolabs.com/en/projects)
Next week we'll have...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [inheritance of archetypes](https://discourse.openehr.org/t/inheritance-of-archetypes/15606)
> Dear all of the technical mailing list,
I made a new message tothis list \(specialized ;\-\), so it will be discussed separately\.
I do that because in the other message, I describe a real problem which needs a solution, and this message is about thinking about a solution in the archetype\-framework, which will takes for years to come \(if it will come, maybe I am wrong in my proposal\)\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Generic vs specific archetype modeling](https://discourse.openehr.org/t/generic-vs-specific-archetype-modeling/16561)
> Dear all,
I have a question and I wonder which choice other people would make in such a situation\.
A simple example to explain the situation: Imagine I want to record a few labtests in a template\.
There are a few choices:
1\) Use a generic lab\-test archetype, and clone it inside a template and give it a label which explains its specific purpose\.
2\) Specialize a generic lab\-test atchetype so it gets an archetype\-id which explains its specific purpose\.
Both have advantages \(and the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [INFORMATION ABOUT THE SYSTEM](https://discourse.openehr.org/t/information-about-the-system/15468)
> Good evening,
I am a postgraduate student in Bioinformatics and it may seem stupid but I would like to ask you a few questions about openEHR , as I was unable to find or understand them\.
What database openEHR uses and what programming language?
Is it possible to alter the schema in order to fit to my needs?
Thank you in advance,
Mema Stamataki\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Two LOINC codes for one lab-item](https://discourse.openehr.org/t/two-loinc-codes-for-one-lab-item/15474)
> Hi all,
When you work with quantities it is possbile to add more units, sometimes, the use of different units have other LOINC-coding, this is for example with
LOINC:
LOINC LongName Component Scale exUCUMunits
2160-0 Creatinine [Mass/volume] in Serum or Plasma Creatinine Qn mg/dL
14682-9 Creatinine [Moles/volume] in Serum or Plasma Creatinine Qn umol/L
Would it be good if it was possible to add code per unit-kind in dv_quantity?
Or are there other suggestions
Thanks
Bert Verhees
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Hand coding templates in ADL 1.4](https://discourse.openehr.org/t/hand-coding-templates-in-adl-1-4/15471)
> Hi,
We are exploring OpenEHR as part of a public health management pilot project in India and have some questions that I am unable to find proper answers.
After studying the available libraries, tools and opensource server implementations, ADL 1.4 seems to be more widely supported than the newer ADL 2.0. The shared archetype repository (CKM) still contains only 1.4 version archetypes. In light of this, I am assuming that for anybody planning to adopt OpenEHR, it will be advisable to stick...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Creating archetypes with alternatives](https://discourse.openehr.org/t/creating-archetypes-with-alternatives/15467)
> Hi,
I'm testing the EHRServer with alternative datatypes for the same ELEMENT.value.
I found the only way of doing that in the Archetype Editor is by setting the node as Any. And there is no way to further constraint the allowed datavalues in the AE.
In the Template Designer I can further constraint that by specifying which specific types can be used, to avoid the possibility of allowing any datavalue to be there. The problem I found is that after setting the allowed datavalues, I can't...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [better diagram for 'clinical investigator recording process'](https://discourse.openehr.org/t/better-diagram-for-clinical-investigator-recording-process/16560)
> I have created a [newer version of the oft-copied and used diagram on clinical process](http://www.openehr.org/releases/RM/latest/docs/ehr/ehr.html#_information_ontology), as part of progressively upgrading diagrams in various specification documents.
Source is in draw.io format; here are the [source XML](https://github.com/openEHR/specifications-RM/blob/master/docs/ehr/diagrams/clinical_investigator_recording_process.xml) along with [generated...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [NHS melt down](https://discourse.openehr.org/t/nhs-melt-down/16559)
> http://www.theregister.co.uk/2017/01/31/nhs_reply_all_email_fail_half_billion_messages/
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [FOR REVIEW: Proposed major RM extension specification - Planned Tasks](https://discourse.openehr.org/t/for-review-proposed-major-rm-extension-specification-planned-tasks/16558)
> There is a new draft specification available for open review, called [Task Planning Information Model](http://www.openehr.org/releases/RM/latest/docs/task_planning/task_planning.html). You can get it at that link, or if you want to find it later, it has links in the usual places on the main [specifications link page](http://www.openehr.org/programs/specification/workingbaseline).
This is an early draft based on an original proposal and model provided by Bjørn Næss at DIPS (Norway). I have so...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ELEMENT.null_reason proposal](https://discourse.openehr.org/t/element-null-reason-proposal/15470)
> Silje has just pinged me again on the question of whether we should have an ELEMENT.null-reason or similar attribute to accommodate specific reasons for null_flavour being set. There are 3 PRs on this as follows:
- [SPECPR-41](https://openehr.atlassian.net/browse/SPECPR-41) - Enable content specific flavours of null to be specified per archetype
- [SPECPR-62](https://openehr.atlassian.net/browse/SPECPR-62) - Add a 'reason for null' text attribute in the Reference model
-...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [post coordinated expressions](https://discourse.openehr.org/t/post-coordinated-expressions/15466)
> Hi,
Last week, I mentioned on this list that the Ocean archetype-editor does not allow post-coordinated SNOMED expressions in terminology-bindings. I also made some JIRA calls for this, also for an abnormality which was related to this.
I also found out that the LinkEHR archetype-editor has the same problem.
So that made me suspicious, and I looked at the ADL 1.4 specifications, and there it was, it is not allowed in ADL 1.4 tot use post-coordinated SNOMED expressions in...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The use of CKM](https://discourse.openehr.org/t/the-use-of-ckm/16557)
> Hi
I have a remark about the use of some archetypes in CKM.
I think that it would be nice to have archetypes of some specific content, for example, medication, always of type cluster, and have container archetypes, for example in this case, of type action to hang them in a composition.
If this was a policy, then the idea of building blocks would be much more usable.
Best regards
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Context in persistent COMPOSITION archetypes?](https://discourse.openehr.org/t/context-in-persistent-composition-archetypes/16562)
> Hi,
Is is possible to add context, ie actual text or other data types, to a persistent composition. The Archetype Editor doesn’t seem to support this. The use case is entries to the Norwegian national summary records, where each entry needs to be given a code (of course using a specific, National code set) about whether this is a new entry, a change to an existing entry, a verification or an refutation. Our hypothesis is to use a specific persistent COMPOSITION archetype for these entries,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Codestrings in archetype editor](https://discourse.openehr.org/t/codestrings-in-archetype-editor/15678)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Runtime name suggestions?](https://discourse.openehr.org/t/runtime-name-suggestions/15601)
> Hi,
We’re trying to finalise the pattern for exclusion archetypes, and would like to use the element names to carry some flavor differences such as “no known history of …” and “no evidence of …”. We’ve considered adding a runtime name constraint to make some level of standardization of these statements, but at the same time we recognize that there will be considerable variation in what will be required as statements in different use cases. So what we’d like to do is to use a kind of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Use of RM:provider](https://discourse.openehr.org/t/use-of-rm-provider/15475)
> Hi everyone,
I’ve got a problem about where to put non-identifying information about the source of information for an ENTRY. The value set we need to store is the code set identified by the OID 2.16.578.1.12.4.1.7498 (Source of information), as following:
1. Result of test/analysis
2. Observed by treating physician
3. Patient’s own information
4. Information from next of kin
5. Obtained from other records
6. Other
7. Reported by responsible clinician
Our first hypothesis was that the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [add terminology-binding to archetype editor](https://discourse.openehr.org/t/add-terminology-binding-to-archetype-editor/15455)
> For my work I need to add a terminology (a local company owned terminology) for the binding section to the archetype-editor, is that possible?
Thanks in advance for reply
Bert
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Seeking views on proposed governance changes.](https://discourse.openehr.org/t/seeking-views-on-proposed-governance-changes/14358)
> We are writing jointly, on behalf of the openEHR Foundation Board of Governors and its elected Management Board, to seek your views on plans we have been developing together, to further support and enhance openEHR as a self-governing and legally and financially accountable community.
We have already given subscribing members an opportunity to review these proposals but are keen to get broader community feedback.
The openEHR Foundation was established in 2002 and operated since then as part...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 56, Issue 3](https://discourse.openehr.org/t/openehr-clinical-digest-vol-56-issue-3/16563)
> Helo Pablo e Heather,
Recently happened the same with me: I'm validating some data in obstetric's archetypes and some informations that were present in some archetypes that I already had downloaded before, were not present in CKM currently. I found out they were "withdrawn".
This fact took our local researchers to ask why they were superseded since that some informations that were present are important and should be maintained in the currently version.
Exemple: in the archetype...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [icons CKM freemind](https://discourse.openehr.org/t/icons-ckm-freemind/15460)
> Does someone know where I can find those beautiful icons which are used in CKM Freemind?
Thanks in advance
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Missing lab test archetypes from CKM](https://discourse.openehr.org/t/missing-lab-test-archetypes-from-ckm/14349)
> I been using these archetypes for some time (created by Ian):
openEHR-EHR-OBSERVATION.lab_test.v1
openEHR-EHR-OBSERVATION.lab_test-blood_glucose.v1
I *believe* those were in the CKM before, but it seems that were removed, the most similar I could find are:
openEHR-EHR-OBSERVATION.laboratory_test.v0
openEHR-EHR-OBSERVATION.pathology_test.v1
openEHR-EHR-OBSERVATION.pathology_test-blood_glucose.v1
If the first two archetypes were on the CKM before and also were overriden by one of the...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [spam measures for openEHR @ Twitter](https://discourse.openehr.org/t/spam-measures-for-openehr-twitter/16555)
> Some will have noticed an increase in spam on the #openehr hashtag that is used to construct the home page twitter feed. The best way to block this is to click through to the posters on Twitter and report them, which is easily done.
You'll see a dialog like this:
If more than one person does this, Twitter should block / remove these accounts.
- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Cloud EHRServer is about to be launched](https://discourse.openehr.org/t/cloud-ehrserver-is-about-to-be-launched/15459)
> Dear friends,
I'm about to launch the Cloud EHRServer, a clinical data repository / health information system backend as a service. I'm very excited about this, since I invested a lot on the EHRServer development and now it seems natural to take this next step to make further development sustainable in time.
This SaaS is based on the EHRServer, the first open source openEHR clinical data repository, I've been developing for the last years. The development and maintenance of the EHRServer...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Exporting from Ocean Template Designer with multiple languages](https://discourse.openehr.org/t/exporting-from-ocean-template-designer-with-multiple-languages/14347)
> Hello,
We are having problems exporting a template in OPT format with multiple languages. Here are the steps to reproduce:
1. Switch your region to English (United Kingdom)
- In Windows 10 it was enough to just set format to English (United Kingdom) under Region -> Formats
2. Start TD and create a new template
3. Add openEHR-EHR-COMPOSITION.encounter.v1 (from ckm) to the template
4. Export to OPT and select additional languages: es, pt-BR
The resulting OPT will have (which are ok):
-...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR developers' workshop at medinfo2017, Xiamen China](https://discourse.openehr.org/t/openehr-developers-workshop-at-medinfo2017-xiamen-china/14348)
> Dear openEHR developers,
We are planing a workshop at the next MEDINFO2017, Xiamen China\.
Would you like to join this workshop?
https://openehr.atlassian.net/wiki/display/resources/The+openEHR+Developers%27+workshop+2017
If you are interested in this workshop\. please feel free to contact me\.
The deadline, Nov 5 is closing and we have to finish until the\.
In addition, we are planning wonderful social events, too\.
Regards,
Shinji Kobayashi
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Could the specs group consider making uid mandatory?](https://discourse.openehr.org/t/could-the-specs-group-consider-making-uid-mandatory/15461)
> Greetings,
Apologies if I missed a discussion about this, but as per [http://www.openehr.org/releases/RM/latest/docs/common/common.html#_unique_node_identification](http://www.openehr.org/releases/RM/latest/docs/common/common.html#_unique_node_identification)
"`LOCATABLE` descendants may have a `*uid*`, containing a GUID"
The optional/recommended nature of uid makes it impossible to implement some features that I have in mind because I can't rely on all implementations to follow the same...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Operational templates, archetype_ref in C_ARCHETYPE_ROOT and node id](https://discourse.openehr.org/t/operational-templates-archetype-ref-in-c-archetype-root-and-node-id/16554)
> A quick question of an implementation detail to which I’m hoping is a simple answer ☺
When we create an Operational Template, we should fill the archetype roots with a copy of the structure of the other archetype\. Then the node id of the C\_ARCHETYPE\_ROOT is set to the id of that archetype\.
This makes it much easier to work with these templates in many cases, since they can be sent to the UI and the UI does not need to retrieve other archetypes to render something and requires much less...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR and terminology servers](https://discourse.openehr.org/t/openehr-and-terminology-servers/15464)
> Dear All,
while thinking about terminology server requirements for openEHR systems
I would like to ask all openEHR implementers about experiences of
different solutions\. Are there any experiences of using openEHR systems
with e\.g\. the FHIR terminology services, CTS2, Ocean TQL, homebrew, etc?
What are the use cases when the terminology servers are used \(e\.g\.
design time, data entry, querying, etc\.\)? What are the "terminological
queries" that are used/needed \(e\.g\....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RM Participations name/role?](https://discourse.openehr.org/t/rm-participations-name-role/15556)
> Hi,
We’re wondering if it’s possible to specify what the role was of each instance of Participation in an OBSERVATION archetype? For instance in a histopathology result the macroscopic description will often be performed by a different person from the microscopic description. We’re thinking both will be listed using participation, but we need to be able to document which person did what.
Kind regards,
**Silje Ljosland Bakke**
Information Architect, RN
Coordinator, National Editorial Board...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question about paths to C_SINGLE_ATTRIBUTE alternatives](https://discourse.openehr.org/t/question-about-paths-to-c-single-attribute-alternatives/15458)
> Hi,
I was chatting with Diego, about the need of nodeIds for ELEMENT.value and I detected some archetypes with alternatives but no nodeIds, I guess, created with the Archetype Editor.
Examples from openEHR-EHR-CLUSTER.timing_daily.v0
...
ELEMENT[at0004] occurrences matches {0..*} matches { -- Specific time
value matches {
DV_TIME matches {*}
DV_INTERVAL matches {
upper matches {
DV_TIME matches {*}
}
lower matches {
DV_TIME matches {*}
}
}
}
}
ELEMENT[at0026] occurrences matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Content of SM. Documentation avalaible](https://discourse.openehr.org/t/content-of-sm-documentation-avalaible/16553)
> Hi All,
I have been Reading the [Service Model Specification](http://www.openehr.org/releases/BASE/latest/docs/architecture_overview/architecture_overview.html#_service_model_sm) and only EHR REST API has a proposal specification (status: v0.1. proposal), isn’t it?.
Have the others(virtual_ehr, terminology, archetype, workflow, demographic) any kind of documentation avalaible or have assigned a team work to design their API’s?
Thanks,
**Javier Solana Huertas**
Software...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [MEDINFO 2017, Xiamen, China](https://discourse.openehr.org/t/medinfo-2017-xiamen-china/15457)
> Dear openEHR mates,
I just started the wiki page for upcoming MEDINFO 2017, Xiamen, China.
[https://openehr.atlassian.net/wiki/display/resources/MEDINFO+2017%2C+Xiamen%2C+China](https://openehr.atlassian.net/wiki/display/resources/MEDINFO+2017%2C+Xiamen%2C+China)
If you are planning to submit / attend MEDINFO2017, please join our activities.
We will make some events happen in MEDINFO as usual.
* Developers...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medications and Parenteral fluids archetypes](https://discourse.openehr.org/t/medications-and-parenteral-fluids-archetypes/16556)
> Hi everyone,
Seeking advice from the broader community regarding an important modelling issue…
At present the Medication Order (INSTRUCTION.medication) archetype is undergoing community review.
The primary author has proposed that the scope include IV and other parenteral fluid administration which is regarded as therapeutic item by many as even fluids such as Normal Saline or Glucose infusions need to be prescribed. This was not clearly represented in the metadata in previous review...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Converting Archetype into Nosql Schemes](https://discourse.openehr.org/t/converting-archetype-into-nosql-schemes/15456)
> Hello,
I am a Phd student, working on the implementation of OpenEhr standard with Nosql technologies in order to study the performances for such plateformes.
And because i have just got familiar with archetypes in the ADL workbench and Ocean informatics, i would like to know is there an automatic way of generating from operational template the adequate sql or nosql tables?
If not should i integrate any other tools or modules in order to do this conversion?
Thanks in advance for your...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [First 'Micro startup' Industry Partner joins openEHR](https://discourse.openehr.org/t/first-micro-startup-industry-partner-joins-openehr/16552)
> The openEHR Management Board is delighted to welcome a new Industry
Partner, Operon Systems Ltd\.
http://openehr.org/industry_partners/operon
Operon are the first Partner to take advantage of our new 'Micro
startup' membership rates which cost only 650 Euro per annum\.
This rate applies only to companies new to the eHealth sector with
less then 3 full\-time equivalent staff working on eHealth projects\. It
is valid for only the first 2 years of membership, then companies...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Christian Chevalley elected to SEC](https://discourse.openehr.org/t/christian-chevalley-elected-to-sec/14342)
> [Christian Chevalley](http://www.openehr.org/programs/specification/editorialcommittee#christian_chevalley), R&D manager at ADOC and the lead developer of the open source [EtherCIS platform](https://github.com/ethercis) based on openEHR has been elected to the openEHR Specifications Editorial Committee (SEC). His term starts on 01 October 2016.
Christian has over 30 years of experience in software design, development, data center architecture and IT security. He has led several developments...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Normal range/reference ranges for text data type](https://discourse.openehr.org/t/normal-range-reference-ranges-for-text-data-type/15463)
> Hi everyone,
We’re working on requirements for labs results, and have bumped into a potential problem. Some results are textual/non-quantitative in nature, for example “positive/negative”, “+/++/+++”, “negative/borderline/positive”. These results also need a kind of “normal range” for the receiving system to be able to mark or emphasise it in the UI. The text data type however doesn’t have any normal range/reference ranges attributes in the reference model like the quantity, count and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype for pain scale (VAS)](https://discourse.openehr.org/t/archetype-for-pain-scale-vas/15462)
> Hi all,
Looking for an archetype for recording VAS scale. Searching suggested that there used to be a CLUSTER.Symptom-pain [Pain symptom] archetype in the international CKM.
I could only find it from the NEHTA CKM but not from the international one. Any thoughts on this?
Thanks,
-Pekka
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Announcement on behalf of the openEHR Foundation Board of Governors](https://discourse.openehr.org/t/announcement-on-behalf-of-the-openehr-foundation-board-of-governors/14341)
> It is a great pleasure to announce that Thomas Beale has accepted to become a Governor of the openEHR Foundation. Thomas has led, and indeed been the driving force in the development of the openEHR specifications - from their earliest days and through many stages of their evolution, based on worldwide implementation experience. His knowledge and commitment will be hugely valued and respected as we continue to work in tandem with the elected Management Board, led by Ian McNicoll and Tomaz...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL form and mind map](https://discourse.openehr.org/t/adl-form-and-mind-map/15447)
> Hello,
I am in the learning process of openEHR as part of my thesis work at Orebro university, Sweden, and I would like to ask quite simple questions which I came across but , couldn’t find any document which deal in the subject.
1) Is there any way to get a mind map view for the archetypes/ templates via one of the modeling tools ? (for ex the ADL)
2) My goal is to model a system via archetype. For ex: a screen which present a patient overview. The screen represent data and does not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [HL7 Specification: Characteristics of a Value Set Definition, Release 1 - open for comments](https://discourse.openehr.org/t/hl7-specification-characteristics-of-a-value-set-definition-release-1-open-for-comments/14340)
> An HL7 specification of the above title is [visible here](http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=189), and open for comments. This is likely to be relevant to our conversations here on terminology + openEHR. I've made some comments as can be seen at that link; others might find it useful to look at the spec draft and possibly comment as well.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How can I model multiple checkboxs options with terminology?](https://discourse.openehr.org/t/how-can-i-model-multiple-checkboxs-options-with-terminology/15450)
> Hi,
Can anyone tell how I can model the example below?
"What parts of the body hurt? [ ] right leg [ ] left leg [ ] head [ ] right arm .."
I know to model a single option (radio-buttom) but I don't know to model a multiple options (checkbox)
The idea is that the options are of the terminology, so I can't model right in the archetype.
I'm using the key-path strategy for data persistence. In the case of the radiobutton leaf is a DV_CODED_TEXT but I don't know when use checkbox.
Note:...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Interval of proportions](https://discourse.openehr.org/t/interval-of-proportions/16551)
> Is interval of proportions a legal data type? If so, which is the correct syntax?
*ELEMENT[at0004] occurrences matches {0..1} matches { -- Proportion of normal daily intake*
*value matches {*
DV_PROPORTION matches {*}
*DV_INTERVAL matches {*
*upper matches {*
DV_PROPORTION matches {*}
*}*
*lower matches {*
DV_PROPORTION matches {*}
*}*
*}*
*}*
*}*
… or …
*ELEMENT[at0004] occurrences matches {0..1} matches { -- Proportion of normal daily...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [More generic reference model](https://discourse.openehr.org/t/more-generic-reference-model/15443)
> Hi,
I am just wondering if there are some opinions about this\.
Do we still need the not so generic reference model which OpenEhr has, with archetypes denoting Observation, Evaluation etc?
Wouldn't a more generic reference model, like ISO13606 be sufficient, when the terminology, worldwide, is moving to SNOMED\-CT?
Because the SNOMED\-concepts already indicate in which hierarchy a data\-item belongs \(clinical finding, procedure, body structure, etc\), and with much more detail then...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issues with OPT exported from the Template Designer: different attribute ordering than the openEHR XSD](https://discourse.openehr.org/t/issues-with-opt-exported-from-the-template-designer-different-attribute-ordering-than-the-openehr-xsd/16549)
> Hi,
I'm working on a small COMPOSITION generation service that will generate valid openEHR instances in XML, providing an OPT.
Playing around with some tests, I detected the Template Designer exports the attributes of the INSTRUCTION in a different order than the specified by the openEHR XSD. The OPT has "activities" before "protocol", and in the XSD those are in the inverse order.
I'm not sure if this is a bug in the TD or if we shouldn't expect the OPT to have the same attribute ordering...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Improved openEHR search](https://discourse.openehr.org/t/improved-openehr-search/15445)
> We've improved the [openEHR search page](http://www.openehr.org/search). It now connects to a better Google search of website + jira + wiki + Github, and also provides links for the search pages of the mailing list web archives.
If you type something into the search box on the top right of any page on the website, you'll end up on this page, with the 'main sites search' box pre-filled.
try it!
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RM ideas to deal better with orders, workflow, panels, order sets](https://discourse.openehr.org/t/rm-ideas-to-deal-better-with-orders-workflow-panels-order-sets/16547)
> A problem the community has been looking at in openEHR for some time is how to deal clearly with order-related meta-data (typically: requestor and receiver ids of various sorts). The topic of 'orderables' has been mentioned in some [recent discussions in CIMI](http://wiki.hl7.org/index.php?title=Proposed_CIMI_Reference_Model), and as a result, some model changes proposed. One is the addition of an 'ENTRY_GROUP' class. A similar idea may be useful in openEHR. The problems it could address...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Do you know of any new openEHR projects?](https://discourse.openehr.org/t/do-you-know-of-any-new-openehr-projects/15449)
> We have updated the [EHR System Components page](http://www.openehr.org/downloads/ehrcomponents) with some of the newer projects we know about. This page doesn't include the commercial products from the [vendor pages ](http://www.openehr.org/industry_partners/index)(maybe it should? Opinions welcome).
Do you know of other projects - open source or other? Do you have more details for the above page?
You can provide information on the lists or by commenting on [this...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RM in OWL](https://discourse.openehr.org/t/rm-in-owl/15451)
> Greetings,
I was wondering if there is any projects out there that provide an OWL version of the RM.
I found this page: [http://trajano.us.es/~isabel/EHR/](http://trajano.us.es/~isabel/EHR/) where an OWL version is kindly provided, though I'll need to get in touch with the author to clarify the terms and conditions of use.
There are papers out there that use an OWL representation of archetypes etc but I could not find any RM representation other than the link above. Any pointers would be...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable?](https://discourse.openehr.org/t/shouldnt-instruction-details-wf-details-be-archetypable/15448)
> Looking at the model, INSTRUCTION_DETAILS.wf_details is an ITEM_STRUCTURE, and that lead me to think that should be archetypable.
Playing around with the archetype editor, it doesn't allow to archetype anything inside INSTRUCTION.instruction_details.
Is this a problem of the AE or that structure is not meant to be archetyped?
If it is not meant to be archetyped, wouldn't that be an issue for querying?
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ISM: initial states for instructions / when do we need actions?](https://discourse.openehr.org/t/ism-initial-states-for-instructions-when-do-we-need-actions/15446)
> Hi all,
This message is related to my previous message "ACTIVITY.description vs ACTION.description archetypes" (didn't got any answers :( but this is focused on when we need actions to change a instruction state, and what's the initial state.
Considering the specs:
[http://www.openehr.org/releases/RM/latest/docs/ehr/ehr.html#_the_standard_instruction_state_machine_ism](http://www.openehr.org/releases/RM/latest/docs/ehr/ehr.html#_the_standard_instruction_state_machine_ism)
I think when an...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ACTIVITY.description vs ACTION.description archetypes](https://discourse.openehr.org/t/activity-description-vs-action-description-archetypes/16550)
> I'm reviewing the current version of the specs and remembered an issue we had in the past about this (check the bold text)
##### 8.2.5.7. Relationship to ArchetypesMuch of the semantics of particular Instructions and Actions derive from archetypes. Currently, archetypes are used to define two groups of Instruction semantics. The first is the descriptions of activities that are defined in Instructions (`ACTIVITY`.`*description*`) and executed in Actions (`ACTION`.`*description*`). **These...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EHRServer v0.7 is out!](https://discourse.openehr.org/t/ehrserver-v0-7-is-out/15670)
> Dear friends,
Just wanted to send a quick message to the lists with exciting news: the openEHR EHRServer v0.7 was released!
Here you can find the code: [https://github.com/ppazos/cabolabs-ehrserver/releases](https://github.com/ppazos/cabolabs-ehrserver/releases)
And here the updated docs: [http://cabolabs.com/en/projects](http://cabolabs.com/en/projects)
If you want to play with it, here is our staging server:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Call for papers to ACI special issue on interoperability and EHR](https://discourse.openehr.org/t/call-for-papers-to-aci-special-issue-on-interoperability-and-ehr/16548)
> Dear openEHRers,
I'd like to give a heads up to the call for papers to the special issue on Interoperability and EHR in Applied Clinical Informatics. Prof. Kerstin Denecke from Bern University of Applied Sciences and I are guest editors and the aim of this special issue is to have informed and balanced papers on the theory and practice of standards to achieve interoperability and to develop EHR systems (that are intraoperable with Grahame's token). **Deadline is 15 January, 2017**.
Link to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specs about ACTIVITY.timing still unclear](https://discourse.openehr.org/t/specs-about-activity-timing-still-unclear/15006)
> Hi,
I was reviewing the latest specs and, compared with 1.0.2 where ACTIVITY.timing usage is not so clear, I think we still need to improve that specific point.
**1. timing description is too focused on medication**
"Many Instructions will have only one Activity, usually describing a medication to be administered and its timing..."
A treatment or procedure instruction can also be repeated, like do physiotherapy 3 times a week, ultrasound application daily for 10 repetitions, etc. (you can...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question about INSTRUCTION.wf_definition modeling](https://discourse.openehr.org/t/question-about-instruction-wf-definition-modeling/14344)
> Hi I'm reviewing the specs and testing the AE to model instructions.
I'm wondering if the wf_definition should be set at design time in the AE or Template Designer, or if it should be set at runtime by an application.
From the 1.0.2 specs: "The entire definition of a workflow is expressed as an optional parsable string, in the wf_definition: DV_PARSABLE attribute of the INSTRUCTION class. Any syntax may currently be used. A workflow syntax is under development by the openEHR Foundation,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issues setting constraints to INSTRUCTIONS in the Archetype Editor](https://discourse.openehr.org/t/issues-setting-constraints-to-instructions-in-the-archetype-editor/15442)
> Hi,
I created an INSTRUCTION archetype, under Definition > Current Activity there is a checkbox "ordered" that seems not to be working since when I check it I see the same on the ADL:
activities cardinality matches {0..*; **unordered**}
This is a question really, since INSTRUCTION.narrative is DV_TEXT, it can also be DV_CODED_TEXT (looking at the specs I couldn't find anything against it). If this is correct, shouldn't the AE provide a feature to set the narrative as coded text?
BTW, I'm...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype OBSERVATION.data.summary](https://discourse.openehr.org/t/archetype-observation-data-summary/16546)
> Hi, I'm trying to archetype the **HISTORY.summary** structure of an OBSERVATION archetype but I can't find that on the archetype editor UI.
I'm using AE 2.2.905 Beta.
Any pointers are welcome.
A thing more related with usability, is that for an OBSERVATION, under the Definition > Data tab, there are the Structure and Events tabs. Adding nodes to the Structure is really adding nodes inside OBS > data > events, but I would expect to do that under the Events tab. On the Events tab I can set...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [INTERVAL_EVENT questions about the correctness of the specs](https://discourse.openehr.org/t/interval-event-questions-about-the-correctness-of-the-specs/14343)
> Hi,
I'm preparing some materials for a course and I was reviewing the HISTORY/EVENT package.
On the INTERVAL_EVENT field descriptions I noted that those might not be 100% correct or clear. Before raising an issue on JIRA I wanted to know what you think.
INTERVAL_EVENT.width: Length of the interval during which the state was true.
- since state can be modeled in two ways, inside the OBSERVATION and inside the EVENT, I think the description should not include the "during which the state was...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [IHE Amsterdam](https://discourse.openehr.org/t/ihe-amsterdam/14338)
> Hi,
Let me tell you some good news\. I am in a hallelujah mode, so beware \.\.\.\.
No, but really
I hear from some people that there was a lot of interest in OpenEHR on IHE Amsterdam\. I was not there myself, although it is very close to my home, the exhibition\-floor\-only tickets were sold out\.
Many people know what OpenEHR is or have heard of it and are interested\. Many people discussing it\. There are companies competing or preparing to compete on the Dutch market in different and in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL Workbench exceptions when opening the audiogram archetype](https://discourse.openehr.org/t/adl-workbench-exceptions-when-opening-the-audiogram-archetype/14334)
> Hi,
I downloaded the ADLWB Windows (32-bit) 2.0.6.2844 from [http://www.openehr.org/downloads/ADLworkbench/home](http://www.openehr.org/downloads/ADLworkbench/home)
And downloaded the audiogram result archetype from here: [http://ckm.openehr.org/ckm/#showArchetype_1013.1.44](http://ckm.openehr.org/ckm/#showArchetype_1013.1.44)
That archetype has some validity warnings and I wanted to see those warnings using the ADLWB, but when I tried to open the archetype, the ADLWB...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL validity rules on CKM](https://discourse.openehr.org/t/adl-validity-rules-on-ckm/15433)
> Hi all,
I'm making a small summary of all the ADL validity rules, taking the ADL 1.4 (1.0.2) spec as my source: [http://openehr.org/releases/1.0.2/architecture/am/adl.pdf](http://openehr.org/releases/1.0.2/architecture/am/adl.pdf)
On the CKM I opened the Audiogram Result archetype that has some validity problems and the rules are: ICARM, VUI and WLIC.
The problem is I can't find where those rules are defined. Are those only defined in the CKM or is there an spec of those (maybe a newer...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [HL7 and negation](https://discourse.openehr.org/t/hl7-and-negation/15438)
> Dear Colleagues,
HL7 is thinking about the problem of negation.
[http://wiki.hl7.org/index.php?title=Negation_Requirements](http://wiki.hl7.org/index.php?title=Negation_Requirements)
The group discussing it created a document with negation use cases.
My questions are:
- Can you let us know your reaction to this list of use cases?
And
- How should ‘negation’ be handled the best in respect of semantic interpretability?
My personal opinions:
- the boolean should not be used
- try to translate...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Personal Health Record using CHBase (related to Health Vault)](https://discourse.openehr.org/t/personal-health-record-using-chbase-related-to-health-vault/14339)
> Hi!
The Swedish Government is financing and handing out a Personal Health Record service/platform to the Swedes. Now developers can find info about it at [http://developer.halsaformig.se/](http://developer.halsaformig.se/)
It seems to be based on CHBase [http://www.getrealhealth.com/chbase/](http://www.getrealhealth.com/chbase/) that uses many of the API features equal or similar to Microsoft Health Vault.
The health-related PHR models are fairly simple (not many datapoints/details) and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new FAQ page - context in openEHR](https://discourse.openehr.org/t/new-faq-page-context-in-openehr/16545)
> in response to some questions in CIMI, I created a new FAQ page - [Context and attribution in openEHR](https://openehr.atlassian.net/wiki/display/resources/Context+and+attribution+in+openEHR).
Feel free to add and improve.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 51, Issue 26](https://discourse.openehr.org/t/openehr-technical-digest-vol-51-issue-26/16543)
> It does include VERY much more than mg or number of tablets. I.a units like in insulin, drops like in a piper, percentage of working substances in herbs and MANY more.
Unfortunately you have to study it yourself 😩
Met vriendelijke groet / With kind regards,
dr. William T.F. Goossen
directeur Results 4 Care B.V.
De Stinse 15
3823 VM Amersfoort
the Netherlands
telefoon +31654614458
e-mail: wgoossen@results4care.nl
DCMHelpdesk@results4care.eu
skype: williamgoossenmobiel
kamer van...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 51, Issue 24](https://discourse.openehr.org/t/openehr-technical-digest-vol-51-issue-24/13798)
> Dear All,
The international pharmacy stakeholers, in particular EMA, FDA, Canada, Japan, Australia have decided that All medicines units shall be expressed in UCUM according ISO IDMP, in particular
EN ISO 11240, Health informatics — Identification of medicinal products — Data elements and structures for the unique identification and exchange of units of measurement.
Even if you would use some Snomed for this internal in a system you will need to map e.g. for decision support that are...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New curated resource on openEHR publications and more](https://discourse.openehr.org/t/new-curated-resource-on-openehr-publications-and-more/16544)
> Dear openEHRers,
[Zotero](https://www.zotero.org/) is a great freely available reference manager tool and we have set up a [group repository for openEHR](https://www.zotero.org/groups/openehr/items/order/dateModified/sort/desc) related publications and other related material (e.g. presentations, blogs, videos and more!). Intended primarily for researchers I think you can all find useful information as the content is very diverse. From the openEHR website we have provided links to the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 51, Issue 17](https://discourse.openehr.org/t/openehr-technical-digest-vol-51-issue-17/16542)
> Dear Grahame, I guess you mean the HL7 v3 approach: human readable and computable codes \+ unit that FHIR correctly adopted?✅
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [UCUM code in body temperature archetype](https://discourse.openehr.org/t/ucum-code-in-body-temperature-archetype/15439)
> Dear All,
it seems the UCUM code for the temperature units in the Body temperature archetype is wrong. It uses the UCUM print symbol, e.g. "°C", rather than the UCUM code "Cel".
[http://www.openehr.org/ckm/#showArchetype_1013.1.49](http://www.openehr.org/ckm/#showArchetype_1013.1.49)
Regards,
Daniel
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archie version 0.1.0 released](https://discourse.openehr.org/t/archie-version-0-1-0-released/15436)
> A few months ago I announced the development of an open source Java openEHR library called Archie\. It has progressed enough that I’m now pleased to announced the release of version 0\.1\.0 of Archie\. It supports the latest ADL 2 and reference model versions and is licensed under the Apache license\.
The documentation and source can be found at https://github.com/nedap/archie. It’s available at Maven Central at com\.nedap\.healthcare:archie:0\.1\.0 \.
Why another library?
The existing...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Interested in participating in a clinical modelling workshop?](https://discourse.openehr.org/t/interested-in-participating-in-a-clinical-modelling-workshop/14345)
> Hi everyone,
I am keen to gauge if there is interest in the openEHR community for running a clinical modelling workshop in the rough geographical and timing proximity as the MIE 2016/HEC 2016 conference - Munich, 28 August-2 September.
Please respond directly to me, especially with your preferred dates, and I will aggregate responses and see if it will be viable.
A typical 2 day seminar/workshop package would consist of:
**Day 1 – Seminar, 9-5:** Attendees can attend only this day if they...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [v0 archetypes in production](https://discourse.openehr.org/t/v0-archetypes-in-production/14337)
> Hi Implementers,
I have a question regarding the use of v0 archetypes in production systems. The Ocean OPT validator implements the archetype ID scheme where v0 is not a valid archetype ID. I think this was changed recently, in ADL2.0 I think? We deliberately did this to ensure we were not using draft archetypes in production systems. We are now looking at using some of the latest draft archetypes in a couple of projects and need to make a decision on how to proceed.
Do others allow v0...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Terminology bindings in openEHR](https://discourse.openehr.org/t/terminology-bindings-in-openehr/15431)
> Hi,
Can I get some insight into how terminology bindings work in openEHR, or how they are supposed to work?
It appears openEHR supports multiple terminologies, in addition to its own internal coding structure (atxxxx). I think there’s a whole terminology service dedicated to this. But my confusion is how to implement the feature.
In the Ocean Template designer as well as the Archetype editor, there are features that allow us specify what terminology we want to use and to ‘manually’ input...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SNOMED](https://discourse.openehr.org/t/snomed/15435)
> Hi,
I got an idea when reading the nice story from Heather on LinkedIn\. In fact it is hers idea, but in a opposing way\.
https://www.linkedin.com/pulse/journey-interoperability-part-i-heather-leslie
https://www.linkedin.com/pulse/journey-interoperability-part-ii-heather-leslie
I wonder in how far it is feasible and useful to create archetypes from SNOMED concepts, it would be possible to generate them, with attributes and so on\.
In a few hours time, one would have a complete forest with...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL Workbench 64 bit build available](https://discourse.openehr.org/t/adl-workbench-64-bit-build-available/14336)
> For those who use the ADL Workbench, there is a new [64-bit Windows build available](http://www.openehr.org/downloads/ADLworkbench/home). See top entry in 'Latest Builds'. This also fixes a number of bugs. A proper release will be posted shortly.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ordinal values without descriptions](https://discourse.openehr.org/t/ordinal-values-without-descriptions/15522)
> Hi everyone,
We’re working on an archetype for the Montgomery-Åsberg Depression Rating Scale (MADRS). This scale contains several ordinal values where there is no description, and some where there is no text at all. This doesn’t work very well in archetypes, and particularly when uploading to a CKM, because there’s an expectation that every field should be filled in, and the CKM will replace empty fields with * or sometimes *([language code]). Is there any way to get around this?
See here...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Secure EPD](https://discourse.openehr.org/t/secure-epd/16541)
> Hi,
I don't know if it is interesting for this forum, and if medical information designers should be busy with this, but since, f\.e\. FHIR is involved in incorporating technical layers, like REST and authorization and authentication, in an information standard, I think there is to come some connection between security and information\-design\.
In my idea, this is not a desirable direction, but it looks like we are going that way\.
"\[Medical devices\] are all running Windows XP...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Upgraded openEHR website](https://discourse.openehr.org/t/upgraded-openehr-website/14335)
> The [openEHR website](http://www.openehr.org/) has been upgraded to do a number of new things:
- fluid layout that works down to about 8" tablet size (try it on your screen), although it is not yet optimised all the way down to mobile phone size.
- new carousel style
- new overall colour scheme using muted colours (the prevailing style these days)
- various other home-page layout improvements
- re-built News & Events display that puts news into a single stream with (clickable) icons...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR Ambassador, China](https://discourse.openehr.org/t/new-openehr-ambassador-china/14326)
> The openEHR Foundation is delighted to announce the appointment of Prof. Huilong Duan as openEHR Ambassador to China.
Prof. Duan is former Dean, Professor of College of Biomedical Engineering & Instrument Science of Zhejiang University. He is a Member of Subject Assessing Group of Academic Degree Committee affiliated with State Council, Executive Director of Chinese Society of Biomedical Engineering, Vice President of Chinese Digital Medicine and Medical Information Professional Committee,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Activity based workflow - request for literature & resources](https://discourse.openehr.org/t/activity-based-workflow-request-for-literature-resources/14898)
> As part of the Activity-based Design (ABD) workflow project on which I am engaged in at Intermountain Health, I agreed to do a literature search on the topic. Since I believe this is of general interest to us in openEHR, I'm making it an open question. Note that the design work of the ABD group will eventually be published open source.
I am particularly interested in formalisms, frameworks and experience with any kind of 'adaptive' or 'cooperative' workflow system, also analytical...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Templates and archetype patterns for PVC usage, emergency wards etc?](https://discourse.openehr.org/t/templates-and-archetype-patterns-for-pvc-usage-emergency-wards-etc/13734)
> Hi!
Does anybody want to share templates or other documented patterns on how to set up recording of some things useful in emergency wards etc? Some examples:
1. [Peripheral venous catheter](https://en.wikipedia.org/wiki/Peripheral_venous_catheter) (pvc) usage (ordering of insertation, insertation, removal) etc?
From reading archetype metadata in the openEHR CKM one can guess that one way is to use the very general openEHR-EHR-INSTRUCTION.request-procedure combined with...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EC EXPERT PANEL ON EFFECTIVE WAYS OF INVESTING IN HEALTH - Disruptive innovation - openEHR comments](https://discourse.openehr.org/t/ec-expert-panel-on-effective-ways-of-investing-in-health-disruptive-innovation-openehr-comments/16537)
> In November 2015, there was an [EC RFI on their draft document on 'disruptive innovation'](http://ec.europa.eu/health/expert_panel/consultations/disruptive_innovation_en.htm) put out, to which openEHR put together a response.
The [new document](http://ec.europa.eu/health/expert_panel/opinions/docs/012_disruptive_innovation_en.pdf) and also the [responses list](http://ec.europa.eu/health/expert_panel/consultations/docs/2016_results_disruptive_innovation_en.pdf) are now published. The openEHR...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM C_STRING - single regex, or a list of strings?](https://discourse.openehr.org/t/aom-c-string-single-regex-or-a-list-of-strings/15430)
> This is a question we have wrestled with in defining the [AOM String constrainer type C_STRING](http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_overview_3). Bert has brought it up with some useful analysis in this issue. I would be interested in other opinions on this question so that we can decide the best form for the C_STRING constraint.
- thomas
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Overview of all (defacto) standards in Health-ICT](https://discourse.openehr.org/t/overview-of-all-defacto-standards-in-health-ict/16539)
> The Dutch government Health\-ICT organization Nictiz, has a website with 112 health related standards\. It has figures of usage, classifications and links, and some intelligence in selecting subsets\. \(in Dutch\)
They did not have OpenEHR and HISA mentioned, but after me informing them yesterday evening, they are going to add them\. This because OpenEHR is commercially implemented in the Netherlands by Code24 and some others, and HISA is a CEN standard\. So both are important to have on...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Approaches to Learning openEHR](https://discourse.openehr.org/t/approaches-to-learning-openehr/15434)
> Hi!
Several years ago some of you in the openEHR community helped us answer questions about learning openEHR. Thank you very much!
For a number of reasons, a proper publication of the results was delayed, sorry about that. On Thursday I'll present our paper "**Approaches to Learning openEHR: a Qualitative Survey, Observations, and Suggestions**" at [http://www.shi2016.org/program.html](http://www.shi2016.org/program.html) Some of you will recognize your own answers :-)
The full paper is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Composition commit and change types](https://discourse.openehr.org/t/composition-commit-and-change-types/15432)
> Hi all, I'm testing some cases in the EHRServer and I want to confirn some grey areas.
If the EHR receives a commit of a persistent composition and the change type is creation, should the EHR create a new composition?
i.e. I don't see an EHR having two different medication lists, is that possible?
I guess persistent compos can only be created one time per archetype (one medication list, one problem list, one vaccination list, etc. per patient), and after the creation, all commits should be...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Medication order archetype review - we need your help!!](https://discourse.openehr.org/t/medication-order-archetype-review-we-need-your-help/16535)
> Hi,
We have had a great response already to the first review round of the
Medication order archetype but would like to extend the review for a
bit longer to get more feedback, given its importance\.
We are particularly interested in those who have already, or might
need to, implement a medication archetype as part of a clinical
system, or as part of national standards development\.
We have been working closely with implementers who are experienced in
this field but the more input we can...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Exclusion of observations/tests/scoring](https://discourse.openehr.org/t/exclusion-of-observations-tests-scoring/16536)
> Hi everyone,
A recent requirement is to be able to record that a specific observation/test/score was not performed and why. The case example is the Children’s Global Assessment Scale (CGAS), which is part of the WHO Multiaxial classification of child and adolescent psychiatric disorders. In the Norwegian context, there’s an added requirement to be able to record that the CGAS scoring was not performed, with two different codes for the reason why.
For now, our hypothesis is that this should...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [RFC:Therapeutic precautions archetype](https://discourse.openehr.org/t/rfc-therapeutic-precautions-archetype/15663)
> Hi everyone,
Based on requirements from the Norwegian National Summary Care Record (Norwegian: “Kjernejournal”), and Heather’s email about therapeutic precautions ([https://omowizard.wordpress.com/2014/07/16/therapeutic-precautions-are-the-new-black/](https://omowizard.wordpress.com/2014/07/16/therapeutic-precautions-are-the-new-black/)), we’ve made an archetype to represent the concept “Therapeutic precaution” in the EHR.
At the moment the archetype is sitting as a proposal in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Adressing of i.e. discharge summaries](https://discourse.openehr.org/t/adressing-of-i-e-discharge-summaries/15437)
> There is a lot of compositions that is created for the purpose of sending the content to another healthcare provider. Discharge summaries is one example.
For instruction health care service request there is some elements and slots added to the protocol part. Here you can add both the requestor and the identifier.
In the Nehta CKM there is a composition archetype for referral. This archetype has some structure under context to add participation and identification of the requestor. I think...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [rm_type_name for the DV_DURATIONs primitive object in XML](https://discourse.openehr.org/t/rm-type-name-for-the-dv-durations-primitive-object-in-xml/15423)
> Dear all,
There are a differences in how the Template Designer and how CKM construct the XML for a DV_Duration:
Take this snippet (from [http://openehr.org/ckm/#showArchetype_1013.1.123_XML](http://openehr.org/ckm/#showArchetype_1013.1.123_XML) )
Hi everyone!
As some of you may have noticed, a paper called “Evaluating Model-Driven Development for large-scale EHRs through the openEHR approach” ([http://www.sciencedirect.com/science/article/pii/S1386505616300247](http://www.sciencedirect.com/science/article/pii/S1386505616300247)) was recently published by a PhD student at the University of Tromsø. The paper has some pretty direct criticism of the ideal of wide clinical engagement in widely reusable information models, as well as the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-Based PhD Thesis Successfully Defended](https://discourse.openehr.org/t/openehr-based-phd-thesis-successfully-defended/15425)
> Dear all,
Following Diego’s email, I would like to also announce my successfully defended PhD thesis (on the 12th of February 2016): [https://openarchive.ki.se/xmlui/handle/10616/44956](https://openarchive.ki.se/xmlui/handle/10616/44956)
This thesis explores ways of how openEHR can come into evidence-based practice via clinical practice guidelines. It covers the following in essence, amongst some other things:
- It proposes a method for representing guidelines based on...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Any work on PHR?](https://discourse.openehr.org/t/any-work-on-phr/16533)
> Hi, are you aware of any openEHR based personal health record project?
The aim would be to capture wellness type of information integrated with recent wearable/smart phone based sensor data.
Preferably open source.
Cheers,
-koray
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GDL rules with "age-dependent" reference ranges](https://discourse.openehr.org/t/gdl-rules-with-age-dependent-reference-ranges/16531)
> Hi there,
besides of our core acitivities, we recently fiddled a little with GDL to evaluate, if it might be of use for a decision support project in the context of a pediatric ICU. One challenge with guidelines in pediatric patients is that the reference ranges of variables depent on the age of a patient at the time of the clinical event.
In SPARQL/SWRL (as in XML) I can easily calculate the number of days between the birth of a patient and the clinical event by simply subtract the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Template Designer alternatives](https://discourse.openehr.org/t/template-designer-alternatives/15424)
> HI all,
I tried the latest release of the TD and keeps having some constraints on modelling, like the impossibility of specifying that a DV_TEXT will be used as DV_CODED_TEXT on the data type option, or removing (0..0) slots that will not be used on the final OPT.
I'm wondering if are there any template designer alternatives to create operational templates, that allows to set DV_TEXTs as DV_CODED_TEXT only or setting the 0..0 occurrence to SLOT nodes.
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Seeking expertise on addiction medicine...](https://discourse.openehr.org/t/seeking-expertise-on-addiction-medicine/15427)
> Hi everyone,
The CKM Editorial teams in Norway and the international openEHR CKM are seeking expertise for development of our tobacco, drug and alcohol archetypes – all of which follow a similar pattern around addition and its management.
The tobacco archetype in particular is causing some difficulty in cracking the best pattern – the multitude of ways that this data is represented in current systems is compounded by the multitude of different forms of tobacco use (non-smoking and smoking)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Usage of Compositoin.Category](https://discourse.openehr.org/t/usage-of-compositoin-category/15422)
> We are discussing the use of Composition.Category which is a DV_CODED_TEXT.
There is a terminology:
Is it required to use only these categories or could an application set any DV_CODED_TEXT?
I think it would be ok to allow any category in this.
To be concrete:
The use-case is discharge summaries. These are Compositions which only (“mostly”) contains links to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Strange use of 'offset' as a settable RM attribute](https://discourse.openehr.org/t/strange-use-of-offset-as-a-settable-rm-attribute/15426)
> Hi,
We noted it is possible to set values from AE/TD to a RM attribute named “offset”
In the [specs](http://www.openehr.org/releases/RM/Release-1.0.3/docs/data_structures/data_structures.html#_event_class) (looked at >1.0.1) it is not a regular attribute but a function which returns a computed value using diff HISTORY.origin and EVENT.time
Note that this diff can also be a negative value – which doesn’t seem to be supported by AE/TD or in instance data
An example ADL:
POINT_EVENT[at0002]...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Architectural choices: One composition archetype per document type, or not?](https://discourse.openehr.org/t/architectural-choices-one-composition-archetype-per-document-type-or-not/15336)
> When implementing an openEHR based system for a large hospital, there will be hundreds if not thousands of document types. Examples of these are admission notes for different departments and specialties, outpatient notes, nursing documentation, check lists, discharge summaries, etc ad infinitum. Each of these could either have its own COMPOSITION archetype, or they could reuse generic compositions but have a separate template for each document type.
What’s the smart architectural choice to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Procedure archetype for operative notes](https://discourse.openehr.org/t/procedure-archetype-for-operative-notes/15421)
> Hi everyone,
We’re trying to model an operative note document - therefore we used the procedure archetype openEHR-EHR-ACTION.procedure.v1 and specialised it by adding other archetypes into the procedure details slot. Within the description of the procedure archetype it says
'Additional structured and detailed information about the procedure can be captured using purpose-specific archetypes inserted into the 'Procedure detail' slot'
but
'this archetype will be used to record only what was...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [A report of openEHR events in Japan](https://discourse.openehr.org/t/a-report-of-openehr-events-in-japan/15428)
> Hi all,
We, openEHR Japan had two events in the last January\.
I wrote a report of the events of them, and please take a look at this\.
http://openehr.jp/documents/8
We appreciate the participants and kind supports from Drs Hugh and
Heather Leslie from Australia, Dr Lu from China, localisation team,
management board, and all the openEHR coleagues\.
Shinji KOBAYASHI
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EHR Archetype for Recording a patient's death](https://discourse.openehr.org/t/ehr-archetype-for-recording-a-patients-death/15415)
> Hi there,
In our operative note document we have a data element to record the decease of a patient during a surgical operation. At our first try, we modelled "time of death" as a single Element to make it fit into a particulare section on the document. However, it feels wrong as I think that the death of a patient is a concept on its own that will be reused in many scenarios and that might need further data elements. In the CKM, there is only the death data archetype (which is a CLUSTER in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updated XSLT](https://discourse.openehr.org/t/updated-xslt/16534)
> Hi,
I'm using the XSLT [openEHR_RMtoHTML.xsl](https://openehr.atlassian.net/wiki/download/attachments/6553643/openEHR_RMtoHTML.xsl?version=1&modificationDate=1227230463000&api=v2) (found here [https://openehr.atlassian.net/wiki/display/dev/openEHR+Composition+XML+to+HTML?focusedCommentId=32014341#comment-32014341](https://openehr.atlassian.net/wiki/display/dev/openEHR+Composition+XML+to+HTML?focusedCommentId=32014341#comment-32014341)) to format XML compositions into HTML in the EHRServer...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Representing microseconds in DateTime](https://discourse.openehr.org/t/representing-microseconds-in-datetime/15418)
> Hi,
I have a requirement to capture timeseries data which happens at 250 microseconds – that is 0.000250 seconds.
While many programming languages, and the ISO8601 spec, supports this [openEHR RM](http://www.openehr.org/releases/RM/latest/docs/support/support.html#_iso8601_time_class) seems to be constrained to milliseconds:
hh:mm:ss[,sss][Z | ±hh[mm]]
Any particular reason we dump microseconds? If not can we add this capability – I think it won’t break any existing code (I...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer whitepaper](https://discourse.openehr.org/t/ehrserver-whitepaper/16532)
> Dear friends,
I'm writing a small white paper about the EHRServer, and wanted to share the v0.1 with you first. Please let me know what you think, and if you find any errors, please let me know where.
[https://drive.google.com/file/d/0B27lX-sxkymfbHNhZEN5RTlvUnc/view?usp=sharing](https://drive.google.com/file/d/0B27lX-sxkymfbHNhZEN5RTlvUnc/view?usp=sharing)
Thanks!
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records](https://discourse.openehr.org/t/phd-thesis-online-detailed-clinical-models-and-their-relation-with-electronic-health-records/15417)
> Hello all,
My thesis "Detailed clinical models and their relation with Electronic
Health Records" is now available online\. Until the university
publishes it on the public repository, here is a link to it\.
https://www.dropbox.com/s/rqmmh9b541u7wpr/TesisDiego_v2.pdf?dl=0
The slides are also available just in case anyone wants a quick summary
http://www.slideshare.net/yampeku/detailed-clinical-models-and-their-relation-with-electronic-health-records
I also attach the abstract...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype relational mapping - a practical openEHR persistence solution](https://discourse.openehr.org/t/archetype-relational-mapping-a-practical-openehr-persistence-solution/15411)
> Interesting paper from China
[http://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-015-0212-0](http://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-015-0212-0)
Ian
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [concept maps (Cmaps) for archetyping?](https://discourse.openehr.org/t/concept-maps-cmaps-for-archetyping/15414)
> this group of researchers appears to have created an approach to modelling health information using something a bit more powerful than mindmaps\. They seem to know about CDA but not openEHR\.
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3833511/pdf/gahmj.2012.1.4.003.pdf
\- thomas
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [two level modeling](https://discourse.openehr.org/t/two-level-modeling/15660)
> Just an idea, about concept and marketing\.
Years ago \(in 2011\), I created the Dutch OpenEHR lemma in Wikipedia\.
It was quite difficult, the struggle to get it published, the Dutch wikipedia\-organization found it too specialistic and to hard to understand for many people\.
It costed me some effort to get it published, and I made some drawings, that...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New EHRServer v0.5 and roadmap](https://discourse.openehr.org/t/new-ehrserver-v0-5-and-roadmap/15412)
> Hi all!
I'm very excited to share the good news with all my openEHR friends here.
We have released EHRServer v0.5! This version is what we could call "feature complete", so it includes all the minimum features of a real openEHR server, the latest ones related to securing the API, and before that, supporting multi-tenancy.
I'll release user documentation and a full REST API documentation in the next couple of days, and will record a demo in English on YouTube via Hangout. I made a demo in...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Specifications Committee meeting Feb 2016 - have your say](https://discourse.openehr.org/t/specifications-committee-meeting-feb-2016-have-your-say/16528)
> There will be a SEC ([Specifications Editorial Committee](http://www.openehr.org/programs/specification/editorialcommittee)) face to face meeting in Stockholm 11 and 12 February. This will do its usual work of considering next releases, processing Problem Reports (PRs), Change Requests, and anything else to do with the openEHR specifications (e.g. documentation, publishing, UML etc).
If you have raised issues (PRs) about specific problems in specifications, they will be dealt with, but you...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Trial of openEHR's own 'stackExchange' on the openEHR wiki](https://discourse.openehr.org/t/trial-of-openehrs-own-stackexchange-on-the-openehr-wiki/15310)
> one of the features we don't use on the wiki is 'Questions', which you can [see here](https://openehr.atlassian.net/wiki/questions).
This supposedly is the same kind of function as StackExchange, which we didn't get off the ground. So maybe we should try locally.
My proposal would be for some community members to raise a question or two at the above link and see what the experience is like for creating answers, upvoting etc. We might find it is good enough.
For reference, here is the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Alive vs Dead](https://discourse.openehr.org/t/alive-vs-dead/15416)
> Hi everyone,
Seeking some advice please.
In the context of a data registry or research database to record if a person is alive or dead. Maybe there might be an alternative value of ‘unsure’ or ‘indeterminate’ as well, I guess.
I’m wondering if there is any naming convention for this data element – I’ve come across ‘Alive status’ and ‘Vital status’ by googling and researching all the places I can think of. Surprisingly there seems very little available on the topic. SNOMED CT has alive and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CAMSS assessment of openEHR](https://discourse.openehr.org/t/camss-assessment-of-openehr/15296)
> Hi guys,
As part of a standards assessment project initiated by the Norwegian Directorate of Health, several health IT standards will be assessed using CAMSS ([https://joinup.ec.europa.eu/node/66790](https://joinup.ec.europa.eu/node/66790)). Have anyone done a CAMSS assessment of the openEHR specifications? If so, would it be possible to share the results?
Kind regards,
**Silje Ljosland Bakke**
Information Architect, RN
Coordinator, National Editorial Board for Archetypes
National ICT...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [some differences between specs and implementation](https://discourse.openehr.org/t/some-differences-between-specs-and-implementation/14333)
> Hi Thomas and others,
Happy Christmas, of course, but maybe, just like for me, workaholics, taking some time to work a bit in Christmas-day?
I am looking at the specs at [http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_validity_rules](http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_validity_rules)
And I see the error:
**VARID**: archetype identifier validity. The archetype must have an identifier that conforms to the openEHR specification for archetype...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Making FHIR work for everybody](https://discourse.openehr.org/t/making-fhir-work-for-everybody/16530)
> Here is a [blog post on a proposal for making FHIR work more easily with other health information architectures](http://wolandscat.net/2015/12/20/making-fhir-work-for-everybody/), including openEHR, which may interest some people here.
- thomas
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medication Order archetype review open](https://discourse.openehr.org/t/medication-order-archetype-review-open/16529)
> Dear colleagues,
Just a quick heads up to let you know that the first review round for the new Medication order has just commenced, the first of the whole family of medication related archetypes.
If you would like to participate:
1. please register on CKM – [www.openEHR.org/ckm](http://www.openEHR.org/ckm); and then
2. ‘adopt’ the archetype to let the Editors know that you want to be included - https://openehr.atlassian.net/wiki/display/healthmod/Adopt+an+archetype.
Due to the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specialization depth](https://discourse.openehr.org/t/specialization-depth/15413)
> Hi all,
I am looking at this error message from [http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_validity_rules](http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_validity_rules)
**VARCN**: archetype concept validity. The `*node_id*` of the root object of the archetype must be of the form `id1{.1}*`, where the number of `.1` components equals the specalisation depth, and must be defined in the terminology.
*(which has a spelling-error in "specalisation", it...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [RM Release 1.0.3 is published](https://discourse.openehr.org/t/rm-release-1-0-3-is-published/16525)
> Release 1.0.3 of the Reference Model (RM), and what we now call the 'Base' specifications (BASE) is now online. The latter contains the Architecture Overview and other generic specifications.
You can find the links from the home page Specifications button as usual, and you will see a new jump page:
The main part of the page contains links to the latest development state of each component (RM, AM, etc).
Release-1.0.3 has taken a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 46, Issue 1](https://discourse.openehr.org/t/openehr-technical-digest-vol-46-issue-1/16527)
> We'll check some out in ICE tomorrow and see what it's doing with them, then go from there\.
It might be smart enough to know to get rid of those, some systems don't mind them\.
Dave Culley
Integration Specialist
West Suffolk NHS Foundation Trust, Hardwick Lane, Bury St Edmunds, IP33 2QZ
Tel: 01284\-712594 |Mobile: 07588 505 206 \(Wednesdays and Fridays\) | E\-mail: dave\.culley@wsh\.nhs\.uk
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [errorhandling in AOM/ADLParser](https://discourse.openehr.org/t/errorhandling-in-aom-adlparser/16524)
> I implemented errorhandling and two errors for testing.
To let it work in my code, this must be added to ADL.g4
```
....
....
grammar Adl;
@parser::header{
import nl.rosa.archetype.errorhandling.ADLParserErrorMessages;
}
//
// ============== Parser rules ==============
//
ad.....
.....
.....
```
The error-handling itself is in the grammar. I needed to change the grammar a little bit:
```
metaDataItem:
metaDataTagAdlVersion '=' adlVersion
> metaDataTagUid '=' GUID
>...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [OpenEHR Grammar CamelCase converter](https://discourse.openehr.org/t/openehr-grammar-camelcase-converter/14324)
> You need the antlr grammars and generated classes to use this class\.
You can also use directly the Adl\.g4 to generate camelCase grammar\-classes for your archetype
The converted openehr\-grammar is here:
https://github.com/BertVerhees/adl-aom/blob/master/src/main/grammar/nl/rosa/archetype/Adl.g4
convert the openEHR\-grammar with is here:
https://github.com/BertVerhees/adl-aom/blob/master/src/main/java/nl/rosa/archetype/util/GrammarToCamelCaseConvertor.java
Bert
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL AOM](https://discourse.openehr.org/t/adl-aom/16526)
> Hi,
I am trying to generate an AOM from a grammar, I used a some open\-sourced of stuff from Pieter Bos and Thomas Beale\.
I modified the grammar, f\.e\. to let it generate camelCase, and I need to do more with the grammar, still studying it\.\.
I do it just for fun, that is all\.
I wanted you to know, so that there are no future misunderstandings
https://github.com/BertVerhees/adl-aom
best regards
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.4 specification - now in Asciidoctor format](https://discourse.openehr.org/t/adl-1-4-specification-now-in-asciidoctor-format/16521)
> The old [ADL 1.4 spec is now online](http://www.openehr.org/releases/AM/latest/ADL1.4.html) in the new format. This was done primarily to:
- fix various formatting
- fix syntax rendering
- provide a source form of the ADL 1.4 spec in case interim releases between 1.4 and 2.0 are required.
- thomas
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer v0.4 released](https://discourse.openehr.org/t/ehrserver-v0-4-released/15403)
> Dear friends, we have released the new version of the EHRServer [https://github.com/ppazos/cabolabs-ehrserver](https://github.com/ppazos/cabolabs-ehrserver)
I'll update the docs soon and deploy the new version on our staging server for anyone who wants to test it.
Feedback is very welcome!
Cheers,
Pablo.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer](https://discourse.openehr.org/t/missing-support-for-ism-transition-transition-in-archetype-editor-and-template-designer/15400)
> Hi
We are currently working on an implementation of some process support. We are in general using archetypes for our modelling and we have found Instruction/Action to be well suited for our current need. Actions will tell the current state of each activity and based on this state new steps will be available. We intend to present this to our user so that only the steps currently available will be presented in the user interface. This can be inferred by our software from the generic ISM and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Party-actor-folder relationships in hierarchy](https://discourse.openehr.org/t/party-actor-folder-relationships-in-hierarchy/15399)
> Hi, I have a lot of practical questions to ask :\)
Let's imagine that I have an EHR database which is shared by several organizations, and each organization manages one or more EHR systems, and each EHR system manages it's own hierarchy of folders\. Something like that:
\- Database
\[C\] ACME company \(1\.1\.1\.1\)
\[S\] EHR System 1 \(1\.1\.1\.1\.1\)
\- Root folder 1
\-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR RM Release-1.0.3 - EHR Extract - SURVEY OF USE](https://discourse.openehr.org/t/openehr-rm-release-1-0-3-ehr-extract-survey-of-use/16519)
> **If your organisation or implementation uses the openEHR EHR Extract specification PLEASE READ THIS.**
Release-1.0.3 is getting close. For those with too much time on their hands, you can follow progress [here on Jira](https://openehr.atlassian.net/projects/SPECRM/versions/10860).
We have implemented a subset of Change Requests on the **EHR Extract specification** ([old Rel-1.0.2 PDF](http://www.openehr.org/releases/1.0.2/architecture/rm/ehr_extract_im.pdf); [new-style latest draft...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Adverse reaction archetype... just published](https://discourse.openehr.org/t/adverse-reaction-archetype-just-published/15406)
> Hi everyone,
Just a quick note to let you know that the Adverse Reaction archetype has been published.
The evolution of the archetype from its first iteration uploaded in July 2008 and first ever review in July 2009 through to today has been fragmented and a bit ‘staccato’ with review contributions coming from the openEHR, NEHTA and Nasjonal IKT CKMs at various times through the process, culminating in publication in the international openEHR CKM. I expect that Norway is likely to follow...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Development based on xml-schemas](https://discourse.openehr.org/t/development-based-on-xml-schemas/16523)
> ```
Hi everyone,
```
```
I'm a researcher of medical systems for ultrasound at company Figlabs in Brazil. I've some difficulties to implement the archetypes/templates into a classes (Python Language).I'm using xml and xsd files and the reference of xsd ([http://schemas.openehr.org/v1](http://schemas.openehr.org/v1)), that shows "Not Found".
In Brazil there are standards that specify the use of XML-schemas for interoperable communication systems, and so we chose to use the reading of the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Industry wide support for vCard BDI import and export?](https://discourse.openehr.org/t/industry-wide-support-for-vcard-bdi-import-and-export/15402)
> Hi, We are trying to get basic demographics import/export \(BDI\) using
vCard/Carddav working industry wide\. This is an important first step for
doing anything with a patient in most systems\. Is it possible for openEHR
to implement import/export by January 1, 2016? My company Astronaut, LLC
which supports a VistA variant has implemented it in approximately 5 hours
of programmer and test time\. Our implementation is open source\. A sample
output is below\. Please let me know as this would...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Memory Clinic / Older Adult Mental Health](https://discourse.openehr.org/t/memory-clinic-older-adult-mental-health/15407)
> I have followed these lists for some years but never posted before. I work in an NHS older adult mental health service in the south of England and the greatest proportion of our workload is in cognitive disorders.
We have significant need to gather a mixture of structured and semi structured or freetext clinical information to support clinical care, audit, service development and research. We have previously worked with UCL CHIME to model the clinical information and built an information...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Maven Archetype – About](https://discourse.openehr.org/t/maven-archetype-about/16522)
> [http://maven.apache.org/archetype/](http://maven.apache.org/archetype/)
Interesting definition (though not related to our models)
Cheers,
-koray
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EQ-5D-5L archetype](https://discourse.openehr.org/t/eq-5d-5l-archetype/15657)
> Has anyone developed a EQ-5D-5L archetype that they can share (and we will get it up on CKM)?
[http://www.euroqol.org/eq-5d-products/eq-5d-5l.html](http://www.euroqol.org/eq-5d-products/eq-5d-5l.html)
Also any issues re licensing?
Ian
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Choice of quantities?](https://discourse.openehr.org/t/choice-of-quantities/15405)
> Hi,
We’re doing some work on the tobacco smoking archetype (yes, still), and one of the identified elements is the amount of tobacco smoked. Smoking tobacco comes in two main forms; cigarettes and loose tobacco for roll-your-own or pipe smoking. This means that the “Amount” element needs to take into account both the amount as a frequency (number of cigarettes per time unit), and a “flow rate” (gram per time unit). We’re trying to make this a choice element between a Quantity (frequency) and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Any InterRAI modelling work out there?](https://discourse.openehr.org/t/any-interrai-modelling-work-out-there/15408)
> Hi,
I’m keen to know if anyone has had experience in modelling work involving [InterRAI](http://www.interrai.org/).
It is a comprehensive clinical assessment of medical, rehabilitation and support needs and abilities such as mobility and self-care used in aged care. In New Zealand we have a national system in place.
Cheers,
-koray
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Jack Rabbit](https://discourse.openehr.org/t/jack-rabbit/15656)
> Did anyone ever heard of Jack Rabbit, and how it behaves in OpenEHR context?
It seems to have much, an OpenEHR database needs\.
It has support for structured and unstructured content, full text search, versioning, transactions, observation
https://jackrabbit.apache.org/oak/
It seems to be actively used:
Mailinglists: 3 lists and 38,604 messages\. First list started in March 2012\. There are 3 active lists, recently accumulating 9 messages per day\.
Best regards
Bert Verhees
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OPT2 specification, choosing terminology bindings...](https://discourse.openehr.org/t/opt2-specification-choosing-terminology-bindings/16117)
> One of the final things to get right in ADL2 is how to choose terminology bindings, also languages and a few other settings when going from source archetypes and templates to the OPT. I have put up a [draft OPT2 specification ](http://www.openehr.org/releases/AM/latest/docs/OPT2/OPT2.html)with some ideas on this, which people may be interested to comment on. The following overview diagram from it gives an idea.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Binding to multiple terminologies / code systems](https://discourse.openehr.org/t/binding-to-multiple-terminologies-code-systems/13958)
> All
I have a modelling issue where I’m trying to bind a single data point or an archetype to a choice of terminology & code systems.
The actual use case is that I’m modelling a new-born hips examination, and the result may be given as either a SNOMED CT concept, a Read 2 code or a CTV3 code (for those unfamiliar with Read 2 & CTV3, they are code systems used (mostly) in primary care in the UK). In the actual instance, each code/concept will have a code system identifier to distinguish the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New open source ADL2-Library](https://discourse.openehr.org/t/new-open-source-adl2-library/13894)
> I would like to announce a new open source ADL2 library, written in Java\.
It is based on the ANTLR\-grammar released very recently by Thomas Beale\.
You can find it at https://github.com/nedap/archie
It is still very much in development, but it is now at a state where it
could be of use to people\. It currently features:
\- an ADL2\-parser that parses the full definition, specialises,
terminology, value sets and \(a subset of\) rules sections
\- an archetype object model implementation
\-...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR White Paper : the vendor-neutral semantic eHealth platform](https://discourse.openehr.org/t/new-openehr-white-paper-the-vendor-neutral-semantic-ehealth-platform/15655)
> openEHR has released a new [White Paper](http://www.openehr.org/resources/white_paper_docs/openEHR_vendor_independent_platform.pdf) describing an open, vendor-neutral semantic platform-based future for health computing.
It describes how a health computing platform built around openEHR offers the most comprehensive semantic framework available in e-health, combining formal clinical modelling, terminology, and a services infrastructure, lowering the costs to market for new eHealth innovators,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OS licences - CC-BY-SA 4 compatible with GPLv3](https://discourse.openehr.org/t/os-licences-cc-by-sa-4-compatible-with-gplv3/16517)
> Announced here officially \- http://creativecommons.org/compatiblelicenses
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Nation wide EHR project by openEHR/ISO13606 got fund in Japan.](https://discourse.openehr.org/t/nation-wide-ehr-project-by-openehr-iso13606-got-fund-in-japan/15404)
> Dear openEHR colleagues,
We are happy to announce that Japan Medical Network Association(JMNA) was designated to implement nation wide EHR with openEHR/ISO 13606 information models in competitive bid by Japan agency for medical research and development.
To the next March, JMNA will implement EHR system with vendors in Japan by this budget, about 5 million USD.
We, openEHR Japan, will contribute to make models for this EHR project.
I wish this achievement would make happy waves to your...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New adl-antlr GitHub project](https://discourse.openehr.org/t/new-adl-antlr-github-project/16516)
> I have created a new [Github project called adl-antlr](https://github.com/openEHR/adl-antlr), to contain a development set of Antlr4 grammars for ODIN and ADL, for use (at least currently) with the Community Edition of IntelliJ IDEA, with the Antlr4 plugin.
See the README page at the above link if you are interested in using this resource, or participating in the development.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM feature request - bulk export of archetypes in XML format](https://discourse.openehr.org/t/ckm-feature-request-bulk-export-of-archetypes-in-xml-format/15398)
> Hi, could you please implement such a function?
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype publication question - implications for implementers](https://discourse.openehr.org/t/archetype-publication-question-implications-for-implementers/13799)
> Hi everyone,
I’m seeking some community input around a conundrum that has arisen regarding archetype governance, or more specifically if we should offer a new version of an archetype that included breaking changes/corrections according to the openEHR specifications but which are not critical in terms of clinical safety – a bit of a grey zone, if you like. If clinical safety were implicated, the decision would be easy.
The Blood Pressure archetype was published in 2009 and I believe is in...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [SNOMED CT constraint syntax - for querying instances or terminology?](https://discourse.openehr.org/t/snomed-ct-constraint-syntax-for-querying-instances-or-terminology/15401)
> The [latest version of the SNOMED CT constraint language ](http://snomed.org/expressionconstraint)proposes expressions like the following:
Section 6.3
....
To find those capsules that have a strength between 500 and 800 mg (inclusive), the following expression constraint may be used:
< 27658006 |amoxicillin| :
411116001 |has dose form| = << 385049006 | capsule|,
{ 111115 |has basis of strength| = ( 111115 |amoxicillin only| :
111115 |strength magnitude| >= #500, 111115 |strength magnitude|...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR and IHTSDO (SNOMED CT)](https://discourse.openehr.org/t/openehr-and-ihtsdo-snomed-ct/15395)
> Hi,
I wonder if there are any current collaborations or collaboration plans between openEHR Foundation and IHTSDO \(which is the organisation that owns and maintains SNOMED CT\.\)
Regards
Mikael
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 41, Issue 8](https://discourse.openehr.org/t/openehr-clinical-digest-vol-41-issue-8/15391)
> Hi all,
Great references and food discussion!
But, I must admit that I do not believe in any universal truths and I do distrust anyone assuming to have one. So the point should be imho to question if BFO is useful? definitely, but universal truth???? No way.!
Is use of ontology necessary for learning about reality? Of course. And can it help with information modeling as abstraction of reality ? That point was made in the on this list very heavily critiqued paper by Blobel, Brochhausen and...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR @ medinfo2015](https://discourse.openehr.org/t/openehr-medinfo2015/15653)
> openEHR was delighted to support the very successful recent Medinfo2015 event in Sāo Paulo, Brazil as a Silver Sponsor.
Having a dedicated stand at a major informatics conference was new ground for openEHR but was highly sucessful, thanks to support from three of our Industry partners - Ocean Informatics, Critical Software and Marand. The combination of a large number of openEHR- themed tutorials, workshops, presentations, papers and posters and a vibrant atmosphere on and around the stand...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [book recommendation - basic formal ontology (BFO) for biomedicine](https://discourse.openehr.org/t/book-recommendation-basic-formal-ontology-bfo-for-biomedicine/15389)
> A new book, **Building Ontologies with Basic Formal Ontology** (BFO2) has been published by Robert Arp, Barry Smith and Andrew Spear.
[Amazon.com](http://www.amazon.com/Building-Ontologies-Basic-Formal-Ontology/dp/0262527812/ref=sr_1_1?ie=UTF8&qid=1441588367&sr=8-1&keywords=basic+formal+ontology)
[Amazon.co.uk](http://www.amazon.co.uk/Building-Ontologies-Basic-Formal-Ontology/dp/0262527812/ref=sr_1_1?ie=UTF8&qid=1441588327&sr=8-1&keywords=basic+formal+ontology)
I've read a pre-print, and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 43, Issue 22](https://discourse.openehr.org/t/openehr-technical-digest-vol-43-issue-22/15384)
> Dear all,
Can anyone explain what ND, SA and RFC stand for?
I personally do not believe in free standards. Standards come at a cost, is the work put in to it and the travels etc for consensus meetings.
We at NEN have deliberately added a price tag to volunteer work put into a standard. Not for being paid, but to get a valid idea of how much people put in to it.
The other thing is how to keep such work sustainable in the long run. If someone makes a business eg from software that runs on...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR is open but ISO may offer some other advatages](https://discourse.openehr.org/t/openehr-is-open-but-iso-may-offer-some-other-advatages/12820)
> Dear friends,
I do not think a semantic discussion on the origin and meanings of the word proprietary is helpful\. To me, also an advocate of formal standards in CEN and ISO, it is clear that we should regard openEHR artefacts as non\-proprietary in line with other communitites in the world of open standards and open source sharing\. I am amazed that some people have questioned this\. The main reasons are two\-fold: a\) The specs are openly available free of charge to read and to use and b\)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [A question about the XML schema for version 1.4 archetypes](https://discourse.openehr.org/t/a-question-about-the-xml-schema-for-version-1-4-archetypes/15393)
> I have a question about the XML schema for archetypes based on ADL version 1.4
The set of schemas we are using to validate XML archetype exports are 1.0.1
ETC..
The issue we are getting is that sometimes an archetype has a tag. All those downloaded from our CKM (ckm.hscic.gov.uk) have this tag, but it’s not present on all...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ACTIONs, OBSERVATIONs and procedures](https://discourse.openehr.org/t/actions-observations-and-procedures/15392)
> Hello,
I have just had an interesting conversation with Diego during a coffee break, and several doubts arose around the representation of procedures.
At the CKM we have an ACTION archetype to represent any type of procedures. It is described as "A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes". So far, so good.
Now the doubt is about what happens when the procedure is something simple and non-invasive that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Advantage of ISO](https://discourse.openehr.org/t/advantage-of-iso/15390)
> I have written a text \(reply to Erik\) in Stackoverflow, describing why it will be good for OpenEHR if AOM2\.0 will become an ISO\-standard in the context of ISO13606 renewal\.
http://stackoverflow.com/questions/32010122/are-the-hl7-fhir-hl7-cda-cimi-openehr-and-iso13606-approaches-aiming-to-solve/
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype versioning: Skipping v1 and going straight to v2?](https://discourse.openehr.org/t/archetype-versioning-skipping-v1-and-going-straight-to-v2/15387)
> Hi everyone,
We’ve bumped into an issue related to versioning of archetypes and implementing non-published versions:
Several implementation projects are using archetypes from the [http://arketyper.no](http://arketyper.no) CKM, many of which are still drafts or under review since the CKM switch to v0 for unpublished archetypes was done only recently, and the publicly available tools all use v1 by default, lots of functionality has already been made using unpublished v1 versions of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ACTION performer?](https://discourse.openehr.org/t/action-performer/15394)
> Hi all,
According to Norwegian law, the performer or main performer of a procedure has to be explicitly recorded. The main performer is not necessarily the same person who records the action, so the COMPOSITION.composer RM object may not be used for this. We can’t seem to find any complete description of the ACTION.participations RM object, but if it’s possible to specify the role of the participant there, this may possibly be used. Or will we have to explicitly model this in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [difference and relationship between openEHR and EN13606](https://discourse.openehr.org/t/difference-and-relationship-between-openehr-and-en13606/15388)
> dear all ,
how could i explain to someone difference and relationship between openEHR and EN13606
thx
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [AQL ANTLR4-grammar](https://discourse.openehr.org/t/aql-antlr4-grammar/16514)
> Hello everyone
Please see further below regarding a few first steps towards "converting" Chunlan's \.g files in combination with Eiffel's lexer files to ANTLR's syntax\. My main motivation for doing this was to produce syntax diagrams for ADL and AQL but very early on I realized that there was no point writing just the EBNF because I could be deriving the ANTLR representation of the grammar and from that be able to produce a parser as well\.
This was going well, until...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL ANTLR4-grammar](https://discourse.openehr.org/t/aql-antlr4-grammar/15386)
> Hi!
At Medinfo2015 i have been positively surprised by all the different openEHR implementations that I had not heard of before.
AQL capability is present or planned in both some of the previously and recently known openEHR implemetnations
It would be good to collaborate around testing, updates and practial application of shared AQL grammar resources so that it becomes easier to support AQL in openEHR implementations.
When implementing AQL in the LiU-EEE REST demonstrator we used Java CC,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [latest updates to AD2 / AOM2 specifications](https://discourse.openehr.org/t/latest-updates-to-ad2-aom2-specifications/16513)
> I am finalising the ADL/AOM2 specifications, mainly updating text, and incorporating content from older separate documents. It's not finished yet, but sections that may interest some people:
- [templates and template overlays](http://www.openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_templates)
- [efficient serialisation formats](http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_serialisation_model) for archetypes (JSON, XML, ODIN, YAML)
- [Antlr4 grammar for ADL...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL versions 1.4, 1.5 and 2.0](https://discourse.openehr.org/t/adl-versions-1-4-1-5-and-2-0/15385)
> All
Hope everyone is well.
I have a few questions on ADL versions
Is there a general view as to when archetypes will be created in an ADL version other than version 1.4?
I’ve sampled CKMs from various countries & found all archetypes (that I sampled) were in the ADL 1.4 format.
Some questions:
Is anyone planning to use anything other than ADL 1.4 in the near future?
How will CKMs cope with multiple ADL versions in a single CKM?
When will tools be available to create archetypes in 1.5...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [MEDINFO program](https://discourse.openehr.org/t/medinfo-program/15373)
> Hello all,
I re-ordered the presentations by time schedule in MEDINFO2015 in Sao Paolo, Brasil.
[https://openehr.atlassian.net/wiki/display/resources/MEDINFO+2015+-+Sao+Paulo%2C+Brazil](https://openehr.atlassian.net/wiki/display/resources/MEDINFO+2015+-+Sao+Paulo%2C+Brazil)
Please have a glance when you make your schedule in MEDINFO.
Regards,
Shinji KOBAYASHI
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [2 constraint bindings in ADL - 1 referenceSetUri in OPT](https://discourse.openehr.org/t/2-constraint-bindings-in-adl-1-referenceseturi-in-opt/15650)
> Hi,
I have created a testing archetype with two constraint bindings:
...
ELEMENT[at0004] occurrences matches {0..1} matches { -- Terminology ref
value matches {
DV_CODED_TEXT matches {
defining_code matches {[ac0001]} -- ref
}
}
...
constraint_definitions = <
["es"] = <
items = <
["ac0001"] = <
text = <"ref">
description = <"ref">
>
>
>
>
constraint_bindings = <
["SNOMED-CT"] = <
items = <
["ac0001"] =
>
>
["AOD2000"] = <
items =...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM for training purposes](https://discourse.openehr.org/t/ckm-for-training-purposes/15652)
> +1 pls
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Term set for DV_PARSABLE.formalism](https://discourse.openehr.org/t/term-set-for-dv-parsable-formalism/15377)
> Reading the specs I realize that there isn't a term set for DV_PARSABLE.formalism and it is a free text attribute.
Since stuff like XML, JSON, CSV, etc. are in fact modeled by DV_PARSABLE, and those have a MIME type associated (text/xml, application/json, text/csv, ...), shouldn't we define a term set for that attribute like we have for DV_MULTIMEDIA.media_type? (of course this attribute is CODE_PHRASE and not String like "formalism").
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template Designer problem when selecting Value Set on DV_TEXT node](https://discourse.openehr.org/t/template-designer-problem-when-selecting-value-set-on-dv-text-node/15651)
> Hi,
I have a text node and was testing different ways of constraining that node from the Template Designer.
I've found that if I select the node, then on the node properties panel go to: Value Set > On the window, under the "Terminology Service" tab, select "Snomed" and check the "Select full terminology", then save the OET. That constraint doesn't appear in the OET file.
If I go to the "Generic Valueset" tab on the same window, and input a Terminology Name and a Subset name, then save the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype schemas](https://discourse.openehr.org/t/archetype-schemas/16511)
> Hi All
Is there a set of schemas that govern archetypes downloaded from a CKM available?
The archetypes I’m using for testing are “Blood Pressure” and “Body temperature” hosted on [http://www.openehr.org/ckm/](http://www.openehr.org/ckm/). (both created in ADL version 1.4)
I’ve looked at the schemas listed at [http://www.openehr.org/releases/trunk/its/XML-schema/](http://www.openehr.org/releases/trunk/its/XML-schema/) , and these produce an error around “IntervalOfDateTime” ,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template Designer: Error exporting OPT that contains the ACTION.procedure archetype](https://discourse.openehr.org/t/template-designer-error-exporting-opt-that-contains-the-action-procedure-archetype/15375)
> Hi, I need to create an OPT that contains the ACTION.procedure archetype, but when exporting the OPT I get this error:
Failed to export operational template.
openEHR-EHR-ACTION.procedure.v1.adl
ERROR - line 1: parse error [last token = V_IDENTIFIER]
line 1: In 'archetype' clause; expecting archetype id (model_issuer-ref_model_class.concept.version) [last token = V_IDENTIFIER]
(Parse failed) (ADL_INTERFACE.parse_archetype)
When I include the archetype in my COMPOSITION template, I can see...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype editor, CKM and v0 & v1](https://discourse.openehr.org/t/archetype-editor-ckm-and-v0-v1/15380)
> Hi All
I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters.
When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example
“openEHR-EHR-OBSERVATION. blood_pressure.v1.adl”
When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Video aulas iniciais](https://discourse.openehr.org/t/video-aulas-iniciais/15647)
> Hi friends.
Where can I video lessons basic for OpenEHR online?
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM error for translator email](https://discourse.openehr.org/t/ckm-error-for-translator-email/16512)
> Sometimes the translator email field appears empty after being recorded.
Today it happened that after recording the email and starting translating some fields, the email appeared empty, then I saw that the accreditaion field had the email value.
Now, after saving a partial translation, and starting again with the translation, the email is empty again, but a weird thing happened: now my email is a field name. See...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR specifications - the future is Asciidoctor + MagicDraw?](https://discourse.openehr.org/t/openehr-specifications-the-future-is-asciidoctor-magicdraw/15374)
> Back at the September 2014 roadmap meeting **we agreed to move from the current specifications documentation** in FrameMaker to a modern tool, preferably text-based. [This wiki page](https://openehr.atlassian.net/wiki/display/spec/openEHR+Specifications+tooling) shows various alternatives under consideration. The other problem **we agreed to deal with was to put all openEHR models into a UML** tool environment.
### ProgressWe've **made a lot of progress** on both of these. The whole of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype Industry Sprint update](https://discourse.openehr.org/t/archetype-industry-sprint-update/15376)
> Hi everyone,
Just a quick update to let you know the wiki pages for the archetype sprint have been updated today\.
We are very privileged to have an extraordinary team of volunteer reviewers who have participated to date\.
As a result of their collective efforts, 5 archetypes have been published in just the past week \- the culmination of months of effort and collaboration across 3 CKMs \(in a number of cases\) and an extraordinary effort from each one of our dedicated reviewers\. Take a...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype Industry Sprint update](https://discourse.openehr.org/t/archetype-industry-sprint-update/15648)
> Hi everyone,
Just a quick update to let you know the wiki pages for the archetype sprint have been updated today.
We are very privileged to have an extraordinary team of volunteer reviewers who have participated to date.
As a result of their collective efforts, 5 archetypes have been published in just the past week - the culmination of months of effort and collaboration across 3 CKMs (in a number of cases) and an extraordinary effort from each one of our dedicated reviewers. Take a look at...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Examination archetypes](https://discourse.openehr.org/t/examination-archetypes/15379)
> Hi everyone,
If you’ve been following @openEHRCKM on twitter in the past couple of days, you will have noticed a flurry of activity.
After many years of experimentation, we have finally devised a solid base pattern for the physical exam findings family of archetypes. This is a massive piece of work if we are to attempt to structure recording/persistence/querying of all clinical examination in a way that allows clinical flexibility and fractal examination processes. You can see our base...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updated Vim mode for ADL syntax](https://discourse.openehr.org/t/updated-vim-mode-for-adl-syntax/15649)
> I have uploaded [new vim syntax colourising files](https://openehr.atlassian.net/wiki/display/dev/ADL+Text+Editors), for those who use vim. I have included a dark blue background custom colour scheme as well. Have a look at the screen shots - I have tried to be somewhat scientific about the colours:
- various shades of blue for RM classes, properties in cADL, and also properties in ODIN sections
- green for terminology codes
Much much more can be done. For those of you who have any idea of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR@ StackExchange - update](https://discourse.openehr.org/t/openehr-stackexchange-update/15378)
> To succeed with openehr.StackExchange.com, the committers phase needs 200 total. We particularly **need people who want to ask questions** to commit ([do it here](http://area51.stackexchange.com/proposals/87508/openehr)).
Secondly, 50% of those committers need 200+ reputation on any other StackExchange site. You can see [all the sites here](http://stackexchange.com/sites).
- For IT devs and other techies, geek docs etc, I recommend you make sure you are always logged in when using...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New paper: Archetype-based data warehouse environment](https://discourse.openehr.org/t/new-paper-archetype-based-data-warehouse-environment/15372)
> Dear all,
My colleagues Luis Marco-Ruiz, José A. Maldonado, Nils Kolstrup, Johan G. Bellika and myself have just published a paper titled "Archetype-based data warehouse environment to enable the reuse of electronic health record data" in the International Journal of Medical Informatics. I think this work can be of interest for many of you.
Best regards,
David
Link:...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [nearly there - openEHR @ StackExchange - 2 questions to go](https://discourse.openehr.org/t/nearly-there-openehr-stackexchange-2-questions-to-go/12607)
> If anyone has any votes left (each user has 5), here is what to do:
- login to the [openEHR Area51 StackExchange page](http://area51.stackexchange.com/proposals/87508/openehr)
- find the two questions with < 10 votes (currently on 6 and 8) - near the bottom of the page - and UPVOTE them
- please DO NOT DOWNVOTE anything
In theory **this requires 4 users**, since each user can only vote once per question, so to get the question with 6 to 10, that's 4 distinct users.
Please don't try...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [VERSION.lifecycle_state options](https://discourse.openehr.org/t/version-lifecycle-state-options/15382)
> Hello all,
Does anybody \(with an openEHR persistence system/solution\) encountered the need to record other states than 'incomplete', complete', 'deleted' for a VERSION\.lifecycle\_state?
The use case is that in some circumstances a version need to become immutable and any change should be forbidden\. Imagine a care plan that was already 'inform\-consented' \- it should not be allowed to be changed in any way, neither logically deleted \(unless perhaps some...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype use for generic patterns and/or for real patient data](https://discourse.openehr.org/t/archetype-use-for-generic-patterns-and-or-for-real-patient-data/15381)
> There are numerous situations in EHR-systems, where a general pattern of what to do exists, and then is used for a patient in a given situation, resulting in EHR-records based on this pattern. It is unclear to me to what extent the archetypes may be used for modelling such patterns, and how to move from such general patterns to the archetypes containing the real patient related data.
The following example is meant to illustrate the issue:
Several patients may have the same medical condition...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHRServer is on the cloud](https://discourse.openehr.org/t/ehrserver-is-on-the-cloud/15369)
> Dear friends,
I'm happy to share with you that our openEHR EHRServer is on the cloud: [http://cabolabs-ehrserver.rhcloud.com/ehr-0.1/](http://cabolabs-ehrserver.rhcloud.com/ehr-0.1/)
This is a pre-beta version, with no security. Anyone can play with it.
Some background info:
EHRServer is an open source, service oriented, openEHR data repository, with archetype-based querying capabilities. It can store any kind of openEHR data without the need of changing the source code or the database...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [News: Specifications Committee May 2015 meeting](https://discourse.openehr.org/t/news-specifications-committee-may-2015-meeting/16506)
> The openEHR [Specifications Editorial Committee (SEC)](http://www.openehr.org/programs/specification/editorialcommittee) met for 2 days in Alkmaar, at the offices of [Code24](http://www.openehr.org/industry_partners/code24) who kindly provided a nice working space, catering and friendly support. Eight of the 12 members were there in person, with remote participation by the remaining four.
We were glad to have the in-person presence of Shinji Kobayashi (SEC member) and an observer, Asst prof...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR @ StackExchange - please subscribe](https://discourse.openehr.org/t/openehr-stackexchange-please-subscribe/15645)
> Ever wanted to know the answer to some specific question about openEHR? Sometimes it's hard to figure out where to look for the answer.
We're proposing a new openEHR site at StackExchange.
To get it going, it would need the following:
- 56 followers
- 40 questions with a score of 10 or more
If you are interested in seeing a dedicated openEHR StackExchange site, please visit [the proposal area](http://area51.stackexchange.com/proposals/87508/openehr?referrer=w4Wq6VpjyxQPC4BojQudOA2), and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Cleaning up the wiki...](https://discourse.openehr.org/t/cleaning-up-the-wiki/15586)
> We appear to be getting more and more newcomers to the openEHR website and wiki - and on the wiki, they are faced with a somewhat chaotic place! I think we should slowly start to clean it up.
### First suggestion:There are two spaces for developers - 'Developers', which has a lot of pages, and needs some re-organisation, and 'Implementation Guidance' which is small and not used much.
I propose to put the pages from the latter under the 'Developers' space and remove the latter space.
###...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Working with templates](https://discourse.openehr.org/t/working-with-templates/16505)
> Hi,
I’ve been working with the java-libs trying to parse templates.
I used the parser and the flattener but when I serialize it to XML and compare it to the flattened (OPT) version from CKM, they are different.
I’ve read the documentation from [http://www.openehr.org/releases/trunk/architecture/am/tom.pdf](http://www.openehr.org/releases/trunk/architecture/am/tom.pdf) and I think I’m missing a compression step.
Is this compression step already implemented on the Java libs or is there a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR archetypes and views](https://discourse.openehr.org/t/openehr-archetypes-and-views/15367)
> Hello,
I am in the learning process of openEHR as part of my thesis work at Orebro university, Sweden, and I would like to ask quite simple questions which I came across but , couldn’t find any document which deal in the subject.
1) Is there any way to get a mind map view for the archetypes/ templates via one of the modeling tools ? (for ex the ADL)
2) My goal is to model a system via archetype. For ex: a screen which present a patient overview. The screen represent data and does not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM Translation details - can we have a concrete proposal?](https://discourse.openehr.org/t/aom-translation-details-can-we-have-a-concrete-proposal/15646)
> As we process outstanding PRs, I discovered an old one from Sebastian Garde \- SPECPR\-24, that initially reports the need for better translation meta\-data\. Silje started a thread on more recent requirements here to which some of us replied\.
Could we have a concrete proposal \- maybe a synthesis of all of this thinking from Sebastian, Silje, and anyone else who specifically is interested in this? My input would be mainly to say: don't try to put every possible meta\-data item in \-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Have your say on existing Problem Reports](https://discourse.openehr.org/t/have-your-say-on-existing-problem-reports/16507)
> All,
there are 114 Problem Reports (PRs) being processed by the Specifications Editorial Committee (SEC) right now, [here on the SPECPR Jira tracker](https://openehr.atlassian.net/projects/SPECPR/issues/SPECPR-46?filter=allopenissues). We are heading to a 2-day meeting (21 May) for the SEC to convert these to Change Requests (CRs) that will be the basis of the next few releases of openEHR.
If you want to make comments or review any of these PRs (or even raise new ones, but please make sure,...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Doubt parsing ADL file](https://discourse.openehr.org/t/doubt-parsing-adl-file/15366)
> Hi,
I’m using the java-libs to parse some adl files from the Clinical Knowledge Manager(CKM).
I’m getting some crashes due to stackoverflow when trying to do Archetype.toString().
When I checked the Archetype I saw a loop. The field Archetype.description.parentResourse was pointing back at the Archetype.
My confusion seems to be in the function org.openehr.rm.common.resource.AuthoredResource.setDescription().
I don’t understand why :
if (description != null &&...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Technical and clinical lists now have searchable archive.](https://discourse.openehr.org/t/technical-and-clinical-lists-now-have-searchable-archive/15362)
> We have uploaded the technical and clinical list archives to mail-archive.com, which is a web-searchable interface to the lists.
[Technical list here](https://www.mail-archive.com/openehr-technical@lists.openehr.org/)
[Clinical list here](https://www.mail-archive.com/openehr-clinical@lists.openehr.org/).
These links are now on the [mailing lists page](http://www.openehr.org/community/mailinglists).
The remaining mailing lists are coming soon.
- thomas
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Should we have an official openEHR maven repository?](https://discourse.openehr.org/t/should-we-have-an-official-openehr-maven-repository/15361)
> Hello all,
I think currently there is no public available maven repository for
the openEHR java\-libs and other related project libraries\. Do you
think it would be interesting to have this kind of official public
repository?
Regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Change type from DV_TEXT to DV_CODED_TEXT in the Template Designer](https://discourse.openehr.org/t/change-type-from-dv-text-to-dv-coded-text-in-the-template-designer/15365)
> Hi,
I'm working with the problem/diagnosis archetype. I want to include it in an OPT but redefine the name constraint that is DV_TEXT to DV_CODED_TEXT, but the TD doesn't show the DV_CODED_TEXT option in the node data type list. See: [http://postimg.org/image/dtb8paha3/](http://postimg.org/image/dtb8paha3/)
Is this possible?
Thanks!
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template Designer missing translations for event type](https://discourse.openehr.org/t/template-designer-missing-translations-for-event-type/16510)
> Hi, I was definig the specific type of an EVENT and the TD ui shows ? instead of the specific Point / Interval.
See screenshot [http://postimg.org/image/7538hrlej/](http://postimg.org/image/7538hrlej/)
I'm working with spanish locale.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template Designer - remove slot](https://discourse.openehr.org/t/template-designer-remove-slot/15364)
> Hi, I'm creating a template from the Encounter archetype using the TD.
That archetype has a slot in the compo.context.other_context. I don't use that slot so I don't want it to appear in my final OPT, but I couldn't find any way in the TD to let me remove that node or put 0..0 on the cardinality, so the exported OPT has the slot.
Is there any way to do this? Maybe other OPT designers?
I'm using TD v2.6.1214Beta
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [This archetype stems from a remote domain and cannot be edited in this CKM.](https://discourse.openehr.org/t/this-archetype-stems-from-a-remote-domain-and-cannot-be-edited-in-this-ckm/15363)
> Hi,
I need to translate and use the progress note OBSERVATION archetype but when I try to translate it in the CKM I receive "This archetype stems from a remote domain and cannot be edited in this CKM."
I know I can download and translate it in the AE, but my translation wouldn't be available for others to use.
Can this, and other archetypes managed by external CKMs, imported into the openEHR CKM?
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [(ignore) clinical list mail archive test message](https://discourse.openehr.org/t/ignore-clinical-list-mail-archive-test-message/16509)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [(ignore} technical list archiving test message](https://discourse.openehr.org/t/ignore-technical-list-archiving-test-message/14329)
> test \#1
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [SNOMED-CT postcoordination support in ADL](https://discourse.openehr.org/t/snomed-ct-postcoordination-support-in-adl/15368)
> Hi,
I am trying to annotate a set of archetypes with SNOMED-CT. I have noticed that in the archetype editor, when I introduce a postcoordinated expressions, the editor deletes the bars and creates a continuous alphanumeric string. Do you know if postcoordinated expressions can be set in the ontology section of the archetype? What are current approaches to overcome this?
A solution could be to insert an id representing the postcoordinated expression and resolve it in my terminology server....
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Specifications program roadmap - have your say](https://discourse.openehr.org/t/specifications-program-roadmap-have-your-say/13479)
> There will be a f2f of the [Specifications Editorial Committee ](http://www.openehr.org/programs/specification/editorialcommittee)(SEC) in Netherlands, 21/22 May. At this meeting, the SEC will try to process the existing [Problem Reports ](https://openehr.atlassian.net/issues/?jql=project%20%3D%20SPECPR%20ORDER%20BY%20created%20DESC)(PRs) and convert them to Change Requests (CRs) on the various [Specifications Trackers](https://openehr.atlassian.net/secure/Dashboard.jspa?selectPageId=10190)....
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Converting ADL to JSON](https://discourse.openehr.org/t/converting-adl-to-json/15352)
> Hi,
First of all I would like to say Hello since this is my first post on the mailing list.
Second, my questions:
I’m trying to do a implementation of OpenEHR in Java with the persistence layer in JSON.
I’ve searched the web but all the implementations/libraries I find use XML to store and the openEHR java-libs to process the ADL files.
My application would try to follow the REST/JSON API in [https://www.ehrscape.com/](https://www.ehrscape.com/) and since the persistence is also made in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Converting to JSON](https://discourse.openehr.org/t/converting-to-json/16508)
> Hi,
First of all I would like to say Hello since this is my first post on the mailing list.
Second, my questions:
I’m trying to do a implementation of OpenEHR in Java with the persistence layer in JSON.
I’ve searched the web but all the implementations/libraries I find use XML to store and the openEHR java-libs to process the ADL files.
My application would try to follow the REST/JSON API in [https://www.ehrscape.com/](https://www.ehrscape.com/) and since the persistence is also made in...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [greetings and 2 questions](https://discourse.openehr.org/t/greetings-and-2-questions/13474)
> Hi,
The following questions may be US centric but my general intent is the general healthcare topic of interoperability:
1. What is the difference between WorldVistA and OpenEHR? I know VistA is written in Mumps which claims a superior organization of vast numbers of dependencies.
2. If HL7 ([FHIR being developed: http://www.hl7.org/FHIR)](http://www.hl7.org/FHIR/) is the standard in data protocol between all healthcare software vendors, doesn't that mean that any system that can use that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR and Oracle XML DB problems](https://discourse.openehr.org/t/openehr-and-oracle-xml-db-problems/13407)
> Hi everyone,
According Bert experience \(https://www.linkedin.com/groups/Choice-OpenEHR-persistence-layer-144276.S.208531138), one must not try to adopt OpenEHR model to relational storage since almost all popular database engines able to process native XML\.
So I'm experimenting with Oracle XML DB for almost two weeks, and I'm in despair and kindly ask you for help\.
Here is a Github repository where I've collected few files \- https://github.com/da-baranov/openehr-ora :
1\)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR .oet XML schema](https://discourse.openehr.org/t/openehr-oet-xml-schema/15351)
> I'm exploring samples from the OpenEHR CKM app (http://openehr.org/ckm/) and see that XML schema namespace for the OET templates is "openEHR/v1/Template". Where that XML Schema is hosted?
As far as I understood, the "openEHR/v1/Template" namespace references an XML template schema definition for version 1.0.1 which is not available for download (http://www.openehr.org/releases/1.0.1/its/XML-schema/)
Tried to use OET XML Schema taken from 1.0.2 distr...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM2 initial working XSDs and example validating XML output.](https://discourse.openehr.org/t/aom2-initial-working-xsds-and-example-validating-xml-output/15644)
> I have been working with the AML (Archetype Modelling Language) team recently, and as a result have produced a set of XSDs for AOM2.
These can be found [here ](https://github.com/openEHR/specifications/tree/master/ITS/AOM2/XML-schema)in Github.
Notes:
- it's initial work, very unlikely not to change
- the schemas were derived from existing AOM Release 1.0.2 schemas, and have been changed fairly significantly
- the underlying class structures are not just AOM classes, but [P_AOM...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New Co-Chairs of Management Board](https://discourse.openehr.org/t/new-co-chairs-of-management-board/15643)
> Dear All
The openEHR Foundation has begun operating as a non-profit organisation. We now have a Management Board with four members. Ian McNicoll and Koray Atalag were elected by the subscribed members and Tomaz Gornik and Rong Chen were elected by the Industry Partners. We have a Board of Governors, chaired by Prof. David Ingram, which formally delegates operational decisions to the Management Board and ensures that the organisation operates within its legal requirements and maximises...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ACTION just as event trigger](https://discourse.openehr.org/t/action-just-as-event-trigger/15355)
> A couple of week ago someone mebtioned that ACTION archetypes are not being developed or used a lot, and maybe is because we actually don't need to put data on ACTIONs as part of the clinical record, but maybe only as event trigger and logs of ehat happened. With tgis I mean: ACTION recording might be used ti send notifications to other statems (like whe a lab test is done, the results are sent or queried), or to keep the log of real world events that happened and may change the status of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Pediatric Glasgow Coma Scale](https://discourse.openehr.org/t/pediatric-glasgow-coma-scale/16502)
> Hi there,
are there current plans to develop an archetype for the pediatric version of GCS? Otherwise I would develop one that fits the local needs of MHH and then it might be used as a starting point for the collaborative development approach.
Best,
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Pre-Easter update More reviews openEHR archetype Sprint reviews for participation](https://discourse.openehr.org/t/pre-easter-update-more-reviews-openehr-archetype-sprint-reviews-for-participation/16499)
> Just a quick pre-Easter notice and feedback about reviews:
All of the reviews, see emails below, are still active with the exception of Urinalysis, which has already been published.
There will be no review closure over the Easter break, so even if the deadline has passed they will remain in the active state until actively closed when the Editors are ready to work on the review.
So if you have some spare time over the holiday, please feel free to review to your heart’s content. J
For some...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [one-to-many term bindings in archetypes](https://discourse.openehr.org/t/one-to-many-term-bindings-in-archetypes/13774)
> Hi,
I was reviewing some archetypes and on the "term_bindings" section there are always one-to-one bindings.
I think we can have many codes in one terminology corresponding to one at code in the archetype, e.g. in the blood pressure archetype we have:
term_bindings = <
["SNOMED-CT"] = <
items = <
["at0000"] = <[SNOMED-CT(2003)::163020007]> -- Blood Pressure
Looking for the 163020007 code in SNOMED, that corresponds to "On Examination Blood Pressure...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New paper: Analysis of Clinical Information Modeling Processes](https://discourse.openehr.org/t/new-paper-analysis-of-clinical-information-modeling-processes/12741)
> Dear all,
My colleagues Alberto Moreno, Wellington Dimas, Marcelo R Santos, José Alberto Maldonado, Montserrat Robles, Dipak Kalra and myself have just published a paper titled "**Clinical information modeling processes for semantic interoperability of electronic health records: systematic review and inductive analysis**" in the Journal of the American Medical Informatics Association.
It can be found in...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype sprint status](https://discourse.openehr.org/t/archetype-sprint-status/16498)
> Hi everyone,
Just to let you know that since the sprint started we have had 6 archetypes published, 3 in the past 2 weeks:
· Medical Device (CLUSTER)
· Adverse Reaction List (COMPOSITION)
· Encounter (COMPOSITION)
· Physical Examination Finding (OBSERVATION)
· Urinalysis (OBSERVATION)
· Adhoc Heading (SECTION)
Currently there are 11 archetypes out for review.
You are welcome to [adopt](https://openehr.atlassian.net/wiki/display/healthmod/Adopt+an+archetype) any or all of these...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [test #1](https://discourse.openehr.org/t/test-1/16504)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OPT generation](https://discourse.openehr.org/t/opt-generation/16500)
> Hi, everyone. I was trying to implement a web OET editor to edit template and use OPT to generate the user interface for users to type in data. I met a problem when trying to convert OET to OPT. I found no libraries that can achieve this. Though I found a OET flattener that can flaten an OET to an Archetype object. And the flattened Archetype object's nodePathMap was weried, combining the original archetype node path and the slotted archetype node path, and the ontology part was empty. Also...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Editing demographic archetypes](https://discourse.openehr.org/t/editing-demographic-archetypes/15642)
> Hi everyone,
The openEHR CKM contains quite a few archetypes of the class DEMOGRAPHIC-*, apparently all authored by a Brazilian team in 2009. These are not editable using the Archetype Editor. How would one go about editing these archetypes? Is editing ADL in a text editor the only way at the moment?
Kind regards,
**Silje Ljosland Bakke**
Coordinator, National Editorial Board for Archetypes, National ICT Norway
Special Adviser, R&D dept, E-health section, Bergen Hospital Trust
Tel. +47...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Representing a Real value in openEHR](https://discourse.openehr.org/t/representing-a-real-value-in-openehr/14116)
> Hello,
It might seem a very basic question, but I couldn't find an appropriate answer anywhere. Which is the best way to model a single Real number in openEHR? For example, a result of a score.
I have found two possible options:
- Use a DV_QUANTITY, with the "Qualified Real" property, that sets the units to an empty String. This approach is used in the "Harris Hip Score" archetype...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Request for help with a study "Investigating the resources available for novice openEHR clinician modelers"](https://discourse.openehr.org/t/request-for-help-with-a-study-investigating-the-resources-available-for-novice-openehr-clinician-modelers/16501)
> Dear All,
I hope this is an ok ask.
My name is Dmitri Wall & I'm a specialist registrar in dermatology (Ireland) who is also learning to be an openEHR modeler. I'm using this experience to describe the clinician's role in developing archetypes as part of a Masters in Health Informatics. I then hope to use this to encourage more clinicians to become actively engaged in the archetype development process.
The help and welcome I have received from a number of people within the openEHR community...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medinfo submissions](https://discourse.openehr.org/t/medinfo-submissions/16503)
> Hi everyone,
A number of people have had submissions accepted for Medinfo 2015 – a couple of excited people celebrating on Twitter.
I’ve updated the wiki page with some of the successes I’m aware of, plus people who are planning to attend - https://openehr.atlassian.net/wiki/display/resources/MEDINFO+2015+-+Sao+Paulo%2C+Brazil
Please feel free to update with your successful proposals, and if you’re planning to attend.
We will need to start considering what community activities we would...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 38](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-38/12461)
> And how would you handle commercial entities willing to share archetypes and not for profit organizations that keep "their" archetypes legacy?
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 29](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-29/15640)
> Dear Silje,
We deal with translations of Detailed Clinical Models from and To Dutch FOR many years and can validate your precedure\.
Also translations of terminologies as ICF and ICNP\.
There are two "rules" we Found out To Be essential\.
1\. Translation should be done on concept level not term level\.
2 similar to scientific instruments, a dual reverse translation is essential \.
Hope this helps
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Multiple translators](https://discourse.openehr.org/t/multiple-translators/15587)
> Hi,
At the Norwegian CKM [http://arketyper.no](http://arketyper.no), we’ve been doing quite extensive translation of international (English language) archetypes into Norwegian. During this process, we’re finding more and more translation isn’t a one-person job, but usually there’s a primary translator and one or more secondary translators. As of now there seems to be only one field in which to put translator information, so to attribute more than one person as the archetype translator, we...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 21](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-21/15357)
> Dear Heather,
Thank you for the invite\. The GCS comment has been submitted\. I updated the UML version a while ago based on feedback from HL7 and LOINC community\. In particular a note of scoring an item is not possible, and proper LOINC codes were changed\.
It is available in the github repository Detailed Clinical Models\. DCM\.
Further, we have an interest in anatomical Locatìon, which DCM we recently started, albeit for a specific use case\. What to do to team up? And would it not be...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 18](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-18/14321)
> Dear Hugh,
Thank you very much for your overview\!
I Wil refrain from now on telling about this fata mogana because I am now convinced there are real world implementations\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Braden (Q) Scale](https://discourse.openehr.org/t/braden-q-scale/15358)
> Hi there,
I'm a little confused about the "openEHR-EHR-OBSERVATION.braden_scale-child.v1" aka "Modified Braden Q Scale" at the openEHR CKM. I would have expected some explanations in the header what has been modified in comparison to the non-modified Braden Q Scale. In fact, it looks mostly like the common Braden Scale expect from an upper boundary on the "Braden Total Score" of 20 instead of 23. As the elements are the same as in the Braden Scale Archetype, I would expect the upper bound to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 9](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-9/14322)
> OK Martin,
I look forward to see OpenEHR in action in Friesland and all, would welcome implementation case reports\!
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 7](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-7/15350)
> Dear Tom,
Thanks for your comments\.
It is getting a long tail, so I will break it down in small pieces\.
Glad we agree on the need for binding to ontologies\.
I see no need to wait for BFO 2\.0 where 1\.0 is available\.
Our model challenge will be exactly to handle such differences of different ontologies all the time\.
Glad we agree on GCM being helpful in analysis\.
My point of no EHR implementations is supported again by your answer\. Yes there are many CKM instances and archetype...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 35, Issue 4](https://discourse.openehr.org/t/openehr-clinical-digest-vol-35-issue-4/15349)
> Hi all,
As one of the author's of the criticized paper by Blobel et al, I feel some need to react and give you some thoughts:
- OpenEHR after 20 or more years is still largely under construction. I have asked many times to get names and locations of reference sites where I can see a real world archetypes based system in action. No response.
- the approach with the archetypes is technology driven: implementation specific, not clinically driven. It lacks the basic conceptual, logical,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [How to fix CKM biggest issue](https://discourse.openehr.org/t/how-to-fix-ckm-biggest-issue/15353)
> Dear all,
I would like to suggest some very important changes for governance model of CKM. As you all know, CKM is a keystone to openEHR, but its actual governance model is outdated and holds the development and inclusion of new archetypes.
As long as I know there are only 2 main editors that can import any type of archetypes to CKM. I'm an editor too, but I can only import to Ophthalmology Project and some other Incubators. The inclusion of new archetypes can not depend on only 2-3 people....
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [LOCATABLE REF and EHR URI](https://discourse.openehr.org/t/locatable-ref-and-ehr-uri/15638)
> Looking at the Locatable Ref class: [http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf](http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf)
The as_uri function of LOCATABLE_REF is defined to return the following: **“ehr://” + id.value + “/” + path**
If we read Architecture Overview: [http://openehr.org/releases/1.0.2/architecture/overview.pdf at page 64](http://openehr.org/releases/1.0.2/architecture/overview.pdf%20at%20page%2064).
The EHR scheme is defined as:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Election results - openEHR Management Board](https://discourse.openehr.org/t/election-results-openehr-management-board/16497)
> Dear All
The individual members and industry partners have voted and we now have a new Management Board. The candidates elected are:
Individual Members:
Ian McNicol, UK
Koray Atalag, NZ
Industry Partners:
Tomaz Gornik, Marand, Slovenia
Rong Chen, Cambio, Sweden
I would like to congratulate the new Board and all the wonderful candidates who put themselves forward. These are the people who will be setting the direction and making day to day decisions in regard to the activities of the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [More reviews openEHR archetype Sprint reviews for participation](https://discourse.openehr.org/t/more-reviews-openehr-archetype-sprint-reviews-for-participation/15356)
> Hi again,
Further to my recent email, two more reviews have commenced:
· Family History - http://www.openehr.org/ckm/#showArchetype_1013.1.1900
· Glasgow Coma Scale - [http://www.openehr.org/ckm/#showArchetype_1013.1.137](http://www.openehr.org/ckm/#showArchetype_1013.1.137)
Again, if you would like to participate in any of these, please register, log in and adopt the archetype and the Editors will add you to the review team.
Regards
Heather
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR archetype Sprint reviews for participation](https://discourse.openehr.org/t/openehr-archetype-sprint-reviews-for-participation/15639)
> Dear Colleagues,
In the past couple of days a number of archetype reviews have been initiated.
· Anatomical Location - [http://www.openehr.org/ckm/#showArchetype_1013.1.587](http://www.openehr.org/ckm/#showArchetype_1013.1.587)
· Relative Anatomical Location - [http://www.openehr.org/ckm/#showArchetype_1013.1.1892](http://www.openehr.org/ckm/#showArchetype_1013.1.1892)
· Adverse Reaction List -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISM Transition : definition of allowed transitions](https://discourse.openehr.org/t/ism-transition-definition-of-allowed-transitions/12404)
> NB! This is a new e-mail on the same subject since I didn’t see any mail on the mailing list. Just to check if it is working
We are currently developing a module for Careplan based on openEHR Archetypes. We are using INSTRUCTION/ACTIVITY/ACTION archetypes to model the clinical process.
One issue we are facing is the need to define which transitions that are allowed for a given Careflow Step.
To explain I will use openEHR-EHR-ACTION.medication.v1 as example. This ACTION archetype have...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR browsable UML model](https://discourse.openehr.org/t/openehr-browsable-uml-model/12324)
> Hi,
The browsable UML documentation which was available on
http://www.openehr.org/local/releases/1.0.1/uml/index.html
seems to be gone\. Is it moved to another place?
Thanks,
Ralph van Etten
MedVision360
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Last Chance to Vote for the Management Board](https://discourse.openehr.org/t/last-chance-to-vote-for-the-management-board/16493)
> Hi All
I have written to all the members to remind them that this is the last week to vote (Election closes on the 28th Feb 2015).
We have a very strong list of candidates and you can vote for 2 of these to take a leadership role in the future of openEHR. The candidates have written a brief description of themselves here:
[http://members.openehr.org/2015-Management-Board-Nominees](http://members.openehr.org/2015-Management-Board-Nominees)
You need to be a member to vote so please join if...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical Modeling - A critical analysis](https://discourse.openehr.org/t/clinical-modeling-a-critical-analysis/15339)
> Hi folks,
recently found this article by Blobel and Goossen:
[http://www.sciencedirect.com/science/article/pii/S1386505613002013](http://www.sciencedirect.com/science/article/pii/S1386505613002013)
Here are some quotes that I found interesting:
"[openEHR Archteypes] they are facing the problem that the architectural representation and composition/decomposition of real-world classes and instances cannot be provided appropriately"
"Nonetheless, their [(openEHR and CIMI)] architectural...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Specifications Editorial Committee (SEC) formation.](https://discourse.openehr.org/t/specifications-editorial-committee-sec-formation/16496)
> As lead on the Specifications Program, I have set up the [initial membership of the Specifications Editorial Committee (SEC) ](http://www.openehr.org/programs/specification/editorialcommittee)being composed of people who have long term competence in openEHR, and who are reasonably representative of the vendors and major research groups using openEHR, as well as the clinical domain. My thanks to these members for agreeing to join and work on the specifications.
The SEC sits within the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question concerning DV_EHR_URI](https://discourse.openehr.org/t/question-concerning-dv-ehr-uri/16494)
> Hi all,
I had a question about the data type DV_EHR_URI. The specifications are a bit vague on this type:
[http://www.openehr.org/local/releases/1.0.1/uml/Browsable/_9_0_76d0249_1109068357612_21665_4527Report.html](http://www.openehr.org/local/releases/1.0.1/uml/Browsable/_9_0_76d0249_1109068357612_21665_4527Report.html)
It only states that it should start with 'ehr'. How should an internal link to an object in an EHR look like? Are there any conventions, examples or ideas about...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Voting for the openEHR Management Board is now open](https://discourse.openehr.org/t/voting-for-the-openehr-management-board-is-now-open/16495)
> Hi Everyone
The elections for the Management Board are now open. We are very fortunate now to have members from more than 40 countries and 7 candidates for the two Individual Member positions.
If you are a member, please go to the following page to register your vote:
[http://members.openehr.org/page-7745](http://members.openehr.org/page-7745)
If you are not yet a member, please go to [http://members.openehr.org](http://members.openehr.org) and Join. You will be able to vote after your...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Management Board](https://discourse.openehr.org/t/openehr-management-board/15635)
> Hi All
We now have more nominations than positions for both the Individual Members and the Industry Partners. Nominations close on the 31st Jan 2015 and voting will begin the following day. How to vote will be clearly visible from the [http://members.openehr.org](http://members.openehr.org) area.
The nominees can be seen with a short position statement at:
[http://members.openehr.org/2015-Management-Board-Nominees](http://members.openehr.org/2015-Management-Board-Nominees)
We hope to have...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 2 update - single file templates; finalisation of AOM and ADL for community process.](https://discourse.openehr.org/t/adl-2-update-single-file-templates-finalisation-of-aom-and-adl-for-community-process/13773)
> For those interested in the progress of ADL/AOM 2, I have updated the [wiki pages explaining the single-file template format](https://openehr.atlassian.net/wiki/display/ADL/ADL+2+templates+as+single+artefacts), and showing examples. This page shows some screenshots and [generated OPTs](https://openehr.atlassian.net/wiki/display/ADL/ADL+2+Operational+Template).
Single-file templates are now implemented completely in the ADL 2 Workbench and will be available in the next release, which should...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Foundation Management Board elections Feb 2015](https://discourse.openehr.org/t/openehr-foundation-management-board-elections-feb-2015/15340)
> Individual members of the openEHR Foundation will elect two members of
the new Management Board in an election to be held throughout February
2015\.
In parallel, our industry partners will elect two representatives from
among their number\.
The openEHR Foundation, which is a not\-for\-profit Company registered
in London, will thereafter, for the first time, operate as a trading
entity, in line with the new governance arrangements that have been
agreed\.
The individual membership currently...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 35, Issue 33](https://discourse.openehr.org/t/openehr-technical-digest-vol-35-issue-33/15343)
> Someone in the OpenEHR world created a nice CDA that uses archetypes\. It was
presented at several meetings in the HL7 space, in particular in the patient
care workgroup\.
However, it was a powerpoint\. The HL7 people asked for the ppt, but that was
never delivered\.
The HL7 people asked the openEHR example of CDA with archetypes, but that
was never delivered\.
So the solution was told to be exist \(CDA filled with archetypes\), but not
made available\. So it in fact does not exist\.
The...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [C-CDA was created because they do not know openEHR? :)](https://discourse.openehr.org/t/c-cda-was-created-because-they-do-not-know-openehr/15636)
> Just for the sake of discussion,
See slides 22 and 23:
[http://www.healthit.gov/sites/default/files/c-cda_and_meaningfulusecertification.pdf](http://www.healthit.gov/sites/default/files/c-cda_and_meaningfulusecertification.pdf)
"As disparate SDOs (HL7, IHE, HITSP, etc.) developed CDA IGs, multiple approaches for documenting template requirements began to diverge threatening interoperability…"
IG = Implementation Guide
So my wild guess is they created a new artifact with the same problems...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question on Stack Overflow re openEHR Persistence using RoR Active Record](https://discourse.openehr.org/t/question-on-stack-overflow-re-openehr-persistence-using-ror-active-record/12058)
> Rails Multi Table Inheritance, Polymorphic association or Single Table
Inheritance?
"I'm trying to implement the OpenEHR reference model in Rails
\(ActiveRecord\), but I'm finding some problems, since it works with a
lot of different of different classess, \.\.\."
http://stackoverflow.com/q/27909328/3973688?sem=2
Anyone want to help?
Ian
Dr Ian McNicoll
mobile \+44 \(0\)775 209 7859
office \+44 \(0\)1536 414994
skype: ianmcnicoll
email: ian@freshehr\.com
twitter:...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Nominations Update - Voting starts Feb 1st](https://discourse.openehr.org/t/nominations-update-voting-starts-feb-1st/15637)
> Dear All
We now have 2 nominations for the Industry Partner Management Board positions as well as the four for the Individual Member positions.
The nominees and a short statement are at [http://members.openehr.org/2015-Management-Board-Nominees](http://members.openehr.org/2015-Management-Board-Nominees)
Nominations close at midnight Jan 31st 2015 UMT.
Please join so you can vote and support the Foundation or donate via the Member Pages at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CRUD Restlet](https://discourse.openehr.org/t/crud-restlet/15738)
> I was looking at EHRScape, I should have posted this question there, but the Community-page does not show any communication-means, only adds.
And maybe the question is also generic and are more people thinking about this.
I am wondering about the HTTP-errors, they seem to be used for communicating application-errors.
I think this could be an error.
For example, if you look at the: DELETE /demographics/party/{partyId}
It can return a 404 with explanation: 404 Not found - the specified...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Upcoming EHR procurment in Sweden](https://discourse.openehr.org/t/upcoming-ehr-procurment-in-sweden/16486)
> Hi!
I just want to notify EHR vendors and other interested parties that there is now a (from Swedish perspective) big procurement/buying process starting. It is the three largest healthcare regions in Sweden covering 5 million of Sweden's 9 million inhabitants, it is the regions containing Sweden's largest cities Stockholm (Stockholms läns landsting), Gothenburg (Västra Götalandsregionen) and Malmö (Region Skåne) that together will attempt to get a good deal for a new (probably) all...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL with Demographics](https://discourse.openehr.org/t/aql-with-demographics/15342)
> Hello,
did any off you thought about how a query should look like suppose I want such like this :
"Give me all **female** patients living in **Paris** and with **no allergies** and a **the last labresult of type Kreatine is < 20 but within a year**"
The hardest part is to combine the demographic information with the medical information. Should you be able to do it with AQL?
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Constraining coded values](https://discourse.openehr.org/t/constraining-coded-values/15348)
> Hello all,
Within an openEHR archetype we have a scenario where we have two elements that need to be coded. Element01 and Element02
Element01 can take on values “01”,”02”,”03”,04”
Element02 can take on a subset of values from superset “A” thru “Z”, depending on the value of Element01
How do we express this in an Observation archetype? Is it possible
thanks
**Richard Kavanagh**
Head of Data Standards
Architecture, Standards & Innovation
Health and Social Care Information...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Update on Nominations and Elections - Please join now and take part](https://discourse.openehr.org/t/update-on-nominations-and-elections-please-join-now-and-take-part/16490)
> Dear All
I hope you are having a good 2015! I am sure everyone in Europe is profoundly effected by events in Paris and we have been thinking of you all. Australia has had a taste of acts to cause offense and reaction - but not on this scale.
Thank you to all those who have joined the Foundation so far. The Foundation is now supporting the hosting of the openEHR website and CKM. We have 50 members! We are hoping for 100 or more for the voting process in February.
The current openEHR...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [AW: lists.openehr.org mailing list memberships reminder](https://discourse.openehr.org/t/aw-lists-openehr-org-mailing-list-memberships-reminder/15633)
> Please take me out of your list\!
Dieter Kampe
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [UITemplates for openEHR / towards generic UI definition and automatic generation](https://discourse.openehr.org/t/uitemplates-for-openehr-towards-generic-ui-definition-and-automatic-generation/15346)
> Hi all,
As some might know I did some work around openEHR and UI generation for medical records in the EHRGen app. Last year we finished a project at Facultad de Ingeniería ([http://www.fing.edu.uy/](http://www.fing.edu.uy/)) to improve the solution provided by EHRGen to generate UI forms. The solution was a very rudimentary XML UI definition and a generator just for web desktop (big screens). Now this solutions has been improved a lot, defining a very generic, technology agnostic UITemplate...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Extension of nominations 31 Jan 2015 - and join up now.](https://discourse.openehr.org/t/extension-of-nominations-31-jan-2015-and-join-up-now/15341)
> Happy Xmas everybody,
Thank you to the new members and Industry Partners that have joined up so far. We have three nominations for the Management Board at this stage. Two of the companies have asked for an extension for the joining date to allow transition to the new Calendar year.
The Board considered their request at the last Board meeting and agreed. Consequently the closure date for nominations has been extended to the 31 Jan 2015.
Please join up by going to...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [OpenEHR Information Design Inquiry](https://discourse.openehr.org/t/openehr-information-design-inquiry/15344)
> Greetings,
We (see below for details) are collecting information about projects that implement openEHR based interfaces or forms, in order to write an article about information design in the openEHR standard elements.
Considering that your company/Institution has been developing openEHR based solutions, we would like you to participate in our study by answering this small...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Faster ADL Workbench available](https://discourse.openehr.org/t/faster-adl-workbench-available/16488)
> For those of you feeling the need for speed, there is a new build [available on this page](http://www.openehr.org/downloads/ADLworkbench/home) that greatly speeds it up. This version reduces the error output a fair bit, and you are recommended to go to Tools > Options > Compiler Settings and set them as follows.
You will notice very little output, except for the new progress counter:
Hi All
Simpa Dania is developing an openEHR based system in Nigeria and is keen to have an advocate visit for this major conference:
[http://wacren.net/conference/2015/cfp](http://wacren.net/conference/2015/cfp)
The group includes many universities and other institutions in Africa. Please contact Simpa if you are interested. I am sure it will be of great interest.
Cheers, Sam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Does anyone implemented a transformation between AQL and XML?](https://discourse.openehr.org/t/does-anyone-implemented-a-transformation-between-aql-and-xml/15345)
> Just curious :)
I'm adding version control features to EHRServer ([https://github.com/ppazos/cabolabs-ehrserver](https://github.com/ppazos/cabolabs-ehrserver)) and I want to add some kind of AQL support in the future. Right now we have an internal querying model that abstracts from the physical database and allows the creation of queries for openEHR data from a UI.
My idea is to have some kind of transformation between the EHRServer query model and AQL, and instead of struggle with AQL...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [How do you represent Coronary Angiography and PCI?](https://discourse.openehr.org/t/how-do-you-represent-coronary-angiography-and-pci/15347)
> Hi everyone,
I reckon *openEHR-EHR-OBSERVATION.imaging_exam.v1* archetype has been used to capture results of invasive angiography (on CKM Heart Failure Clinic First Visit Summary template) as well as non-invasive imaging tests. We are modelling for CathLab registry data here in NZ and would like to get your views on how best to represent both angiography and PCI?
To me angiography is an imaging study and PCI is a procedure but they happen simultaneously – I guess I’m asking how best to...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL 2 Workbench release](https://discourse.openehr.org/t/adl-2-workbench-release/16485)
> A [new release](http://www.openehr.org/downloads/ADLworkbench/home) of the ADL Workbench is available. It implements the latest draft of the ADL/AOM 2 formalism, integrates with Github, implements the ADL 2 meta-data model, and supports CIMI archetypes.
## From the [release notes](http://www.openehr.org/downloads/ADLworkbench/release_notes):### 04 December 2014 - ADL 2.0.5 ([Github tag adl_2.0.5](https://github.com/openEHR/adl-tools/tree/adl_2.0.5)) (Jira - [new...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [new openEHR wiki](https://discourse.openehr.org/t/new-openehr-wiki/16489)
> Some users are finding they have no permission on the wiki when they login for the first time at the new location. This is because they have two (or more) ids. The problem can easily be fixed - please email [admin@openehr.org](mailto:admin@openehr.org)
- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [new openEHR wiki and Jira](https://discourse.openehr.org/t/new-openehr-wiki-and-jira/16481)
> The openEHR wiki and Jira are now sited at Atlassian OnDemand (AOD) and the following URLs now redirect there:
- wiki: [http://www.openehr.org/wiki](http://www.openehr.org/wiki)
- Jira: [http://www.openehr.org/issues](http://www.openehr.org/issues)
As far as we can tell, all content is intact and working normally. We will make the old sites available through alternate URLs for a limited time.
However, the new locations are not fully proxied, only redirects for the moment, which means that...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR wiki and Jira issue tracker - readonly for a few hours](https://discourse.openehr.org/t/openehr-wiki-and-jira-issue-tracker-readonly-for-a-few-hours/16482)
> We have performed a migration of the openEHR wiki and Jira standalone instances to Atlassian on demand (AOD). We will undertake some checking for the next few hours, in order to determine if we will put the new site live.
During this period, it would be **preferable if noone** __*updates*__ **either the wiki or Jira issues tracker** (reading is fine).
Once we are done, we will switch the Apache proxy settings to point to the new location and we are then live. An announcement on this will...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Recording of estimates using reference model attributes](https://discourse.openehr.org/t/recording-of-estimates-using-reference-model-attributes/15579)
> Hi everyone,
During a recent review of the Body weight archetype in the Norwegian CKM ([http://arketyper.no/ckm/#showArchetype_1078.36.25](http://arketyper.no/ckm/#showArchetype_1078.36.25)), the following comment was submitted for the «Use» element :
*“The text needs better specification of how the reference model is to be used to record estimates. There are attributes for "accuracy" and "precision" but it is not obvious how these could be used to explicitly record an estimate.”*
This...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [MedInfo 2015 openEHR tutorials](https://discourse.openehr.org/t/medinfo-2015-openehr-tutorials/16487)
> Hi Evelyn,
I’m very interested in the work you’re doing with this. I’ve just got confirmation I can attend Medinfo next year, so I’d be very happy to be part of this discussion there.
I’d also like to contribute to the clinical modelling tutorial/workshop, as outlined on the wiki page. Has anyone taken the lead on submitting the proposals? If so, is there anything I can do? If not, is anyone planning to?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issue with terminology bindings with SNOMED-CT](https://discourse.openehr.org/t/issue-with-terminology-bindings-with-snomed-ct/15338)
> Hello,
I’m trying to get a terminology binding to an external terminology of SNOMED-CT.
I’ve already read some articles about mapping Entries afterwards onto SNOMED-CT.
This is not what I want.
I would like to have Live query to SNOMED-CT while entering the data into an Archetype.
I’ve read about TQL which is used for query an Terminology set and that OTS and the UMLS can be used but I just can’t figure I what I have to do to realise that.
I’m using the Ocean ArchetypeEditor.
Thanking you...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Finalising archetype meta-data](https://discourse.openehr.org/t/finalising-archetype-meta-data/15330)
> There is a [test archetype here ](https://github.com/openEHR/adl-archetypes/blob/master/ADL15-reference/features/meta_data/openehr-test_pkg-WHOLE.full_meta_data.v0.0.1.adls)that shows an example of proposed new meta-data items.
Things to notice:
- 'rm_release=1.0.2' in the top line. Rm_release is now a mandatory item in ADL 2 (but easy to synthesise in converters)
- 'copyright' is now at the outer level, before it was in the translatable part, i.e. with 'keywords' etc - now there is only...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 33, Issue 29](https://discourse.openehr.org/t/openehr-technical-digest-vol-33-issue-29/16480)
> Dear Jan,
I am referring to the generic knowledge for procedures\. Not to the local variations, the latter must be handled in the system according the reference model\.
Let's stop the mails on it, I think it is clear to all what the options are\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetype UIDs](https://discourse.openehr.org/t/archetype-uids/16484)
> We are finalising the last details of the ADL 2/AOM 2 specifications for a Trial release. One detail is the question of UIDs. The current AOM 2 specification shows two UIDs: provenance_id and instance_id. The former is created at archetype creation and never updated, even with major archetype version changes, meaning that it can always be used to track an archetype, including all versions and copies, through time.
The latter is updated every time anything at all changes with the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 33, Issue 24](https://discourse.openehr.org/t/openehr-technical-digest-vol-33-issue-24/15335)
> Response to message: Message: 3
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 33, Issue 23](https://discourse.openehr.org/t/openehr-technical-digest-vol-33-issue-23/15632)
> Hi Pablo, Thomas,
The attestation knowledge getting lost except perhaps in Dipak and Sam's minds is more often occurring in clinical models\.
In the ISO technical specification for detailed clinical models there is an option to include such specific information in one of the clinical fields as evidence base, instruction or interpretation\. Best used it it is a clinical mind required\.
Or in traceability to other standards if a specific guideline or protocol is used, or issues if it is a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ORIGINAL_VERSION.attestations is needed in the IM?](https://discourse.openehr.org/t/original-version-attestations-is-needed-in-the-im/15631)
> I'm reviewing the versioning aspects of the IM for a new course I'm giving, and I'm not understanding why we need more than one attestation per ORIGINAL_VERSION.
A composition shouldn't be signed by just one person?
Also, I found a bug:
6.2.5. Contributions (in common_im page 41)
attestation of item: a new ATTESTATION is added to the attestations list of an existing ORIGINAL_VERSION; the ATTESTATION.commit_audit.change_type is set to the code for ‘attestation’.
Should be...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Postulate: DV_QUANTITY should be modelled with fewest possible units](https://discourse.openehr.org/t/postulate-dv-quantity-should-be-modelled-with-fewest-possible-units/15327)
> I want to try out a postulate regarding modelling of datavalues, and more specific DV_QUANTITY.
The postulate is:
**Postulate 1: A data type of DV_QUANTITY should be modelled with fewest possible units!**
Reason behind this is to make queries and reasoning over the values easy. This makes it both faster and safer building sustainable software and systems using these values.
I also think that converting between i.e. grams and kilos should be done in the client (user interface / integration...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Another meta-data requirement from CIMI](https://discourse.openehr.org/t/another-meta-data-requirement-from-cimi/15326)
> In CIMI, there are now some thousands of archetypes, 90% converted from Intermountain CEMs\. We can start converting openEHR archetypes to CIMI form as well, for contribution to CIMI\. To provide traceability, we probably are going to need a new meta\-data item where some information about model conversion/import can be represented\. In the current CIMI generated archetypes \(not the reference ones\), it could be information like:
"converted with IHCModelConverter v3\.134\.0\.78, on...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR Confluence and Jira - Atlassian on Demand is available to us](https://discourse.openehr.org/t/openehr-confluence-and-jira-atlassian-on-demand-is-available-to-us/16483)
> Historically Atlassian has provided openEHR Foundation with a 'community licence' to use Confluence and Jira for free, which has been great, and much appreciated. However, the downside has been the system administration side of things, and we have had problems in the past with stability and occasionally with upgrades.
It turns out that openEHR qualifies for Atlassian 'open source' status, and they have now approved our use of Atlassian On Demand (AOD) for Jira and Confluence. This would mean...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes - new meta-data elements for 3rd party copyrights?](https://discourse.openehr.org/t/archetypes-new-meta-data-elements-for-3rd-party-copyrights/15331)
> Something that has become clear in CIMI, and will affect openEHR, 13606 and most likely any archetype developer is that acknowledgements of 3rd party copyrights and trademarks need to be made. The most obvious common one is likely to be for SNOMED CT codes in archetype bindings (Stan Huff at Intermountain is still working on whether such acknowledgements are needed for LOINC codes). However, it could be for anything, e.g. rights to use a scale like Barthel or Waterlow.
At the moment there is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [My first steps in setting the OpenEHR Server](https://discourse.openehr.org/t/my-first-steps-in-setting-the-openehr-server/15203)
> Dear Fellows,
I am just starting my OpenEHR journey and I have successfully installed the server\. However, I got on error message as one of the groovy grail libraries cannot be identified:
org\.codehaus\.groovy\.grails\.commons\.ApplicationHolder\.
Any clue on how to go about this error?
best regards,
Osama
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.4 migration roadmap - a start](https://discourse.openehr.org/t/adl-1-4-migration-roadmap-a-start/15328)
> I have started an [ADL 1.4 migration roadmap page](http://www.openehr.org/wiki/display/ADL/ADL+1.4+Migration+Roadmap). This currently consists of a list of all changes made from 1.4 => 2.0 (as it now is), with an idea of which retrospective interim version (i.e. 1.5, 1.6, 1.7 etc) the change could go in. Although this isn't the way things are normally done, there is one major advantage: the way things are working now in ADL/AOM 2 are pretty good and have been re-engineered a few times over...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem-oriented records and querying by problem](https://discourse.openehr.org/t/problem-oriented-records-and-querying-by-problem/15630)
> Hi, another question related to querying:
I have a case of problem-oriented records, where I need to query all the COMPOSITIONS related to a specific problem (evolutions, controls, etc).
Since we have a Problem List persistent archetype that records OBSERVATIONS about the health problems:
- Would it be a good solution to use LINKs between those OBSERVATIONs and the COMPOSITIONs related to those problems in order to solve the "query COMPOSITIONS by health problem"?
Is there another...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Doctor specialty in the IM](https://discourse.openehr.org/t/doctor-specialty-in-the-im/15333)
> Hi, I have a small question: if I need to record the specialty of an attending doctor:
1. Should I use the PARTICIPATION.function attribute?
2. Another option is to have that in the CAPABILITY.credentials from the demographic model.
3. And a third option I can think of is to use EVENT_CONTEXT.other_context structure.
4. Other?
My idea is to let users to find records by the specialty of the composer.
In the 1st option I need to create a PARTICIPATION for the composer so I can use the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Seminar in Kyoto](https://discourse.openehr.org/t/seminar-in-kyoto/16479)
> Dear openEHR colleagues,
I am happy to announce that we publish the movies of the seminar
"Design of clinical models and standards" by Prof\. Dipak Kalra and Dr
Stanley Huffl, we had in this May in Kyoto, Japan\.
http://ocw.kyoto-u.ac.jp/en/international-conference-en/ehr/videos
It is our pleasure if you like these movies\.
Best regards,
Shinji KOBAYASHI
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XSL transform files for other languages?](https://discourse.openehr.org/t/xsl-transform-files-for-other-languages/15577)
> Hi everyone,
Are there any alternative XSL transform files like tdo-csharp.xsl but for other languages available anywhere? Specifically, a VB.net one would be very useful.
Kind regards,
**Silje Ljosland Bakke**
Coordinator, National Editorial Board for Archetypes, National ICT Norway
Adviser, R&D dept, E-health section, Bergen Hospital Trust
Tel. +47 40203298
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Templates and RM](https://discourse.openehr.org/t/templates-and-rm/15332)
> Last week we had an interesting discussion about templates/standards, and some related issues\.
Thomas had written a blog related to this discussion,
\( http://wolandscat.net/2014/10/25/what-is-a-standard-legislation-or-utilisation \)
and in the comments he linked to this example as being an example of what a template is \(or will be\) in...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Nominations are open for the openEHR Foundation Management Board (Closes 28th December)](https://discourse.openehr.org/t/nominations-are-open-for-the-openehr-foundation-management-board-closes-28th-december/15629)
> Dear All,
On behalf of the interim Board of the openEHR Foundation we are very pleased to invite each of you to become an Individual Member of the Foundation.
You can __*join the openEHR Foundation*__ here: [http://members.openehr.org/join-us](http://members.openehr.org/join-us)
The engagement of Individual Members is key to the Foundation moving to an operational mode and establishing the election of members to the new Management Board, which will be responsible for the operation of the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Any prep for MIE 2015 in Madrid?](https://discourse.openehr.org/t/any-prep-for-mie-2015-in-madrid/15325)
> Hi, I was just wondering if there’s any activity planned for [MIE 2015](http://www.mie2015.es/) in next May – the deadline for submissions has just been extended:
**Deadline for Papers and Posters (indexed) is extended to November 17th, 2014**
**Deadline for Workshops, Panels, Special events (nonindexed) proposals is December 1st.**
If nothing I guess there will be some individual participations – I’m keen to attend and coordinate things.
Cheers,
-koray
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Defining multiple constraint bindings in AOM/ADL 1.4](https://discourse.openehr.org/t/defining-multiple-constraint-bindings-in-aom-adl-1-4/15316)
> Hello,
A very direct question: Why it is not possible to define multiple constraint bindings for the same archetype node and the same terminology in AOM/ADL 1.4? I know in AOM/ADL 2.0 the management of these constraints change completely, but the following is the situation (limitation?) in existing 1.4.
For a given textual node, it is possible to define multiple term definitions (atNNNN codes), for example:
DV_CODED_TEXT matches {
defining_code matches...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Relationship openEHR/CIMI](https://discourse.openehr.org/t/relationship-openehr-cimi/15322)
> Hi everyone,
Recently Gartner released [a survey of EHR suppliers in the Norwegian market](http://www.regjeringen.no/pages/38845466/gartner_survey_ehr_suppliers_systems_norwegian_market.pdf), as commissioned by the Norwegian Ministry of Health and Care Services. In the report, they stated the following (bullet and footnote, page 26 of PDF file):
“OpenEHR and archetypes is an example of CIMIs1 (Clinical Information Modeling Initiative). CIMI and thus OpenEHR are regarded by Gartner to be an...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Volume of distinct "artifacts" made in openEHR](https://discourse.openehr.org/t/volume-of-distinct-artifacts-made-in-openehr/16478)
> Does anyone have an overview over current production of archetypes?
Content, provenance, versions \(language\)?
If I have a part/component of an archetype, \- can I search for overlaps/differences?
Best regards,
\-\-\- Øystein Nytrø
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Error in ADL workbench](https://discourse.openehr.org/t/error-in-adl-workbench/15320)
> Hi there,
just for the case it won't get broad attention in the issue tracker (It seems to be the first time an issue got submitted :): I got some trouble with the most recent version of the ADL workbench. Has anyone else faced this issue?
[https://github.com/openEHR/adl-tools/issues/1](https://github.com/openEHR/adl-tools/issues/1)
Are there any builts of former versions ready to download or would I have to build them myself?
Best,
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 32, Issue 62](https://discourse.openehr.org/t/openehr-technical-digest-vol-32-issue-62/16475)
> I agree Bert,
OpenEHR is not a standards developing organization\. It creates specifications\.
These are found to be useful by some\.
But are sometimes in conflict with standards\.\.\.\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [OpenEHR University](https://discourse.openehr.org/t/openehr-university/15623)
> Hi All,
My company \(Sabaoth Technologies Ltd\) is interested in creating and
funding The OpenEHR University\.
The University would be a training portal for developers and clinician to
learn openEHR in three broad categories: beginner, intermediate and
advanced courses\.
It would be online and consist of multimedia content/screenshots for
learning and tutorials/test for assessment\. It eould be designed to be
self paced\.
We are looking for resource persons who would commit to developing...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Our work Introduction and New online archetype and template tooling project](https://discourse.openehr.org/t/our-work-introduction-and-new-online-archetype-and-template-tooling-project/16474)
> Hello, I'm Choi Dong-Won.
I have been joining in teleconference as an observer, and take a great interest in this project.
I am a member of [nousco.co](http://nousco.co/).,ltd.([www.nousco.com](http://www.nousco.com/))
We are developing the EHR platform based on openEHR.
As a developer, I am developing Template Designer.
I would like introduce our work to you and hope to give me your advice, opinion or comment.
And I want to contribute to tooling project.
Our project's name is the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [template formal definition](https://discourse.openehr.org/t/template-formal-definition/15317)
> Hi,
I must have been overlooking it all the time, but I cannot find the formal definition of the OET\-XML
Thanks for helping me out\.
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Second review round commenced for the joint FHIR/openEHR Adverse Reaction Risk archetype](https://discourse.openehr.org/t/second-review-round-commenced-for-the-joint-fhir-openehr-adverse-reaction-risk-archetype/14327)
> Hi everyone,
I have just sent out the second review invitations to those who have registered an interest in the joint FHIR/openEHR Adverse Reaction Risk archetype. You can view the latest version here: http://www.openehr.org/ckm/#showArchetype_1013.1.1713
The resolution process was long and detailed and took somewhat longer than the Editors had anticipated, however we are very pleased with the way that the archetype is taking shape. There are some tensions between the way that the HL7...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [November openEHR modelling course in Bergen, Norway](https://discourse.openehr.org/t/november-openehr-modelling-course-in-bergen-norway/16477)
> Dear openEHR clinical community,
To facilitate cross border contact between openEHR communities as well as distribute costs, National ICT Norway would like to invite the international community to a two day course on openEHR and practical archetype/template modelling taking place in late November, in Bergen, Norway.
More information:
**•** **Course Content:**
- Overview of openEHR
- Practical management of archetypes
- Practical modelling of archetypes
- Practical modelling of templates
•...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype Sprint reviews now active](https://discourse.openehr.org/t/archetype-sprint-reviews-now-active/14331)
> Hi everyone,
A quick update on progress with the archetype sprint…
Archetype reviews for the following are now active:
· CLUSTER.device
· COMPOSITION.encounter
· SECTION.adhoc
· OBSERVATION.indirect_oximetry
· EVALUATION.adverse_reaction_fhir – the results of this joint openEHR & HL7 FHIR review will be used to derive a pure openEHR archetype that will be published with content common to the corresponding FHIR resource.
If you would like to participate in the review of these...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Board Communique](https://discourse.openehr.org/t/board-communique/15625)
> Hi Everyone
The openEHR interim Management Board met on Tuesday last week to consider how we finalise the move to a new organisational structure. We have had a lot of feedback from the wonderful meeting in Oslo and understand that there are now a range of issues that people and industry want to address collectively. Thank you to DIPS in Norway for hosting this meeting.
The final governance arrangements are clearly of concern to some parties. The Board has decided to have a teleconference...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New online archetype and template tooling project](https://discourse.openehr.org/t/new-online-archetype-and-template-tooling-project/15324)
> Dear openEHR community!
The openEHR 2014 roadmap meeting in Norway agreed on starting a community tooling project to create a new open source based web-accessible archetype and template editing framework/workbench capable of ADL 2.0 (formerly named ADL 1.5).
A wiki-page contains the basic info you need to join or monitor this...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR 2014 roadmap meeting - report](https://discourse.openehr.org/t/openehr-2014-roadmap-meeting-report/15624)
> The report of this meeting is now available [here on the website](http://www.openehr.org/news_events/2014-09-16_openehr_meeting_report).
Some of the key outcomes:
- **ADL/AOM 1.5 will be renamed to ADL 2**, due to breaking changes being added in recent times (including CIMI-related)
- A **next generation archetype tooling project** will be commenced that will replace all the current modelling tools.
- The **specifications will be converted to an ASCII-based format within a tool chain**,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Is there an archetype to represent images obtained in imaging exams?](https://discourse.openehr.org/t/is-there-an-archetype-to-represent-images-obtained-in-imaging-exams/15719)
> Hi,
I have some problems in using the openEHR\-EHR\-OBSERVATION\.imaging\_exam\.v1 archetype from CKM\. The information about images is placed under the protocol section\. Is it better to view images as observation data obtained from patient and put images into standalone observation archetype?
Thanks
Li Wang
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR/FHIR Adverse Reaction archetype review progress](https://discourse.openehr.org/t/openehr-fhir-adverse-reaction-archetype-review-progress/14330)
> Dear colleagues,
Apologies for cross posting.
*(Note to Webmaster: Perhaps we need a Clinical Modelling list, or guidance that we can subvert the ‘clinical ‘ list for modelling purposes. But that is not my core reason for posting)*
We are very pleased to announce that the Editors have completed resolution of all comments from the first review round and are about to send the revised archetype out for the second review round in the next day or so.
This resolution process has not been...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org outage - GMT (UTC+1) 13:30](https://discourse.openehr.org/t/openehr-org-outage-gmt-utc-1-13-30/16472)
> the openEHR server will be restarted at GMT 13:30; down time should be around 10 mins\. This affects the website, Jira and the wiki\. It does NOT AFFECT openEHR\.org CKM
please email admin@openehr\.org if this poses a problem\.
thanks
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [notification](https://discourse.openehr.org/t/notification/15622)
> I don't know who and where to notify but the Wiki\-server has a problem
http://www.openehr.org/wiki/
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 32, Issue 31](https://discourse.openehr.org/t/openehr-technical-digest-vol-32-issue-31/15318)
> Take care of a big caveat please: all health information systems start and
end with the human being\. We should use the IT support that Thomas suggests
where possible, but\.\.\.\. to the extend that humans cannot make mistakes\. And
the governance of archetypes / DCMs / valuesets / etc does require human
intervention and hence human understanding\. So naming conventions are
important and are a different beast than the versioning of the file /
content\.
Thomas' trick with the software...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 30, Issue 19](https://discourse.openehr.org/t/openehr-clinical-digest-vol-30-issue-19/16469)
> The ISO TS 13972 is in publication stage\.
It States that Detailed Clinical Models shall have versioning identified\. I am practicing a v0\.1 v0\.2 etc FOR any development and verification and validation phase and from 1\.0 it is safe to use for patient care\.
I am happy that archetypes will soon allow versioning, that has been one factor for not using them because you never know what you get\. \(Old, new, unknown changes, different with same name etc\)\. Too dangerous for patient...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Problem saving in archetype editor](https://discourse.openehr.org/t/problem-saving-in-archetype-editor/14332)
> I’m having trouble saving a particular archetype from Archetype Editor. Other archetypes are apparently saved without issue. I’m getting the following error message. The archetype is attached to this email. I’d be extremely happy if anyone could tell me why this happens and how to fix it… J
Kind regards,
**Silje Ljosland Bakke**
Coordinator, National Editorial Board for Archetypes, National ICT...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Licensing of specs and artifacts](https://discourse.openehr.org/t/licensing-of-specs-and-artifacts/15620)
> Hi everyone,
In light of [the recent re-licensing of FHIR](http://www.healthintersections.com.au/?p=2248) using the Creative Commons CC0 Public Domain Dedication as well as the discussion about licensing at the [2014 openEHR Roadmap Meeting](http://www.openehr.org/wiki/display/oecom/September+2014+Roadmap+Meeting) in Lillestrøm on September 16 and 17, I’d like to restart the discussion on licensing of openEHR specifications and artefacts (mainly archetypes, but also potentially templates and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype Naming proposals - do we need V0?](https://discourse.openehr.org/t/archetype-naming-proposals-do-we-need-v0/15726)
> Hi all,
Apologies for cross-posting in both clinical and technical but this does neatly cross that divide.
We are getting close in CKM to implementing the ADL1.5 archetype naming /versioning rules proposed at
[http://www.openehr.org/wiki/display/ADL/Knowledge+Artefact+Identification](http://www.openehr.org/wiki/display/ADL/Knowledge+Artefact+Identification)
mostly by adding the metadata to the ADL other_details section, which means we can carry the information in ADL 1.4 archetypes...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR archetype publication sprint IS GO!](https://discourse.openehr.org/t/openehr-archetype-publication-sprint-is-go/16473)
> Hi everyone,
With great pleasure we can now announce that the promised program to publish a significant number of core archetypes in the openEHR international CKM has kicked off today, resourced by the founding 6 openEHR [Industry Partners](http://www.openehr.org/industry_partners/).
We now have Editors that will be focussed on delivering a selected, core set of 69 clinical archetypes that cover the breadth of content required for clinical continuity of care, such as health summaries and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Missing DV_PROPORTION validity rule?](https://discourse.openehr.org/t/missing-dv-proportion-validity-rule/16470)
> Hi, I'm adding support to more datatypes to EHRServer and was surprised that the DV_PROPORTION specs doesn't define that the denominator should be != 0.
Is this on purpose?
Is _infinite_ a valid value for DV_PROPORTION.magnitude()?
Or is just a missing validity rule?
thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes vs. Templates, archetype version in slots](https://discourse.openehr.org/t/archetypes-vs-templates-archetype-version-in-slots/15621)
> Hi,
While reviewing CKM archetypes we found that slots are usually
pointing to other v1 archetypes\.
Shouldn't archetype slots point to any version of the included
archetypes and not a single archetype? Shouldn't be Templates the ones
pointing to an specific archetype?
This is also true even for "archetype and all its children" slots
\(e\.g\. openEHR\-EHR\-OBSERVATION\\\.
respiration\(\-\[a\-zA\-Z0\-9\_\]\+\)\*\\\.v1\) in
which the v1 seems to be even more misplaced as it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes vs. Templates, archetype version in slots](https://discourse.openehr.org/t/archetypes-vs-templates-archetype-version-in-slots/15323)
> Hi,
While reviewing CKM archetypes we found that slots are usually
pointing to other v1 archetypes\.
Shouldn't archetype slots point to any version of the included
archetypes and not a single archetype? Shouldn't be Templates the ones
pointing to an specific archetype?
This is also true even for "archetype and all its children" slots
\(e\.g\. openEHR\-EHR\-OBSERVATION\\\.respiration\(\-\[a\-zA\-Z0\-9\_\]\+\)\*\\\.v1\) in
which the v1 seems to be even more misplaced as it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Texts about transforming between openEHR and other formalisms](https://discourse.openehr.org/t/texts-about-transforming-between-openehr-and-other-formalisms/15319)
> Hi,
I’m wondering if anyone could point me to any publically available texts about transforming archetypes (and templates) from openEHR to other formalisms. Academic publications exploring the (im)possibilities of automatic transformation would be ideal.
Kind regards,
**Silje Ljosland Bakke**
Coordinator, National Editorial Board for Archetypes, National ICT Norway
Adviser, R&D dept, E-health section, Bergen Hospital Trust
Tel. +47 40203298
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with version and specialisation](https://discourse.openehr.org/t/problem-with-version-and-specialisation/15321)
> > Dear All,
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [2014 Roadmap meeting conclusion](https://discourse.openehr.org/t/2014-roadmap-meeting-conclusion/14328)
> The 2014 Roadmap meeting has now concluded. Thanks to all who attended (some 32 or so attendees, plus online participation).
The aim for the meeting was to generate a) a roadmap for tooling, specifications and clinical modelling for the next 6-12 months and b) to generate as many actions and decisions as possible on pressing outstanding issues. We achieved much of what was needed, with some further specific meetings and discussions agreed to to finalise various roadmap details.
Most of what...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [roadmap 2014 meeting streaming](https://discourse.openehr.org/t/roadmap-2014-meeting-streaming/15309)
> All who are interested / wanted to follow the meeting, our meeting was moved to a different venue, and the only streaming we were able to run LYNC, which is a Microsoft tool\. This won't work for people on Linux unfortunately\.
We probably can't do anything about this tomorrow \(especially as the wifi is somewhat limiting at the venue\), but we will upload all the sessions as mp4s or similar, so at least you will be able to listen to the meeting proceedings\.
We are also live...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR roadmap meeting streaming link](https://discourse.openehr.org/t/openehr-roadmap-meeting-streaming-link/15307)
> we now have a link to a LYNC session which should be broadcasting the meeting\.
https://meet.dips.no/bna/P5C52K35
We will have someone watching the chat, so if there are questions, please raise them via the chat\.
\- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR 2014 roadmap meeting - Lillestrom / Oslo 16/17 September](https://discourse.openehr.org/t/openehr-2014-roadmap-meeting-lillestrom-oslo-16-17-september/13163)
> The openEHR 2014 roadmap meeting gets underway tomorrow, and runs for 2 days, just outside of Oslo. The [agenda (as of today ;-) is here](http://www.openehr.org/wiki/display/oecom/September+2014+Roadmap+Meeting), for those interested in following. This will change somewhat organically, since this is a working meeting. Some media details:
- We are going to try to create a live stream of at least audio, with audience participation by chat channel. We'll notify details of that here as soon as...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Hello I'm Din, interesting in openehr](https://discourse.openehr.org/t/hello-im-din-interesting-in-openehr/16471)
> I want to make knowlege server.
1. how can i get [openehr.org/ckm](http://openehr.org/ckm) source? is it open source?
1-1. is it this? [https://github.com/openEHR/openehr-website](https://github.com/openEHR/openehr-website)
2. does ckm have licence?
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [How to model relationship between archetypes?](https://discourse.openehr.org/t/how-to-model-relationship-between-archetypes/15304)
> Hi,
I'm try to understand how to model relationship between archetypes. For example, there are two archetypes in CKM,
openEHR-EHR-INSTRUCTION.request-lab_test.v1 and
openEHR-EHR-OBSERVATION.lab_test.v1
My question is, how to express the relationship that openEHR-EHR-OBSERVATION.lab_test.v1 relates to openEHR-EHR-INSTRUCTION.request-lab_test.v1?
I tried possible methods:
1. Add an attribute in openEHR-EHR-OBSERVATION.lab_test.v1 referring to uid of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Commits and Contributions](https://discourse.openehr.org/t/commits-and-contributions/15308)
> Hi, I'm working on EHRServer, trying to improve how the XML is committed and processed to simplify querying.
Right now I have a web app that commits a list of VERSIONs to the EHRServer. That service is based on the Ocean's commitContribution service [http://www.openehr.org/wiki/display/spec/Ocean+Informatics+EHR+Service+Interface](http://www.openehr.org/wiki/display/spec/Ocean+Informatics+EHR+Service+Interface)
The CONTRIBUTION instance for the committed VERSIONs is created by the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [transfer/move archetype?](https://discourse.openehr.org/t/transfer-move-archetype/15312)
> Hi again,
I was wondering if somebody has put some thoughts on a "patient transfer" archetype which would serve to record the transfer of patients between different wards within a hospital. Why would it be interesting to have this information archetyped? For example we'd like to calculate the time that a catheter has been applied at the ICU. As a catheter often doesn't get removed when the patient leaves the ICU, we need to calculate the time by using both the catheter documentation and the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ALS archetype challenge.](https://discourse.openehr.org/t/als-archetype-challenge/14315)
> Hi all,
I took over ALS ice bucket challenge from Dr Sam Heard nomination\.
In addition, I would like to make archetypes for ALS and neuron
degenerative disorders\.
Please see here, for brief summary of my challenge\.
http://ehr.design.kyoto-u.ac.jp/201409_als.html
I am considering about ICF\(International Classification of
Functionality\) to evaluate and record functionality\.
Do you have any idea about to this challenge?
Shinji KOBAYASHI
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Indirect Oximetry](https://discourse.openehr.org/t/indirect-oximetry/15313)
> Hi Folks,
quick question (hope this has not been asked before. Is there a way to quickly search in the archive?). As far I'm able to work with the CKM, it seems it has never been discussed why events in the indirect oximetry archetype have a limit of 1. Is there a reason for this limitation while other vital parameters I know of may contain an unlimited number of events?
I know that I would be able to change the archetype for our use case (automized vital parameter monitoring at ICUs) but I...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Details of meeting in Istanbul](https://discourse.openehr.org/t/details-of-meeting-in-istanbul/15619)
> Dear All
A few of us will be meeting at the Larespark Hotel, Istanbul
We will meet in the AKIK Meeting Room between 14:00 and 17:00
Would be good if you can let us know you will attend at:
[http://members.openehr.org/event-1731059](http://members.openehr.org/event-1731059)
Hope to see some of you there.
Cheers, Sam
Dr Sam Heard
Chairman, openEHR Foundation
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Meeting on Saturday Prior to MIE](https://discourse.openehr.org/t/meeting-on-saturday-prior-to-mie/15618)
> Hi Everyone
We plan to hold the openEHR meeting prior to MIE at 2.00pm at the Larespark Hotel Istanbul. Please register at the link below so we can make adequate preparations.
[http://members.openehr.org/events](http://members.openehr.org/events)
Look forward to seeing you there.
Cheers Sam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Small question about commits and AUDIT_DETAILS.system_id](https://discourse.openehr.org/t/small-question-about-commits-and-audit-details-system-id/15311)
> Hi,
I'm reviewing the common_im specs, and the description for AUDIT_DETAILS.system_id is: "Identity of the system where the change was committed. Ideally this is a machine- and human-processable identifier, but it may not be".
I have an architecture like this:
EMR: data input, transactional, specific for 1 medical specialty
Mobile APP: data input, transactional, for patient data input
EHR: where commits are done to the patient EHR from EMR, Mobile APP and other systems
All the system...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New Membership and Partnership Arrangements](https://discourse.openehr.org/t/new-membership-and-partnership-arrangements/16464)
> openEHR Foundation Update
The openEHR Foundation is pleased to announce a number of changes in time for the MIE conference. These changes aim to provide stable, democratic and transparent governance of the Foundation into the future while raising sufficient funds to provide the openEHR community with basic support and advocacy.
The changes are:
1. Members will be able to nominate and vote for two members of the Management Board. In order to nominate and to vote, Members will need to...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR website in Portuguese now online](https://discourse.openehr.org/t/openehr-website-in-portuguese-now-online/14317)
> thanks to the efforts of Jussara Rotzsch and her team in Brasil, and Adriana Danilakova working on the openEHR website, the initial Portuguese language version of the main openEHR website is now online. It is indicated by the Brasilian flag (hopefully openEHR users from Portugal and other PT-language countries can live with this!).
The translation is not complete of course, but what is important is that:
- PT-language translation...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR Information Design](https://discourse.openehr.org/t/openehr-information-design/16466)
> Greetings,
We (see below for details) are collecting information about projects that implement openEHR based interfaces or forms, in order to write an article about information design in the openEHR standard elements.
Considering that your company/Institution has been developing openEHR based solutions, we would like you to participate in our study by answering this small...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL Workbench on Linux amd64](https://discourse.openehr.org/t/adl-workbench-on-linux-amd64/15306)
> If you are attempting to run the ADL Workbench on 64 bit systems with MultiArch support you will need to setup support for the 32 bit libs and install them.
For example Ubuntu 14.04LTS, you will probably need to perform these steps:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
sudo apt-get install libgtk2.0-0:i386
Tom, you may want to add this to the installation instructions.
HTH,
Tim
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Intro to openEHR clinical modelling training course, London, September](https://discourse.openehr.org/t/intro-to-openehr-clinical-modelling-training-course-london-september/15190)
> Hi everyone,
Just to let you know that Ocean will be holding a training course in London on September 8 & 9, 2014.
“Clinical Modelling, openEHR style” is an introductory course on clinical modelling. Details here: [https://2014-openehr-training-london.eventbrite.com.au](https://2014-openehr-training-london.eventbrite.com.au)
Regards
Heather
**Dr Heather Leslie**
MBBS FRACGP FACHI
Director/Consulting Lead
**[Ocean Informatics](http://www.oceaninformatics.com/)**
Phone - +61 418 966...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Meeting from 2pm on Saturday August 30th in Istanbul](https://discourse.openehr.org/t/meeting-from-2pm-on-saturday-august-30th-in-istanbul/16465)
> Hi Everyone
Some of the key Industry Partners and community members will be meeting in Istanbul before MIE and have a social evening on Saturday the 30th of August. We are looking for a place to meet close to the conference that would allow for discussion and then somewhere to relax and have a few drinks and a chat at about 5pm.
Please let me know at [sam.heard@openEHRFoundation.org](mailto:sam.heard@openEHRFoundation.org) if you would like to attend and/or you know an ideal venue. I will...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [MedInfo 2015 openEHR tutorials](https://discourse.openehr.org/t/medinfo-2015-openehr-tutorials/15127)
> Hi all!
Since next MedInfo is in Brazil (near Uruguay) I'll be attending for sure. I also might present a paper or two and want to propose an openEHR related tutorial.
Is other people planning to present openEHR papers or tutorials? It would be great if we can coordinate tutorials (and topics) together so we can have our "openEHR day" at MedInfo.
What do you think?
We have 1 year to plan this, and that's not a lot of time!
I hope we can join forces and do something nice for the south...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR roadmap meeting Sep 2014](https://discourse.openehr.org/t/openehr-roadmap-meeting-sep-2014/16468)
> This is to announce a [face to face openEHR 2014 roadmap meeting in Oslo](http://www.openehr.org/wiki/display/oecom/September+2014+Roadmap+Meeting) aimed at kick-starting the roadmap for specifications, implementation, clinical model development, and particularly, the overall platform vision for the next 18 months or so. See the link for full meeting details.
DIPS asa, a major Norwegian EHR vendor and openEHR implementer has very kindly agreed to host the meeting at their Oslo offices....
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Reminder: joint FHIR/openEHR review of Allergy/Intolerance closes July 28.](https://discourse.openehr.org/t/reminder-joint-fhir-openehr-review-of-allergy-intolerance-closes-july-28/16467)
> Hi everyone,
If you haven’t already, a gently reminder that it is not too late to get involved in the joint Allergy/Intolerance review. Editors will start collating your feedback early next week.
Instructions are below.
Regards
Heather
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EHR_STATUS in XSD](https://discourse.openehr.org/t/ehr-status-in-xsd/15616)
> Hi,
I was not able to find the XSD in which EHR\_STATUS is\.
Or isn't it defined in an XSD?
Thanks
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR at MIE 2014](https://discourse.openehr.org/t/openehr-at-mie-2014/15128)
> Just wondering what openEHR presentations/papers/workshops we can expect at MIE in Istanbul next month?
It might be good to pull together a web page as a resource alongside previous conference offerings.
I will be attending but not presenting
Regards
Heather
**Dr Heather Leslie**
MBBS FRACGP FACHI
Director/Consulting Lead
**[Ocean Informatics](http://www.oceaninformatics.com/)**
Phone - +61 418 966 670
Skype - heatherleslie
Twitter - @omowizard
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The joint openEHR/FHIR review of Allergy/Intolerance is open](https://discourse.openehr.org/t/the-joint-openehr-fhir-review-of-allergy-intolerance-is-open/15617)
> hi All
We have opened the joint openEHR/FHIR review of Allergy/Intolerance:
http://omowizard.wordpress.com/2014/07/11/inaugural-joint-archetype-review-by-hl7-openehr/
http://www.healthintersections.com.au/?p=2169
The review is open until July 28th\. We would like to encourage
everyone to contribute to the review; whether you are a clinician, a
programmer, a systems analyst\. Clinicians, it would be great if you
can reach out to your systems vendor and encourage them to
participate\.
I...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Potential interest in establishment of an academic CKM instance?](https://discourse.openehr.org/t/potential-interest-in-establishment-of-an-academic-ckm-instance/15104)
> Hi everyone,
*I cautiously send this email as I’m aware that it can be perceived to border on the line between commercial and community, so request if anyone is interested in following through with my idea to email me privately and not use the list any further.*
I’ve been approached by someone requesting an academic CKM instance that could be used for university teaching purposes.
So I am curious to see if there was broader interest in establishing a shared academic CKM for use by...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Chinese archetypes](https://discourse.openehr.org/t/chinese-archetypes/15297)
> Hi,
I was wondering whether there are any Chinese archetypes \(or Chinese translations\) available beyond the 8 archetypes listed in the Clinical Knowledge Manager \[1\] ?
Thanks,
Ralph van Etten
MEDvision360
\[1\]: http://openehr.org/ckm/
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR ecore model?](https://discourse.openehr.org/t/openehr-ecore-model/15298)
> Hi all,
Is there an "official" or at least "proposed" openEHR ecore model? It
seems to be stated in the GitHub description but I haven't been able
to find it there\.
I have found one openEHR ecore model in another repository, but I
don't know who created it or it correctness\.
https://github.com/Malinoski/IMT/blob/master/OpenEHR2RichUbi.v5/metamodels/openehr/openehr2008v3.ecore
Regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [BMM (Basic Meta-Model) upgrade](https://discourse.openehr.org/t/bmm-basic-meta-model-upgrade/14314)
> The openEHR BMM format which we use for the computable representation of the openEHR model has been upgraded to support enumeration types and nested generic and container types. The [BMM Github repo](https://github.com/openEHR/bmm/wiki) has some basic documentation, and all the relevant links.
Coming very soon: support for documentation fields.
Here's an example of an enumerated type in BMM syntax, from the openEHR RM:
```
["PROPORTION_KIND_2"] = (P_BMM_ENUMERATION_INTEGER) <
name =...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Announcement: LinkEHR support for templates (OPT and OET)](https://discourse.openehr.org/t/announcement-linkehr-support-for-templates-opt-and-oet/15294)
> Hello all,
After the Tromsø conference we started working with the template model
and its different representations and we can finally announce that
LinkEHR platform fully supports importing of archetype templates
defined in both OPT and OET format\. This way existing templates can be
used as basis for LinkEHR data transformation, working with templates
created with Template Designer\.
During this work, we found some inconsistencies in OET format\. Is
there a place where we can discuss...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Link between goals and other clinical concepts](https://discourse.openehr.org/t/link-between-goals-and-other-clinical-concepts/15050)
> Hi, if I want to establish a goal for body weight, I think there's a need of linking the goal concept with the body weight concept, but the body weight archetype is for measuring the weight not to specify a goal for it.
I understand the difference between a goal (what you want to achieve, fixed value) and the measures (to control your progress and compare with the goal, variable value through time).
Also, I think the target measurement from the goal archetype will depend on the specific...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Joint OpenEHR / FHIR review of Allergy-related Resources](https://discourse.openehr.org/t/joint-openehr-fhir-review-of-allergy-related-resources/16463)
> Hi Everyone
Just a heads up to what is coming in the near future:
[http://www.healthintersections.com.au/?p=2137](http://www.healthintersections.com.au/?p=2137)
One of us (Heather Leslie or I) will post more about this shortly.
Grahame
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Arctic 'dual-level modelling' conference 2014 - videos](https://discourse.openehr.org/t/arctic-dual-level-modelling-conference-2014-videos/16462)
> The Arctic conference on dual level modelling and clinical decision support took place last week. The majority of presentations were about the use of openEHR in real systems, and/or as a basis for decision support.
The conference was videoed, and the presentations are here, with the timings:
([Conference page](http://telemed.custompublish.com/project-sub-pages.250370.en.html))
### Day 1 -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ocean Template Designer crashes](https://discourse.openehr.org/t/ocean-template-designer-crashes/15293)
> Hi all (mostly Ocean guys :), in the last couple of months I've been actively working to add support to OPTs in my software instead of using archetypes directly as I was doing before.
I'm very close to the full support for OPTs in software and I want to get a smooth process from the creation/use of archetypes, creation of templates, generation of OTPs and use of OTPs for UI generation, DB schema generation, data validation and data querying.
The only problem I have right now to get a smooth...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ADL / AOM 1.5 wiki resources have moved to new 'ADL' space](https://discourse.openehr.org/t/adl-aom-1-5-wiki-resources-have-moved-to-new-adl-space/16458)
> Interest in ADL & AOM 1.5 is growing daily now.
In order to enable visitors new and old to more easily find the ADL and AOM pages on the openEHR wiki, I have moved them to a new [ADL space](http://www.openehr.org/wiki/display/ADL/ADL+Home). This even has its own logo, so you can see it more easily when you log into the wiki.
I have renamed some pages in an effort to obtain better URLs (it's not always that easy to work out...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Cyclic datatypes: OpenEHR virus](https://discourse.openehr.org/t/cyclic-datatypes-openehr-virus/13141)
> Hi,
I found a peculiarity which causes me some trouble\. Not that my trouble is a problem, I can solve that, but not without breaking some rules, and the solutions is quite arbitrarily\.
The solution is to check if there is any cyclic recursive going on and break at a certain arbitrary moment\. But it is not a nice solution\.
How many times do we see an archetype with an ELEMENT with DV\_TEXT matches \{\*\} in it?
So, there are almost no constraints at all on that value\.
Condition: The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [open platforms blog post](https://discourse.openehr.org/t/open-platforms-blog-post/15615)
> Although not directly about openEHR, I made a [recent blog post](http://wolandscat.net/2014/05/07/what-is-an-open-platform/) on open platforms that some people here may find useful, e.g. in advocacy inside your organisations.
- thomas
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [DV_ABSOLUTE_QUANTITY Class](https://discourse.openehr.org/t/dv-absolute-quantity-class/16461)
> Hi,
In the Data Types IM I find on 6\.2\.12 the class DV\_ABSOLUTE\_QUANTITY\.
I did not find it in the XML Schema: BaseTypes\.xsd on github\.
Is that on purpose or is that an error?
Thanks in advance for clarification
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Prof Barry Smith - lecture on 'Ontology of disease' - April 29 Kings College London](https://discourse.openehr.org/t/prof-barry-smith-lecture-on-ontology-of-disease-april-29-kings-college-london/16459)
> Prof Barry Smith (philosophy, Buffalo) will be talking on "The Ontology of Health and Disease" in King's College, London at 1.30pm on April 29.
[http://www.kcl.ac.uk/innovation/groups/chh/eventrecords/Philosophy-of-Medicine-Seminar-Barry-Smith.aspx](http://www.kcl.ac.uk/innovation/groups/chh/eventrecords/Philosophy-of-Medicine-Seminar-Barry-Smith.aspx)
Abstract:
"The Ontology of Disease"
A recent paper in the journal
Healthcare Informatics Researchidentifies a paradigm shift -...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM new release // Change Requests](https://discourse.openehr.org/t/ckm-new-release-change-requests/14229)
> Hi all,
We have upgraded the Clinical Knowledge Manager at [http://openehr.org/ckm](http://openehr.org/ckm)
This release adds **Change Requests** to CKM archetypes (and templates, termsets and release sets as well).
Any registered user can now create Change Requests...just right-click on the resource in the left-hand panel and select "Change Requests".
Check out all the details at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Composition commit format to EHR](https://discourse.openehr.org/t/composition-commit-format-to-ehr/15299)
> Hi all!
I'm wondering how implementers are sending/committing COMPOSITIONs to their openEHR EHR implementations.
A little context about what I'm doing right now:
1. I've implemented an openEHR Service-Oriented (REST) repo that accepts commits of COMPOSITIONS in XML
2. I use flat archetypes to define those COMPO's (i.e. one archetype with all slots resolved, so it's auto-contained)
3. Now I'm changing the flat archetypes for OPT support, yay! :)
4. The XML accepted by the EHRServer have...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 ANTLR definitions...and a few questions.](https://discourse.openehr.org/t/adl-1-5-antlr-definitions-and-a-few-questions/16460)
> Hello everyone
A brief email to let you know that a first version of ADL and cADL
expressed in EBNF and ANTLR's meta\-language is now avaialble at:
https://github.com/aanastasiou/adl_ebnf
Next up is ODIN\.
The ANTLR definitions specifically are available at:
https://github.com/aanastasiou/adl_ebnf/tree/master/src/antlrDefs/adl
In general, transcribing from:
http://www.openehr.org/wiki/display/spec/ADL+1.5+parser+resources was a
straightforward task for the majority of the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 single-file templates proposal](https://discourse.openehr.org/t/adl-1-5-single-file-templates-proposal/16452)
> There is a [new page here](http://www.openehr.org/wiki/display/spec/ADL+1.5+templates+as+single+artefacts) that describes a proposal for ADL 1.5 single file templates. Note that other useful rsources are on the [ADL/AOM 1.5 parent page](http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633), now re-organised.
If you are feeling lazy and just want to see what one looks like,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Alignment of languages and translations in templates (was: Invalid language codes in languages codeset)](https://discourse.openehr.org/t/alignment-of-languages-and-translations-in-templates-was-invalid-language-codes-in-languages-codeset/15295)
> I repost this discussion from the java implementation list, I think it could be interesting to get feedback from the general implementers community.
[details="(attachments)"]
[/details]
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [2 openEHR-announce moderator request(s) waiting](https://discourse.openehr.org/t/2-openehr-announce-moderator-request-s-waiting/16455)
> The openEHR\-announce@lists\.openehr\.org mailing list has 2 request\(s\)
waiting for your consideration at:
http://lists.openehr.org/mailman/admindb/openehr-announce_lists.openehr.org
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending posts:
Cause: Post by non\-member to a members\-only list
Cause: Post by non\-member to a members\-only list
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 23, Issue 5](https://discourse.openehr.org/t/openehr-clinical-digest-vol-23-issue-5/16454)
> Thanks Diego and David\!
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [13606 implementation?](https://discourse.openehr.org/t/13606-implementation/14313)
> Dear Diego,
I am currently working on an ISO standard covering the basics for
electronic prescriptions of medicinal products\.
Could your work for the ministry of health in Spain be seen as an implementation site for 13606 based implementation?
In other words, can I put the Spanish project in the ISO document ?
If so, what does Procedimiento mean in English?
and is HojaMedicacionActiva the medication list?
Which of the archetypes is actually including an electronic prescription of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 23, Issue 4](https://discourse.openehr.org/t/openehr-clinical-digest-vol-23-issue-4/16457)
> Dear Diego,
That is impressive work\!
I have been checking a few I am currently working on\.
heart frequency for example\.
I see you express the value in PQ \(Physical Quantity\)\. Does this mean you use ISO 21090 data types?
And am I correct that there are no linkages to external code systems such as for this example Snomed CT or LOINC?
Thanks for any clarification\.
sincerly yours,
dr\. William TF Goossen
Director Results 4 Care B\.V\. the Netherlands
De Stinse 15
3823 VM...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The Spanish Ministry of Health has published the official archetypes for national EHR communication](https://discourse.openehr.org/t/the-spanish-ministry-of-health-has-published-the-official-archetypes-for-national-ehr-communication/15288)
> The Spanish Ministry of Health, Social Services, and Equality has
published an official set of ISO13606 archetypes and derived artifacts
for the communication of EHR among the regions of Spain\. These
archetypes have been developed by the UPV based on the official
"Clinical Report Minimum Data Set" \(CMDIC \- Conjunto Mínimo de Datos
de Informes Clínicos\)\.
https://www.msssi.gob.es/profesionales/hcdsns/areaRecursosSem/Rec_mod_clinico_arquetipos.htm
Currently it includes the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADLParser ArchetypeInternalRef (corrected question)](https://discourse.openehr.org/t/adlparser-archetypeinternalref-corrected-question/15612)
> Hi,
I think I found something strange in the ADL-parser.
See following ADL:
`attribute3 matches {`
`use_node SECTION /items[at0001]`
`use_node SECTION /items[at0002]`
`}`
`attribute4 cardinality matches {0..*} matches {`
`use_node SECTION[at0006] /items[at0002]`
`use_node SECTION[at0005] /items[at0001]`
`}`
The nodes where pointed to, exist, they look like this
`items cardinality matches {0..*} matches {`
`SECTION[at0001] occurrences matches {0..1} matches {*}`
`SECTION[at0002]...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADLParser ArchetypeInternalRef](https://discourse.openehr.org/t/adlparser-archetypeinternalref/15613)
> Hi,
I think I found something strange in the ADL-parser.
See following ADL:
`attribute3 matches {`
`use_node SECTION /items[at0001]`
`use_node SECTION /items[at0002]`
`}`
`attribute4 cardinality matches {0..*} matches {`
`use_node SECTION[at0006] /items[at0002]`
`use_node SECTION[at0005] /items[at0001]`
`}`
The nodes where pointed to, exist, they look like this
`items cardinality matches {0..*} matches {`
`SECTION[at0001] occurrences matches {0..1} matches {*}`
`SECTION[at0002]...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype for patient demographics.](https://discourse.openehr.org/t/archetype-for-patient-demographics/15564)
> Hi.
We are developing a RIS, which eo archetypes should be used to record patient demographics?
We have reviewed the following archetypes in openEHR CKM of:
* - Patients (Model Arquetype)
* - Person name (Archetype Model)
* - Person data (Structure)
* - Person name (Arquetype)
They should build a template with these? We should use just one? We would appreciate recommendations.
regards
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Pediatric Glasgow Coma Scale information request](https://discourse.openehr.org/t/pediatric-glasgow-coma-scale-information-request/15429)
> Dear all,
I am currently working on the DCM for the Glasgow Coma Scale (GCS). This was balloted in 2010 and reconciled. I am trying to work on the reconciliation despite that HL7 Int is not further interesting in publishing this kind of work.
One of the issues is that there is a pediatric GCS apparently. However, that was not included in the DCM GCS.
Given the completely different target group, and hence differences in interpretations and probably scores, I think this must be a different...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 definitions](https://discourse.openehr.org/t/adl-1-5-definitions/15286)
> Hello everyone
Are there any resources that define the structure of ADL 1\.5? As always,
BNF would be great but other files that could help in deriving BNF would
also be useful\.
Also, can i please ask if there are any plans to update the archetype
query language with the rest of the operations that could be carried out
over openEHR? At the moment, AQL supports data manipulation only and
specifically querying\. What about other operations such as update /
insert / delete?\)
Looking forward...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Wrong link to openEHR XSDs?](https://discourse.openehr.org/t/wrong-link-to-openehr-xsds/15287)
> In the spec page, the link to XSDs show me a raw HTML page: https://raw.github.com/openEHR/specifications/Release-1.0.2/publishing/its/XML-schema/index.html
Anybody can see the page itself instead of the HTML?
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL Workbench 1.5beta10 new release](https://discourse.openehr.org/t/adl-workbench-1-5beta10-new-release/16456)
> A [new beta of the ADL 1.5 workbench](http://www.openehr.org/downloads/ADLworkbench/home) has been released. It now includes the proposed new internal code system, codes on all nodes (compatible with 13606-based archetype tools), explicit value sets, full ADL 1.4 conversion, IHTSDO configurable URIs for term binding, namespaced identifiers, standard lifecycle states, greatly improved terminology visualisation and much more.
We have been working with the submitter group for the OMG RfP...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XSLT Processors and the TDD_to_openEHR.xsl](https://discourse.openehr.org/t/xslt-processors-and-the-tdd-to-openehr-xsl/16724)
> Hi everybody,
I got a question regarding the TDD_to_openEHR.xsl. So far I used the XSLT processor of altova which works great. Nevertheless, to achieve a better integration into Microsoft SSIS, I would like to use a .net based processor. I tried to use recent versions of Saxon and XMLPrime but failed (the created target document is blank). I guess those processors are more complient with w3c specs than altova but I still have not found the point of failure.
Do you have any experience...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Clinical Knowledge Manager update + Github Mirror](https://discourse.openehr.org/t/clinical-knowledge-manager-update-github-mirror/15291)
> Clinical and technical members may be interested to know that a new
version of CKM has been released\.
www\.openehr\.org/ckm
In particular this release adds an automatic export of all resources
\(archetypes, templates and termsets\) that are uploaded to CKM to a Git
repository\. This will be automatically updated to mirror the contents
of the CKM Trunk\.
The github repository can be found at https://github.com/openEHR/CKM-mirror
Note that the CKM Trunk is an 'editorial view' and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 22, Issue 15](https://discourse.openehr.org/t/openehr-clinical-digest-vol-22-issue-15/14319)
> Hi Ian,
We will opt for what is available. We are scheduling trainings for China in July and Manila in November.
In communication now with Heather Leslie..
A certificate of proficiency will definitely be a plus. A certificate of attendance will suffice if that is what's currently available..
Thanks!
alvin
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 22, Issue 13](https://discourse.openehr.org/t/openehr-clinical-digest-vol-22-issue-13/16453)
> Hi Ian,
A regional approach might work for us in AeHIN. If the board can authorize a regional provider, we can discuss details with them...but since it is an openEHR certification, it should be Board-authorized...
alvin
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 22, Issue 11](https://discourse.openehr.org/t/openehr-clinical-digest-vol-22-issue-11/14320)
> I agree with Pablo. Governance is important. Some operational models you may emulate are TOGAF and COBIT.
Our network AeHIN ([www.aehin.org](http://www.aehin.org)) is investing heavily on certification of our members (many from ministries of health and ICT). So far these are our schedules:
Enterprise architecture using TOGAF KL, March 25-28
IT Governance using COBIT Manila April 22-25
IT Governance using COBIT Myanmar May 27-30
IT Governance using COBIT China July (dates to follow)
We...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Too much implied semantics for acxxxx code?](https://discourse.openehr.org/t/too-much-implied-semantics-for-acxxxx-code/16451)
> (Posting this here as Ian suggested)
I was looking at the Demonstration archetype and found something strange.
When I look where ac0001 is used in this archetype I feel that too much implied knowledge is being used.
ELEMENT[at0011] matches { -- Text That is Sourced From an External Terminology
value matches {
DV_CODED_TEXT matches {
defining_code matches {[ac0001]} -- SubsetA
}
}
}
As defining_code is a CODE_PHRASE, which is an entity with a code and another entity of TERMINOLOGY_ID type,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [What does ADL 1.5 look like?](https://discourse.openehr.org/t/what-does-adl-1-5-look-like/15611)
> For intrest - some real world archetypes are posted [here](http://www.openehr.org/wiki/display/spec/ADL+1.5.1+Example+Archetypes). Also a link to the newly upgraded ADL regression test archetypes, for the masochists here :)
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CIMI archetype examples using latest openEHR AOM & ADL](https://discourse.openehr.org/t/cimi-archetype-examples-using-latest-openehr-aom-adl/15284)
> For those of you following CIMI, there is now a [dedicated CIMI space](http://www.openehr.org/wiki/display/CIMI/CIMI+Home) on the openEHR wiki. [This page](http://www.openehr.org/wiki/display/CIMI/CIMI+Entry-in-Entry+Modelling+Pattern) summarises some recent developments on the question of 'panels in panels' and 'Entries in Entries'. Essentially we are trying to merge aspects of the modelling styles of Intermountain Healthcare, openEHR and others, to cover more modelling use cases.
The...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 22, Issue 1](https://discourse.openehr.org/t/openehr-clinical-digest-vol-22-issue-1/16723)
> Hi all,
Just Wanted to know if there's is a certification training/program for openehr?
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Representing HbA1c result (mmol/mol) in AE](https://discourse.openehr.org/t/representing-hba1c-result-mmol-mol-in-ae/15290)
> Hi,
Any idea how to choose mmol/mol for HbA1c result using DV_QUANTITY in Archetype Editor?
It used to be a proportion (%) but now the international agreement is to use this unit which does not come as an option. Wonder if I exists in UCUM?
This is such a commonly used Lab item – I’m sure someone else must have hit the issue.
Cheers,
-koray
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 24, Issue 1](https://discourse.openehr.org/t/openehr-technical-digest-vol-24-issue-1/16449)
> PortaVita MGRID database does exactly this job, but based on HL7 v3 templates\. It allows storage of source documents, querying against Snomed CT etc on details and allows Full XML handling\.
Vriendelijke groet,
Dr\. William Goossen
Directeur Results 4 Care BV
\+31654614458
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Persistence of Compositions](https://discourse.openehr.org/t/persistence-of-compositions/15560)
> Hey there,
we make good progress in understanding and applying openEHR to our Data Warehouse project. First data mappings have been done and a poc ETL process utilizing mapforce generated c# code has been created for vital parameters (originating from the ICU). Currently, I'm working on the data model of the persistence layer. I know that there has been some discussion about this topic in the past and recently. I checked implementation examples like Pablo's ehrGEN project and Erik Sundvalls'...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Update on meta-data for openEHR and 13606](https://discourse.openehr.org/t/update-on-meta-data-for-openehr-and-13606/15285)
> Following conversations with Ian McNicoll and others working on the archetype meta-data question, I have [posted a possible revised model](http://www.openehr.org/wiki/display/spec/Knowledge+Artefact+Meta-data) containing the following changes to the current one:
- copyright has been moved to the non-translated top-level description
- license has been added to the description
- custodian_namespace has been added to the description
- custodian_organisation has been added to the description
We...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 23, Issue 8](https://discourse.openehr.org/t/openehr-technical-digest-vol-23-issue-8/16447)
> I agree with both your comments Pablo
William
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Invalid language codes in languages codeset](https://discourse.openehr.org/t/invalid-language-codes-in-languages-codeset/15283)
> Hi,
I noticed there are invalid ISO 639\-1 language codes used in
https://github.com/openEHR/terminology/blob/master/openEHR_RM/RM/Release-1.0.2/external_terminologies.xml#L263
For instance, "ar\-sa", "en\-us" or "nl\-be" are all invalid ISO 639\-1
codes\. Only codes consisting of two letters are allowed according to ISO
639\-1\.
Is this on purpose?
If it is on purpose, then what standard is used to define the language
code? And shouldn't the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [radical idea - where term value sets should be defined in archetypes.](https://discourse.openehr.org/t/radical-idea-where-term-value-sets-should-be-defined-in-archetypes/15289)
> I have created a [wiki page](http://www.openehr.org/wiki/display/spec/ADL+1.5+-+where+to+define+value+sets) to describe a possibly radical idea about how we define value sets (like body position etc) in archetypes.
all feedback welcome.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL & AOM specifications upgraded](https://discourse.openehr.org/t/adl-aom-specifications-upgraded/16448)
> The ADL and AOM specification documents have now been upgraded to reflect recent developments. They new include the new identification system, plus terminology URIs, as well as other simplifications and cleaning up. These changes are all implemented in the forthcoming ADL workbench.
See here:
- [AOM](http://www.openehr.org/releases/trunk/architecture/am/aom1.5.pdf)
- [ADL](http://www.openehr.org/releases/trunk/architecture/am/adl1.5.pdf)
The new node id rules and identifier types have not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL/AOM 1.5 progress](https://discourse.openehr.org/t/adl-aom-1-5-progress/16450)
> I have uploaded a new ADL 1.5 and AOM 1.5 specification, showing recent major improvements:
- new identification approach
- removal of AOM CONSTRAINT_REF class
- removal of AOM C_REFERENCE_OBJECT class
- simplification of archetype terminology
They will contain a errors in prose parts, but the formal parts should be reasonably good. I still have to do a proper review. See:
- [ADL 1.5 spec](http://www.openehr.org/releases/trunk/architecture/am/adl1.5.pdf)
- [AOM 1.5...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL/AOM 1.5 - id-codes unification - the final change](https://discourse.openehr.org/t/adl-aom-1-5-id-codes-unification-the-final-change/15282)
> happy new year and best wishes for 2014. I hope your new year's day is a bright one (unless you live in the UK, in which case it's a lost cause today ;-)
I have been working in the last few months to produce a final version of ADL/AOM 1.5, based on:
- [existing requirements](http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633),
- emerging requirements - Intermountain, CIMI,
- Harold Solbrig's proposals for terms-as-URIs,
- [Dave Carlson's MDHT...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Open source Reference Implementation](https://discourse.openehr.org/t/open-source-reference-implementation/15292)
> Hi all,
We would proudly like to announce that we have open sourced MEDrecord. This an implementation of the full openEHR Reference Model, see for yourself at [https://www.medrecord.nl/users-guide/](https://www.medrecord.nl/users-guide/)
The stack is already installed by others, so you could give it a go. Any comments are more than welcome...:-).
Cheers!
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Industry Partners](https://discourse.openehr.org/t/industry-partners/15608)
> Dear All,
We have put out a press release today about the openEHR Foundation Industry Partnership.
[http://www.openehr.org/news_events/foundation_news.php?id=87](http://www.openehr.org/news_events/foundation_news.php?id=87)
This will initially involve seven companies who will fund collective developments that increase the value of openEHR as a way to record and share health information inside systems.
It has been a long road to establish the value of a non-proprietary means of capturing...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Editor Primitive Constraints](https://discourse.openehr.org/t/archetype-editor-primitive-constraints/16446)
> Hi all, I-m doing some formal testing ni my software and fixing some bugs on the java ref impl, creating some complex archetypes with many RM types and different constraints.
I'm trying to create a DV_TEXT with a C_STRING pattern constraint over it's value, but I can't find how to do that with the AE. I imagine a simple use case for this when recording demographic data, to have a regex of the email to validate patient's email.
It seems I can't create C_INTEGER list or range constraints or...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Establishing the Management Board](https://discourse.openehr.org/t/establishing-the-management-board/16445)
> Hi Everyone
We are announcing the move to becoming an operational organisation tomorrow with information about our new Industry Partners who begin collective support for activities that enhance the utility of openEHR in their commercial software. As part of this process we are changing the Governance of the Foundation to be more inclusive and representative.
Our collectively developed statement on management is as follows:
The openEHR Foundation will be governed in terms of legal and...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype Editor Language/terminology related problems](https://discourse.openehr.org/t/archetype-editor-language-terminology-related-problems/16328)
> Hi all, I'm working on a couple of openEHR workshops I'll give in Argentina: [http://translate.google.com/translate?hl=es&sl=es&tl=en&u=http://informatica-medica.blogspot.com/2013/11/talleres-de-openehr.html](http://translate.google.com/translate?hl=es&sl=es&tl=en&u=http://informatica-medica.blogspot.com/2013/11/talleres-de-openehr.html)
Doing a little testing of my examples, if found two possible bugs on AE v2.2.905 beta
1. When I add and remove EVENTs from an OBSERVATION, and then go to...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [archetype_details in item_tree](https://discourse.openehr.org/t/archetype-details-in-item-tree/16444)
> Hi all,
I have a question about the archetype_details attribute in LOCATABLE class.
The attribute is not getting populated by the SkeletonGenerator for ITEM_TREE class even when the ITEM_TREE object is the root of the hierarchy, but we need that for our processing. I can change that behavior in the SkeletonGenerator, but that would break the tests.
I wonder if that change would be against the spec.
Thanks in advance,
Jacobo
Java developer @ Hospital Universitario Río Hortega
Sacyl...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from pazospablo@hotmail.com requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-pazospablo-hotmail-com-requires-approval/16699)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@lists\.openehr\.org
Reason: Message body is too big: 111408 bytes with a limit of 50 KB
At your convenience, visit:
http://lists.openehr.org/mailman/admindb/openehr-implementers_lists.openehr.org
to approve or deny the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Exception messages on TemplateDesigner 2.7.60.2](https://discourse.openehr.org/t/exception-messages-on-templatedesigner-2-7-60-2/15277)
> Hi all, I'm creating a template from scratch with my own archetypes created using Archetype Editor (attached). When I try to save the template I get weird messages:
- Cannot access a disposed object. Object name: 'FileSystemWatcher'.
- Object reference not set to an instance of an object.
Any ideas?
 I spent a bit of time trawling back through that last discussion on C_OBJECT.node_id (the property that carries at-codes) and whether it should be mandatory or optional, and also whether empty is valid.
Currently it is mandatory, and can't be empty.
We need to make the spec work for 2 distinct styles of modelling:
- 13606 style - requires an at-code on every node, but only some have to be defined in the ontology section
- in this case, the node codes really are like identifiers only, some...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Musings about a more web-friendly openehr](https://discourse.openehr.org/t/musings-about-a-more-web-friendly-openehr/15271)
> Hey folks,
Following on from the discussion about adl path / xpath, XSDs, and so forth\. Here's something semi\-random that I've been thinking about for a while and I thought I might share\. I figured now might be a good time for that, with the work ongoing on openehr 2\.0\.
Status
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [XML COMPOSITIONS for OPT testing](https://discourse.openehr.org/t/xml-compositions-for-opt-testing/16441)
> Hi all,
I'm adding support for Operational Templates (OPTs) to the EHRServer. I'm using the current templates in the CKM as test cases: eReferral, Heart Failure and Demo with hide-on-form.
Does anyone have a XML COMPOSITON instance created for any of those templates?
The idea is to use those instances to commit them to the server and verify that all the data is queryable without human intervention.
If anyone has other OPTs with sample XML COMPOSITION instances, is also good!
Thanks for...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ALDParser and DADLParse](https://discourse.openehr.org/t/aldparser-and-dadlparse/16440)
> Hello, I am trying to use the Rm Skeleton Generator but when I try to build the source from GitHub it asks for the classes ADLParser and DADLParser, but they dont exist there..
Can someone help me with this issue? Thank you!
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Index in array's in ADL](https://discourse.openehr.org/t/index-in-arrays-in-adl/13136)
> Hi all,
I had following interesting discussion\.
Suppose we have a cluster containing name of a person\.
There is a field called firstname, and a field called lastname\.
The problem is concerning the ADL\-path, what should be used\.
This is a part of the archetype:
CLUSTER\[at0007\] occurrences matches \{0\.\.1\} matches \{ \-\-...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Ocean's Template Designer and allowedType rules](https://discourse.openehr.org/t/oceans-template-designer-and-allowedtype-rules/15272)
> Hi all,
I'm playing with the TD v2.7.60Beta to include openEHR template support to CaboLabs EHRServer ([http://www.youtube.com/watch?v=D-hs-Ofb8SY](http://www.youtube.com/watch?v=D-hs-Ofb8SY))
I opened the Blood Pressure archetype and tryied to constraint the Any Event node of type EVENT to allow only POINT_EVENT, and I get this rule:
**PointInTime**
Shouldn't "PointInTime"...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Study about clinical information modelling tools](https://discourse.openehr.org/t/study-about-clinical-information-modelling-tools/15273)
> My name is Alberto Moreno, PhD student at University College London. As part of my PhD I am conducting a Delphi study about functional requirements that should be satisfied by clinical information modeling tools. Rather than identify which functionalities are currently available in existing tools the questionnaire aims to identify functionalities that should be covered in order to provide guidance about how to evolve the existing tools.
In this study it is used the concept Clinical...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [various reference implementation patches](https://discourse.openehr.org/t/various-reference-implementation-patches/16722)
> Hi everyone,
Pleased to meet you\.\.\.I'm Leo, I work at MEDvision \(formerly known as ZorgGemak, one of those shiny Dutch openEHR companies\), I do some work on our version of Bert's openEHR kernel\. I come bearing patches\!
We've been making some more extended use of the reference implementation in our own codebase, particularly for doing some code and data generation, and for some associated automated testing\. That means I'm slowly accumalating a batch of patches...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Instruction archetypes and overlaping nodes with INSTRUCTION.narrative](https://discourse.openehr.org/t/instruction-archetypes-and-overlaping-nodes-with-instruction-narrative/15280)
> Hi, I'm reviewing archetypes for a project. Looking at referral request archetype on the CKM, there are some nodes (Reason for request & Reason description) that seems to match the semantics of INSTRUCTION.narrative property.
Using that archetype to generate the UI in EHRGen, the overlaping was clear (I though if a doctor records the reason, he/she will have no information to record on narrative). The problem is that narrative is mandatory on the IM, and I doubt what to do in cases like this...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Exchanging data](https://discourse.openehr.org/t/exchanging-data/15607)
> Hello,
I’m new to this list and in openEHR. I studied openEHR pdfs about adl, aom, em etc., watched Tomas Beal’s adl tutorial on youtube. I partial understand openEHR but I have big holes between those parts, so I hope someone will answer my questions because I am not sure that I am going the right way.
I managed to get the TDD, but I am not sure if the purpose of TDD is exchanging or something else.
How to exchange data between two OpenEHR systems and between systems in which one of them...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EHRServer demo online](https://discourse.openehr.org/t/ehrserver-demo-online/15062)
> Hi all,
Tomorrow I'll do a small demo of our EHRServer project.
I'll show the EHRServer functionalities, mainly commit and querying, the UI, and a couple of client apps.
This will be the same demo as last week (in spanish) [https://www.youtube.com/watch?v=08vAk15utss](https://www.youtube.com/watch?v=08vAk15utss)
This will be a Hangout on air. Please check details here:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [regular expressions](https://discourse.openehr.org/t/regular-expressions/15278)
> I have a question about the ADL\-parser concerning the the regular\-expressions\.
I checked page 65 in:
http://www.openehr.org/releases/1.0.2/architecture/am/adl.pdf
Can someone please explain why this fails:
value existence matches \{1\.\.1\} matches \{/\[0\-9\]\{1,8\}/\}
Error:
se\.acode\.openehr\.parser\.ParseException: Encountered " "/" "/ "" at line 186, column 57\.
Was expecting:
"\}" \.\.\.
Thanks very much
Bert...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Rich text format in DV_TEXT](https://discourse.openehr.org/t/rich-text-format-in-dv-text/15274)
> Hello,
we are using an archetypes from the CKM called **openEHR-EHR-EVALUATION.clinical_synopsis.v1**. Over there is an DV_TEXT element called **Synopsis**
One of our clients want to use rich text format inside that field. According the specification it is not allowed to put formatted text over there. I rather should use a DV_PARSABLE.
How should i handle this correctly? The options i see are :
- specialise the archetype and add an DV_PARSABLE, and leaf the existing DV_TEXT empty
- create...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM 1.5 update published](https://discourse.openehr.org/t/aom-1-5-update-published/16432)
> The latest version of AOM 1.5 is now published [here](http://www.openehr.org/releases/trunk/architecture/am/aom1.5.pdf).
Changes:
- remodelling / rationalisation of C_PRIMITIVE_OBJECT classes (types expressing constraints on Integer, Boolean, Date, String, Terminology_code etc)
- simplification of Tuple model, to achieve the same effect as before - complete replacement of openEHR 'special syntax'
- all ADL 1.4 openEHR archetypes now parse to the new tuple syntax
- the 'openEHR Archetype...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical unsubscribe notification](https://discourse.openehr.org/t/openehr-technical-unsubscribe-notification/16439)
> ivan@carolmarden\.com has been removed from openEHR\-technical\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [State transitions - ACTIVITY/ACTION](https://discourse.openehr.org/t/state-transitions-activity-action/15275)
> Hi all.
We are discussing some details with the INSTRUCTION STATE MACINE. I will go directly to my two questions:
1
The state machine define transition from all not-terminated states to a terminated state. Except from POSTPONED state. There is no defined transition from POSTPONED to CANCELLED. The question is how we should model the scenario where the ACTIVITY is in POSTPONED and the user want to CANCEL the ACTIVITY in one step?
Is there a missing transition in the specification or did we...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Comment on archetype metadata](https://discourse.openehr.org/t/comment-on-archetype-metadata/15605)
> I just posted a comment here
[http://www.openehr.org/wiki/display/spec/Knowledge+Artefact+Meta-data?focusedCommentId=48037902#comment-48037902](http://www.openehr.org/wiki/display/spec/Knowledge+Artefact+Meta-data?focusedCommentId=48037902#comment-48037902)
Ian
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Path in use_node](https://discourse.openehr.org/t/path-in-use-node/16443)
> Hi All,
We had a discussion about data\-pointds being identified by archetype\-path, not archetypenode\-id\.
I agree with that, but I am a bit confused how to do following\.
consider following fantasy archetype
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [concerning adl-parser](https://discourse.openehr.org/t/concerning-adl-parser/16438)
> LinkEHR writes an archetypenode id in a use\_node, the Java ADL\-parser regards this as erroneous, although it is permitted in the AOM, where there is an nodeId in the ArchetypeInternalRef constructor\.
The repair in adl\.jj was, however simply to do\. I tested it with all available testfiles, and also with adding an nodeId in the adl\-test\-entry\.archetype\_internal\_ref\.test\-arc hetype, like this:
attribute3 matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [date-time pattern](https://discourse.openehr.org/t/date-time-pattern/15266)
> I have received a few archetypes created with the LinkEHR editor\.
In there is a dateTime pattern like this:
time existence matches \{1\.\.1\} matches \{????\-??\-??T??:??:??\}
I wonder if it is a legal pattern according to the specifications\. I must say that it is an EN13606 archetype\.
If it is legal, then we \(or me\) need to change the Java\-software, because at this time, it does not accept this pattern\.
se\.acode\.openehr\.parser\.ParseException: Encountered " "?"...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [concerning adl-parser](https://discourse.openehr.org/t/concerning-adl-parser/16437)
> LinkEHR writes an archetypenode id in a use\_node, the Java ADL\-parser regards this as erroneous, although it is permitted in the AOM, where there is an nodeId in the ArchetypeInternalRef constructor\.
The repair in adl\.jj was, however simply to do\. I tested it with all available testfiles, and also with adding an nodeId in the adl\-test\-entry\.archetype\_internal\_ref\.test\-arc hetype, like this:
attribute3 matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR and Data Warehousing](https://discourse.openehr.org/t/openehr-and-data-warehousing/15265)
> Hello everybody,
at first I'd like to introduce myself: I'm a research associate the University of Braunschweig, Germany. We are involved in a clinical data warehouse project at Hannover Medical School. I got a background in biomedical informatics and computer science.
We would like to use openEHR to generate a somewhat generic data model that serves the need of researchers in translational medicine. I have an architecture in mind as follows:
Specialists create archetypes and templates for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Semantic artifacts](https://discourse.openehr.org/t/semantic-artifacts/15604)
> Gerard,
I created the about 5000 concepts with unique Snomed ct, LOINC, ICF, icpc, icd10, ICNP or other code and represented them in HL7 clinical statements and combined the relevant selection in specific messages as for data exchange in perinatology , diabetes care , oncology nursing, 24 month follow up for prematures, youth preventive care records\.
The archetype creation failed miserably because nobody has an interest\. And that was to a large extend the same stuff as for the messages\....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Nodes](https://discourse.openehr.org/t/archetype-nodes/15264)
> Dear Bert,
I mean any kind of archetype, but in particular different archetypes for the same concept, eg blood pressure\.
Thy can have internally the same atXxxx code for different nodes\.
I mean the the harmonization of data elements is done manually by human beings, in order to allow data exchange by different systems\.
I find it awkward that similar to archetypes, the message or CDA content for clinical concepts that are equal are coded / defined differently\. This prevents reuse and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 18, Issue 50](https://discourse.openehr.org/t/openehr-technical-digest-vol-18-issue-50/15263)
> Semantic interoperability is absolutely compromised when for the same clinical concept variants of archetypes are created\.
If justified for internal system development , the moment exchange with another system requires harmonizing on datapoint to datapoint level\. I have done about 2000 in perinatology 800 in stroke care 1250 in youth care 100 in nursing oncology 20 in reuma, 400 in general nursing 250 in diabetes care 200 in GP care 100 in cardiology\. In the past 13 years\.
The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 18, Issue 38](https://discourse.openehr.org/t/openehr-technical-digest-vol-18-issue-38/15260)
> There is plenty of health informatics science that tells that combining data from various systems is only possible when each data element is uniquely coded\.
That single use case alone \- reusing data from multiple systems \- justifies the SHALL linkage between data element/node and terminology as Snomed CT\.
I agree with Sam that the meaning should be derived from the DCM and the collection of data elements in it\.
Here is where the science of data Modelling and the science of clinical...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 18, Issue 37](https://discourse.openehr.org/t/openehr-technical-digest-vol-18-issue-37/15256)
> The General problem with the at codes is that each archetype has the same at codes\. Hence it is not an ontology it refers to but is an internal micro\-ontology only \.
In the DCM approach each node SHALL have a minimum of one external code, preferable Snomed CT, which links the data element in the archetype to an external ontology, which importantly allows external maintenance and governance and facilitates the use in other archetypes or templates as defined in OpenEHR\.
Vriendelijke...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New source code for java-libs (v1.0.4) and gdl-tools (v0.92)](https://discourse.openehr.org/t/new-source-code-for-java-libs-v1-0-4-and-gdl-tools-v0-92/16434)
> Hi everybody,
just finished updating the both projects on github (java-libs & gdl-tools).
We have removed the openehr package inside gdl-tools and synched it with the one in the java-libs repository.
The updates on the gdl-tools are the same as commented for the binary release:
+ Source code editing support
+ Domain display on elements and archetype references
+ Clinical content on documents folder
and some bug fixes
For java-libs you will find a release tag v1.0.4, where you can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Polishing node identifier (at-codes) use cases.](https://discourse.openehr.org/t/polishing-node-identifier-at-codes-use-cases/15068)
> Thinking a little about node identifiers I have thought some
problematic use cases\.
First, this is the current 'rule' in the wiki
\(http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633) for
when node identifiers are really needed\. I copy the relevant part for
ease the discussion:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL-parser, two questions](https://discourse.openehr.org/t/adl-parser-two-questions/15261)
> Hi Rong,
1\)
According the ADL\-specs, page 89
\-\-\-\-\-\-\-\-\-\-/\* identifiers \*/ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
\[a\-z\]\[a\-zA\-Z0\-9\_\]\* V\_ATTRIBUTE\_IDENTIFIER
in adl\.jj however:
< V\_ATTRIBUTE\_IDENTIFIER: \["a"\-"z"\]\(<LET\_DIG\_U>\)\* >
Is there a reason for it?
2\)
The ADL\-Parser is not capable of parsing EN13606 archetypes because of the keyword "units" which...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL/AOM 1.5 progress update](https://discourse.openehr.org/t/adl-aom-1-5-progress-update/15258)
> For those interested in ADL/AOM 1.5, I made a [post in my blog](http://wolandscat.net/2013/08/21/adlaom-1-5-major-progress-update/) giving a progress update. It's getting simpler, more powerful, and more generic.
- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from bna@dips.no requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-bna-dips-no-requires-approval/16433)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@lists\.openehr\.org
Reason: Message body is too big: 75013 bytes with a limit of 50 KB
At your convenience, visit:
http://lists.openehr.org/mailman/admindb/openehr-implementers_lists.openehr.org
to approve or deny the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Want to test an openEHR repository?](https://discourse.openehr.org/t/want-to-test-an-openehr-repository/15262)
> Hi everybody!
I'm building a very simple Shared EHR Server with Composition commit and query services.
The project is here: [https://github.com/ppazos/cabolabs-ehrserver](https://github.com/ppazos/cabolabs-ehrserver)
The server is working but I'm finishing some improvements on the backend.
I hope to deploy an instance online in a couple of weeks to play around, just for coordination purposes:
**does anyone want to try the commit and query services?**
I'll publish some basic documentation...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [At MedInfo? Use #openehratmedinfo](https://discourse.openehr.org/t/at-medinfo-use-openehratmedinfo/16436)
> for those at MedInfo, or wanting to follow, tweets with \#openehratmedinfo will be tracked on the main website starting sometime today\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [New release for GDL Editor (v0.92)](https://discourse.openehr.org/t/new-release-for-gdl-editor-v0-92/15259)
> Hi everybody,
Today we are releasing a new version of the GDL editor (v0.92)!
You can find the binaries at the SourceForge page: [https://sourceforge.net/projects/gdl-editor](https://sourceforge.net/projects/gdl-editor)
To download directly the installer (Windows only): [http://sourceforge.net/projects/gdl-editor/files/gdl-editor-installer-v0.92.exe/download](http://sourceforge.net/projects/gdl-editor/files/gdl-editor-installer-v0.92.exe/download)
To download the executable binaries...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Meetup in Copenhagen at Medinfo 2013](https://discourse.openehr.org/t/meetup-in-copenhagen-at-medinfo-2013/16435)
> Ian
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org DNS problem - fixed (functionally)](https://discourse.openehr.org/t/openehr-org-dns-problem-fixed-functionally/15602)
> We have changed the openEHR\.org server DNS resolver settings to point preferentially at Google DNS servers for now, which means all URLs with openEHR\.org and subdomains on the website will be served correctly\. openEHR\.org and subdomains in URLs used elsewhere are not affected \(since the problem is limited to the DNS servers on the openEHR\.org infrastructure\)\.
Although the underlying problem is still be be fixed, the above should remove any issues functionally\.
Thanks for your...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM Android Viewer](https://discourse.openehr.org/t/ckm-android-viewer/15603)
> Hello all,
We had a student develop an Android based CKM viewer. For the moment we consider it to be in beta stage, but could be useful. Currently only Observations are fully processed (and have their structure analyzed). For the remaining archetype entities only the header is shown. If there is enough interest then we will work on improving it.
We are working on publishing it into the Google Play store, but you can install this apk in the meantime (requires to allow the installation from...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ACTIVITY and timing](https://discourse.openehr.org/t/activity-and-timing/15255)
> Hi
ACTIVITY has a field for timing. It's datatype is parsable.
Some archetypes use a CLUSTER archetype to define detailed timing information for the given ACTIVITY.
I am curious if anyone have experiences with implementing timing for Activity and which strategy you are using?
Will detailed timing information in a CLUSTER make timing information on Activity obsolete? Or will detailed timing information on Activity remove the need for a timing CLUSTER?
Bjørn Næss
Product Owner
DIPS ASA
Mobil...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org wiki and jira - unavailable](https://discourse.openehr.org/t/openehr-org-wiki-and-jira-unavailable/13654)
> We are experiencing problems with Confluence and Jira serving from openehr\.org, due to underlying DNS problems at the date centre provider\. We expect that these problems should be resolved in the next few hours\.
Apologies for the inconvenience\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to start](https://discourse.openehr.org/t/how-to-start/13668)
> I am a Java developer. I am assigned to develop EHR based on OpenEHR. I read some specifications and they seem very complex to me. For instance, I want to create a web page like:
Last Name:
First Name:
Date of Birth Date:
Gender:
Phone:
Email:
Emergency Contact Person:
How do I map this object to Archetype?
David
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Meeting at Medinfo?](https://discourse.openehr.org/t/meeting-at-medinfo/15267)
> I’ll be there and I’d love to catch up with all of you.
Evelyn
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Syntax Diagram for the Archetype Query Language](https://discourse.openehr.org/t/syntax-diagram-for-the-archetype-query-language/14312)
> Hello Everyone
Since i needed an overview of AQL to understand its overall structure, i
took a little bit of time to create its syntax diagram today\.
A similar diagram is available from:
http://www.openehr.org/wiki/display/spec/Archetype+Query+Language+Grammar
The diagram i produced is based on the BNF rules found in the ANTLR AQL
definition \(http://www.openehr.org/wiki/display/spec/ANTLR+AQL+grammar)
and differs from the existing one in three points:
1\) It was rendered using...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL / ADL BNF specifications...](https://discourse.openehr.org/t/aql-adl-bnf-specifications/15257)
> Hello everyone
I am primarily interested in the BNF form of AQL and i was wondering if
it would be available from somewhere on the project's github space
\(?\)\.\.\.\(so far i can not locate it\. \)
Also, the java reference implementation included the javacc definitions
for parsing dADL and cADL but is there a stand\-alone BNF specification
for ADL 1\.5 now?
Looking forward to hearing from you
Athanasios Anastasiou
This email and any files with it are confidential and intended solely...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Recording absence of (clinical) information](https://discourse.openehr.org/t/recording-absence-of-clinical-information/15025)
> Hi everyone,
This is to do with my long standing issue about recording absence of info. In endoscopy models the “Presence” of endoscopic findings was represented as a CLUSTER where a special ELEMENT (that is internally referenced many times for each finding thereafter) captured ”Presence” of a finding and also if/why information about a particular finding was not available. This I thought was a quick and dirty fix to a larger problem which I reckon applies to all data structures and types...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New masters thesis on GDL, decision support from Karolinska Institute](https://discourse.openehr.org/t/new-masters-thesis-on-gdl-decision-support-from-karolinska-institute/14311)
> A [new thesis](http://www.openehr.org/resources/publications#decision_support) has been published on guidelines, working with the Guideline Definition Language (GDL), by Konstantinos Kalliamvakos from Karolinska Institutet.
Title: **Evaluation of the Guideline Definition Language (GDL) in the clinical area of severe sepsis and septic shock**
### Abstract- **Background**: The currently existing Guideline Representation Models(GRM) present limitations which hinder the adoption of guideline...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org server back up](https://discourse.openehr.org/t/openehr-org-server-back-up/16429)
> We are monitoring for any further instability. Please report any problems to [webmaster@openehr.org](mailto:webmaster@openehr.org)
thanks for your understanding.
- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org unscheduled outage](https://discourse.openehr.org/t/openehr-org-unscheduled-outage/16431)
> the openEHR\.org server appears to be having some problems\. We will be taking it down and running some checks on it in the next hour\.
Sorry for the inconvenience\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR website is down](https://discourse.openehr.org/t/openehr-website-is-down/15600)
> Both website and CKM are down\. Was this stop intended?
Regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Regarding the use of the Demographics Package...](https://discourse.openehr.org/t/regarding-the-use-of-the-demographics-package/15242)
> Hello everyone
Would it be good practice to use the demographics package to describe
both the patients for which data are available in a system but also the
users of the system?
As far as the first part is concerned, the demographics package provides
a very good level of detail for describing the parties that could be
involved in healthcare provision for some event\.
However, was / is there also the intention of using the same demographic
entities "data store" to perform...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Identification System for Knowledge Artefacts - major update.](https://discourse.openehr.org/t/identification-system-for-knowledge-artefacts-major-update/16426)
> A major update of the Identification System for Knowledge Artefacts draft specification is available [here](http://www.openehr.org/wiki/display/spec/Development+and+Governance+of+Knowledge+Artefacts).
This update (0.7.0) includes:
- major updates to text
- rewritten grammar
- rewritten 'references' section
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OMG Berlin e-health summit](https://discourse.openehr.org/t/omg-berlin-e-health-summit/16427)
> Rong Chen and myself attended the recent [e-health summit day](http://www.omg.org/news/meetings/tc/berlin-13/special-events/Health_Community_Summit.htm) at the Berlin OMG meeting. I made a [few notes about it](http://wolandscat.net/2013/06/20/omg-e-health-platform-summit-berlin-2013/) on my blog, for those interested.
- thomas
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR and twitter; fixed (sort of)](https://discourse.openehr.org/t/openehr-and-twitter-fixed-sort-of/16430)
> Some of you may know that twitter\.com turned everything upside down in the last couple of weeks by pulling their working 1\.0 API, which is what was used with everyone's nice embedded twitter widgets on websites\.
This is now gone, and like everyone else we have had to approximate what was there before, with a far less intelligent widget\.
For tweets you may have missed, go to the home page and click on the \#openEHR link\.
\- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Open EHRGen Guide in English!](https://discourse.openehr.org/t/open-ehrgen-guide-in-english/16428)
> Dear friends and colleagues, I'm very happy to announce that we have published a guide to our EHRGen system, now translated to english!
This implied a great effort, but I believe it was worth it.
I kindly ask you to review the document and drop me a line if you notice any errors or something that is not clear, or propose improvements to the doc, etc. All the help will be appreciated.
As any open source project, all of you who want to contribute with code, testing or documentation will be...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR infrastructure - status update](https://discourse.openehr.org/t/openehr-infrastructure-status-update/16419)
> The openEHR infrastructure has been (somewhat slowly) updated over the last few months as follows:
- the [website](http://www.openehr.org/) is now on a hosted server with latest Ubuntu / LAMP stack; practically speaking this means we can take advantage of anything recent / modern in latest Apache, PHP, Git etc
- nearing completion: MySQL-backed news posting capability, which will replace the static news article pages (the look and feel will be more or less the same)
- getting started -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [TDS (and TDD) implementations?](https://discourse.openehr.org/t/tds-and-tdd-implementations/15244)
> Hi!
Which projects and products out there support TDS (Template Data Schema)? And do they support conversion of TDDs (Template Data Documents) to standard "canonical" openEHR RM instances (in e.g. XML)? Is there any available XSLT, webservice or other thing that can convert bidirectionally between TDD and openEHR RM-based instances?
What about a TDS specification? Is there any published or work-in-progress document? If not is there any entity, group or person that could/should be sponsored...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetypes on CKM encoding problem (UTF-8 with BOM)](https://discourse.openehr.org/t/archetypes-on-ckm-encoding-problem-utf-8-with-bom/13595)
> Hi all,
I've downloaded a couple of archetypes from the CKM to start playing around with ADL on PHP :)
I've noticed those archetypes contain the BOM (byte order mark), the weird characters at the beginning of the ADL.
Shouldn't the ADL files be UTF-8 without BOM?
```
[0] => **ï»****¿**archetype (adl_version=1.4)
[1] => openEHR-EHR-OBSERVATION.apgar.v1
```
```
[0] => **ï»****¿**archetype (adl_version=1.4)
[1] => openEHR-EHR-OBSERVATION.body_mass_index.v1
```
```
[0] =>...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes at OMG](https://discourse.openehr.org/t/archetypes-at-omg/15253)
> Some of you may be interested to note that a new OMG RfP 'Archetype Modelling Language (AML)' will be under discussion at the [June OMG meeting](http://hssp.wikispaces.com/event-2013-06-OMG-Berlin).
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [rm-validator?](https://discourse.openehr.org/t/rm-validator/16425)
> Hi!
I am currently creating a Maven configuration for the LiU EEE experimental openEHR+REST-implementation so that we can release the code on GitHub in an organized manner and without violating any licenses for included libraries. In the same move I try to update to use the latest open ehr java-libs release.
In the code we have been using the library "rm-validator-1.0.2-SNAPSHOT.jar" that we got from another project. Now I can not find that component in the latest Java reference...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Void archetype accessing CKM web service (and website?)](https://discourse.openehr.org/t/void-archetype-accessing-ckm-web-service-and-website/14093)
> Accessing CKM via web service I have found that the archetype
openEHR\-EHR\-OBSERVATION\.intravascular\_pressure\-cvp\.v1 returns an empty
archetype \(0kb size\)
http://openehr.org/ckm/services/ArchetypeFinderBean/getArchetypeInADL?archetypeId=openEHR-EHR-OBSERVATION.intravascular_pressure-cvp.v1
Related archetypes
openEHR\-EHR\-OBSERVATION\.intravascular\_pressure\-jvp\.v1...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to model this XML type as Archetype?](https://discourse.openehr.org/t/how-to-model-this-xml-type-as-archetype/15247)
> Authorities require the reporting of injury. It is defined XSD for the message to be sent. Some items have numbers. These are perfect ordinal. The problem is the following XML type. How should these be modeled as archetype data types?
Archetype --> Template or mind maps --> Template --> Archetype
Thank you for your help
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[559] Bug fix to the Archetype Validation of Specialised archetypes where in some case a CDvQuantity (or similiar type from the openEHR profile) would be cast to a CComplexObject.](https://discourse.openehr.org/t/559-bug-fix-to-the-archetype-validation-of-specialised-archetypes-where-in-some-case-a-cdvquantity-or-similiar-type-from-the-openehr-profile-would-be-cast-to-a-ccomplexobject/13100)
> Revision: 559
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 parser grammars](https://discourse.openehr.org/t/adl-1-5-parser-grammars/13871)
> Seref alerted me to the fact that the grammars used in the current ADL reference compiler are not that easy to find (actually he said something else, but I can't print that;-), so I added a [small guide](http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633#openEHRADL%26AOM1.5-TemplatesandSpecialisedArchetypes-Parsergrammars) to the bottom of the ADL 1.5 page. Hope this helps various people engaged in looking at parsers for archetypes. Feedback welcome. I track the page, so you can...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1669] Correct SVN properties of various parser files.](https://discourse.openehr.org/t/ref-impl-eiffel-1669-correct-svn-properties-of-various-parser-files/13869)
> Revision: 1669
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1668] Improve adl parser grammar to remove any need for description section in template overlays .](https://discourse.openehr.org/t/ref-impl-eiffel-1668-improve-adl-parser-grammar-to-remove-any-need-for-description-section-in-template-overlays/13855)
> Revision: 1668
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR mailing lists - moving](https://discourse.openehr.org/t/openehr-mailing-lists-moving/15140)
> there is an urgent need to move the openEHR community mailing lists from their current location at CHIME, UCL to another location. We have now researched commercial options for handling mailman lists, and have found a number of suitable providers. In all cases, we would move the archives of all lists, as well as automatically resubscribing all members of all lists.
For most of these offerings, it looks as if we will have to change list address, i.e....
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [HIMSS12 presence for openEHR?](https://discourse.openehr.org/t/himss12-presence-for-openehr/13813)
> Hi everyone,
Ocean has booked a booth at HIMSS12 in Las Vegas next month! Sounds exciting, but I’m feeling rather daunted - last year they had 1032 exhibition booths and over 31,500 attendees!
So am wondering if there is anyone else in the openEHR community attending or will be on a booth.
Just thinking that it would be good to collaborate and provide a coordinated openEHR community message, if we can.
Perhaps if there are others involved, we could develop a page on the wiki as we often...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Mind map module](https://discourse.openehr.org/t/mind-map-module/15136)
> Everybody,
The module in the CKM for visualising arketypes as mind maps - is it open source and how can we get access to it? Is there a plan to in
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Examination findings - how much structured detail](https://discourse.openehr.org/t/examination-findings-how-much-structured-detail/15142)
> Controversy alert\!\!
In modern medicine, how much effort should we be putting into creating
detailed archetypes of physical examination findings? When I learn't
medicine, 30 years ago, there was a still a huge focus on detailed
examination technique and documentation e\.g\. clubbing, pulse
description, detailed murmur description etc\. Although cast down on
tablets of stone, a lot of this is very poorly researched and
validated, barely reproducable and is increasingly being bypassed...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Help on generating XSD for importing date](https://discourse.openehr.org/t/help-on-generating-xsd-for-importing-date/13760)
> hello
I am extracting data from EHR to an open EHR platform. I have built a template using ocean template designer and I can export this template as XSD file. can I use this XSD file directly with out generating the operational template for importing that data to the open EHR platform?
the other problem I have is that I get error when I try to open the operational template using the template designer, how can i open the opt file.
It would be great if you share me ideas from your experience...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Extracts validation against openEHR schema](https://discourse.openehr.org/t/extracts-validation-against-openehr-schema/13037)
> I am trying to validate two openEHR EHR extracts against the openEHR schema but getting some errors.
Here are the two...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Regionalisation - Lessons from HL7 affiliate experience](https://discourse.openehr.org/t/regionalisation-lessons-from-hl7-affiliate-experience/13738)
> Those of you considering developing Regional or national openEHR
organisations, may find these reflections from Rene Spronk \(who is on
these lists\) of interest
http://www.ringholm.com/column/HL7_membership_model.htm
Ian
Dr Ian McNicoll
office \+44 \(0\)1536 414 994
fax \+44 \(0\)1536 516317
mobile \+44 \(0\)775 209 7859
skype ianmcnicoll
ian\.mcnicoll@oceaninformatics\.com
Clinical Modelling Consultant, Ocean Informatics, UK
Director/Clinical Knowledge Editor openEHR Foundation ...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New content review round for Adverse Reaction](https://discourse.openehr.org/t/new-content-review-round-for-adverse-reaction/15133)
> Just to let you all know that I have just uploaded a significantly remodelled Adverse Reaction draft archetype and initiated a review round for it.
It has certainly been some time since the first review round, yet there has been considerable activity elsewhere. The time has come to consolidate this work and seek openEHR community input again.
This latest archetype has been fundamentally reworked based on previous openEHR review comments, research and inclusion of input from HL7, ICH,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM XML Schema](https://discourse.openehr.org/t/aom-xml-schema/16694)
> After checking the schema, I have seen some places that the schema
\(specifically basetypes\.xsd\) is missing things that are indeed
supported by ADL \(namely assumed\_values, lists, etc\.\)
What is the process to update the schema?
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[558] added a few testcases around archetype header parsing](https://discourse.openehr.org/t/558-added-a-few-testcases-around-archetype-header-parsing/13669)
> Revision: 558
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[557] small adjustments to the updated AOM classes](https://discourse.openehr.org/t/557-small-adjustments-to-the-updated-aom-classes/13624)
> Revision: 557
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[556] small adjustments of the class MultiplicityInterval](https://discourse.openehr.org/t/556-small-adjustments-of-the-class-multiplicityinterval/13583)
> Revision: 556
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[555] Removed javaCC src for ADL 1.4 and most of legacy testcases](https://discourse.openehr.org/t/555-removed-javacc-src-for-adl-1-4-and-most-of-legacy-testcases/12917)
> Revision: 555
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_DURATION as ranges](https://discourse.openehr.org/t/dv-duration-as-ranges/15132)
> As Ian suggested I copy this issue from CKM to the technical list\.
I have seen that in some archetypes \(e\.g\. Apgar or BloodPressure\) that
use DV\_Duration restrictions \(such as the width of the interval event
in the blood pressure archetype or the famous offset in the apgar
archetype\) define them like this:
offset existence matches \{1\.\.1\} matches...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Translation approaches](https://discourse.openehr.org/t/translation-approaches/15134)
> I recently posted the question below to the CKM General Discussion
list\. Replies there please, if possible\.
Hi all,
It is great to see increasing numbers of translations being offered
for archetypes but I have a question for those of us working in
languages which have national/cultural variants e\.g English, UK
English, US English or Spanish , Argentinian Spanish\.
Creating and maintaining translations will be quite onerous\. At the
moment, each translation of every sub\-language is...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[554] Added support for template parsing; not yet connected with updated AOM classes](https://discourse.openehr.org/t/554-added-support-for-template-parsing-not-yet-connected-with-updated-aom-classes/13475)
> Revision: 554
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New AOM and ADL specs](https://discourse.openehr.org/t/new-aom-and-adl-specs/12812)
> I have uploaded significantly improved versions of the documents linked from this page. There are some formal (minor) changes to the models, including: the template 'object model' has been absorbed into the AOM (there is just the AOM for everything now), and much better explanation of templates in the AOM spec, along with some diagrams.
See the openEHR [CIMI home page](http://www.openehr.org/wiki/display/stds/CIMI+Home+Page), or go straight to the changed docs:
- [ADL...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to use C_DURATION pattern constraint](https://discourse.openehr.org/t/how-to-use-c-duration-pattern-constraint/16693)
> Hi all,
maybe this is a silly question, but I didn't find a point in the specs where this is clearly explained:
The following notation on ADL:
ELEMENT[at0009] occurrences matches {0..1} matches { -- Pattern
value matches {
DV_DURATION matches {
value matches {PYM}
}
}
}
constraints the data to have a DV_DURATION element with both year and month specified (both part are mandatory) or with year and/or month specified (both part are optional)!?
Thanks
leo
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[553] Completed simplification around cADL, dADL parsing; added annotations parsing support and fixed some issues with interval parsing](https://discourse.openehr.org/t/553-completed-simplification-around-cadl-dadl-parsing-added-annotations-parsing-support-and-fixed-some-issues-with-interval-parsing/13381)
> Revision: 553
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Python / Django experience??](https://discourse.openehr.org/t/python-django-experience/15141)
> Hi all,
Would any of you with Python / Django experience be interested in
helping with a small open\-source project to establish a 'Clinical
Knowledge Incubator' website under the auspices of the Foundation? The
intention is to establish a very lightly\-governed archetype
collaboration, simple review and discussion space to enable early
communication between possible archetype developers\. This is not
intended to compete with a more formally\-governed repository such as
CKM but to...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[552] First iteration for implementing changes that come with adl 1.5.](https://discourse.openehr.org/t/552-first-iteration-for-implementing-changes-that-come-with-adl-1-5/13302)
> Revision: 552
Author: seref\.arikan
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[551] First iteration for implementing changes that come with adl 1.5.](https://discourse.openehr.org/t/551-first-iteration-for-implementing-changes-that-come-with-adl-1-5/12703)
> Revision: 551
Author: seref\.arikan
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[550] First iteration for implementing changes that come with adl 1.5.](https://discourse.openehr.org/t/550-first-iteration-for-implementing-changes-that-come-with-adl-1-5/13252)
> Revision: 550
Author: seref\.arikan
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[549] First iteration for implementing changes that come with adl 1.5.](https://discourse.openehr.org/t/549-first-iteration-for-implementing-changes-that-come-with-adl-1-5/13228)
> Revision: 549
Author: seref\.arikan
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[548]](https://discourse.openehr.org/t/topic/13179)
> Revision: 548
Author: seref\.arikan
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR conference - proposal for Lake Bled, Slovenia 2012 - POLL](https://discourse.openehr.org/t/openehr-conference-proposal-for-lake-bled-slovenia-2012-poll/15137)
> Dear all,
for some years now, people have expressed interest in a live openEHR event. There is no doubt it is overdue! One nice place for such an event happens to be available for 2012: **Lake Bled, Slovenia**, sometime in the period **mid September - mid October** - if we act fast. **Nothing has been booked**: the purpose of this post is for you to decide if you like the idea, and vote on the doodle poll below, so we can determine interest and dates. PLEASE RESPOND AS SOON AS YOU RECEIVE...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Carriage returns in DV_TEXT not allowed](https://discourse.openehr.org/t/carriage-returns-in-dv-text-not-allowed/15120)
> If DV_TEXT doesn't allow to use carriage returns, line feeds, or other non-printing characters, as stated in [http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf](http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf), pag 29, there is a way to represent short text with minimal formatting characters (carriage returns)? Which data type should be used?
Thank you.
Regards
leo
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [termbinding constraints in the archetype editor](https://discourse.openehr.org/t/termbinding-constraints-in-the-archetype-editor/15129)
> Everybody,
I am trying to bind an attribute in an archetype to a value set from a terminology server. The data in the termserver is availiable through web services. In practice, it should thus be possible to specify a URI in an archetype constraint for the elementattribute. Can't figure out how this is meant to be done in AE. Anyone with experience of how to do this in practice?
Does anyone know what the AE does when you enter the interface screen. Is the constraint executed, if not, when...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Constraints on class methods](https://discourse.openehr.org/t/constraints-on-class-methods/15125)
> When I was trying to validate an archetype with the reference model
\(openEHR\-EHR\-OBSERVATION\.apgar\), I found something strange on all
'event' archetypes\.
The EVENT class has a function \(method\) that calculates the offset\.
However, in that archetype the offset was restricted as if it was an
attribute\.
What is the sense for this? Shouldn't this restriction be expressed as
an assertion over the different attributes? \(that is, a restriction
that must be checked at runtime...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [bugs in domain types in XMLserializer](https://discourse.openehr.org/t/bugs-in-domain-types-in-xmlserializer/15126)
> Hello everyone :\)
This one is related to my post on the the technical list\. I have found
some missing things on the XMLserializer \(I would make the changes
myself, but I have yet to connect to the SVN\)
\-regarding domain types:
\-missing assumed\_values in both schema and the serializer
\-code\_phrase: code\_list is really called code\_string on the schema
I have also found some places \(printCDate, printCDateTime, etc\.\) where
the java implementation is more powerful than both the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1667] Enable RM paths for annotations.](https://discourse.openehr.org/t/ref-impl-eiffel-1667-enable-rm-paths-for-annotations/12582)
> Revision: 1667
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[547] fixed term_code parsing issue in dadl parser](https://discourse.openehr.org/t/547-fixed-term-code-parsing-issue-in-dadl-parser/12579)
> Revision: 547
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[546] check in initial adl1.5 javacc src file](https://discourse.openehr.org/t/546-check-in-initial-adl1-5-javacc-src-file/12575)
> Revision: 546
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How is assumed value marked on domain types? (in XML)](https://discourse.openehr.org/t/how-is-assumed-value-marked-on-domain-types-in-xml/15123)
> In ADL, the assumed value of a domain type is marked like this:
defining\_code matches \{
\[local::
at1000, \-\- Standing
at1001, \-\- Sitting
at1002, \-\- Reclining
at1003, \-\- Lying
at1014; \-\- Lying with tilt to left
at1001\] \-\-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [pass_through attribute in ADL 1.5](https://discourse.openehr.org/t/pass-through-attribute-in-adl-1-5/15130)
> Put a couple of comments on the wiki, but I think it is a thing that
should be discussed on the list\.
In ADL 1\.5 a flag 'pass\_through' was added\. Its definition is 'Allows
nodes required for structuring data but otherwise redundant for screen
display and reporting to be detected by rendering software'\. So now we
have a GUI directive on the ADL\. Shouldn't this be a part of the
reference model information \(if it is never supposed to be displayed\)
or part of a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Did anybody implement AQL with a LL parser framework?](https://discourse.openehr.org/t/did-anybody-implement-aql-with-a-ll-parser-framework/15566)
> Greetings,
The AQL grammar from the wiki has direct and indirect left recursion. Which means without changes in the grammar, LL parser generators (both JavaCC and Anltr) can't generate parsers for this grammar.
I'm curious if anybody has refactored this grammar for LL parser generators. Shinji? Your latest release includes an AQL parser does not it? Could you please share your method? I can always look at the code, but you'd probably save me time :)
I'm interested in experiences of others...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reference Model based application development - RIMBAA March 8 in Gothenburg](https://discourse.openehr.org/t/reference-model-based-application-development-rimbaa-march-8-in-gothenburg/15965)
> The location and date of the Reference Model based implementers meeting
\(HL7 RIMBAA\) have been confirmed:
\*\* March 8, 2012, RIMBAA, in Gothenburg, Sweden
Core topic: software implementation aspects of Refence Model based
applications, focusing on both the 13606/OpenEHR RM as well as the HL7
RIM\. Sweden has opted to use 13606/OpenEHR as the base standards for its
national infrastructure, which means there should be lots of
opportunities to discuss RM based implementation issues at this...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[545] added ADL 1.5 test files and adjusted the javacc file path](https://discourse.openehr.org/t/545-added-adl-1-5-test-files-and-adjusted-the-javacc-file-path/12481)
> Revision: 545
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Outcomes & conclusions of the openEHR course in spanish (& ideas for the future)](https://discourse.openehr.org/t/outcomes-conclusions-of-the-openehr-course-in-spanish-ideas-for-the-future/15121)
> Hi everyone,
Recently we have ended the first edition of the course with a huge success. And now we are thinking about the next steps to take.
Here is a post on my blog about the conclusions and future actions: [http://informatica-medica.blogspot.com/2012/01/conclusiones-del-curso-de-openehr-en.html](http://informatica-medica.blogspot.com/2012/01/conclusiones-del-curso-de-openehr-en.html)
(yo can see it in english by clicking ENGLISH on the top right corner of the blog).
**I want to share...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Does XMLSerializer (java) create archetype slots with too much extra information?](https://discourse.openehr.org/t/does-xmlserializer-java-create-archetype-slots-with-too-much-extra-information/16691)
> This is a simple question: Why does a simple archetype slot like this \(ADL\)
allow\_archetype ELEMENT\[at0001\] occurrences matches \{0\.\.\*\} matches \{
\-\- Archetype slot
include
archetype\_id/value matches \{/\.\*/\}
\}
ends up like this?
<children...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Pulmonary Function Test Arquetype](https://discourse.openehr.org/t/pulmonary-function-test-arquetype/15950)
> Dear Ian:
Sorry it took me some days to get back to you. I´m also sending this mail to the Clinical Discussion List as it may benefit others.
The proposed pulmonary function archetype is also adequate for adult use, I took some extra time to have it checked by the Chief of Intensive Care at my Hospital. The archetype is detailed enough for international use.
Your assumption is correct *VO2max* does merit a **separate archetype** included as a subset of a more detailed "*Exercise Stress...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[544] Testing removal of UTF-8 BOM marker at beginning of file to get Maven builds working on Mac OS](https://discourse.openehr.org/t/544-testing-removal-of-utf-8-bom-marker-at-beginning-of-file-to-get-maven-builds-working-on-mac-os/12823)
> Revision: 544
Author: erik\.sundvall
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1666] Add support for RM-path annotations.](https://discourse.openehr.org/t/ref-impl-eiffel-1666-add-support-for-rm-path-annotations/12811)
> Revision: 1666
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1665] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1665-changes/12777)
> Revision: 1665
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Ruby implementation version1.0.0 released](https://discourse.openehr.org/t/ruby-implementation-version1-0-0-released/15124)
> Happy holidays, folks\!
I just released Ruby implementation of the openEHR specification version
1\.0\.0\. This is the first stable branch of our porject\. Our project is
still in progress and not so matured as other implementation, but it
covers almost all specifications of the openEHR specification documents\.
This release includes:
\* ADL 1\.4 parser
\* AOM packages based on specification release 1\.0\.2
\* RM packages based on specification release 1\.0\.2
\* Change license to Apache...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Happy Xmas openEHR and IP Allocations from Ocean and UCL](https://discourse.openehr.org/t/happy-xmas-openehr-and-ip-allocations-from-ocean-and-ucl/12328)
> Happy Xmas to the openEHR Community
2011 has been our year of greatest impact culminating in the decision by the international Clinical Information Modelling Initiative to use ADL. What many in the CIMI group do not yet know is how much effort has been expended and knowledge gained about how to govern these models and implement them in software. The discussion at CIMI will now move to replication of effort (a fresh start) or building on the openEHR effort and review of 13606. Developing ADL...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question to clinical modellers: are you usually online when you're working?](https://discourse.openehr.org/t/question-to-clinical-modellers-are-you-usually-online-when-youre-working/15117)
> Greetings,
I would like to get the opinion of clinical modelling community about the requirement of being online.
This is not a question about using web based tools. Even if you're using a modelling tool that does not require a browser, would it be a problem for you if the tool required that you are online?
There are some quite convenient features that I would like to think I can introduce to modelling tools, but the problem is, some of these features may require lots of computing power,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [evaluate sport activity](https://discourse.openehr.org/t/evaluate-sport-activity/15118)
> Hi all,
Can someone give me a hint about how I should do following, which kind
of entries are most suitable for this?
There is a software\-requirement, I work with, which says that a patient
should do sport, exercises\.
And to encourage the patient, there must be some kind of decision
support, which checks, the exercises the patient has done, and this
evalution must be stored for a later look\-back how the patient is doing\.
So, there must be an archetype which is able to decribe the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Basetypes (schema/specification)](https://discourse.openehr.org/t/basetypes-schema-specification/15115)
> I have been doing some tests with the file archetype\.xsd available on
the webpage and I have run with some problems\.
The main one is regarding BaseTypes\.xsd, which supposedly defines
types such as intervalOfInteger, intervalOfDate\.\.\., but doesn't
contain them\. Documentation
\(http://www.openehr.org/svn/specification/TRUNK/publishing/its/XML-schema/documentation/BaseTypes.xsd.html#h888547087)
says otherwise, so I'm not sure how are documentation and schema
generated/related\.
I...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [HIER_OBJECT_ID extension property](https://discourse.openehr.org/t/hier-object-id-extension-property/15114)
> Hi,
By spec UID_BASED_ID property extension is required.
I use HIER_OBJECT_ID and I don't know what to write to extension property? I don't found any examples in spec.
Gediminas
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1664] Add a further correction to YAML indentation logic.](https://discourse.openehr.org/t/ref-impl-eiffel-1664-add-a-further-correction-to-yaml-indentation-logic/15911)
> Revision: 1664
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Extracts availability](https://discourse.openehr.org/t/extracts-availability/16718)
> Hi,
I require some openEHR EHR Extracts for my research. Where can I get a few exemplary Extracts?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CIMI home page](https://discourse.openehr.org/t/cimi-home-page/12197)
> I have constructed a [home page for CIMI visitors](http://www.openehr.org/wiki/display/stds/CIMI+Home+Page). For those interested in this activity, please feel free to review, and provide feedback to me, or fix any obvious errors / omissions directly on the page. Please be aware that there may be a significant number of new visitors to the openEHR wiki not (currently) from the openEHR community, and this page will act as an entry point for them.
- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1663] Refactoring of class / feature names in archetype annotations classes.](https://discourse.openehr.org/t/ref-impl-eiffel-1663-refactoring-of-class-feature-names-in-archetype-annotations-classes/12524)
> Revision: 1663
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [AOM 1.5 - single v multiple attributes](https://discourse.openehr.org/t/aom-1-5-single-v-multiple-attributes/15110)
> A discussion I think has occurred in the distant past\.\. and it is now
more relevant than before, with the new interest in ADL/AOM by the CIMI
group\.
do we really need C\_SINGLE\_ATTRIBUTE and C\_MULTIPLE\_ATTRIBUTE
descendants of C\_ATTRIBUTE in the AOM? In the reference compiler I have
always had just C\_ATTRIBUTE with an is\_multiple flag\. This flag is set
at object creation time \(or it could be later\), but is independent of
whether the C\_ATTRIBUTE has multiple 'children'...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1661] Improve UI for turning on and off line-numbers in serialised and source formats .](https://discourse.openehr.org/t/ref-impl-eiffel-1661-improve-ui-for-turning-on-and-off-line-numbers-in-serialised-and-source-formats/12415)
> Revision: 1661
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1660] Missed minor code change as part of last commit.](https://discourse.openehr.org/t/ref-impl-eiffel-1660-missed-minor-code-change-as-part-of-last-commit/12377)
> Revision: 1660
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1659] Modified YAML serialiser to use the '- ' sequence item marker in a more normal way, and to only use double quotes on Strings, not characters, codes or other data types.](https://discourse.openehr.org/t/ref-impl-eiffel-1659-modified-yaml-serialiser-to-use-the-sequence-item-marker-in-a-more-normal-way-and-to-only-use-double-quotes-on-strings-not-characters-codes-or-other-data-types/12351)
> Revision: 1659
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[543] Create ADL 1.5 dev branch](https://discourse.openehr.org/t/543-create-adl-1-5-dev-branch/15818)
> Revision: 543
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [13606 revisited - list proposal](https://discourse.openehr.org/t/13606-revisited-list-proposal/15113)
> At the CIMI meeting last week and elsewhere, I have noticed a lot of
interest in the ISO 13606 2012 revision, specifically in a\) whether the
openEHR and 13606 reference models can be brought together for part 1 of
the revision and b\) in finalising ADL/AOM 1\.5 for providing a new
snapshot to ISO for part 2\.
It seems to me that it would be useful to have a dedicated place to
discuss this, so I would like to propose a new mailing list,
13606\-alignment@openehr\.org
Does this seem like a...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [CIMI group goes with openEHR archetypes & UML profile](https://discourse.openehr.org/t/cimi-group-goes-with-openehr-archetypes-uml-profile/15112)
> [press release from the CIMI group]
The Clinical Information Modeling Initiative is an international collaboration that is dedicated to providing a common format for detailed specifications for the representation of health information content so that semantically interoperable information may be created and shared in health records, messages and documents. CIMI has been holding meetings in various locations around the world since July, 2011. All funding and resources for these meetings have...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 62, Issue 10](https://discourse.openehr.org/t/openehr-clinical-digest-vol-62-issue-10/15789)
> Dear gerard,
If i want to collect the ff simple data for claims, will 13606 suffice?
Patient id
Last name
Given name
Birthday
Sex
Provider id
Facility id
Icd10 diagnosis main
Icd10 diagnosis cooccuring
Cpt code main
Cpt code others
Fulltext diagnosis
Fulltext procedures
Timestamp
Alvin
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1658] First version of YAML 1.1 serialiser.](https://discourse.openehr.org/t/ref-impl-eiffel-1658-first-version-of-yaml-1-1-serialiser/12082)
> Revision: 1658
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Revision of Instructions - clinical implications](https://discourse.openehr.org/t/revision-of-instructions-clinical-implications/15116)
> There is a discussion on the technical lists about handling
INSTRUCTIONS and subsequent ACTIONS in openEHR\. Heather Leslie has
provided an excellent explanation of the process but there is one
comment that I feel merits some further clinical discussion\.
"But: how is that change of the Instruction state recorded on the EHR?
\[HL>\] The INSTRUCTION for a procedure remains unchanged, unless the
clinician changes the nature of the original order and this is carried
out with a revision...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers Digest, Vol 56, Issue 4](https://discourse.openehr.org/t/openehr-implementers-digest-vol-56-issue-4/16518)
> Dear Thomas,
"Right now, I would go where
there are more tools & technology that correspond to your particular needs\."
Thanks\. I'd like to release an XML schema that constrains a medical insurance claim \(maybe between 10\-15 elements\)\. But later, we'll start adding elements/details until the claimants \(clinics and hospitals\) realize that they have already built an EMR\.
I think the claims paradigm is a strong driver for clinic/hospital automation, and releasing...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Security implementation or specification?](https://discourse.openehr.org/t/security-implementation-or-specification/11994)
> Dear all,
I am looking for an implementation of ACCESS_CONTROL_SETTINGS in EHR_ACCESS or specification of "openEHR security information model".
Could anyone give some pointers related to those subject?
Thanks in advance.
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Wrong C_DOMAIN_TYPE subclass C_CODED_TEXT in aom and aom1.5?](https://discourse.openehr.org/t/wrong-c-domain-type-subclass-c-coded-text-in-aom-and-aom1-5/15111)
> Hi,
I'm working with archetypes that have DV_CODED_TEXT nodes, and those nodes are always constrained by C_COMPLEX_OBJECT, not by C_CODED_TEXT. And the internal constraint is C_CODE_PHRASE.
Is there any case that use the C_CODED_TEXT constraint instead of the combination of C_COMPLEX_OBJECT/C_CODE_PHRASE?
Thanks!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM new Release](https://discourse.openehr.org/t/ckm-new-release/16379)
> Dear all,
We have released a new version of CKM \- up and running at
openehr\.org/knowledge
The 1\.1\.5 release of CKM is a release that contains some major new
functionality and some minor usability changes and bugfixes\.
Most prominently, it features the newly developed review functionality
for terminology subsets \(termsets\) within CKM following a similar
process to the currently available archetype content reviews\.
Some new functionality has been integrated into this release in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [open source openEHR-related EHR systems; How do you want to be cited...](https://discourse.openehr.org/t/open-source-openehr-related-ehr-systems-how-do-you-want-to-be-cited/15102)
> Hi!
We now getting the LiU EEE paper "Applying REST Architecture to Archetype-based EHR systems" (by Erik Sundvall, Mikael Nyström, Daniel Karlsson, Martin Eneling, Rong Chen and Håkan Örman) finished for submission, and in a background passage we mention other openEHR based EHR systems (where you can enter and query pateint data) that are open source:
"...the situation has changed to the better and more open source alternatives [opereffa, openEHRgen, GastrOS, oship/MLHIM] that explores...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Questions about Version and Attestation](https://discourse.openehr.org/t/questions-about-version-and-attestation/12935)
> Hi,
I'm going through the specs to create ppts for the openEHR course in spanish, now I'm trying to explain about the electronic signature generation for a clinical record.
Should a non persistent compositon be versioned?
If not, is the only way of signing that non versioned composition to have an attestation with a reference to that composition in its "items"?
If that's right, I think this constraint should be added to the invariants on ATTESTATION or in the description of the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Questions about the relationship between Instruction, workflow and Action](https://discourse.openehr.org/t/questions-about-the-relationship-between-instruction-workflow-and-action/15101)
> Hi everyone!
I'm trying to understand how to execute a state machine of a fully structured INSTRUCTION, and I have some questions and thoughts to share with you...
The first issue is about archetyping an ACTION that execute and ACTIVITY of an INSTRUCTION. Modeling an ACTION, the Archetype Editor let me archetype the ACTION.ism_transition attribute, but not the ACTION.instruction_details. Both attribute classes (ISM_TRANSITION and INSTRUCTION_DETAILS) are specializations of PATHABLE, so...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers Digest, Vol 56, Issue 1](https://discourse.openehr.org/t/openehr-implementers-digest-vol-56-issue-1/14244)
> Thanks for the comments\.
If I want to go for 13606 \(not yet the full openehr implementation\), where do I start?
I want to release schemas for insurance claims\.\.\.and I don't want to bother with creating applications for the hospitals but just constrain them on the format of the claim\.
Alvin
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Start with openEHR or with HL7 CDAv2?](https://discourse.openehr.org/t/start-with-openehr-or-with-hl7-cdav2/15107)
> Hi Thomas, openehr team,
If a developing country had a chance to implement an EHR extraction standard, and they wish to do this incrementally:
should they start with HL7 CDA2's XML schema and then mature towards a full openehr implementation
OR
should they start with the openehr schema and constrain it to become as simple as the CDA2?
I think my question is which schema to use -- CDA2 or openehr?
I am basing my question on a paper by Peter that compared openehr, 13606, HL7 3 and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL Workbench beta 5](https://discourse.openehr.org/t/adl-workbench-beta-5/15099)
> This new beta, available [here](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html), includes the following features:
- new Class Tool: [properties view](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/images/class_tool.png), [ancestors view](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/images/class_tool_ancestors.png), [descendants...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1657] Update the download information on the main help page.](https://discourse.openehr.org/t/ref-impl-eiffel-1657-update-the-download-information-on-the-main-help-page/14232)
> Revision: 1657
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1656] Update release notes SVN rev link](https://discourse.openehr.org/t/ref-impl-eiffel-1656-update-release-notes-svn-rev-link/14231)
> Revision: 1656
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1655] Update release notes SVN rev link](https://discourse.openehr.org/t/ref-impl-eiffel-1655-update-release-notes-svn-rev-link/14228)
> Revision: 1655
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1654] Bug fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1654-bug-fixes/16378)
> Revision: 1654
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1653] Commit after merging and testing of adl 1.5 rev 1651](https://discourse.openehr.org/t/ref-impl-eiffel-1653-commit-after-merging-and-testing-of-adl-1-5-rev-1651/15504)
> Revision: 1653
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1652] commented out code in experimental_app which is not used at the moment, also removed statements to set current item in the archetype catalague, which is not required anyway.](https://discourse.openehr.org/t/ref-impl-eiffel-1652-commented-out-code-in-experimental-app-which-is-not-used-at-the-moment-also-removed-statements-to-set-current-item-in-the-archetype-catalague-which-is-not-required-anyway/14227)
> Revision: 1652
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1651] Minor bug fixes to ADL Compiler command line app (simulates Seref' s build).](https://discourse.openehr.org/t/ref-impl-eiffel-1651-minor-bug-fixes-to-adl-compiler-command-line-app-simulates-seref-s-build/14226)
> Revision: 1651
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1650] commit after merge with 1601-1647 of adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1650-commit-after-merge-with-1601-1647-of-adl-1-5/16377)
> Revision: 1650
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1649] Update ext-ref SVN rev for knowledge2 repo, so that the correct BMM schemas are picked up in builds.](https://discourse.openehr.org/t/ref-impl-eiffel-1649-update-ext-ref-svn-rev-for-knowledge2-repo-so-that-the-correct-bmm-schemas-are-picked-up-in-builds/16376)
> Revision: 1649
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1648] after attempts at serializing protocol buffer wrappers to string, I had to give up, since Java side can' t decode binary strings without an encoding.](https://discourse.openehr.org/t/ref-impl-eiffel-1648-after-attempts-at-serializing-protocol-buffer-wrappers-to-string-i-had-to-give-up-since-java-side-can-t-decode-binary-strings-without-an-encoding/16375)
> Revision: 1648
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1647] Updated version info for build.](https://discourse.openehr.org/t/ref-impl-eiffel-1647-updated-version-info-for-build/14225)
> Revision: 1647
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1646] Copy latest documentation to TRUNK, for display on web.](https://discourse.openehr.org/t/ref-impl-eiffel-1646-copy-latest-documentation-to-trunk-for-display-on-web/14224)
> Revision: 1646
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1645] Fixed some errors in error/warning propagation in BMM processing.](https://discourse.openehr.org/t/ref-impl-eiffel-1645-fixed-some-errors-in-error-warning-propagation-in-bmm-processing/14223)
> Revision: 1645
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1644] Improve Class Tool icons.](https://discourse.openehr.org/t/ref-impl-eiffel-1644-improve-class-tool-icons/14222)
> Revision: 1644
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1643] Update release notes page SVN rev.](https://discourse.openehr.org/t/ref-impl-eiffel-1643-update-release-notes-page-svn-rev/16374)
> Revision: 1643
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1642] Update documentation for beta release 5.](https://discourse.openehr.org/t/ref-impl-eiffel-1642-update-documentation-for-beta-release-5/16373)
> Revision: 1642
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1641] Add some entries to File menu, and also Catalogue context menu to allow Save As, Export As and Export flat as.](https://discourse.openehr.org/t/ref-impl-eiffel-1641-add-some-entries-to-file-menu-and-also-catalogue-context-menu-to-allow-save-as-export-as-and-export-flat-as/16372)
> Revision: 1641
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1640] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1640-changes/16370)
> Revision: 1640
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [a first attempt JSON archetype](https://discourse.openehr.org/t/a-first-attempt-json-archetype/15106)
> The JSON archetype below was generated by traversing the P_XX class structure I have developed that simplifies the persisted form of an archetype. It mainly turns a lot of fields into Strings, including our old friends occurrences and cardinality. Things to note:
- ordering of attributes is somewhat random
- JSON is pretty mindless in some ways - Hash keys are serialised in the same way as attribute names, which must make input parsing pretty annoying. At least I think I have this...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CIMI Meeting next week in London](https://discourse.openehr.org/t/cimi-meeting-next-week-in-london/16369)
> Hi Sam,
This is great news\. A lot of thanks for your longstanding input as well\. I tend to think that you're the other driving force behind openEHR\.
If the people who have to vote next week are open for arguments and keep the real desired outcome in mind, i'm convinced they'll choose for openEHR\.
Cheers,
Stef
Begin doorgestuurd bericht:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Could YAML replace dADL as human readable AOM serialization format?](https://discourse.openehr.org/t/could-yaml-replace-dadl-as-human-readable-aom-serialization-format/15105)
> Hi!
A little suggestion/thought (that might be of value also for CIMI-folks and others looking at "archetyping" using ADL and AOM and wondering if a specific language is needed).
**Limitations:**
For efficient handling of RM (Reference Model) instances (patient data) flying back and forth between systems you'd probably want some binary format ([protobuf](http://code.google.com/p/protobuf/), [thrift datatypes](http://thrift.apache.org/), serialized Java objects or whatever), this is NOT what...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [CIMI Meeting next week in London](https://discourse.openehr.org/t/cimi-meeting-next-week-in-london/16371)
> Hi everyone,
A quick update from me personally. There is a meeting of the Clinical Information Modelling Initiative led by Stan Huff from Intermountain next week in London to firm up the preferred option for the primary clinical model authoring environment. A preliminary vote has been held, and despite some strong lobbying from Europe by some small interest groups, openEHR ADL is on the table with UML as the two most popular candidates.
This is no mean feat, and regardless of the outcome...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1639] Fix bug where selection history was not properly shared to all subtools of the GUI_CATALOGUE_TOOL .](https://discourse.openehr.org/t/ref-impl-eiffel-1639-fix-bug-where-selection-history-was-not-properly-shared-to-all-subtools-of-the-gui-catalogue-tool/14220)
> Revision: 1639
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Bosphorus web services beta announcement](https://discourse.openehr.org/t/bosphorus-web-services-beta-announcement/15103)
> Dear members of the openEHR community,
Having reached a point where project Bosphorus has reached a functional state, we have deployed and experimental web service under Opereffa's current server.
The web service exposes the archetype parser functionality of Thomas Beale's Eiffel code base with XML and JSON output. There is a simple web application at [http://opereffa.chime.ucl.ac.uk/bosphorus/](http://opereffa.chime.ucl.ac.uk/bosphorus/) which uses this web service to display XML and JSON...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[542] Correct Norwegian codes and Kasakh language code](https://discourse.openehr.org/t/542-correct-norwegian-codes-and-kasakh-language-code/14219)
> Revision: 542
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Norwegian languages in openehr terminology](https://discourse.openehr.org/t/norwegian-languages-in-openehr-terminology/15100)
> Dear all,
in the Java openEHR terminology file ( mini-termserv\src\main\resources\openehr_terminology_en.xml)
there are the following entries for the Norwegian language:
I have also added a statistics page to the Archetype tool, currently with an output like the following:
I...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1628] Minor additional refactoring prior to addition of RM viewing tool.](https://discourse.openehr.org/t/ref-impl-eiffel-1628-minor-additional-refactoring-prior-to-addition-of-rm-viewing-tool/15465)
> Revision: 1628
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1627] Rename GUI_RM_SCHEMA_TOOL -> GUI_RM_SCHEMA_EXPLORER to make way for individual schema tool.](https://discourse.openehr.org/t/ref-impl-eiffel-1627-rename-gui-rm-schema-tool-gui-rm-schema-explorer-to-make-way-for-individual-schema-tool/16368)
> Revision: 1627
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1626] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1626-changes/14205)
> Revision: 1626
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR course in spanish](https://discourse.openehr.org/t/openehr-course-in-spanish/14199)
> Hi,
I'm trying to impart a course on openEHR for spanish speakers audiences, here is the agenda for the course: [http://informatica-medica.blogspot.com/2011/10/curso-de-openehr-en-espanol.html](http://informatica-medica.blogspot.com/2011/10/curso-de-openehr-en-espanol.html)
Please click on the "ENGLISH" link on the top-right corner to translate the page.
This are my 2 cents in spreading openEHR in the latin-american medical informatics communities.
It would be nice to have the feedback of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1625] Missed statistics class from previous commit;](https://discourse.openehr.org/t/ref-impl-eiffel-1625-missed-statistics-class-from-previous-commit/14203)
> Revision: 1625
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1624] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1624-changes/14196)
> Revision: 1624
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1623] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1623-changes/16367)
> Revision: 1623
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR BMM schemas - who is using them](https://discourse.openehr.org/t/openehr-bmm-schemas-who-is-using-them/14198)
> I would like to know if anyone is currently directly using the BMM (basic meta-model) [schemas](http://www.openehr.org/wsvn/knowledge2/TRUNK/rm_schemas/) that drive the ADL Workbench. I am working on a major software update that will require these schemas to change their format.
thanks
- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes for "Body fluid or substance" and "Bodily output"](https://discourse.openehr.org/t/archetypes-for-body-fluid-or-substance-and-bodily-output/15095)
> Hi!
We’re slowly getting into translating a small set of archetypes into Norwegian, and we’re a bit confused about some properties from the archetypes Body fluid or substance and Bodily output. Bodily output is described as “*Recording of findings and measurement (or estimation) of bodily output such as fluid output and defaecation.*”, and Body fluid or substance as “*Details of the findings relating to a bodily fluid, secretion or substance.*”.
In relation to these, we’re wondering why the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from thomas.beale@oceaninformatics.com requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-thomas-beale-oceaninformatics-com-requires-approval/14195)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@openehr\.org
Reason: Message body is too big: 72664 bytes with a limit of 40 KB
At your convenience, visit:
http://lists.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
to approve or deny the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Questions about the necessity of ITEM_SINGLE](https://discourse.openehr.org/t/questions-about-the-necessity-of-item-single/15092)
> Hi everyone,
I've been studying how to simplify the ITEM_STRUCTURE model to enhance the persistence performance of our Open EHR-Gen project (http://code.google.com/p/open-ehr-gen-framework).
Now I'm reaching a point in which I doubt about the necessity of ITEM_SINGLE in the RM (as a subclass of ITEM_STRUCTURE) and I want to expose some arguments and hear your comments about it.
Semantic argument: As I understand ITEM_SINGLE, the semantics of this class are the same as an ITEM_LIST or...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR schemas](https://discourse.openehr.org/t/openehr-schemas/13931)
> Hello,
After studying the documentation and the xsd schemas published on your website (openEHR Release 1.0.2 Archetype XML schema, Authored by Ocean Informatics 2008.12.22 and OpenEHR Release 1.0.2 documentation) I found out that they are not 100% in sync.
The differences that I found until now are in Archetype package:
1. for complexType C_DATE, C_DATE_TIME, C_TIME, C_DURATION the element name="pattern" is not present in the documentation instead other elements are for i.e month_validity,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1622] Various bug fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1622-various-bug-fixes/16366)
> Revision: 1622
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1621] Minor corrections to error db files.](https://discourse.openehr.org/t/ref-impl-eiffel-1621-minor-corrections-to-error-db-files/16365)
> Revision: 1621
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1620] update error DB for adl_compiler_app.](https://discourse.openehr.org/t/ref-impl-eiffel-1620-update-error-db-for-adl-compiler-app/16364)
> Revision: 1620
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1619] Correct error database, to use separate files for the GUI interface and the errors from the compiler](https://discourse.openehr.org/t/ref-impl-eiffel-1619-correct-error-database-to-use-separate-files-for-the-gui-interface-and-the-errors-from-the-compiler/15454)
> Revision: 1619
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1618] Correct compiler errors in adl_compiler_app due to more recent changes in adl_workbench .](https://discourse.openehr.org/t/ref-impl-eiffel-1618-correct-compiler-errors-in-adl-compiler-app-due-to-more-recent-changes-in-adl-workbench/15453)
> Revision: 1618
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New release of the Open EHR-Gen framework v0.6](https://discourse.openehr.org/t/new-release-of-the-open-ehr-gen-framework-v0-6/16362)
> Hi everyone!
I'm very pleased to annouce the new version of our openEHR-based framework.
Here is a description of the release (spanish only): http://informatica-medica.blogspot.com/2011/09/nueva-version-de-openehr-gen-framework.html
English (automatically translated): http://translate.google.com/translate?sl=es&tl=en&js=n&prev=_t&hl=es&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Finformatica-medica.blogspot.com%2F2011%2F09%2Fnueva-version-de-openehr-gen-framework.html
Enjoy!
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Status of Java RI and openEHR in general](https://discourse.openehr.org/t/status-of-java-ri-and-openehr-in-general/15090)
> Hello,
I heard about the openEHR initiative some time ago and have been following it with interest, from a developer perspective. The recent transition announcement sounds encouraging, however there are some questions which I feel are left unanswered, after doing my best to read through the openEHR documentation on the website:
1) It would be great to have a more detailed and up-to-date status of projects. Looking at the Java reference implementation, I see it is incomplete, lagging behind...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [templates and views](https://discourse.openehr.org/t/templates-and-views/14194)
> Hi all,
I am preety new to openEHR and even newer to all these kinds of mailiing lists so please correct me if this question is sent to wrong list.
I am now implementing openEHR for my master's thesis and stuck with views. I have figured out that openEHR template is basically a scheme for the view. It only describes what elements the view is going to contain, but it does not says how are they placed. So I have taken Demo-with-hide-on-form template from clinical manager, wrote XSLT for it...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Doubt about the link between archetypes' ontology and reference model](https://discourse.openehr.org/t/doubt-about-the-link-between-archetypes-ontology-and-reference-model/15088)
> I have recently started working with archetypes and medical terminologies, and I have a doubt regarding how the terms in the ontology section of archetypes are related to the underlying reference model. For example, if I am not wrong, the "meaning" attribute of the RECORD_COMPONENT class of the reference model of the CEN 13606 standard is the place where the ontology term will be stored for that record component. An example will make this more clear. Suppose we have an archetype like...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [future of CEN 13606 data types](https://discourse.openehr.org/t/future-of-cen-13606-data-types/13868)
> At the HL7 meeting last week in San Diego, Grahame Grieve presented something called [Resources for Healthcare](http://www.healthintersections.com.au/rfh/introduction.htm) (RFH), essentially a replacement model for much of HL7v3, for 'practical use'. The driver was the well-known over-complexity of HL7v3. According to [his report](http://www.healthintersections.com.au/?p=610) on the reception of RFH at the HL7 meeting, there appears to be a real appetite for change at HL7, which is good to...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1617] Remove old file preventing server compilation completing](https://discourse.openehr.org/t/ref-impl-eiffel-1617-remove-old-file-preventing-server-compilation-completing/14193)
> Revision: 1617
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1616] Small adjustment to icons.](https://discourse.openehr.org/t/ref-impl-eiffel-1616-small-adjustment-to-icons/14192)
> Revision: 1616
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1615] Correct a subtle bug affecting matching of classes to archetypes in the Archetype Catalogue .](https://discourse.openehr.org/t/ref-impl-eiffel-1615-correct-a-subtle-bug-affecting-matching-of-classes-to-archetypes-in-the-archetype-catalogue/14191)
> Revision: 1615
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1614] Change Archetype and Template catalog to Notebook format.](https://discourse.openehr.org/t/ref-impl-eiffel-1614-change-archetype-and-template-catalog-to-notebook-format/14190)
> Revision: 1614
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype licensing - CC-BY-SA proposal clarified](https://discourse.openehr.org/t/archetype-licensing-cc-by-sa-proposal-clarified/15089)
> It turns out that the white paper does not describe very clearly what was intended by the use of CC-BY-SA for archetypes. After discussion with Sam, I have created a [new wiki page ](http://www.openehr.org/wiki/display/oecom/Archetype+licensing+-+the+case+for+CC-BY-SA)describing in detail the intended proposal. I think wider understanding and more informed debate of the proposal will now be possible.
- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR and ISO EN 13606](https://discourse.openehr.org/t/openehr-and-iso-en-13606/14189)
> Dear Colleagues,
I am often asked about the relationship between ISO EN 13606 and openEHR, and I note this topic has recently been raised on our lists\.
To say straight off, some people imagine there are tensions between these, but most of the people active in taking forward 13606 are also active in openEHR, and see value in both\. I certainly do\. Inevitably those close up to this subject tend to focus on fine differences, while those further away cannot understand what the differences are...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1613] Remove need to expand unexpanded class nodes in Class Tool.](https://discourse.openehr.org/t/ref-impl-eiffel-1613-remove-need-to-expand-unexpanded-class-nodes-in-class-tool/15444)
> Revision: 1613
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1612] Correct Address bar focus problem.](https://discourse.openehr.org/t/ref-impl-eiffel-1612-correct-address-bar-focus-problem/15441)
> Revision: 1612
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1611] Update RM schemas to knowledge2 SVN rev 56](https://discourse.openehr.org/t/ref-impl-eiffel-1611-update-rm-schemas-to-knowledge2-svn-rev-56/15440)
> Revision: 1611
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1610] Fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1610-fixes/14188)
> Revision: 1610
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Transition: Web-based tools?](https://discourse.openehr.org/t/openehr-transition-web-based-tools/15086)
> Hi all,
One of the suggestions in the White Paper which appears to have
universal support is a move to support much more open\-source tools
development\. Clearly some tooling must be web\-based e\.g repository
management and associated formal and informal discussion e\.g\. CKM and
any new community repository\.
However, I am much less clear on why we might need web\-based primary
authoring tools for archetypes and templates\. Diego, Pablo and Sam are
all keen on this approach but I remain...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR Transition feedback / ideas wiki page](https://discourse.openehr.org/t/openehr-transition-feedback-ideas-wiki-page/14197)
> There is [this wiki page ](http://www.openehr.org/wiki/display/oecom/openEHR+Transition+Feedback+Page)for feedback that some of you have already used. Please feel free to add to it, including subpages, for larger content.
I re-organised the [parent page ](http://www.openehr.org/wiki/pages/viewpage.action?pageId=196692)(which points to discssions about licenses, among other things) as well to be more logical.
- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EN/ISO 13606 & openEHR - harmonisation possibilities](https://discourse.openehr.org/t/en-iso-13606-openehr-harmonisation-possibilities/15093)
> As you may have noticed, the new release of the [ADL Workbench ](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html)enables exploration of multiple reference models and their classes. Although the [13606 schema](http://www.openehr.org/svn/knowledge2/TRUNK/rm_schemas/cen_EN13606_0.95.bmm) is not yet complete (in particular the data types require work), it is now possible to see the [differences and similarities...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL 1.5 Workbench beta 4 release - major new features](https://discourse.openehr.org/t/adl-1-5-workbench-beta-4-release-major-new-features/15096)
> A new beta release of the ADL 1.5 Workbench is now available [here](http://www.openehr.org/svn/ref_impl_eiffel/BRANCHES/adl1.5/apps/adl_workbench/doc/web/index.html). Quite a lot of new features have been added, as described in the [release notes](http://www.openehr.org/svn/ref_impl_eiffel/BRANCHES/adl1.5/apps/adl_workbench/doc/web/release_notes.html). Please note that this release only includes a Windows build; Linux and Mac builds will follow in the next couple of weeks. (I would be...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1609] Add Beta number to splash screen info](https://discourse.openehr.org/t/ref-impl-eiffel-1609-add-beta-number-to-splash-screen-info/16361)
> Revision: 1609
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1608] Update version file.](https://discourse.openehr.org/t/ref-impl-eiffel-1608-update-version-file/16360)
> Revision: 1608
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1607] Add new files to TRUNK documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1607-add-new-files-to-trunk-documentation/16359)
> Revision: 1607
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1606] Final doc updates.](https://discourse.openehr.org/t/ref-impl-eiffel-1606-final-doc-updates/16358)
> Revision: 1606
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1605] Update documentation on TRUNK so that online help links work properly.](https://discourse.openehr.org/t/ref-impl-eiffel-1605-update-documentation-on-trunk-so-that-online-help-links-work-properly/16357)
> Revision: 1605
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1604] Further documentation updates.](https://discourse.openehr.org/t/ref-impl-eiffel-1604-further-documentation-updates/14187)
> Revision: 1604
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1603] Documentation updates.](https://discourse.openehr.org/t/ref-impl-eiffel-1603-documentation-updates/14184)
> Revision: 1603
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1602] Clarify error messages and add rescue clauses to protect against problems in parsing / validating BMM RM schemas.](https://discourse.openehr.org/t/ref-impl-eiffel-1602-clarify-error-messages-and-add-rescue-clauses-to-protect-against-problems-in-parsing-validating-bmm-rm-schemas/14183)
> Revision: 1602
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1601] Correct double appearance of right-click menu in archetype catalog.](https://discourse.openehr.org/t/ref-impl-eiffel-1601-correct-double-appearance-of-right-click-menu-in-archetype-catalog/14182)
> Revision: 1601
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1600] Commit after merging adl 1.5 branch with revisions 1261-1589](https://discourse.openehr.org/t/ref-impl-eiffel-1600-commit-after-merging-adl-1-5-branch-with-revisions-1261-1589/14181)
> Revision: 1600
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1599] Branch for switch to ADL 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1599-branch-for-switch-to-adl-1-5/14180)
> Revision: 1599
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1598] Failed attempt to merge adl 1.5 and existing Bosphorus work](https://discourse.openehr.org/t/ref-impl-eiffel-1598-failed-attempt-to-merge-adl-1-5-and-existing-bosphorus-work/14179)
> Revision: 1598
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1597] commit after Bosphorus branch under ..ref_impl_eiffel/BRANCHES/ Java has been merged](https://discourse.openehr.org/t/ref-impl-eiffel-1597-commit-after-bosphorus-branch-under-ref-impl-eiffel-branches-java-has-been-merged/14178)
> Revision: 1597
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1596] First commit after merge from adl 1.5 branch ( no Bosphorus related content yet)](https://discourse.openehr.org/t/ref-impl-eiffel-1596-first-commit-after-merge-from-adl-1-5-branch-no-bosphorus-related-content-yet/14177)
> Revision: 1596
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1595] Bosphorus branch for adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1595-bosphorus-branch-for-adl-1-5/14176)
> Revision: 1595
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1594] typo in dir name](https://discourse.openehr.org/t/ref-impl-eiffel-1594-typo-in-dir-name/14175)
> Revision: 1594
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1593] Bosphorus branch to use adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1593-bosphorus-branch-to-use-adl-1-5/14173)
> Revision: 1593
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1592] needs recreating due to problems in merge from adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1592-needs-recreating-due-to-problems-in-merge-from-adl-1-5/14172)
> Revision: 1592
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1591] Commit after merge from 1583-1589 revisions of ADL 1.5 ( recursive merge chosen from options)](https://discourse.openehr.org/t/ref-impl-eiffel-1591-commit-after-merge-from-1583-1589-revisions-of-adl-1-5-recursive-merge-chosen-from-options/14167)
> Revision: 1591
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1590] commits after initial fixes in Bosphorus related types, that occured due to jump to adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1590-commits-after-initial-fixes-in-bosphorus-related-types-that-occured-due-to-jump-to-adl-1-5/16356)
> Revision: 1590
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1589] Fix recompute agent call.](https://discourse.openehr.org/t/ref-impl-eiffel-1589-fix-recompute-agent-call/14166)
> Revision: 1589
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1588] Minor adjustments to event handling.](https://discourse.openehr.org/t/ref-impl-eiffel-1588-minor-adjustments-to-event-handling/15420)
> Revision: 1588
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1587] Make right-click menu work on templates; bug found by Peter Gummer.](https://discourse.openehr.org/t/ref-impl-eiffel-1587-make-right-click-menu-work-on-templates-bug-found-by-peter-gummer/14165)
> Revision: 1587
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1586] Correct bugs to do with changing RM schema directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1586-correct-bugs-to-do-with-changing-rm-schema-directory/14164)
> Revision: 1586
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1585] Correct open .adl file error found by Peter Gummer.](https://discourse.openehr.org/t/ref-impl-eiffel-1585-correct-open-adl-file-error-found-by-peter-gummer/15419)
> Revision: 1585
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1584] Missed class from last checkin.](https://discourse.openehr.org/t/ref-impl-eiffel-1584-missed-class-from-last-checkin/14163)
> Revision: 1584
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1583] Commit various fixes found due to cross-check of RM by Seref Arikan, as part of Bosphorus work.](https://discourse.openehr.org/t/ref-impl-eiffel-1583-commit-various-fixes-found-due-to-cross-check-of-rm-by-seref-arikan-as-part-of-bosphorus-work/14162)
> Revision: 1583
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1582]](https://discourse.openehr.org/t/ref-impl-eiffel-1582/14160)
> Revision: 1582
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1581] initial branch for adl 1.5 based Bosphorus](https://discourse.openehr.org/t/ref-impl-eiffel-1581-initial-branch-for-adl-1-5-based-bosphorus/14159)
> Revision: 1581
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1580]](https://discourse.openehr.org/t/ref-impl-eiffel-1580/14156)
> Revision: 1580
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1579] Branch from adl 1.5 to facilitate merge to adl 1.5](https://discourse.openehr.org/t/ref-impl-eiffel-1579-branch-from-adl-1-5-to-facilitate-merge-to-adl-1-5/14155)
> Revision: 1579
Author: seref\.arikan
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR Transition: Community Knowledge repository](https://discourse.openehr.org/t/openehr-transition-community-knowledge-repository/14574)
> Hi Diego,
I am strongly in favour of establishing a community\-led/
lightly\-governed clinical knowledge repository as suggested by Shinji,
particularly if we can arrange some sort of federation between this
and a number of locally or regionally managed repositories\.
However, these must sit quite separately from the openEHR CKM or any
other nationally governed repositories\. I would anticipate that many
of the archetypes from this repositories would find there way into the
governed CKMs...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1577] Two further UI changes from Sebastian.](https://discourse.openehr.org/t/ref-impl-eiffel-1577-two-further-ui-changes-from-sebastian/14153)
> Revision: 1577
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1576] Documentation updates.](https://discourse.openehr.org/t/ref-impl-eiffel-1576-documentation-updates/16355)
> Revision: 1576
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1575] New logo on web page](https://discourse.openehr.org/t/ref-impl-eiffel-1575-new-logo-on-web-page/15410)
> Revision: 1575
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Bosphorus Web Services and an open source communication layer for openEHR implementers](https://discourse.openehr.org/t/bosphorus-web-services-and-an-open-source-communication-layer-for-openehr-implementers/15077)
> Dear members of the openEHR community,
We announced Project Bosphorus from UCL, CHIME at the end of 2010 and
have been preparing an update on progress, including access to source
code and a web services implementation, for testing purposes \. Recent
questions on the openEHR lists are relevant to the progress made and
the following is therefore posted as an interim update, indicating the
open source materials that we expect to release shortly, as a further
component of the Opereffa platform,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1574] Make right click on any coded node in archetype definition tree cause open of ontology control at that code .](https://discourse.openehr.org/t/ref-impl-eiffel-1574-make-right-click-on-any-coded-node-in-archetype-definition-tree-cause-open-of-ontology-control-at-that-code/16354)
> Revision: 1574
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[541] Correcting the order of some elements from the XMLSerializer to correspond with the published xsd at http ://www.openehr.org/releases/1.0.2/its/XML-schema/index.html](https://discourse.openehr.org/t/541-correcting-the-order-of-some-elements-from-the-xmlserializer-to-correspond-with-the-published-xsd-at-http-www-openehr-org-releases-1-0-2-its-xml-schema-index-html/15409)
> Revision: 541
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [Ref_impl_eiffel unsubscribe notification](https://discourse.openehr.org/t/ref-impl-eiffel-unsubscribe-notification/15396)
> lxdlxd@mail\.hz\.zj\.cn has been removed from Ref\_impl\_eiffel\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1573] Minor fixes due to Sebastian's feedback.](https://discourse.openehr.org/t/ref-impl-eiffel-1573-minor-fixes-due-to-sebastians-feedback/14152)
> Revision: 1573
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1572] Make the schema context menu expansion options work properly](https://discourse.openehr.org/t/ref-impl-eiffel-1572-make-the-schema-context-menu-expansion-options-work-properly/14151)
> Revision: 1572
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1571] Convert archetype and template explorer context menus and selection to node-based style .](https://discourse.openehr.org/t/ref-impl-eiffel-1571-convert-archetype-and-template-explorer-context-menus-and-selection-to-node-based-style/14150)
> Revision: 1571
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1570] Add missing menu.show calls.](https://discourse.openehr.org/t/ref-impl-eiffel-1570-add-missing-menu-show-calls/14149)
> Revision: 1570
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1569] Make the search bar work for the RM schemas as well as archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-1569-make-the-search-bar-work-for-the-rm-schemas-as-well-as-archetypes/14148)
> Revision: 1569
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM Archetypes in XML don't seem to validate properly against available XSDs](https://discourse.openehr.org/t/ckm-archetypes-in-xml-dont-seem-to-validate-properly-against-available-xsds/15082)
> Hello everyone
Maybe there has been some intermediate change that i am missing here but
i am trying to validate "openEHR\-EHR\-OBSERVATION\.blood\_pressure\.v1\.xml"
\(downloaded as XML from the CKM editor today\) through the available XSDs
from http://www.openehr.org/releases/1.0.2/its/XML-schema/index.html and
i am getting a very large number of errors\.
Just as an indication, all the errors are "Invalid content was found"
mostly for the elements "existence"...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [feedback to openEHR Transition post](https://discourse.openehr.org/t/feedback-to-openehr-transition-post/14145)
> [PLEASE DO NOT REPLY TO THIS POST - USE THE OPTIONS BELOW]
To all who would like to provide feedback to the post by Sam Heard earlier today, please choose one or more of the following:
- discuss on the main lists, i.e. openehr-technical and/or openehr-clinical (although this is less than ideal, we feel it is better to keep the number of lists down in openEHR)
- provide direct private feedback to [Sam.Heard@OceanInformatics.com](mailto:Sam.Heard@OceanInformatics.com), in his capacity as...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Transition: two procedural and one licensing question](https://discourse.openehr.org/t/openehr-transition-two-procedural-and-one-licensing-question/15076)
> Hi!
Kudos for moving forward!
Plans seem to take some promising directions even though that whitepaper at...
[http://www.openehr.org:8888/openehr/321-OE/version/default/part/AttachmentData/data/openEHR%20Foundation%20moving%20forward.pdf](http://www.openehr.org:8888/openehr/321-OE/version/default/part/AttachmentData/data/openEHR%20Foundation%20moving%20forward.pdf)
...still needs some serious editing in order to better strengthen trust in openEHRs future.
**1. First a procedural...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Transition Announcement](https://discourse.openehr.org/t/openehr-transition-announcement/15084)
> Dear All,
I am writing on behalf of the new Transitional Board of *open*EHR to share our plans to take *open*EHR to a new level of operations; a new structure, business model and governance. Our vision is the creation of a thriving community that works collaboratively to benefit humanity through efficient and effective electronic health records (EHRs) that support the highest quality health care for the least effort.
Until now, the *open*EHR Foundation has functioned as an owner of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1568] Correct right click behaviour for classes.](https://discourse.openehr.org/t/ref-impl-eiffel-1568-correct-right-click-behaviour-for-classes/14147)
> Revision: 1568
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1566] Add context menu to RM schema node in schema tool.](https://discourse.openehr.org/t/ref-impl-eiffel-1566-add-context-menu-to-rm-schema-node-in-schema-tool/15397)
> Revision: 1566
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1565] Correct small rendering error in flat template visualisation.](https://discourse.openehr.org/t/ref-impl-eiffel-1565-correct-small-rendering-error-in-flat-template-visualisation/14141)
> Revision: 1565
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1564] Documentation updates](https://discourse.openehr.org/t/ref-impl-eiffel-1564-documentation-updates/14140)
> Revision: 1564
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1563] Add context menu source schema edit from class icons in Schema tree.](https://discourse.openehr.org/t/ref-impl-eiffel-1563-add-context-menu-source-schema-edit-from-class-icons-in-schema-tree/14139)
> Revision: 1563
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1562] Improve control layout slightly on Class tool, property view.](https://discourse.openehr.org/t/ref-impl-eiffel-1562-improve-control-layout-slightly-on-class-tool-property-view/14138)
> Revision: 1562
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1561] Correct some minor rendering bugs in template visualisation.](https://discourse.openehr.org/t/ref-impl-eiffel-1561-correct-some-minor-rendering-bugs-in-template-visualisation/16353)
> Revision: 1561
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1560] Improve validation in BMM schema loading process.](https://discourse.openehr.org/t/ref-impl-eiffel-1560-improve-validation-in-bmm-schema-loading-process/16352)
> Revision: 1560
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EHR Extracts](https://discourse.openehr.org/t/ehr-extracts/14137)
> I am working on interoperability aspect between healthcare standards\. For
running end to end scenarios I require openEHR messages \(EHR Extracts\)\. So
my queries are
1\. Can I be provided with EHR Extracts related to blood pressure, laboratory
messages etc that should be in the form of concrete openEHR messages to be
communicated between different HIS\.
2\. EHR Extracts are in the form of \.adls extension\. How to convert that to
XML form, are there any tools available to convert ADLS form...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1559] Slightly modify one icon; update knowledge2 external to rev 51.](https://discourse.openehr.org/t/ref-impl-eiffel-1559-slightly-modify-one-icon-update-knowledge2-external-to-rev-51/14136)
> Revision: 1559
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1558] Update to rev 50 of knowledge2;](https://discourse.openehr.org/t/ref-impl-eiffel-1558-update-to-rev-50-of-knowledge2/14135)
> Revision: 1558
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1557] added more copy methods to archetype_wrapper_generator. e also added methods to copy cprimitive subtypes to bosphorus_pb_visitor. e dv_date.e dv_time.e and dv_quantity. e are replaced with their current versions from the trunk, si](https://discourse.openehr.org/t/ref-impl-eiffel-1557-added-more-copy-methods-to-archetype-wrapper-generator-e-also-added-methods-to-copy-cprimitive-subtypes-to-bosphorus-pb-visitor-e-dv-date-e-dv-time-e-and-dv-quantity-e-are-replaced-with-their-current-versions-from-the-trunk-si/14134)
> Revision: 1557
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1556] Try to force a new build to pick up correct schemas.](https://discourse.openehr.org/t/ref-impl-eiffel-1556-try-to-force-a-new-build-to-pick-up-correct-schemas/14132)
> Revision: 1556
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1555] Partially correct duplication of classes in packages when doing post-load pacakge merge .](https://discourse.openehr.org/t/ref-impl-eiffel-1555-partially-correct-duplication-of-classes-in-packages-when-doing-post-load-pacakge-merge/14127)
> Revision: 1555
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1554] Change colour of folder icon in Catalogue view - because it is not a technical package , but an additional namespace structure for archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-1554-change-colour-of-folder-icon-in-catalogue-view-because-it-is-not-a-technical-package-but-an-additional-namespace-structure-for-archetypes/15383)
> Revision: 1554
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1553] Implement class ancestor view.](https://discourse.openehr.org/t/ref-impl-eiffel-1553-implement-class-ancestor-view/14126)
> Revision: 1553
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1552] Refactor class tool into two windows - prperties & inheritance.](https://discourse.openehr.org/t/ref-impl-eiffel-1552-refactor-class-tool-into-two-windows-prperties-inheritance/14125)
> Revision: 1552
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Mappings between openEHR and HL7 CDA](https://discourse.openehr.org/t/mappings-between-openehr-and-hl7-cda/15079)
> I am working on running an end to end scenario between HL7 CDA and openEHR. For the very said reason I have performed ontology mappings of the two standards ontologies for the mapping file to be generated. Other than the mapping file, I found few concepts of HL7 CDA schema to be mapped with openEHR concepts. The list of the mappings are (Left hand side are HL7 CDA concepts while right hand side concepts are of open EHR)
1. Author *equals* Related Party
2. CDA Code *equals* Archetype...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EHR Extracts Information](https://discourse.openehr.org/t/ehr-extracts-information/14128)
> I am working on interoperability aspect between healthcare standards. For running end to end scenarios I require openEHR messages (EHR Extracts). So my queries are
1. Can I be provided with EHR Extracts related to blood pressure, laboratory messages etc that should be in the form of concrete openEHR messages to be communicated between different HIS.
2. EHR Extracts are in the form of .adls extension. How to convert that to XML form, are there any tools available to convert ADLS form to...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1551] Further directory renaming in GUI class src tree](https://discourse.openehr.org/t/ref-impl-eiffel-1551-further-directory-renaming-in-gui-class-src-tree/14124)
> Revision: 1551
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1550] Some directory renaming in GUI class src tree](https://discourse.openehr.org/t/ref-impl-eiffel-1550-some-directory-renaming-in-gui-class-src-tree/14123)
> Revision: 1550
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1549] Finalise separation technical package structure from 'model' structure, where a 'model' is a grouping construct used to define the namespace for archetypes within a issuer .](https://discourse.openehr.org/t/ref-impl-eiffel-1549-finalise-separation-technical-package-structure-from-model-structure-where-a-model-is-a-grouping-construct-used-to-define-the-namespace-for-archetypes-within-a-issuer/14122)
> Revision: 1549
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Why there is building blocks in OpenEHR, not founded on top of Archetypes](https://discourse.openehr.org/t/why-there-is-building-blocks-in-openehr-not-founded-on-top-of-archetypes/16192)
> Hi
OpenEHR is a great effort, but some questions remained with me yet. The two level approach to Reference Model, is undertaken to help physical implementation to remain apart and unchanged once domain level knowledge changes. So why do we have other building blocks (e.g. Demographic package or version etc.) built without using this fundamental concept and formed fixed structures. (I know that a link to an archetype exists that for example may further describe PERSON or ORGANIZATION, but...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1548] Make the console popup when a profile is being populated.](https://discourse.openehr.org/t/ref-impl-eiffel-1548-make-the-console-popup-when-a-profile-is-being-populated/16351)
> Revision: 1548
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1547] Make console tool pop up when compilation is occurring](https://discourse.openehr.org/t/ref-impl-eiffel-1547-make-console-tool-pop-up-when-compilation-is-occurring/16350)
> Revision: 1547
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1546] Remove unneeded icons](https://discourse.openehr.org/t/ref-impl-eiffel-1546-remove-unneeded-icons/14121)
> Revision: 1546
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1545] Further refactoring in docking classes;](https://discourse.openehr.org/t/ref-impl-eiffel-1545-further-refactoring-in-docking-classes/14120)
> Revision: 1545
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1544] AWB Documentation updates](https://discourse.openehr.org/t/ref-impl-eiffel-1544-awb-documentation-updates/15371)
> Revision: 1544
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1543] added new method to fetch an archetype wrapper from an archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-1543-added-new-method-to-fetch-an-archetype-wrapper-from-an-archetype/15370)
> Revision: 1543
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1542] Correct error where compiler 'gen' directories not being properly initialised on startup.](https://discourse.openehr.org/t/ref-impl-eiffel-1542-correct-error-where-compiler-gen-directories-not-being-properly-initialised-on-startup/14119)
> Revision: 1542
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1541] Fix error where single-valued attribute nodes allowed addition of more than one sub-node .](https://discourse.openehr.org/t/ref-impl-eiffel-1541-fix-error-where-single-valued-attribute-nodes-allowed-addition-of-more-than-one-sub-node/14115)
> Revision: 1541
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1540] added void safety preconditions and void checking statements to archetype_wrapper_generator .e](https://discourse.openehr.org/t/ref-impl-eiffel-1540-added-void-safety-preconditions-and-void-checking-statements-to-archetype-wrapper-generator-e/14114)
> Revision: 1540
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1539] Fix dumb icon reference error.](https://discourse.openehr.org/t/ref-impl-eiffel-1539-fix-dumb-icon-reference-error/14113)
> Revision: 1539
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1538] Various refactoring of docking and Class and Archetype Tool classes.](https://discourse.openehr.org/t/ref-impl-eiffel-1538-various-refactoring-of-docking-and-class-and-archetype-tool-classes/14112)
> Revision: 1538
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1537] added the main class for copying archetype class features to pb wrapper.](https://discourse.openehr.org/t/ref-impl-eiffel-1537-added-the-main-class-for-copying-archetype-class-features-to-pb-wrapper/14111)
> Revision: 1537
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [Bounce action notification](https://discourse.openehr.org/t/bounce-action-notification/14110)
> This is a Mailman mailing list bounce action notice:
List: Ref\_impl\_eiffel
Member: lxdlxd@mail\.hz\.zj\.cn
Action: Subscription disabled\.
Reason: Excessive or fatal bounces\.
The triggering bounce notice is attached below\.
Questions? Contact the Mailman site administrator at
mailman@openehr\.org\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1536] Updates to AWB documentation and images.](https://discourse.openehr.org/t/ref-impl-eiffel-1536-updates-to-awb-documentation-and-images/16349)
> Revision: 1536
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1535] Upload a set of .png openEHR RM icons, adapted from Sebastian' s icons, plus various minor adjustments to visualisation.](https://discourse.openehr.org/t/ref-impl-eiffel-1535-upload-a-set-of-png-openehr-rm-icons-adapted-from-sebastian-s-icons-plus-various-minor-adjustments-to-visualisation/14109)
> Revision: 1535
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1534] Add RM icons checkbox to node map, and improve visualisation logic, so that RM attributes can be turned on and off independently of other options .](https://discourse.openehr.org/t/ref-impl-eiffel-1534-add-rm-icons-checkbox-to-node-map-and-improve-visualisation-logic-so-that-rm-attributes-can-be-turned-on-and-off-independently-of-other-options/16348)
> Revision: 1534
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1533] Fix a precondition violation that occurred during application start-up.](https://discourse.openehr.org/t/ref-impl-eiffel-1533-fix-a-precondition-violation-that-occurred-during-application-start-up/15360)
> Revision: 1533
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1532] Correct error where change of language disrupted node map structure s adjusted by user ;](https://discourse.openehr.org/t/ref-impl-eiffel-1532-correct-error-where-change-of-language-disrupted-node-map-structure-s-adjusted-by-user/15359)
> Revision: 1532
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1531] Add the ability for RM-specific sets of icons to be swapped in for visualising the archetype definition .](https://discourse.openehr.org/t/ref-impl-eiffel-1531-add-the-ability-for-rm-specific-sets-of-icons-to-be-swapped-in-for-visualising-the-archetype-definition/14108)
> Revision: 1531
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1530] Fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1530-fixes/14107)
> Revision: 1530
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1529] Modified project to allow running in standalone mode.](https://discourse.openehr.org/t/ref-impl-eiffel-1529-modified-project-to-allow-running-in-standalone-mode/14106)
> Revision: 1529
Author: seref\.arikan
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Personal message from the openEHR chairman, prof David Ingram](https://discourse.openehr.org/t/personal-message-from-the-openehr-chairman-prof-david-ingram/15075)
> from David Ingram, chair of the [openEHR Foundation board](http://www.openehr.org/about/bod.html),
[professor of health informatics](http://www.ucl.ac.uk/chime/people/ingramd/) at University College London,
[Centre for Health Informatics and Multi-professional Education](http://www.ucl.ac.uk/chime/).
**A Personal Message to the openEHR Community**
I wrote here some time ago of my forthcoming retirement and our wish and intention, as a Board, to pass the mantle of openEHR to the best...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Multiple archetypes in a single concept as a way to create an archetype collaborative](https://discourse.openehr.org/t/multiple-archetypes-in-a-single-concept-as-a-way-to-create-an-archetype-collaborative/15080)
> Hi,
Apologies in advance if this is the incorrect email list for this topic, but I thought it was the most relevant.
I'm a member of OpenMRS and there we are discussion a way to have users share the concepts (a limited form of an archetype) created in their systems. This means that for a single concept you could have many concepts from different implementations. This could be because of language or because different words refer to the same concept. For example, Gender in the US might be Sex...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1528] Ensure output ADL version can be changed during program execution.](https://discourse.openehr.org/t/ref-impl-eiffel-1528-ensure-output-adl-version-can-be-changed-during-program-execution/14102)
> Revision: 1528
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1527] Convert more of GUI text to dADL lang-indept data files.](https://discourse.openehr.org/t/ref-impl-eiffel-1527-convert-more-of-gui-text-to-dadl-lang-indept-data-files/14101)
> Revision: 1527
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question about occurrences and cardinality values in the Blood Pressure archetype](https://discourse.openehr.org/t/question-about-occurrences-and-cardinality-values-in-the-blood-pressure-archetype/15081)
> Greetings,
Am I suffering from acute caffeine deficiency syndrome \(just made it
up\) or is there a problem with the occurrences of event and
interval\_events in the blood pressure archetype?
In the published blood pressure archetype in the CKM, HISTORY\[at0001\]
has events with cardinality \{1\.\.\*; unordered\}
However "EVENT\[at0006\] occurrences matches \{0\.\.\*\}" and
"INTERVAL\_EVENT\[at1042\] occurrences matches \{0\.\.1\}" under the history
allow zero instances of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Multiple values in C_DV_ORDINAL constraints](https://discourse.openehr.org/t/multiple-values-in-c-dv-ordinal-constraints/15083)
> I have come across an interesting example of where we might want to
model an ordinal constraint where the values associated with each term
are not unique\.
The example is the Waterlow Score
http://www.judy-waterlow.co.uk/downloads/Waterlow%20Score%20Card-front.pdf
If you look at the bottom\-right corner "Major surgery / Trauma" you
will se that two terms have identical values\.
Currently the openEHR Archetype Editor will not let me add duplicate
values with separate terms\. It...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EQL v0.6 to JAVACC fix download link (Rong Chen)](https://discourse.openehr.org/t/eql-v0-6-to-javacc-fix-download-link-rong-chen/14100)
> Hi dear Rong Chen
I am working hard to implement EQL\-OM and binding EQL query to EQL Object
model base on gibello ZSql open source project \(with some modification\)\.
I hope it will release at next week\!
Mahdi Asgari
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 60, Issue 7](https://discourse.openehr.org/t/openehr-technical-digest-vol-60-issue-7/14099)
> Thanks Heath Frankel
I try to implement EQL AOM and translate result to XPath query,
Please guide me to stay in correct way at next\.
Thanks in advance
Mahdi Asgari
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Ref_impl_java Digest, Vol 63, Issue 7](https://discourse.openehr.org/t/ref-impl-java-digest-vol-63-issue-7/14098)
> Did you check
http://www.openehr.org/svn/ref_impl_java/TAGS
or
http://www.openehr.org/svn/ref_impl_java/BRANCHES
Mahdi Asgari
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EQL v0.6 to JAVACC fix download link](https://discourse.openehr.org/t/eql-v0-6-to-javacc-fix-download-link/15078)
> Hi dear all
I convert EQL_v0.6.grm to javaCC, in addition I add Distinct, Cast ,limit, offset and aggregation like (sum, max, min, count and avg) functions to parser
Please download it from link bellow
Click [EQL.jj](https://docs.google.com/leaf?id=0BzYouy8_oFpZMGNhYzkyYjMtNmM1Ny00MWQ4LThhMWUtYTFjZmM5ZWUyZTc0&sort=name&layout=list&num=50)
or visit
https://docs.google.com/leaf?id=0BzYouy8_oFpZMGNhYzkyYjMtNmM1Ny00MWQ4LThhMWUtYTFjZmM5ZWUyZTc0&sort=name&layout=list&num=50
Mahdi Asgari
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EQL v0.6 to JAVACC](https://discourse.openehr.org/t/eql-v0-6-to-javacc/14097)
> Hi dear all
I convert EQL_v0.6.grm to javaCC, in addition I add Distinct, Cast ,limit, offset and aggregation like (sum, max, min, count and avg) functions to parser
Please download it from link bellow
[https://docs.google.com/leaf?id=0BzYouy8_oFpZMGNhYzkyYjMtNmM1Ny00MWQ4LThhMWUtYTFjZmM5ZWUyZTc0&hl=en_US](https://docs.google.com/leaf?id=0BzYouy8_oFpZMGNhYzkyYjMtNmM1Ny00MWQ4LThhMWUtYTFjZmM5ZWUyZTc0&hl=en_US)
Any idea !!?
Mahdi Asgari
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL VersionedObject Grammar](https://discourse.openehr.org/t/aql-versionedobject-grammar/14186)
> Hi dear All
I confuse to make a AQL query using versioned_object or Version,
Does anyone know some example of using versioned_object and version?
Thanks in advance
Mahdi Asgari
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1526] Make it so that if user changes XML rules file, changes are re-read.](https://discourse.openehr.org/t/ref-impl-eiffel-1526-make-it-so-that-if-user-changes-xml-rules-file-changes-are-re-read/14096)
> Revision: 1526
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Where to get the old jars of openEHR?](https://discourse.openehr.org/t/where-to-get-the-old-jars-of-openehr/16347)
> Sorry if this is not the right forum to ask this question. I am new to openEHR.
I was trying to test the ehr2ont sandbox. For that I downloaded the following jars of openEHR: [http://www.openehr.org/wiki/display/projects/Java+Project+Download](http://www.openehr.org/wiki/display/projects/Java+Project+Download)
But when I tried to compile the project it gave me some errors. I think that is because I was using the latest versions of openEHR jars, whereas, the ehr2ont maintainers are...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1525] Correct right-click behaviour to properly select nodes with context selection .](https://discourse.openehr.org/t/ref-impl-eiffel-1525-correct-right-click-behaviour-to-properly-select-nodes-with-context-selection/16346)
> Revision: 1525
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1524] AWB-170: Update the developer page to EiffelStudio 6.8.](https://discourse.openehr.org/t/ref-impl-eiffel-1524-awb-170-update-the-developer-page-to-eiffelstudio-6-8/16345)
> Revision: 1524
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1523] AWB-170: Upgrade the vendor fix for the GTK implementation of EV_TREE_IMP to EiffelStudio 6 .8.](https://discourse.openehr.org/t/ref-impl-eiffel-1523-awb-170-upgrade-the-vendor-fix-for-the-gtk-implementation-of-ev-tree-imp-to-eiffelstudio-6-8/14095)
> Revision: 1523
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[540] implemented stringExpression in archetype_slot parsing](https://discourse.openehr.org/t/540-implemented-stringexpression-in-archetype-slot-parsing/14094)
> Revision: 540
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[539] fixed speacial case with CString in ExpressionItem.toString() function](https://discourse.openehr.org/t/539-fixed-speacial-case-with-cstring-in-expressionitem-tostring-function/14092)
> Revision: 539
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[538] added toString function to ExpressionItem and its subclasses](https://discourse.openehr.org/t/538-added-tostring-function-to-expressionitem-and-its-subclasses/14091)
> Revision: 538
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[537] added a testcase for parsing archetype_slot with single include](https://discourse.openehr.org/t/537-added-a-testcase-for-parsing-archetype-slot-with-single-include/14087)
> Revision: 537
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 57, Issue 3](https://discourse.openehr.org/t/openehr-clinical-digest-vol-57-issue-3/14086)
> CCR is not further supported \(overdue\), it has been replaced by HL7 CCD
William
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CCR model](https://discourse.openehr.org/t/ccr-model/13278)
> Hi All, I need CCR model ASAP\. has anyone worked on this\. Possible to share?
Cheers,
\-koray
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1522] The class explorer now does something quite cool - from the context menu on any class node that has subtypes , choose a subtype, and it re-writes the tree from that point down.](https://discourse.openehr.org/t/ref-impl-eiffel-1522-the-class-explorer-now-does-something-quite-cool-from-the-context-menu-on-any-class-node-that-has-subtypes-choose-a-subtype-and-it-re-writes-the-tree-from-that-point-down/14085)
> Revision: 1522
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1521] Missed new files on previous check-in](https://discourse.openehr.org/t/ref-impl-eiffel-1521-missed-new-files-on-previous-check-in/14084)
> Revision: 1521
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1520] Working form of improved RM class tool, with property & object nodes , visualised depending on category (class, container type, generic type, generic parameter).](https://discourse.openehr.org/t/ref-impl-eiffel-1520-working-form-of-improved-rm-class-tool-with-property-object-nodes-visualised-depending-on-category-class-container-type-generic-type-generic-parameter/14083)
> Revision: 1520
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1519] Slightly improved class browser tool, with paths and collapsed tree.](https://discourse.openehr.org/t/ref-impl-eiffel-1519-slightly-improved-class-browser-tool-with-paths-and-collapsed-tree/14082)
> Revision: 1519
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1518] Minor refactoring to do with serialisation functions available from ADL15_ENGINE and also DADL_ENGINE .](https://discourse.openehr.org/t/ref-impl-eiffel-1518-minor-refactoring-to-do-with-serialisation-functions-available-from-adl15-engine-and-also-dadl-engine/14081)
> Revision: 1518
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ADL.jj parser problem](https://discourse.openehr.org/t/adl-jj-parser-problem/14078)
> Hi dear all
I found ADL parser does not set stringExpression of Assertion while parsing ArchetypeSlot
The codes bellow are my change to fix this problem!
I will happy if anybody have new idea idea!
File: adl.jj
Line: 1399
{
return new Assertion(tag, expression, stringExpression, variables);
}
Change to
{
ExpressionLeaf leftOperand = (ExpressionLeaf)((ExpressionBinaryOperator) expression).getLeftOperand();
ExpressionLeaf rightOperand = (ExpressionLeaf)((ExpressionBinaryOperator)...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1517] First part of serialiser refactoring ( system will not build temporarily)](https://discourse.openehr.org/t/ref-impl-eiffel-1517-first-part-of-serialiser-refactoring-system-will-not-build-temporarily/14080)
> Revision: 1517
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1516] Various renaming in preparation for rationalised serialisation options](https://discourse.openehr.org/t/ref-impl-eiffel-1516-various-renaming-in-preparation-for-rationalised-serialisation-options/14079)
> Revision: 1516
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1515] SMall cleanup to serialisastion routines in ARCH_CAT_ARCHETYPE](https://discourse.openehr.org/t/ref-impl-eiffel-1515-small-cleanup-to-serialisastion-routines-in-arch-cat-archetype/16344)
> Revision: 1515
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[openhealth] OpenGALEN and OpenEHR](https://discourse.openehr.org/t/openhealth-opengalen-and-openehr/14089)
> Many of you probably got this but ...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers Digest, Vol 50, Issue 2](https://discourse.openehr.org/t/openehr-implementers-digest-vol-50-issue-2/14088)
> Hello, Thomas,
We could use "unknown" value for all NodeIDs that are not stated explicitly,
however, this brings more issues:
1) How would we deal with C_Object.NodeID validation requirement "Each node_id must be
defined in the archetype ontology as a term code" (AOM1.5.pdf, page 41)?
2) How would we conform to "NodeID" naming semantics, especially when specializing such "unknown" nodes?
It would be incorrect to name specialized node "unknown.1.1", because it would not conform to pattern...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Structuring healthcare information](https://discourse.openehr.org/t/structuring-healthcare-information/14171)
> >
Hi,
[http://www.isdscotland.org/Products-and-Services/Structuring-Healthcare-Information/](http://www.isdscotland.org/Products-and-Services/Structuring-Healthcare-Information/) from Information Services Division, Scotland containing the [Compound Healthcare Headings Structure](http://www.isdscotland.org/Products-and-Services/Structuring-Healthcare-Information/Compound-Healthcare-Headings-Model/CHHModelHTML/index.html) (CHH) which is based on several...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is not intervalofinteger supposed to be in BaseTypes.xsd document (current baseline) ?](https://discourse.openehr.org/t/is-not-intervalofinteger-supposed-to-be-in-basetypes-xsd-document-current-baseline/15329)
> Greetings,
The type intervalofinteger is documented under BaseTypes schema
according to http://www.openehr.org/svn/specification/TRUNK/publishing/its/XML-schema/documentation/BaseTypes.xsd.html
However, the xsd does not contain any definitions for this type, nor
any other xsds under the same branch\. Am I missing something obvious?
It is the same with intervalofreal, intervalofdate etc\.\.\.
Kind regards
Seref
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1514] Separate error and console tools.](https://discourse.openehr.org/t/ref-impl-eiffel-1514-separate-error-and-console-tools/14077)
> Revision: 1514
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Problem lists](https://discourse.openehr.org/t/problem-lists/14075)
> There is some interesting material emerging from the US as they try to
gear up for electronic records\.
THE PROBLEMS WITH PROBLEM LISTS
http://journal.ahima.org/wp-content/uploads/JAHIMA-problemlists.pdf
Clinician attitudes toward and use of electronic problem lists: a
thematic analysis
http://www.biomedcentral.com/1472-6947/11/36
Although skewed to US health system, most of the points made are
universal\. Although openEHR supports the principle of maintained
Problem lists via Persistent...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 59, Issue 23](https://discourse.openehr.org/t/openehr-technical-digest-vol-59-issue-23/14074)
> Dear <pashutin@ivc\-1\.ru>
Sorry my mail client does not display Russian characters and I see all of
them as ??????
According to xml\-serializer project I think that we must implement an
independent project to serialize the AOM, to use JAXB we need some META\-DATA
information on how to serialize objects so we need to modify openehr\-aom
project, so to save compatibility to original source , i prefer to have an
independent project to JAXB, XSTream or any other solutions\!
Are you think...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Xml Deserializer](https://discourse.openehr.org/t/archetype-xml-deserializer/15315)
> Hi dear all
Is anybody implement Deserialization of archetype from xml to AOM?
If no, I want to start xml to aom serializer project!
Mahdi Asgari
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1513] In the SConstruct and the NSIS installer script, install default_ui_config.cfg into the application directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1513-in-the-sconstruct-and-the-nsis-installer-script-install-default-ui-config-cfg-into-the-application-directory/14073)
> Revision: 1513
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1512] Reasonable (but rough) layout capture, using internal docking_manager facility.](https://discourse.openehr.org/t/ref-impl-eiffel-1512-reasonable-but-rough-layout-capture-using-internal-docking-manager-facility/14072)
> Revision: 1512
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1511] Make catalogue tool docking code follow model of other tools.](https://discourse.openehr.org/t/ref-impl-eiffel-1511-make-catalogue-tool-docking-code-follow-model-of-other-tools/14071)
> Revision: 1511
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1510] Fix non-compilation](https://discourse.openehr.org/t/ref-impl-eiffel-1510-fix-non-compilation/14070)
> Revision: 1510
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1509] Fix bug where new archetype tool was trying to populate with no archtype selected , due to a class being selected instead.](https://discourse.openehr.org/t/ref-impl-eiffel-1509-fix-bug-where-new-archetype-tool-was-trying-to-populate-with-no-archtype-selected-due-to-a-class-being-selected-instead/14069)
> Revision: 1509
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1508] Archetype catalogue is now a docking widget and separate 'tool' class.](https://discourse.openehr.org/t/ref-impl-eiffel-1508-archetype-catalogue-is-now-a-docking-widget-and-separate-tool-class/14068)
> Revision: 1508
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1507] Refactor Archetype and template GUI view controls out of Eiffel Build.](https://discourse.openehr.org/t/ref-impl-eiffel-1507-refactor-archetype-and-template-gui-view-controls-out-of-eiffel-build/14067)
> Revision: 1507
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1506] Fix a bug where the class tool was referencing the currently selected class node , which was not set, when manually selected after an archetype tool was created and populated.](https://discourse.openehr.org/t/ref-impl-eiffel-1506-fix-a-bug-where-the-class-tool-was-referencing-the-currently-selected-class-node-which-was-not-set-when-manually-selected-after-an-archetype-tool-was-created-and-populated/15314)
> Revision: 1506
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1505] Further refactoring.](https://discourse.openehr.org/t/ref-impl-eiffel-1505-further-refactoring/14066)
> Revision: 1505
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1504] Major refactoring of visual interface.](https://discourse.openehr.org/t/ref-impl-eiffel-1504-major-refactoring-of-visual-interface/16343)
> Revision: 1504
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM progress and Archetype versioning on CKM](https://discourse.openehr.org/t/ckm-progress-and-archetype-versioning-on-ckm/15066)
> Hi Erik, Thomas,
I think we need to address three issues separately here. The first is the archetype identification in CKM; the second is use of the draft archetypes and the third, the apparent lack of progress of archetype publication in the openEHR CKM.
Archetype identification is ultimately a technical issue and one in which I normally don’t have an opinion. Clearly it is useful from an implementation point of view to have unique IDs for each archetype and be able to determine diffs etc....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADLs documentation?](https://discourse.openehr.org/t/adls-documentation/12909)
> Hello everyone,
I have been trying to found information about ADLs, but there is no
information on current \(1\.4\) ADL document\.
Searching the wiki for 'ADLs' doesn't work as returns all 'ADL' results\.
Do you know where the documentation about ADLs can be found?
Regards
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1503] Set of changes that create working tabbing...](https://discourse.openehr.org/t/ref-impl-eiffel-1503-set-of-changes-that-create-working-tabbing/14061)
> Revision: 1503
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1502] Current state of docking changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1502-current-state-of-docking-changes/14060)
> Revision: 1502
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1501] Initial steps with docking, to show the basic idea.](https://discourse.openehr.org/t/ref-impl-eiffel-1501-initial-steps-with-docking-to-show-the-basic-idea/14059)
> Revision: 1501
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Maybe an opportunity? For someone?](https://discourse.openehr.org/t/maybe-an-opportunity-for-someone/15305)
> opensuse\-medical
http://en.opensuse.org/Portal:Medical
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [AOM/Archetype Slot: How to get include and exclude information?](https://discourse.openehr.org/t/aom-archetype-slot-how-to-get-include-and-exclude-information/14065)
> Dear all,
after parsing an archetype \(openEHR\-EHR\-OBSERVATION\.sample\_blood\_pressure\.v1\.adl \- see below\) which contains archetype slots I tried to use its AOM\-representation to identify archetypes which are allowed for these slots\.
I used the following code to display information on archetype slots:
private void printInfo \(ArchetypeSlot archetypeSlot\_, int iLevel\_\)
\{
Iterator<Assertion> iterator\_;
Assertion...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Put open clinical data/databases on the web](https://discourse.openehr.org/t/put-open-clinical-data-databases-on-the-web/15073)
> Hi,
I've been following the "Dual Model EHR implementation" discussion and it just
occurred to me that all these approaches would make much more sense if they have
been accompanied by sample clinical data, databases open to the public\.
Scientifically speaking one has to test any method with data to judge
efficiency, etc\.\.\.
Something which is also very true in most cases is that in most EHR systems a
specific database modeling, implementation approach has been chosen due...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [I'm looking for opportunities to do my master studies](https://discourse.openehr.org/t/im-looking-for-opportunities-to-do-my-master-studies/14051)
> Hi everyone,
I've been around the openEHR community since 2006, when I met the medical informatics domain. I've been facinated with this field since then, and I've been learning all I could about it.
Now I've have my degree in computer ingeneering, and I want to continue my studies on medical informatics and the application of standards.
This email goes to the openEHR lists because I know there is a lot of academic participation, and I would be glad to know if there are any opportunity to...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1500] checkpoint upload of first step of re-engineering of GUI:](https://discourse.openehr.org/t/ref-impl-eiffel-1500-checkpoint-upload-of-first-step-of-re-engineering-of-gui/14058)
> Revision: 1500
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1499] Correct missed refactoring change in cADL scanner .l file;](https://discourse.openehr.org/t/ref-impl-eiffel-1499-correct-missed-refactoring-change-in-cadl-scanner-l-file/15303)
> Revision: 1499
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1498] Various file moves of GUI source code](https://discourse.openehr.org/t/ref-impl-eiffel-1498-various-file-moves-of-gui-source-code/15302)
> Revision: 1498
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1497] Various file moves of GUI source code](https://discourse.openehr.org/t/ref-impl-eiffel-1497-various-file-moves-of-gui-source-code/14057)
> Revision: 1497
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1496] Add another GUI source directory](https://discourse.openehr.org/t/ref-impl-eiffel-1496-add-another-gui-source-directory/14056)
> Revision: 1496
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1495] Slight re-arrangement of toolbar buttons - Edit and Parse are now on context menu for an archetype .](https://discourse.openehr.org/t/ref-impl-eiffel-1495-slight-re-arrangement-of-toolbar-buttons-edit-and-parse-are-now-on-context-menu-for-an-archetype/14055)
> Revision: 1495
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Regarding the use of the dual model approach and openEHR in clinical trial management software](https://discourse.openehr.org/t/regarding-the-use-of-the-dual-model-approach-and-openehr-in-clinical-trial-management-software/14158)
> Hello everyone
I was just wondering if there are any projects out there that have been
looking at employing the dual model approach to describe clinical trial
data or that are using openEHR at the back\-end \(?\)
I may be searching in the literature using the wrong \(and obvious\) terms
but nothing much is coming up so far\.
Looking forward to hearing from you
Athanasios Anastasiou
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Implementation of the use of medical devices](https://discourse.openehr.org/t/implementation-of-the-use-of-medical-devices/15070)
> Hi!
We are investigating how to implement the use of medical devices with archetypes/templates. E.g. a doctor says that a patient needs to have a drain tube from tomorrow and for a few days. A nurse inserts the drain tube as the doctor has ordered. After a while she needs to change it and when she does she also register how much fluid that has exited the body. She continues doing this in the period of the doctors order.
When we investigate the archetypes and documentation from openEHR.org,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1494] Correct a small bug to with with recent rewrite of node map visualisation.](https://discourse.openehr.org/t/ref-impl-eiffel-1494-correct-a-small-bug-to-with-with-recent-rewrite-of-node-map-visualisation/14054)
> Revision: 1494
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1493] Fix a small bug that has somehow passed unnoticed in the flattener merge code , but just now caused a crash of the tool on the demographic / person & patient archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-1493-fix-a-small-bug-that-has-somehow-passed-unnoticed-in-the-flattener-merge-code-but-just-now-caused-a-crash-of-the-tool-on-the-demographic-person-patient-archetypes/16342)
> Revision: 1493
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1492] Further renaming of 'archetype directory' concept to ' archetype catalogue'.](https://discourse.openehr.org/t/ref-impl-eiffel-1492-further-renaming-of-archetype-directory-concept-to-archetype-catalogue/16341)
> Revision: 1492
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR FAQ and related web pages => wiki](https://discourse.openehr.org/t/openehr-faq-and-related-web-pages-wiki/12826)
> I have moved some of the old FAQ content from the website to the wiki, under the [resources space](http://www.openehr.org/wiki/display/resources/Resources+Home) - where it belongs if it is to be maintained. I did some cleaning up, but have not radically tried to change the content. Most of it is from a time when not many people knew much at all, including openEHR designers, so it may just need rewriting. The experience level has radically changed today, and I would like to encourage the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1491] Rename various classes so that ARCH_REP_XX become ARCH_CAT_XX and ARCHETYPE_DIRECTORY becomes ARCHETYPE_CATALOGUE .](https://discourse.openehr.org/t/ref-impl-eiffel-1491-rename-various-classes-so-that-arch-rep-xx-become-arch-cat-xx-and-archetype-directory-becomes-archetype-catalogue/14052)
> Revision: 1491
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ushahidi- open source software for information collection, visualization and interactive mapping](https://discourse.openehr.org/t/ushahidi-open-source-software-for-information-collection-visualization-and-interactive-mapping/15301)
> FYI,
Some of you will have come across this before I assume?
I'd heard of it before but not seen their site\.\.
http://www.ushahidi.com/
As we all continue to explore how communities can collaborate towards
shared goals, this example surely deserves a little "wow"\.
Thoughts on lessons for openEHR welcome\.\.\.
Tony
Dr\. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics, Leeds Teaching Hospitals
Chair, Clinical Review...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Ushahidi- open source software for information collection, visualization and interactive mapping](https://discourse.openehr.org/t/ushahidi-open-source-software-for-information-collection-visualization-and-interactive-mapping/15300)
> FYI,
Some of you will have come across this before I assume?
I'd heard of it before but not seen their site\.\.
http://www.ushahidi.com/
As we all continue to explore how communities can collaborate towards
shared goals, this example surely deserves a little "wow"\.
Thoughts on lessons for openEHR welcome\.\.\.
Tony
Dr\. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics, Leeds Teaching Hospitals
Chair, Clinical Review...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1490] Correct missed creation instruction in GUI node map builder.](https://discourse.openehr.org/t/ref-impl-eiffel-1490-correct-missed-creation-instruction-in-gui-node-map-builder/14047)
> Revision: 1490
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1489] Refactor validation further and add phase 3 validation, which operates on the flattened archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-1489-refactor-validation-further-and-add-phase-3-validation-which-operates-on-the-flattened-archetype/14046)
> Revision: 1489
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1488] Catch up on various file renamings due to earlier class name changes .](https://discourse.openehr.org/t/ref-impl-eiffel-1488-catch-up-on-various-file-renamings-due-to-earlier-class-name-changes/14045)
> Revision: 1488
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1487] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1487-changes/14044)
> Revision: 1487
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1486] Some stylistic cleaning up.](https://discourse.openehr.org/t/ref-impl-eiffel-1486-some-stylistic-cleaning-up/14043)
> Revision: 1486
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1485] Rewrite the horrible code in GUI_NODE_MAP_CONTROL using a regular C_VISITOR .](https://discourse.openehr.org/t/ref-impl-eiffel-1485-rewrite-the-horrible-code-in-gui-node-map-control-using-a-regular-c-visitor/14042)
> Revision: 1485
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Dual Model EHR implementation](https://discourse.openehr.org/t/dual-model-ehr-implementation/15071)
> Dear all,
Within the Virgen del Rocio University Hospital we are analysing how to implement a EHR based on Dual Model Approach. When we analysed direct implementation a database based on of either OpenEHR Reference Model or ISO 13606, we have detected that it could have slow performance . Given that we are concerned about this problem, we would like to know possible strategies have been identified by implementers in order to fasten the performance of storage and query.
Also the granularity...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1484] SMall adjustment to XML generation - only output DT node_ids if not numeric (either way could make sense, we will see after more practical experimentation).](https://discourse.openehr.org/t/ref-impl-eiffel-1484-small-adjustment-to-xml-generation-only-output-dt-node-ids-if-not-numeric-either-way-could-make-sense-we-will-see-after-more-practical-experimentation/14041)
> Revision: 1484
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Anonymous viewing of openEHR Jira server turned on](https://discourse.openehr.org/t/anonymous-viewing-of-openehr-jira-server-turned-on/12954)
> For those who want to see the openEHR issue trackers without having to
log in, you now can\. This means that when a URL like
http://www.openehr.org/issues/browse/SPECPR-10 is mentioned here, anyone
can see it in one click\. If you go to the home link
http://www.openehr.org/issues/secure/Dashboard.jspa you should be able
to see all the openEHR projects, which are divided into two groups:
'development trackers' and 'public issue trackers'\. The latter is where
to look for what...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [HISTORY, ITEM_TREE and other LOCATABLE at-codes](https://discourse.openehr.org/t/history-item-tree-and-other-locatable-at-codes/12725)
> Hello,
I've been looking through a very useful set of ADL 1.5 test archetypes related to Specialization feature of OpenEHR via "Knowledge2" repository ( [http://www.openehr.org/wsvn/knowledge2/TRUNK/archetypes/ADL_1.5_test/validity/specialisation](http://www.openehr.org/wsvn/knowledge2/TRUNK/archetypes/ADL_1.5_test/validity/specialisation) ).
I think some of archetype nodes lack "at"-codes.
For example OBSERVATION archetype "openEHR-EHR-OBSERVATION.spec_test_obs.v1" uses such types as...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[536] Fix and expand Archetype Validation of VACMC errors](https://discourse.openehr.org/t/536-fix-and-expand-archetype-validation-of-vacmc-errors/15281)
> Revision: 536
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1483] In the SConstruct and the NSIS installer script, install sample_xml_rules.cfg into the application directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1483-in-the-sconstruct-and-the-nsis-installer-script-install-sample-xml-rules-cfg-into-the-application-directory/16340)
> Revision: 1483
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1482] Add some further XML attributes into tags in DT_XML_SERIALISER.](https://discourse.openehr.org/t/ref-impl-eiffel-1482-add-some-further-xml-attributes-into-tags-in-dt-xml-serialiser/14040)
> Revision: 1482
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1481] Minor fix to correctly update XML tab status when flat/ differential view changed.](https://discourse.openehr.org/t/ref-impl-eiffel-1481-minor-fix-to-correctly-update-xml-tab-status-when-flat-differential-view-changed/14039)
> Revision: 1481
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Participation is not locatable](https://discourse.openehr.org/t/participation-is-not-locatable/12702)
> Hi,
Participation is not locatable. Is it going to be changed into locatable in future?
There is no possibility to get participation by atcode in data and determine which constraint describes it.
For example:
other_participations cardinality matches {1..2; unordered} matches {
PARTICIPATION occurrences matches {0..1} matches {
function matches {
DV_CODED_TEXT matches {
defining_code matches {[local::at0002]} -- Doctor
}
}
}
PARTICIPATION occurrences matches {1..1} matches {
function...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1480] Upload some fixes to make builds of the other apps work properly.](https://discourse.openehr.org/t/ref-impl-eiffel-1480-upload-some-fixes-to-make-builds-of-the-other-apps-work-properly/14038)
> Revision: 1480
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1479] This set of changes introduces a basic rule-based framework for driving XML serialisation from a Data Tree (DT).](https://discourse.openehr.org/t/ref-impl-eiffel-1479-this-set-of-changes-introduces-a-basic-rule-based-framework-for-driving-xml-serialisation-from-a-data-tree-dt/14037)
> Revision: 1479
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from isabel@trajano.us.es requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-isabel-trajano-us-es-requires-approval/14036)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@openehr\.org
Reason: Message body is too big: 118325 bytes with a limit of 40 KB
At your convenience, visit:
http://lists.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
to approve or deny the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1478] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1478-changes/15270)
> Revision: 1478
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1477] Fix dumb error created by typing too fast in wrong class box :(](https://discourse.openehr.org/t/ref-impl-eiffel-1477-fix-dumb-error-created-by-typing-too-fast-in-wrong-class-box/14032)
> Revision: 1477
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1476] An initial very rough cut of XML-ised P_XX classes via DT structure.](https://discourse.openehr.org/t/ref-impl-eiffel-1476-an-initial-very-rough-cut-of-xml-ised-p-xx-classes-via-dt-structure/14031)
> Revision: 1476
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Valid values](https://discourse.openehr.org/t/valid-values/12697)
> I have a doubt about valid values \(or ranges\) for clinical data\. Has
clinical sense to define a range with discontinuous domain?
I am thinking if something like 'critical range' with \[\-100, 0\] and
\[100, 200\] makes sense at all\. Or maybe something like 'any positive
or negative number but zero' \]\-inf,0\[ & \]0,\+inf\[
I am not talking about normal or reference ranges, but more on the
kind of ranges that are currently being archetyped
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1475] Update SVN mime-type properties (missing on many files)](https://discourse.openehr.org/t/ref-impl-eiffel-1475-update-svn-mime-type-properties-missing-on-many-files/14030)
> Revision: 1475
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1474] Minor bug-fixes following recent changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1474-minor-bug-fixes-following-recent-changes/15269)
> Revision: 1474
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1473] Commit the changes of rev 1472 on ADL2.0 branch, as well as a lot of minor changes that were detected in a manual diff of the ADL2 .0 and ADL1.5 branches.](https://discourse.openehr.org/t/ref-impl-eiffel-1473-commit-the-changes-of-rev-1472-on-adl2-0-branch-as-well-as-a-lot-of-minor-changes-that-were-detected-in-a-manual-diff-of-the-adl2-0-and-adl1-5-branches/15268)
> Revision: 1473
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1472] Changes](https://discourse.openehr.org/t/ref-impl-eiffel-1472-changes/16339)
> Revision: 1472
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1471] Manual merge of code from revs 1465, 1466, 1468-70 from ADL2. 0 branch to ADL1.5.](https://discourse.openehr.org/t/ref-impl-eiffel-1471-manual-merge-of-code-from-revs-1465-1466-1468-70-from-adl2-0-branch-to-adl1-5/16338)
> Revision: 1471
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1470] Remove ADL2_ENGINE.](https://discourse.openehr.org/t/ref-impl-eiffel-1470-remove-adl2-engine/16337)
> Revision: 1470
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1469] Perform some renames caught by from-scratch Eiffel compile.](https://discourse.openehr.org/t/ref-impl-eiffel-1469-perform-some-renames-caught-by-from-scratch-eiffel-compile/14029)
> Revision: 1469
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1468] Update compiler state machine diag](https://discourse.openehr.org/t/ref-impl-eiffel-1468-update-compiler-state-machine-diag/14028)
> Revision: 1468
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1467] Re-instate some old removals](https://discourse.openehr.org/t/ref-impl-eiffel-1467-re-instate-some-old-removals/14027)
> Revision: 1467
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1466] Correct various errors due to dADL round-trip work, and also some old bugs, undetected until now:](https://discourse.openehr.org/t/ref-impl-eiffel-1466-correct-various-errors-due-to-dadl-round-trip-work-and-also-some-old-bugs-undetected-until-now/14026)
> Revision: 1466
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1465] Working interim update of dADL (what was called 'ADL2') archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-1465-working-interim-update-of-dadl-what-was-called-adl2-archetypes/14025)
> Revision: 1465
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Archetypes Development](https://discourse.openehr.org/t/openehr-archetypes-development/15072)
> Hi All
Wondering if you could help.
I wanted to confirm whether one can request for archetype development for free if one does not currently exist.
Are there any costs associated with this?
Many thanks.
Eunice
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openehr usage](https://discourse.openehr.org/t/openehr-usage/12659)
> Dear All
I have just subscribed to this service. I wondered if you could help.
I am trying to introduce the usage of these archetypes to the people I work with within the NHS. I usually work with the clinical / technical community to develop information standards for clinical and la systems.
The problem has often been that there is confusion on developing standards and how to actually ensure these are standards .... with commissioning standards, there is usually a requirement to reference...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New Zealand's Interoperability Reference Architecture is out - open for public comment](https://discourse.openehr.org/t/new-zealands-interoperability-reference-architecture-is-out-open-for-public-comment/14034)
> Didn’t seem to appear on technical list – resending. Sorry for cross-post
Cheers,
-koray
[details="(attachments)"]
[ATT00001.txt|attachment](upload://6OueH0TJmOePK7isQZZkSESOj8L.txt) (172 Bytes)
[/details]
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New Zealand's Interoperability Reference Architecture is out - open for public comment](https://discourse.openehr.org/t/new-zealands-interoperability-reference-architecture-is-out-open-for-public-comment/14022)
> Hi Folks,
This is a chance to openly view NZ’s national (still draft though) reference architecture for interoperability. Underpinned by DCM – well practically archetypes (13606/openEHR), we suggest the use of numerous standards together in a pragmatic way. CDA, IHE and especially SOA is there.
So this is open for public comment until 3rd June and this is a chance where you can really make valuable contributions. Here’s the link to the blog post for details (and download the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [How to add reference to a person in the data structure](https://discourse.openehr.org/t/how-to-add-reference-to-a-person-in-the-data-structure/12645)
> Is there a possibility to add a reference to a person in the data structure, for example, in ITEM_LIST? For now i can only add DATA_VALUE in this list.
I viewed some archetypes in OpenEHR knowledge base and found some examples: there were added CLUSTER 'Refferring doctor' with three ELEMENTS: 'ID', 'Family name' and 'Last name'(openEHR-EHR-ADMIN_ENTRY.admission.v1). How should it look in the UI?
I want to allow user to select person from list or from auto completion box but not to alllow to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Who is using openEHR pages: UPDATES REQUESTED](https://discourse.openehr.org/t/who-is-using-openehr-pages-updates-requested/14015)
> As the number of organisations using openEHR grows, it would be useful to keep the 'Who is using it' pages up to date. Please review the following pages.
- [commercial orgs](http://www.openehr.org/shared-resources/usage/commercial.html)
- [government programmes](http://www.openehr.org/shared-resources/usage/government.html)
- [academic organisations](http://www.openehr.org/shared-resources/usage/academic.html)
- [non-profit...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1464] Make the resources config file that is set up by APPLICATION_TEMPLATE a shared object , so that objects other than the main application object can access it.](https://discourse.openehr.org/t/ref-impl-eiffel-1464-make-the-resources-config-file-that-is-set-up-by-application-template-a-shared-object-so-that-objects-other-than-the-main-application-object-can-access-it/14020)
> Revision: 1464
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1463] Missed new class from last commit](https://discourse.openehr.org/t/ref-impl-eiffel-1463-missed-new-class-from-last-commit/14019)
> Revision: 1463
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1462] Missed new class from last commit](https://discourse.openehr.org/t/ref-impl-eiffel-1462-missed-new-class-from-last-commit/15241)
> Revision: 1462
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1461] Refactoring to clarify 'generic' and 'mutliple' flag meanings in OG_ATTRIBUTE_NODE and DT_ATTRIBUTE.](https://discourse.openehr.org/t/ref-impl-eiffel-1461-refactoring-to-clarify-generic-and-mutliple-flag-meanings-in-og-attribute-node-and-dt-attribute/14018)
> Revision: 1461
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1460] Refactoring to clarify 'generic' and 'mutliple' flag meanings in OG_ATTRIBUTE_NODE and DT_ATTRIBUTE.](https://discourse.openehr.org/t/ref-impl-eiffel-1460-refactoring-to-clarify-generic-and-mutliple-flag-meanings-in-og-attribute-node-and-dt-attribute/16336)
> Revision: 1460
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 49, Issue 12 (RE:ArchetypeNodeId of an archetypeslot)](https://discourse.openehr.org/t/openehr-technical-digest-vol-49-issue-12-re-archetypenodeid-of-an-archetypeslot/13008)
> Dear Thomas
If I assume your response?
> just to clarify a bit:
> * occurrences etc are defined in the archetype, on slot nodes, as
> for any other object node in an archetype
> * when a slot is being filled (in a template), the id used for the
> archetype_node_id at the root node of the filler archetype in the
> resulting structure is the archetype_id of that archetype.
> * this means you never see at0000 in the resulting structure (called
> an operational template), and therefore,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1459] Perform rename of DADL2_VALIDATOR to DADL_VALIDATOR - now synchronised with ADL 2 .0 and ETHZ code.](https://discourse.openehr.org/t/ref-impl-eiffel-1459-perform-rename-of-dadl2-validator-to-dadl-validator-now-synchronised-with-adl-2-0-and-ethz-code/16335)
> Revision: 1459
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1458] Synchronised (most) changes from dADL in ABEL project at ETHZ with ADL 1.5 and ADL 2. 0 dADL implementations.](https://discourse.openehr.org/t/ref-impl-eiffel-1458-synchronised-most-changes-from-dadl-in-abel-project-at-ethz-with-adl-1-5-and-adl-2-0-dadl-implementations/14017)
> Revision: 1458
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1457] Synchronised (most) changes from dADL in ABEL project at ETHZ with ADL 1.5 and ADL 2. 0 dADL implementations.](https://discourse.openehr.org/t/ref-impl-eiffel-1457-synchronised-most-changes-from-dadl-in-abel-project-at-ethz-with-adl-1-5-and-adl-2-0-dadl-implementations/14016)
> Revision: 1457
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1456] Following breaking changes in revisions 1311 and 1312, and earlier, various revisions fixed APPLICATION_TEMPLATE so that Ostore applications can compile again .](https://discourse.openehr.org/t/ref-impl-eiffel-1456-following-breaking-changes-in-revisions-1311-and-1312-and-earlier-various-revisions-fixed-application-template-so-that-ostore-applications-can-compile-again/14014)
> Revision: 1456
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1455] In the SCons Eiffel builder, handle EiffelStudio' s predefined $ECF_CONFIG_PATH environment variable with or without parentheses .](https://discourse.openehr.org/t/ref-impl-eiffel-1455-in-the-scons-eiffel-builder-handle-eiffelstudio-s-predefined-ecf-config-path-environment-variable-with-or-without-parentheses/16334)
> Revision: 1455
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [One model vs One framework in e-health .....](https://discourse.openehr.org/t/one-model-vs-one-framework-in-e-health/15067)
> Hi Thomas,
I will agree with you, yes there has to be a generic health information model but in my opinion it has to span over all three main layers of software architecture
1. Physical/persistence layer
2. Conceptual/Application/Object layer
3. User interface layer/Serialized representation (XML,etc....)
RIMBAA technology matrix describes in the best way the different paths one can follow to solve parts of the generic problem.
The big challenge in my opinion is that there has not been...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1454] Missed changes from ADL 2.0 branch:](https://discourse.openehr.org/t/ref-impl-eiffel-1454-missed-changes-from-adl-2-0-branch/16333)
> Revision: 1454
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1453] Following changes same as in ADL 1.5 branch:](https://discourse.openehr.org/t/ref-impl-eiffel-1453-following-changes-same-as-in-adl-1-5-branch/16332)
> Revision: 1453
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1452] Various bug fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1452-various-bug-fixes/16331)
> Revision: 1452
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [on the possibility of 'one information model' in e-health](https://discourse.openehr.org/t/on-the-possibility-of-one-information-model-in-e-health/15069)
> this is an often debated question, and after coming across (for the 100th time) just such a debate recently online, I thought it might be interesting to try to get to the bottom of the question in some way. The basic idea posted [here](http://wolandscat.net/2011/05/05/no-single-information-model/). It is of course not scientific work, but I would be interested in the views of others on this concept.
- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR & 13606 EHR Extract](https://discourse.openehr.org/t/openehr-13606-ehr-extract/15061)
> I have updated the page [http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract](http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract) on the openEHR EHR Extract to now include a reference to a new ADL 1.5 template example for a full Extract of a simple discharge summary (do an SVN update on your local copy of the [http://www.openehr.org/svn/knowledge2/](http://www.openehr.org/svn/knowledge2/) repository to get the new archetypes and templates).
This work illustrates a large,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Thanks for your replies](https://discourse.openehr.org/t/thanks-for-your-replies/15230)
> Hi all, Thank for your replies\! I graduated as a nurse in 2007 after
30 years in technology including 15 years in the NSW ambulance as a
rural\-remote ambo\. I'm working as a nurse in a medical ward\. Now is my
time to put health and technology together, YAY\!\. I'm just starting
out on the road to a PhD and am writing my proposal lit review\.
Consequently I am following three threads of enquiry in the review\.
Nurse outcome indicators, the nurse practice environment and
electronic...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1451] In the SCons Eiffel builder, fix a problem that it was assuming that an environment variable in the ECF would always have a left parenthesis .](https://discourse.openehr.org/t/ref-impl-eiffel-1451-in-the-scons-eiffel-builder-fix-a-problem-that-it-was-assuming-that-an-environment-variable-in-the-ecf-would-always-have-a-left-parenthesis/16330)
> Revision: 1451
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1450] Copy revision 1449' s fix for APPLICATION_TEMPLATE from the TRUNK to the two branches where most work is currently being done , in order to avoid the fix getting overwritten by some future merge.](https://discourse.openehr.org/t/ref-impl-eiffel-1450-copy-revision-1449-s-fix-for-application-template-from-the-trunk-to-the-two-branches-where-most-work-is-currently-being-done-in-order-to-avoid-the-fix-getting-overwritten-by-some-future-merge/15229)
> Revision: 1450
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1449] Revision 1429 fixed APPLICATION_TEMPLATE so that Ostore applications can compile again following breaking changes in revisions 1311 and 1312 .](https://discourse.openehr.org/t/ref-impl-eiffel-1449-revision-1429-fixed-application-template-so-that-ostore-applications-can-compile-again-following-breaking-changes-in-revisions-1311-and-1312/14009)
> Revision: 1449
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR outputs](https://discourse.openehr.org/t/openehr-outputs/15063)
> Hi all, I'm doing research regarding the affect of a change of system
from manual to openehr on nursing\. I'm trying to understand where
nurse indicators can be measured and which indicators to use\. Goks
thesis about the implementation of openEHR in the austin hospital has
been helpful\. The usual indicators are falls, pressure ulcers and
nosocomial events but the link from them to a change in system is
tenuous\. I think I would be better served looking at what nurse
outcome...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 49, Issue 12 (ArchetypeNodeId of an archetypeslot)](https://discourse.openehr.org/t/openehr-technical-digest-vol-49-issue-12-archetypenodeid-of-an-archetypeslot/14008)
> Thanks sam
The main issues is how to apply constraint on Slots? Such as occurrence?
So if I used archetype_id instead of archetype_node_id, then how can I found correct Slot if more than one slot is used, to apply occurrence constraint?
I think I must test if archetype_id matches by Slot/include regular expression? So how to solve conflicts if archetype_id matches with two slot/include regular expression?
Is this a new issue? On validation RMObject via archetype ?
Thanks in...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1448] Move the SCons Eiffel builder to the scripts subdirectory.](https://discourse.openehr.org/t/ref-impl-eiffel-1448-move-the-scons-eiffel-builder-to-the-scripts-subdirectory/16327)
> Revision: 1448
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1447] In the SCons Eiffel builder, handle EiffelStudio' s predefined $ECF_CONFIG_PATH environment variable, which refers to the location of the ECF.](https://discourse.openehr.org/t/ref-impl-eiffel-1447-in-the-scons-eiffel-builder-handle-eiffelstudio-s-predefined-ecf-config-path-environment-variable-which-refers-to-the-location-of-the-ecf/16326)
> Revision: 1447
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [clinical mailing list](https://discourse.openehr.org/t/clinical-mailing-list/16325)
> **Peter Linhardt** **•** **Competence Center eHeealth manager** **•** **Division Public**
Ness Slovakia a.s.
Galvaniho Business Centre, Galvaniho 15/C,
821 04 Bratislava,
Slovakia
Tel.: +421 2 6826 1000
Mobile: + 421 911 899 827
[peter.linhardt@ness.com](mailto:peter.linhardt@ness.com) |www.ness.com
Please consider the environment before printing this e-mail
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 49, Issue 12](https://discourse.openehr.org/t/openehr-technical-digest-vol-49-issue-12/15060)
> Hi dear Ian
According to openEHR\-technical Digest, Vol 49, Issue 12 you saied two bellow
statement are correct \(in scope of ADL 1\.4\):
1\- The archetype\-node\-id in a locatable constructed around an archetype
in an archetypeslot is the archetype\-node\-id it gets from its own archetype
\(which is called in the slot\)\.
2\- The archetype\-node\-id in a locatable constructed around the
archetype calling the archetypeslot is to be ignored\.
I have a validation problem:
If the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[Re: Archetype versioning on CKM]](https://discourse.openehr.org/t/re-archetype-versioning-on-ckm/15216)
> From Stefan...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Unable to express an unit of measurements in UCUM syntax](https://discourse.openehr.org/t/unable-to-express-an-unit-of-measurements-in-ucum-syntax/15059)
> In cardiology, left ventricular mass (LVM) is often indexed to better identify left ventricular hypertrophy.
Possible indexations are:
- LVM/BSA (body surface area)
- LVM/height
- LVM/height^2.7
The first and the latter are often used.
The units of measurement of the latter is usually g/m2.7 [gram/(meter^2.7)].
In DV_QUANTITY, "units" attribute should be expressed in UCUM unit syntax. UCUM doesn't allow not integer exponent (see...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype versioning on CKM](https://discourse.openehr.org/t/archetype-versioning-on-ckm/15010)
> Hello,
With the latest Demographic archetypes updates on the CKM I think we
have to be careful with archetype versioning\. The new archetypes seem
quite different of the ones that were uploaded some time ago\. They are
different on structure but the version of the archetype has not been
improved \(and the last archetype is just missing from the CKM\)\.
Shouldn't a change on the archetype structure create a new version
\(v2\) of the archetype?
I think changes like "significant...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reverse Relations](https://discourse.openehr.org/t/reverse-relations/14002)
> Hi,
Excuse for the bit complex text below, I don't know how to say it more simple
I have a small problem with the way ReverseRelationships are connected to Party in the Demographic RM.
Maybe my problem is because of my misunderstanding.
The problem is not only conceptual, but it also causes problems in coding (programming) the kernel.
The problem is that ReverseRelationships are a Set of LocatableRef. This means that the PartyRelationship has to be stored before it can be added to a party...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [UCUM units of measurement in Archetype Editor](https://discourse.openehr.org/t/ucum-units-of-measurement-in-archetype-editor/14007)
> Archetype Editor let's to specify the list of units of measurement for a DV_QUANTITY element (C_DV_QUANTITY constraint). Not all the UCUM units of measurement are selectable from Archetype Editor. For example [MET] (metabolic equivalent) is defined in UCUM specs ([http://aurora.regenstrief.org/~ucum/ucum.html#para-44](http://aurora.regenstrief.org/%7Eucum/ucum.html#para-44)) but I didn't find it in Archetype Editor.
Using Archetype Editor, how can I define a DV_QUANTITY as...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype rules](https://discourse.openehr.org/t/archetype-rules/15058)
> Archetype has collection of rules. I can add assertions to this collection. Is there a possibility to associate assertion with human readable text?
I only found function which serializes rule statement to adl string form.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR artefact namespace identifiers](https://discourse.openehr.org/t/openehr-artefact-namespace-identifiers/15054)
> Hi,
About a year ago Thomas published a draft of some detailed artefact identification proposals at [http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/knowledge_id_system.pdf](http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/knowledge_id_system.pdf)
to help with the rapidly approaching scenario of having to cope with similarly named artefacts being published by different authorities. We are starting to see this scenario emerging in real-world...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR @ MIE 2011 + SHI 2011 Oslo, Norway](https://discourse.openehr.org/t/openehr-mie-2011-shi-2011-oslo-norway/14006)
> Hi\!
I have created a wikipage\.\.\.
http://www.openehr.org/wiki/display/resources/MIE+2011+-+SHI+2011+-+Oslo%2C+Norway
\.\.\.where you can add openEHR related contributions that you know have
been accepted to the MIE 2011 conference\.
Please add more information if you have\. If you know about a
contribution, but don't know how to edit the wiki, then please respond
by mail instead\.
Shortened URL to the wikipage:
http://www.openehr.org/wiki/x/BwBLAQ
Best regards,
Erik...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Overview](https://discourse.openehr.org/t/overview/15057)
> Dear Friends,
I started OpenEHR and want to know the project.
Any good references, over-views and ... can help me.
I planned to know the concept, architecture and source subsequently.
Any help will be appreciated before.
Regards,
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [OxFEFF breaks tests in MacOS](https://discourse.openehr.org/t/oxfeff-breaks-tests-in-macos/15056)
> Hi,
some of the archetypes and templates of oet-parser project starts with 0xFEFF. All of them are listed below. This causes the tests of this project to fail. I have just removed that char from those files and everything worked fine. Am I missing something or those chars should be removed? A similar fresh working copy on windows does not causes errors like in the MacOS.
M src/test/resources/archetypes/openEHR-EHR-COMPOSITION.test.v1.adl
M...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Survey Invitation for study on knowledge transfer techniques in healthcare virtual IT project teams](https://discourse.openehr.org/t/survey-invitation-for-study-on-knowledge-transfer-techniques-in-healthcare-virtual-it-project-teams/16322)
> Hi,
I am a PhD student at DePaul University in Chicago in the College of Computing and Digital Media. As part of my dissertation, I am completing a study that proposes to identify and evaluate specific knowledge transfer techniques in healthcare virtual IT project teams to determine which forms are most often associated with successful projects. The use of virtual IT project teams in healthcare has increased over time and the use of such teams is expected to continue increasing. One of the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1446] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1446-changes/16323)
> Revision: 1446
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1445] Renamed class DADL2_VALIDATOR to DADL_VALIDATOR](https://discourse.openehr.org/t/ref-impl-eiffel-1445-renamed-class-dadl2-validator-to-dadl-validator/16321)
> Revision: 1445
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1444] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1444-changes/16320)
> Revision: 1444
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1443] Various changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1443-various-changes/16319)
> Revision: 1443
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1442] Manual merge of ADL2.0 changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1442-manual-merge-of-adl2-0-changes/15206)
> Revision: 1442
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Use Archetypes and ADL file in Java](https://discourse.openehr.org/t/use-archetypes-and-adl-file-in-java/15055)
> Hi everybody I'm Alessandro OpenEhr is I'm working on for my thesis\.For the
moment I'm using java in the ADLParser file for the openEHR EHRS\-\.
blood\_pressure\.\-OBSERVATION v1\.0 adl\. I wanted to know, via java objects,
how to handle this archetype in java and assign values, such as the systolic
pressure\. More generally, how can I access the OpenEhr archetypes in java?
I attach the file that I have produced so far\.
Thank you for your attention, good job\.
Alessandro...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SNOMED-CT approach to term rubrics for openEHR nodes?](https://discourse.openehr.org/t/snomed-ct-approach-to-term-rubrics-for-openehr-nodes/15204)
> Hi all,
Any thoughts on the possibility of using the SNOMED approach to term rubrics (i.e 403234567|Some SNOMED term|) to make the human identification of atNodes and archetypeIDs easier in documentation and AQL statements
i.e. node_identifier|rubric|?
The rubric aspect is purely for human identification and would be completely ignored by any processing. The text would be assumed to be from the native archetype language but could be in any...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GUI stuff in AOM/ADL? (Was: future ADL-versions)](https://discourse.openehr.org/t/gui-stuff-in-aom-adl-was-future-adl-versions/15052)
> Hi!
Yesterday I asked if anybody had any motivated objections to using the openEHR template formalism as a layer to catch some GUI-hints/rules. I bring it up again to get some response :-)
The point to have separate concerns in separate artifacts is often good. Regarding GUI-hints it seems reasonable to not have them at the clinical archetype level, and in some cases not at a first clinically focused template level either. But, as we have discussed earlier, through specialisation and/or...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Versioning of archetypes using the Archetype Editor](https://discourse.openehr.org/t/versioning-of-archetypes-using-the-archetype-editor/15053)
> Hi!
I’m trying to learn how to use the Archetype Editor software and there is one thing I just can’t understand – and I haven’t found any description of this in the documentation (yet):
How does versioning of archetypes work in the Archetype Editor?
An example: The archetype openEHR-EHR-OBSERVATION.body_weight.v1.adl is in versjon 1 according to the “v1” ending. If I open it in the Archetype Editor, change it and save it, it still has the ending v1; what should I have done to make it “v2”?...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [is_integral attribute for DV_PROPORTION](https://discourse.openehr.org/t/is-integral-attribute-for-dv-proportion/16318)
> Archetype editor uses the attribute is\_integral for DV\_PROPORTION, but there is not an equivalent RM attribute\.
Should it be considered as a contraint on precision RM attribute \(when is\_integral=true \-\-> precision=0\)?
Anf when is\_integral is false, this means precision should be>= 1? or whatever?
Why is not a precision attribute used?
Thank you\.
Regards
leo
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [post-coordinated code on DV_CODED_TEXT?](https://discourse.openehr.org/t/post-coordinated-code-on-dv-coded-text/16324)
> Hello,
So I was looking to the Text package in the data\_types specification
and I was wondering how is supposed a DV\_CODED\_TEXT to handle a
post\-coordinated term \(from for example SNOMED\)\. If I understand
correctly is something that relies in a supposed terminology service?
isn't doing that making the system dependent of a technology or how a
system understands some terminology queries? Can someone provide a XML
snippet for the example “foot has\-laterality left”?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [C_DATE_TIME and RM instances](https://discourse.openehr.org/t/c-date-time-and-rm-instances/16717)
> When we define a C_DATE_TIME element like this
ELEMENT[at0061] occurrences matches {0..1} matches { -- Date/Time element
value matches {
DV_DATE_TIME matches {*}
}
}
we said that element at0061 can contains a Date/time value, a date only or a time only (indeed Archetype Editor show the label "Allow all").
From the point of view of RM instances, this means we can have
2011-03-18T11:01:28
but also
I'm wondering how to set code\_string value for a DV\_ORDINAL\.
Having a DV\_ORDINAL a structure like this:
<items archetype\_node\_id="at0004\.1" xsi:type="ELEMENT">
<name>
<value>Element name</value>
</name>
<value xsi:type="DV\_ORDINAL">
<value>5</value>
<symbol>
<value>Description...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [fyi: article; Open Source, Open Standards, and Health Care Information Systems](https://discourse.openehr.org/t/fyi-article-open-source-open-standards-and-health-care-information-systems/14011)
> FYI\.\.\.timely article on the role of open standards and open source in healthcare available here\.\.
http://www.jmir.org/2011/1/e24/
"Open Source, Open Standards, and Health Care Information Systems"
Carl J Reynolds1, BSC\(Hons\) MB BS; Jeremy C Wyatt2, MB BS DM FRCP
1Centre for Health Informatics and Multiprofessional Education, UCL Medical School, London, United Kingdom
2Institute for Digital Health care, International Digital Laboratory, Warwick University, Coventry, United...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1441] Fix some comment blocks in various files.](https://discourse.openehr.org/t/ref-impl-eiffel-1441-fix-some-comment-blocks-in-various-files/14005)
> Revision: 1441
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [future ADL-versions](https://discourse.openehr.org/t/future-adl-versions/15046)
> Hi,
I am sorry, but I am to busy to read all the discussions on future
ADL\-versions\.
So, now I have a small question, which possible is already explained,
Is it possible to write conditional constraints in future ADL?
The question is about implementing care\-protocol into an archetype\.
For example, if blood\-pressure is > 200, force to use another entry, for
example also look at heartbeat
Is there any idea when this new specifications will be in final version?
Thanks
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [null value of Element](https://discourse.openehr.org/t/null-value-of-element/12925)
> Hi,
I have an archetype with following Element
ELEMENT\[at0033\] occurrences matches \{0\.\.1\} matches \{ \-\- Condition Status
value matches \{
DV\_TEXT matches \{\*\}
\}
\}
I noticed that it is not possible te create an Element\-instance with
data\-value null, because my own Object\-validator validates against this
archetype and complains that in this case, value is a required attribute\.
Now I...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Editor (whishes)](https://discourse.openehr.org/t/archetype-editor-whishes/15047)
> Just for considering,
It would be a nice thing if GENERIC\_ENTRY was an option in the
Archetype\-Editor
\(also demographics, but that is an old discussion\)
Thanks,
Bert Verhees
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[535] Minor change to XMLSerializer.java: Added required namespace declaration: xmlns:xsd="http://www.w3.org/2001/ XMLSchema"](https://discourse.openehr.org/t/535-minor-change-to-xmlserializer-java-added-required-namespace-declaration-xmlns-xsd-http-www-w3-org-2001-xmlschema/14004)
> Revision: 535
Author: sebastian\.garde
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [First release of open source openEHR for .Net](https://discourse.openehr.org/t/first-release-of-open-source-openehr-for-net/14003)
> The first release of **openEHR.NET** is available at [http://openehr.codeplex.com/](http://openehr.codeplex.com/). openEHR.NET is a C# implementation of the [openEHR](http://www.openehr.org) Reference Model (RM) and Archetype Model (AM) specifications (Release 1.0.1), allowing developers to build openEHR applications by composing RM objects, validate against AM objects and serialise to/from XML. The aim of this release is to help all .Net development share the same core classes, and of course...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XMI exchange of class models](https://discourse.openehr.org/t/xmi-exchange-of-class-models/15191)
> Hi all!
I am on a trip in Brazil to learn more about openEHR/13606/MLHIM-related projects, actors and companies. At [LNCC](http://www.lncc.br/) we discussed among other things [EMF](http://www.eclipse.org/modeling/emf/) versions of openEHR models and then I realized there was an off-list discussion that some of us had and intended to move to the tech-list but obviously forgot to. Below you find a slightly shortened version of the discussion.
Feel free to join in.
If I understood things...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [fyi: US Veterans Administration Open Source RFI](https://discourse.openehr.org/t/fyi-us-veterans-administration-open-source-rfi/12418)
> FYI,
You may be interested to know that the US Veterans Administration has
just recently released this RFI on migrating their VISTA technology
towards "an openly architected, modular and standards based platform"
via an open source model\.
community\. Thoughts please\.\.
http://www.openehr.org/wiki/download/attachments/6553716/RFI-OpenSourceOrganizationForVistA-VA118-11-RI-0194-000.pdf
\(I have cut and pasted some key elements from the document\)
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1440] Fix some wrong source code indentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1440-fix-some-wrong-source-code-indentation/14001)
> Revision: 1440
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1439] Fix an Eiffel compiler warning about a call to an obsolete feature.](https://discourse.openehr.org/t/ref-impl-eiffel-1439-fix-an-eiffel-compiler-warning-about-a-call-to-an-obsolete-feature/13998)
> Revision: 1439
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1438] Work on aom_visitor. e to develop a proper stack based mechanism for building an object hierarchy bottom to top](https://discourse.openehr.org/t/ref-impl-eiffel-1438-work-on-aom-visitor-e-to-develop-a-proper-stack-based-mechanism-for-building-an-object-hierarchy-bottom-to-top/13997)
> Revision: 1438
Author: seref\.arikan
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Back-end for repository implementation](https://discourse.openehr.org/t/back-end-for-repository-implementation/15045)
> Hello everyone,
Does anybody knows a study for choosing between the different choices
for the back\-end, namely file system based \(adl or xml set of files\),
XML database, database for objects or even the relational databases?
Thanks for your time, best regards,
Tiago Pedrosa
Departamento de Informática e Comunicações / Department of Computing
and Communications
Instituto Politécnico de Bragança / Polytechnic Institute of Bragança
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Sample OpenEHR records](https://discourse.openehr.org/t/sample-openehr-records/15042)
> Hi everyone,
I'm looking for sampling OpenEHR records data\. I will like to feed my
repository with some sample data to make some test and try new
services, does anyone knows where can I get that ?
Thank you for your time, best regards,
Tiago Pedrosa
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Change Request on Composition.territory attribute](https://discourse.openehr.org/t/change-request-on-composition-territory-attribute/13988)
> Hi,
We have a case where we need to specify some country subdivision localization for a clinical document (Composition), but the Composition.territory attribute only have a country level.
The Composition.territory is contraint by the ISO 3166-1 vocabulary. Can we (maybe) have a Composition.territory constrained by the ISO 3166-2 for a country/subdivision specification? (http://en.wikipedia.org/wiki/ISO_3166-2).
Maybe this can be a CR for ADL 1.5.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1437] Although the last revision worked, further testing shows that it was doing more work than necessary in ARCHETYPE_ONTOLOGY .finalise_dt.](https://discourse.openehr.org/t/ref-impl-eiffel-1437-although-the-last-revision-worked-further-testing-shows-that-it-was-doing-more-work-than-necessary-in-archetype-ontology-finalise-dt/13996)
> Revision: 1437
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1436] Fix a precondition violation in ARCHETYPE_ONTOLOGY. remove_term_binding, which was failing when called from remove_term_definition.](https://discourse.openehr.org/t/ref-impl-eiffel-1436-fix-a-precondition-violation-in-archetype-ontology-remove-term-binding-which-was-failing-when-called-from-remove-term-definition/16317)
> Revision: 1436
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1435] Fix a precondition violation in DT_ATTRIBUTE_NODE. set_container_object_data_from_dt, which was failing because the node was not multiple.](https://discourse.openehr.org/t/ref-impl-eiffel-1435-fix-a-precondition-violation-in-dt-attribute-node-set-container-object-data-from-dt-which-was-failing-because-the-node-was-not-multiple/16316)
> Revision: 1435
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1434] Correct a postcondition in DT_ATTRIBUTE_NODE.set_generic.](https://discourse.openehr.org/t/ref-impl-eiffel-1434-correct-a-postcondition-in-dt-attribute-node-set-generic/15182)
> Revision: 1434
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1433] Remove a wrong postcondition in CADL_ENGINE.parse.](https://discourse.openehr.org/t/ref-impl-eiffel-1433-remove-a-wrong-postcondition-in-cadl-engine-parse/15179)
> Revision: 1433
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1432] Put up changes taken from last ADL 1.5 branch modification.](https://discourse.openehr.org/t/ref-impl-eiffel-1432-put-up-changes-taken-from-last-adl-1-5-branch-modification/15178)
> Revision: 1432
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1431] Upload slightly revised AWB help pages with Archetype Editor links & explanation .](https://discourse.openehr.org/t/ref-impl-eiffel-1431-upload-slightly-revised-awb-help-pages-with-archetype-editor-links-explanation/13995)
> Revision: 1431
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1430] Add links and explanation regarding how to use the Archetype Editor with the AWB .](https://discourse.openehr.org/t/ref-impl-eiffel-1430-add-links-and-explanation-regarding-how-to-use-the-archetype-editor-with-the-awb/13994)
> Revision: 1430
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [constraint binding error](https://discourse.openehr.org/t/constraint-binding-error/15051)
> Hello,
somebody knows which is the correct type of a constraint binding? In
all the examples I have checked and in the ADL grammar \(adl\.jj\), it is
specified by using an URL\.
for instance:
\[“ac0001”\] = <http://terminology.org?query_id=12345>
but I have seen in other archetypes something like this:
\["ac0001"\] = <\[CONSULTA::1\]>
The ADL parser throws an error with this last one\. is it right?
Thanks\!\!
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Are you aware of any archetypes for thyroid related data?](https://discourse.openehr.org/t/are-you-aware-of-any-archetypes-for-thyroid-related-data/15049)
> Dear all,
In the context of my PhD work at UCL, I'll be needing some archetypes
to model the clinical data which I'll be using\. If by any chance\. I
can get my hands on some existing archetypes which are likely to
contain the domain information that I'm working on, that'd help a lot\.
At the moment I'm working on some thyroid data, and in worst case I'll
be creating a dummy archetype which would probably be a nightmare from
an experience modeller's point of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Why the type function of the PARTY_RELATIONSHIP retrun an instance of DV_TEXT](https://discourse.openehr.org/t/why-the-type-function-of-the-party-relationship-retrun-an-instance-of-dv-text/15944)
> Dear all,
PARTY_RELATIONSHIP has a function named type, If type is the meaning of the relationships such as "employment", "authority", "health provision", why type return DV_TEXT instead of DV_CODED_TEXT?
By this type (DV_TEXT) we cannot use terminology coding system?
Is there any future think, that does not implemented or documented yet?
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1429] Adjust APPLICATION_TEMPLATE so that Ostore applications can compile again following breaking changes in revisions 1311 and 1312 .](https://discourse.openehr.org/t/ref-impl-eiffel-1429-adjust-application-template-so-that-ostore-applications-can-compile-again-following-breaking-changes-in-revisions-1311-and-1312/13993)
> Revision: 1429
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1428] Initial working changes to show how to generate a dadl ('ADL2') serialisation of an archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-1428-initial-working-changes-to-show-how-to-generate-a-dadl-adl2-serialisation-of-an-archetype/13992)
> Revision: 1428
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Survey on openEHR usage in health information systems](https://discourse.openehr.org/t/survey-on-openehr-usage-in-health-information-systems/13990)
> Dear all,
We’re currently studying the openEHR standard, in order to understand
the level of utilization of openEHR standard in the implementation of
healthcare information systems\. I would like to invite you to
participate in a short\-survey about this standard available at
http://www.fe.up.pt/~jfbc/openehr/
This survey is targeted to all professionals interested in healthcare
information systems, so we kindly ask if you can announce it to your
colleagues and related institutions\....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Survey on openEHR usage in health information systems](https://discourse.openehr.org/t/survey-on-openehr-usage-in-health-information-systems/15171)
> Dear all,
We’re currently studying the openEHR standard, in order to understand
the level of utilization of openEHR standard in the implementation of
healthcare information systems\. I would like to invite you to
participate in a short\-survey about this standard available at
http://www.fe.up.pt/~jfbc/openehr/
This survey is targeted to all professionals interested in healthcare
information systems, so we kindly ask if you can announce it to your
colleagues and related institutions\....
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [HL7 CTS data types](https://discourse.openehr.org/t/hl7-cts-data-types/15167)
> Hi,
I'm going to develop a java web service to provide some basic terminology services for openEHR such as: ConvertTermToCode
These methods accept inputs in specific data type such as: DV_CodedText
I don't know how can I leverage these data types in the source of my web service.
Would you please help me?
Kind regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR ADL/XML 1.5 Operational Template not far away](https://discourse.openehr.org/t/openehr-adl-xml-1-5-operational-template-not-far-away/15169)
> In the working build of the ADL 1.5 Workbench, we now have ADL Operational Templates working in a reasonable form. The example below is the test template found in the SVN knowledge2 repository [here](http://www.openehr.org/svn/knowledge2/TRUNK/archetypes/openEHR_examples/demographic_template/) (have a close look at the definition section - you can see archetype ids indicating where sub-part archetypes / templates have been included; also see the component_ontologies final section). Before...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR future directions](https://discourse.openehr.org/t/openehr-future-directions/15043)
> > Please see the announcement below for your attention\.
> Your views on the future direction of openEHR are especially important
> at this time\.
> Please feedback any/all views to this list to generate the discussion we
> need\.
Hi Tony\!
Thanks for inviting comments in an open way\. Organisational issues
have been touched upon earlier \(see previous discussions on the
technical list\)\. I believe some of us would like to know what will
happen to the feedback this time\. Some previous...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1427] Fix the adl_parser and dadl_test projects to compile following changes in revisions 1423 and 1424 .](https://discourse.openehr.org/t/ref-impl-eiffel-1427-fix-the-adl-parser-and-dadl-test-projects-to-compile-following-changes-in-revisions-1423-and-1424/13989)
> Revision: 1427
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Representing binary values with DV_BOOLEAN](https://discourse.openehr.org/t/representing-binary-values-with-dv-boolean/15041)
> Hi All, I’d like to get feedback on this issue before we move on with implementing.
In short whether we should use DV_BOOLEAN to represent the result of a Lab test as Positive/Negative. This particular test can have only two values (well plus the null case of course). I suspect this wasn’t the purpose of this data type in the first place and was for really no-brainer yes/no items as you would expect in any computer program. But, as ever, clinical medicine is wicked and makes me think out of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1426] Create new ADL2 branch.](https://discourse.openehr.org/t/ref-impl-eiffel-1426-create-new-adl2-branch/13983)
> Revision: 1426
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1425] Cosmetic fixes; add a new ADL2_ENGINE class.](https://discourse.openehr.org/t/ref-impl-eiffel-1425-cosmetic-fixes-add-a-new-adl2-engine-class/13982)
> Revision: 1425
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1424] Small amount of cleaning up, plus rename ADL_ENGINE to ADL15_ENGINE in preparation for creating an ADL2_engine that handles ADL2 style DT representation of the whole archetype and dADL syntax .](https://discourse.openehr.org/t/ref-impl-eiffel-1424-small-amount-of-cleaning-up-plus-rename-adl-engine-to-adl15-engine-in-preparation-for-creating-an-adl2-engine-that-handles-adl2-style-dt-representation-of-the-whole-archetype-and-dadl-syntax/13981)
> Revision: 1424
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1423] Changes as follows:](https://discourse.openehr.org/t/ref-impl-eiffel-1423-changes-as-follows/16315)
> Revision: 1423
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1422] Revision 1404 ensured that reselection of the same node in the archetype or template tree caused the widgets to be repopulated from that archetype or template .](https://discourse.openehr.org/t/ref-impl-eiffel-1422-revision-1404-ensured-that-reselection-of-the-same-node-in-the-archetype-or-template-tree-caused-the-widgets-to-be-repopulated-from-that-archetype-or-template/16314)
> Revision: 1422
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1421] Add the new BMM demo application to the SConstruct.](https://discourse.openehr.org/t/ref-impl-eiffel-1421-add-the-new-bmm-demo-application-to-the-sconstruct/13980)
> Revision: 1421
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1420] Add BMM demo application to show how to use BMM in its minimal form.](https://discourse.openehr.org/t/ref-impl-eiffel-1420-add-bmm-demo-application-to-show-how-to-use-bmm-in-its-minimal-form/13979)
> Revision: 1420
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1419] Minor additional RM schema refactoring](https://discourse.openehr.org/t/ref-impl-eiffel-1419-minor-additional-rm-schema-refactoring/13978)
> Revision: 1419
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1418] Further refactoring on REFERENCE_MODEL_ACCESS.](https://discourse.openehr.org/t/ref-impl-eiffel-1418-further-refactoring-on-reference-model-access/16313)
> Revision: 1418
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1417] Minor addition to BMM refactoring.](https://discourse.openehr.org/t/ref-impl-eiffel-1417-minor-addition-to-bmm-refactoring/15155)
> Revision: 1417
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1416] Refactor SCHEMA_ACCESS and BMM_SCHEMA so that BMM_SCHEMA carries all the schema routines .](https://discourse.openehr.org/t/ref-impl-eiffel-1416-refactor-schema-access-and-bmm-schema-so-that-bmm-schema-carries-all-the-schema-routines/13977)
> Revision: 1416
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1415] Correct an error in serialising clot fillers in flat archetypes (i.e .](https://discourse.openehr.org/t/ref-impl-eiffel-1415-correct-an-error-in-serialising-clot-fillers-in-flat-archetypes-i-e/13976)
> Revision: 1415
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Joint HL7 RIMBAA / OpenEHR implementers list](https://discourse.openehr.org/t/joint-hl7-rimbaa-openehr-implementers-list/15558)
> During the HL7 WGM the HL7 RIMBAA group \(software developers that use
the HL7 RIM for persistence and in memory processing\) met with OpenEHR
implementers \(mainly: representatives from Ocean Informatics\)\.
We found we have a lot in common when it comes to architectural and
implementation approaches\. See
http://wiki.hl7.org/index.php?title=RIMBAA_201103_Agenda for minutes of
that meeting \(browse down a bot until you reach the minutes of the
Thursday meeting\) ,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR template and oet template](https://discourse.openehr.org/t/openehr-template-and-oet-template/13970)
> Hi all;
I'd really appreciate your opinion about some issues about openEHR template concept in AOM 1.5. From current development specifications found here:
http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/aom1.5.pdf
http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/adl1.5.pdf
http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/tom.pdf
I see that Templates are defined in the form of specialised archetypes.
On...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1414] Update 1. 5 branch with missed final pre-release fixes to documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1414-update-1-5-branch-with-missed-final-pre-release-fixes-to-documentation/13975)
> Revision: 1414
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1413] Fix a precondition failure that occurred when trying to display the error dialog to inform the user that the archetype must be compiled before it can be saved .](https://discourse.openehr.org/t/ref-impl-eiffel-1413-fix-a-precondition-failure-that-occurred-when-trying-to-display-the-error-dialog-to-inform-the-user-that-the-archetype-must-be-compiled-before-it-can-be-saved/13974)
> Revision: 1413
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MULTIPLICITY_INTERVAL class documentation lost](https://discourse.openehr.org/t/multiplicity-interval-class-documentation-lost/15146)
> Hello,
There has been a change in AOM 1.5, where a class MULTIPLICITY_INTERVAL was introduced.
It is used as data type in various places (C_OBJECT, C_OBJECT_GROUP, etc.), but I am not able to find a piece of documentation on this class.
Can anyone help with MULTIPLICITY_INTERVAL documentation?
Regards,
Justinas Prelgauskas
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Imaging Exam Archetype](https://discourse.openehr.org/t/imaging-exam-archetype/15048)
> hi Ian \(and others\)
I spent some time today working on the imaging exam
archetype with Heather\. We had some questions about
the Finding Details section, and Heather thought that
you are responsible for this part\. And that part certainly
leaves me confused\.
There is a part called Detailed findings\. In it, there is
Finding name: Text
The name of the finding e\.g Chest, heart or bones for a Chest x\-ray\.
Finding: Text
Brief description, often coded, of an...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Use of Identifiers in archetypes](https://discourse.openehr.org/t/use-of-identifiers-in-archetypes/15044)
> hi Tom
I was working with Heather today on the imaging exam archetype\. Two
different considerations associated with identifiers came up during our
work\.
The first is that in the archetype design we came up with \(still be posed
on CKM yet\), there's a lot of identifiers present\. These identifiers are
required to deal with the interoperability aspects of the imaging exam
report \(i\.e\. PACS reigsters images with RIS, RIS provides report to
EHR, EHR tracks identifiers so it can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Thoughts after 7 Years of Being a Web-based Patient Registry Architect](https://discourse.openehr.org/t/thoughts-after-7-years-of-being-a-web-based-patient-registry-architect/16311)
> The blog entry by Ogbujis linked below may be of solace to some of us \-
it includes this conclusion\.\.
I also think much of the risk aversion associated with the atmosphere I
found myself \.\.\. in large institutions contributes to why the very
evident opportunities in leveraging rich web application \(“web 2\.0”\) and
semantic web infrastructure \(“web 3\.0”\) have not had as much penetration
in healthcare information technology as one would...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL 1.5 Workbench beta 3 released](https://discourse.openehr.org/t/adl-1-5-workbench-beta-3-released/16312)
> The latest beta of the ADL 1.5 Workbench for Windows, Mac and Linux can now be downloaded from [http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html)
It includes significant UI improvements, and an implementation of annotations as recently discussed on the lists. Release notes...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1412] Minor corrections to the online help.](https://discourse.openehr.org/t/ref-impl-eiffel-1412-minor-corrections-to-the-online-help/13969)
> Revision: 1412
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1411] Minor corrections to the online help.](https://discourse.openehr.org/t/ref-impl-eiffel-1411-minor-corrections-to-the-online-help/15144)
> Revision: 1411
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1410] Merge revision 1409 from BRANCHES/adl1.5 into the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1410-merge-revision-1409-from-branches-adl1-5-into-the-trunk/15143)
> Revision: 1410
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1409] Update the copyright date to 2011.](https://discourse.openehr.org/t/ref-impl-eiffel-1409-update-the-copyright-date-to-2011/13968)
> Revision: 1409
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1408] Add some links to the Release notes and home page.](https://discourse.openehr.org/t/ref-impl-eiffel-1408-add-some-links-to-the-release-notes-and-home-page/13967)
> Revision: 1408
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1407] Update duplicate error_db files.](https://discourse.openehr.org/t/ref-impl-eiffel-1407-update-duplicate-error-db-files/13966)
> Revision: 1407
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1406] Full merge of adl1.5 branch, with some subsequent updates to the documentation and images.](https://discourse.openehr.org/t/ref-impl-eiffel-1406-full-merge-of-adl1-5-branch-with-some-subsequent-updates-to-the-documentation-and-images/13965)
> Revision: 1406
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1405] Final updates to documentation for this beta.](https://discourse.openehr.org/t/ref-impl-eiffel-1405-final-updates-to-documentation-for-this-beta/13964)
> Revision: 1405
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1404] Correct bug where reselection of same node in archetype or template tree did nothing , even after actions in other controls.](https://discourse.openehr.org/t/ref-impl-eiffel-1404-correct-bug-where-reselection-of-same-node-in-archetype-or-template-tree-did-nothing-even-after-actions-in-other-controls/13963)
> Revision: 1404
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Should this list receive notifications for changes to ADL reference archetypes & schemas?](https://discourse.openehr.org/t/should-this-list-receive-notifications-for-changes-to-adl-reference-archetypes-schemas/15279)
> The SVN repository at [http://www.openehr.org/svn/knowledge2/](http://www.openehr.org/svn/knowledge2/) contains a library of ADL 1.5 reference test archetypes, 13606 test archetypes, openEHR RM tool schemas, a draft EN13606 tool schema. It is growing slowly to include all archetypes needed for testing and certifying any archetype tool. The test archetypes are also a good way for archetype authors to learn about ADL 1.5, using the ADL Workbench, so the repository has some educational value as...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1403] Correct problem where add new profile from REPOSITORY_DIALOG caused the new profile to be selected but not populated .](https://discourse.openehr.org/t/ref-impl-eiffel-1403-correct-problem-where-add-new-profile-from-repository-dialog-caused-the-new-profile-to-be-selected-but-not-populated/13962)
> Revision: 1403
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1401] Replace a call to ARRAY.make, which is obsolete, with make_filled.](https://discourse.openehr.org/t/ref-impl-eiffel-1401-replace-a-call-to-array-make-which-is-obsolete-with-make-filled/13960)
> Revision: 1401
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1400] Re-implement annotations classes to align with other parts of AUTHORED_RESOURCE and the way dADL is used to instantiate these object and serialise them .](https://discourse.openehr.org/t/ref-impl-eiffel-1400-re-implement-annotations-classes-to-align-with-other-parts-of-authored-resource-and-the-way-dadl-is-used-to-instantiate-these-object-and-serialise-them/13959)
> Revision: 1400
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1399] Various cosmetic and renames.](https://discourse.openehr.org/t/ref-impl-eiffel-1399-various-cosmetic-and-renames/13956)
> Revision: 1399
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1398] Create annotation nodes in grid expanded](https://discourse.openehr.org/t/ref-impl-eiffel-1398-create-annotation-nodes-in-grid-expanded/15131)
> Revision: 1398
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1397] When displaying line numbers on the ADL tab, append a tab character after each line number rather than padding out with spaces .](https://discourse.openehr.org/t/ref-impl-eiffel-1397-when-displaying-line-numbers-on-the-adl-tab-append-a-tab-character-after-each-line-number-rather-than-padding-out-with-spaces/13955)
> Revision: 1397
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1396] Updates for annotations control.](https://discourse.openehr.org/t/ref-impl-eiffel-1396-updates-for-annotations-control/13954)
> Revision: 1396
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1395] Initial basic implementation of annotations control ( test with EVALUATION. annotations archetype in ADL test archetypes in knowledge2 SVN).](https://discourse.openehr.org/t/ref-impl-eiffel-1395-initial-basic-implementation-of-annotations-control-test-with-evaluation-annotations-archetype-in-adl-test-archetypes-in-knowledge2-svn/13953)
> Revision: 1395
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1394] Revert changes to MAIN_WINDOW accidentally committed in revision 1392.](https://discourse.openehr.org/t/ref-impl-eiffel-1394-revert-changes-to-main-window-accidentally-committed-in-revision-1392/13952)
> Revision: 1394
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1393] Further deletion to ensure compilation.](https://discourse.openehr.org/t/ref-impl-eiffel-1393-further-deletion-to-ensure-compilation/13951)
> Revision: 1393
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1392] Remove some unused and ancient classes.](https://discourse.openehr.org/t/ref-impl-eiffel-1392-remove-some-unused-and-ancient-classes/13950)
> Revision: 1392
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [opereffa ArchetypeWrapper and unit types](https://discourse.openehr.org/t/opereffa-archetypewrapper-and-unit-types/15034)
> Hello,
As far as I understand, in opereffa, **unit** of an item is not retreived from the ADL file and should be set manually like :
pArchetypeWrapper.getElementAtNode(path).setUnitOfQuantity(....);
Am I missing something here, or is it the way it works?
I think since the unit and type of each item is already stored in the ADL file, while parsing the ADL file to the ArchetypeWrapper, these types of information should be set automatically in ElementWrappers in that ArchetypeWrapper.
Best...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype class](https://discourse.openehr.org/t/archetype-class/12363)
> Hello,
I was wondering whether there is a way to change one archetype class to another; for instance to 'save as' a CLUSTER archetype as an OBSERVATION (different class of archetype, the same items)
Best Regards
Pariya
MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of Technology
[http://www.ait.gu.se/kontaktaoss/personal/hajar-kashfi/](http://www.ait.gu.se/kontaktaoss/personal/hajar-kashfi/)
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1391] Add a unit test demonstrating that rebuilding a repository that had already been built violated a precondition that there must not be more compiled archetypes than the total number of archetypes in the repository .](https://discourse.openehr.org/t/ref-impl-eiffel-1391-add-a-unit-test-demonstrating-that-rebuilding-a-repository-that-had-already-been-built-violated-a-precondition-that-there-must-not-be-more-compiled-archetypes-than-the-total-number-of-archetypes-in-the-repository/13948)
> Revision: 1391
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1390] Fix display of UTF chars in archetype keywords and contributors lists.](https://discourse.openehr.org/t/ref-impl-eiffel-1390-fix-display-of-utf-chars-in-archetype-keywords-and-contributors-lists/13947)
> Revision: 1390
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1389] Remove am incorrect precondition that was preventing the user from clearing the work repository if it had already been set .](https://discourse.openehr.org/t/ref-impl-eiffel-1389-remove-am-incorrect-precondition-that-was-preventing-the-user-from-clearing-the-work-repository-if-it-had-already-been-set/15119)
> Revision: 1389
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1388] Add new thumbnails to cover all other screen shots.](https://discourse.openehr.org/t/ref-impl-eiffel-1388-add-new-thumbnails-to-cover-all-other-screen-shots/13945)
> Revision: 1388
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1387] Update all thumbnails ( done using Thumbs plus batch processor to generate resized . jpgs with altered filenames).](https://discourse.openehr.org/t/ref-impl-eiffel-1387-update-all-thumbnails-done-using-thumbs-plus-batch-processor-to-generate-resized-jpgs-with-altered-filenames/13944)
> Revision: 1387
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1386] New screenshot images for entire documentation, using new UI.](https://discourse.openehr.org/t/ref-impl-eiffel-1386-new-screenshot-images-for-entire-documentation-using-new-ui/13943)
> Revision: 1386
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1385] In the repository profile dialog, prevent the user from entering an empty profile name.](https://discourse.openehr.org/t/ref-impl-eiffel-1385-in-the-repository-profile-dialog-prevent-the-user-from-entering-an-empty-profile-name/13942)
> Revision: 1385
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1384] Correct source rich text tab size to something reasonable.](https://discourse.openehr.org/t/ref-impl-eiffel-1384-correct-source-rich-text-tab-size-to-something-reasonable/13941)
> Revision: 1384
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1383] Correct initial condition in ARCHETYPE_COMPILER.](https://discourse.openehr.org/t/ref-impl-eiffel-1383-correct-initial-condition-in-archetype-compiler/13940)
> Revision: 1383
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1382] Initial steps toward a proper state machine model for ARCHETYPE_COMPILER.](https://discourse.openehr.org/t/ref-impl-eiffel-1382-initial-steps-toward-a-proper-state-machine-model-for-archetype-compiler/13939)
> Revision: 1382
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1381] Various fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1381-various-fixes/15109)
> Revision: 1381
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1380] In the repository profile dialog, fix a bug that prevented the user from setting the working repository of an existing profile .](https://discourse.openehr.org/t/ref-impl-eiffel-1380-in-the-repository-profile-dialog-fix-a-bug-that-prevented-the-user-from-setting-the-working-repository-of-an-existing-profile/13938)
> Revision: 1380
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1379] In the repository profile dialog, prevent the user from renaming a profile to the name of another existing profile .](https://discourse.openehr.org/t/ref-impl-eiffel-1379-in-the-repository-profile-dialog-prevent-the-user-from-renaming-a-profile-to-the-name-of-another-existing-profile/13937)
> Revision: 1379
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1378] In the repository profile dialog, if the user edits the name of an existing profile, fix an invariant failure that the selected profile name was not matching the corresponding profile in the repository profiles configuration objec](https://discourse.openehr.org/t/ref-impl-eiffel-1378-in-the-repository-profile-dialog-if-the-user-edits-the-name-of-an-existing-profile-fix-an-invariant-failure-that-the-selected-profile-name-was-not-matching-the-corresponding-profile-in-the-repository-profiles-configuration-objec/15108)
> Revision: 1378
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1377] In the repository profile dialog, do nothing if the user clicks the Edit button when there are not yet any profiles .](https://discourse.openehr.org/t/ref-impl-eiffel-1377-in-the-repository-profile-dialog-do-nothing-if-the-user-clicks-the-edit-button-when-there-are-not-yet-any-profiles/13935)
> Revision: 1377
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1376] Fix a void target call that occurred on starting ADL Workbench if the config file contained the list of profiles but it was empty .](https://discourse.openehr.org/t/ref-impl-eiffel-1376-fix-a-void-target-call-that-occurred-on-starting-adl-workbench-if-the-config-file-contained-the-list-of-profiles-but-it-was-empty/13934)
> Revision: 1376
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1375] Fix a precondition violation that occurred in the RM Schema dialog if the user clicked the Browse button but then cancelled in the directory selection dialog .](https://discourse.openehr.org/t/ref-impl-eiffel-1375-fix-a-precondition-violation-that-occurred-in-the-rm-schema-dialog-if-the-user-clicked-the-browse-button-but-then-cancelled-in-the-directory-selection-dialog/13932)
> Revision: 1375
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1374] On opening the repository profile configuration dialog, synchronise the profile list box with the profile that is currently selected .](https://discourse.openehr.org/t/ref-impl-eiffel-1374-on-opening-the-repository-profile-configuration-dialog-synchronise-the-profile-list-box-with-the-profile-that-is-currently-selected/13930)
> Revision: 1374
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1373] Add a compile / pause button to user interface](https://discourse.openehr.org/t/ref-impl-eiffel-1373-add-a-compile-pause-button-to-user-interface/16310)
> Revision: 1373
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1372] Remove constant definition of AWB logo icon from the EBuild files, and define it in the normal way in SHARED_APP_UI_RESOURCES.](https://discourse.openehr.org/t/ref-impl-eiffel-1372-remove-constant-definition-of-awb-logo-icon-from-the-ebuild-files-and-define-it-in-the-normal-way-in-shared-app-ui-resources/15098)
> Revision: 1372
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1371] Fix the compilation which was broken by the last revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1371-fix-the-compilation-which-was-broken-by-the-last-revision/16309)
> Revision: 1371
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1370] More cosmetic adjustments.](https://discourse.openehr.org/t/ref-impl-eiffel-1370-more-cosmetic-adjustments/16308)
> Revision: 1370
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1369] Added a new log and improved (debatably) the splash screen and ' about' dialog appearance.](https://discourse.openehr.org/t/ref-impl-eiffel-1369-added-a-new-log-and-improved-debatably-the-splash-screen-and-about-dialog-appearance/13929)
> Revision: 1369
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1368] Cosmetic code changes; added annotations tab with grid ( no implementation yet).](https://discourse.openehr.org/t/ref-impl-eiffel-1368-cosmetic-code-changes-added-annotations-tab-with-grid-no-implementation-yet/13928)
> Revision: 1368
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1367] UI changes that re-arrange the description tab items into sub-tabs according to (hopefully) logical groups.](https://discourse.openehr.org/t/ref-impl-eiffel-1367-ui-changes-that-re-arrange-the-description-tab-items-into-sub-tabs-according-to-hopefully-logical-groups/13927)
> Revision: 1367
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1366] Correct shortcut for differential view from 't' to 'd' key.](https://discourse.openehr.org/t/ref-impl-eiffel-1366-correct-shortcut-for-differential-view-from-t-to-d-key/13926)
> Revision: 1366
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1365] Various improvements in user interface:](https://discourse.openehr.org/t/ref-impl-eiffel-1365-various-improvements-in-user-interface/13925)
> Revision: 1365
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1364] A few more UI correctness changes.](https://discourse.openehr.org/t/ref-impl-eiffel-1364-a-few-more-ui-correctness-changes/13924)
> Revision: 1364
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1363] Make the main UI populate routines slightly safer with better contracts.](https://discourse.openehr.org/t/ref-impl-eiffel-1363-make-the-main-ui-populate-routines-slightly-safer-with-better-contracts/13923)
> Revision: 1363
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1362] Add some decent flat & short icons;](https://discourse.openehr.org/t/ref-impl-eiffel-1362-add-some-decent-flat-short-icons/13922)
> Revision: 1362
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1361] Fix the compilation which was broken by the last revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1361-fix-the-compilation-which-was-broken-by-the-last-revision/13921)
> Revision: 1361
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1360] Initial re-arrangement of GUI to factor out flat/ diff button on to tool bar, along with global flag, which is saved in the . cfg file.](https://discourse.openehr.org/t/ref-impl-eiffel-1360-initial-re-arrangement-of-gui-to-factor-out-flat-diff-button-on-to-tool-bar-along-with-global-flag-which-is-saved-in-the-cfg-file/13920)
> Revision: 1360
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1359] Reinstate a few improvements to the repository profile configuration dialog that were originally committed in revision 1353 but zapped by revision 1355 :](https://discourse.openehr.org/t/ref-impl-eiffel-1359-reinstate-a-few-improvements-to-the-repository-profile-configuration-dialog-that-were-originally-committed-in-revision-1353-but-zapped-by-revision-1355/15085)
> Revision: 1359
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1358] Revert an annoying message about duplicate sub-schemas being found ( which is entirely normal) to 'info' level from 'warning' level;](https://discourse.openehr.org/t/ref-impl-eiffel-1358-revert-an-annoying-message-about-duplicate-sub-schemas-being-found-which-is-entirely-normal-to-info-level-from-warning-level/13915)
> Revision: 1358
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1357] Further corrections:](https://discourse.openehr.org/t/ref-impl-eiffel-1357-further-corrections/16307)
> Revision: 1357
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issue with class PARTICIPATION. Should it be Locatable or Pathable?](https://discourse.openehr.org/t/issue-with-class-participation-should-it-be-locatable-or-pathable/15848)
> Hello,
We are having some problems with Reference Model class PARTICIPATION.
We want to define an archetype of COMPOSITION type and state, that it could have two types of participants: Doctors and Patients; At least one Doctor and one Patient participant must be specified.
After we create an archetype (we use Ocean Archetype Editor v2.2) and constrain PARTICIPATION.function using "at0007" = Doctor & "at0008" = Person, we get following XML (I removed all unnecessary elements):
Revision: 1356
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1355] Correct various bugs to do with starting fresh, i.e.](https://discourse.openehr.org/t/ref-impl-eiffel-1355-correct-various-bugs-to-do-with-starting-fresh-i-e/13913)
> Revision: 1355
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML Extracts availability](https://discourse.openehr.org/t/xml-extracts-availability/15032)
> Hello,
does anybody know where could I find XML data extracts for OpenEHR or ISO 13606?
Thank you.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1354] Fix a typo.](https://discourse.openehr.org/t/ref-impl-eiffel-1354-fix-a-typo/13912)
> Revision: 1354
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1353] A few improvements to the repository profile configuration dialog and the profile edit dialog :](https://discourse.openehr.org/t/ref-impl-eiffel-1353-a-few-improvements-to-the-repository-profile-configuration-dialog-and-the-profile-edit-dialog/13911)
> Revision: 1353
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1352] Rewrite repository profile dialog as per http://www.openehr.org/ issues/browse/AWB-30 .](https://discourse.openehr.org/t/ref-impl-eiffel-1352-rewrite-repository-profile-dialog-as-per-http-www-openehr-org-issues-browse-awb-30/13910)
> Revision: 1352
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Brazil chooses openEHR for EHR at all levels of government](https://discourse.openehr.org/t/brazil-chooses-openehr-for-ehr-at-all-levels-of-government/13917)
> Brazil has chosen to use openEHR and archetypes for the shareable EHR at three levels of government - federal, state and municipal. The details:
On December 16 2010, at the 8th ordinary meeting of the Brazilian Tripartite Commission (CTI), a draft Ministerial Order establishing the standards for interoperability to be adopted by health information systems of the various levels of the Brazilian National Health System (SUS) was submitted for agreement. CTI is the Brazilian collegiate body...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1351] Fix the ARCHETYPE_DIRECTORY unit tests.](https://discourse.openehr.org/t/ref-impl-eiffel-1351-fix-the-archetype-directory-unit-tests/13909)
> Revision: 1351
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1350] Correct error in ISO8601_DURATION where the 'value' attribute was not correctly set in some circumstances (not 100% clear when ).](https://discourse.openehr.org/t/ref-impl-eiffel-1350-correct-error-in-iso8601-duration-where-the-value-attribute-was-not-correctly-set-in-some-circumstances-not-100-clear-when/15074)
> Revision: 1350
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1349] Fix the BMM unit tests.](https://discourse.openehr.org/t/ref-impl-eiffel-1349-fix-the-bmm-unit-tests/13902)
> Revision: 1349
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1348] Minor corrections:](https://discourse.openehr.org/t/ref-impl-eiffel-1348-minor-corrections/13901)
> Revision: 1348
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1347] Correct an error in error message for not-found RM schemas](https://discourse.openehr.org/t/ref-impl-eiffel-1347-correct-an-error-in-error-message-for-not-found-rm-schemas/13900)
> Revision: 1347
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1346] On opening the RM schema dialog, the text boxes were empty.](https://discourse.openehr.org/t/ref-impl-eiffel-1346-on-opening-the-rm-schema-dialog-the-text-boxes-were-empty/13899)
> Revision: 1346
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1345] When generating the SCons Eiffel builder:](https://discourse.openehr.org/t/ref-impl-eiffel-1345-when-generating-the-scons-eiffel-builder/15065)
> Revision: 1345
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1344] Fix the Linux tar archive for ADL Workbench, which did not install the rm_schemas directory correctly.](https://discourse.openehr.org/t/ref-impl-eiffel-1344-fix-the-linux-tar-archive-for-adl-workbench-which-did-not-install-the-rm-schemas-directory-correctly/13898)
> Revision: 1344
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype & Template ANNOTATIONS - requirements?](https://discourse.openehr.org/t/archetype-template-annotations-requirements/16716)
> All,
the next beta of the archetype workbench, which is progressively implementing all of ADL 1.5 will include 'annotations', which is a feature enabling a set of comments to be created on a per-node level in an archetype. The raw ADL appearance of this is typified by the following two test archetypes (go to the bottom):...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data retrieval in opereffa](https://discourse.openehr.org/t/data-retrieval-in-opereffa/15846)
> Hello there,
Is data retrieval implemented in opereffa? For instance, is it possible to pass a patient name(contextId) to the framework to get all archetype data available for that patient?
In the simple example provided by oepreffa, by passing **contextId** and **sessionId,** data is retrieved
```
ArrayList archetypeDatas = new ArrayList(testInstance.getArchetypeDataList(sessionId, contextId));
```
But the point is that this **sessionId** is not part of patient data.
A real scenario will...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1343] Correct missing annotations in flattening of top-level archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-1343-correct-missing-annotations-in-flattening-of-top-level-archetype/16306)
> Revision: 1343
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1342] Upgrade documentation; including release notes, preparatory to next release.](https://discourse.openehr.org/t/ref-impl-eiffel-1342-upgrade-documentation-including-release-notes-preparatory-to-next-release/16305)
> Revision: 1342
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1341] Fix some basic bugs; now flat view works again, and logic of validation of annotation paths is correct.](https://discourse.openehr.org/t/ref-impl-eiffel-1341-fix-some-basic-bugs-now-flat-view-works-again-and-logic-of-validation-of-annotation-paths-is-correct/13897)
> Revision: 1341
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [info: UK EHR conference May 2011](https://discourse.openehr.org/t/info-uk-ehr-conference-may-2011/13905)
> This conference may be of interest to UK / European members:
Electronic Health Records are a major focus of the Coalition's Liberating the NHS: An Information Revolution strategic review on information management across health and social care. With the consultation responses under consideration, **Capita’s Electronic Health Records Conference** is timed to examine the primary drivers emerging from this bold new decentralisation strategy . Electronic health records will be at the heart of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1340] First cut of working archetype Annotations:](https://discourse.openehr.org/t/ref-impl-eiffel-1340-first-cut-of-working-archetype-annotations/15064)
> Revision: 1340
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Announcement concerning progress with IHTSDO and future directions](https://discourse.openehr.org/t/announcement-concerning-progress-with-ihtsdo-and-future-directions/13906)
> Dear Colleagues,
Please see the announcement below for your attention\.
Your views on the future direction of openEHR are especially important
at this time\.
Please feedback any/all views to this list to generate the discussion we
need\.
Kind regards,
Tony
Dr\. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics, Leeds Teaching Hospitals
Chair, Clinical Review Board, openEHR Foundation
\+44\.789\.988 5068 ...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Announcement concerning progress with IHTSDO and future directions](https://discourse.openehr.org/t/announcement-concerning-progress-with-ihtsdo-and-future-directions/13904)
> At its October meeting in Toronto, the General Assembly of the IHTSDO received and discussed a proposal, submitted by its Management Board, to support, develop and maintain the IP in *open*EHR, within a broader framework of IHTSDO governance for clinical content of the electronic health record.
**IHTSDO Decision**
The *open*EHR Foundation Board has now heard from the IHTSDO Management Board, saying that, whilst the objective of the proposal was considered by the GA to be within the scope of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1339] Fix a void target call that occurred when quickly selecting various different items in the archetype and template trees .](https://discourse.openehr.org/t/ref-impl-eiffel-1339-fix-a-void-target-call-that-occurred-when-quickly-selecting-various-different-items-in-the-archetype-and-template-trees/13896)
> Revision: 1339
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1338] Fix many void target calls, and a couple of precondition violations, that occurred if the current archetype directory has not been set yet when selecting the RM schemas .](https://discourse.openehr.org/t/ref-impl-eiffel-1338-fix-many-void-target-calls-and-a-couple-of-precondition-violations-that-occurred-if-the-current-archetype-directory-has-not-been-set-yet-when-selecting-the-rm-schemas/13895)
> Revision: 1338
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR sessions at HL7 Jan 2011 WGM, Sydney](https://discourse.openehr.org/t/openehr-sessions-at-hl7-jan-2011-wgm-sydney/13889)
> For those going to Sydney in January...
two openEHR sessions are scheduled at the next HL7 WGM in Sydney, both on Friday 14 January, the last day of the meeting.
- The first session is 'openEHR - Introduction to openEHR, Archetypes & Templates', 9:00 - 12:30.
- The second is 'openEHR - Application of openEHR with HL7 & SNOMED'.
- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Archetype Editor new beta release](https://discourse.openehr.org/t/archetype-editor-new-beta-release/13888)
> A new beta release of the Archetype Editor is now available [here](http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor/Help/index.html). Bug fixes and enhancements are described in the [release notes](http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor/Help/release_notes.html). Issues can be reported on the Problem Report tracker [here](http://www.openehr.org/issues/browse/AEPR). Thanks to Peter Gummer at Ocean Informatics for ongoing software support...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [What is the status of occurrences handling in Java AOM code](https://discourse.openehr.org/t/what-is-the-status-of-occurrences-handling-in-java-aom-code/15842)
> Dear all,
I've seen that Rong has committed new code regarding adl 1.5. The code I'm using requires that occurrences is not null in AOM, and is therefore not in sync with the change explained here: [http://www.openehr.org/issues/browse/SPEC-303](http://www.openehr.org/issues/browse/SPEC-303)
Does the latest version of AOM code allow this? I have a quite complex development setup, so I'd appreciate your input before planning an update.
Best Regards
Seref
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1337] AWB-169: Remove the override class for FORMAT_DOUBLE, because EiffelStudio 6.7 incorporates all of the fixes to that class.](https://discourse.openehr.org/t/ref-impl-eiffel-1337-awb-169-remove-the-override-class-for-format-double-because-eiffelstudio-6-7-incorporates-all-of-the-fixes-to-that-class/16304)
> Revision: 1337
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_QUANTITY or DV_DURATION?](https://discourse.openehr.org/t/dv-quantity-or-dv-duration/15035)
> I'm wondering which is the correct use of DV\_DURATION and DV\_QUANTITY\.\.\.
When using DV\_QUANTITY with property attribute 'time' \(openehr::128\) and
when using DV\_DURATION?
Regards
leo
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New release of the Clinical Knowledge Manager (CKM)](https://discourse.openehr.org/t/new-release-of-the-clinical-knowledge-manager-ckm/15033)
> Dear all,
We have released a new version of the Clinical Knowledge Manager at [http://www.openehr.org/knowledge](http://www.openehr.org/knowledge)
Once an archetype is published, it will normally have to be translated into various languages without changing the definition of the archetype itself or the terms in existing language. In general it is better to use the online translation facility built into CKM but it will sometimes be the case that a translation is added locally to an archetype...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1336] AWB-169: Because EiffelStudio 6. 7 compiles test clusters defined in a project, these must now be treated as dependencies of an Eiffel project.](https://discourse.openehr.org/t/ref-impl-eiffel-1336-awb-169-because-eiffelstudio-6-7-compiles-test-clusters-defined-in-a-project-these-must-now-be-treated-as-dependencies-of-an-eiffel-project/16303)
> Revision: 1336
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1335] AWB-169: Complete the upgrade to EiffelStudio 6.7, which has just been released.](https://discourse.openehr.org/t/ref-impl-eiffel-1335-awb-169-complete-the-upgrade-to-eiffelstudio-6-7-which-has-just-been-released/13887)
> Revision: 1335
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1334] deleted IArchetypeVisitor.cpp and Logger.cpp](https://discourse.openehr.org/t/ref-impl-eiffel-1334-deleted-iarchetypevisitor-cpp-and-logger-cpp/13886)
> Revision: 1334
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1333] modified exported types from base libraries (INTEGER) but it led to an error during compilation, so cancelled the change.](https://discourse.openehr.org/t/ref-impl-eiffel-1333-modified-exported-types-from-base-libraries-integer-but-it-led-to-an-error-during-compilation-so-cancelled-the-change/13885)
> Revision: 1333
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1332] Added getIntegerAttributeFromObj to ExperimentalApplicationEiffelAccessHelper](https://discourse.openehr.org/t/ref-impl-eiffel-1332-added-getintegerattributefromobj-to-experimentalapplicationeiffelaccesshelper/13884)
> Revision: 1332
Author: seref\.arikan
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CUI discussions and CURIO project](https://discourse.openehr.org/t/cui-discussions-and-curio-project/13893)
> Over the past year, UCL CHIME has been running a small joint project with the NHS Data Standards and Products Group in the UK, to deliver open source implementations of some key components of the NHS Common User Interface (CUI) specifications. Named CURIO, this very practically focused project has allowed us to gain insight into generic and cutting edge UI requirements for delivery of capable clinical information systems.
The outputs from the CURIO project will be made publicly available,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Opereffa and Project Bosphorus](https://discourse.openehr.org/t/opereffa-and-project-bosphorus/13892)
> As *open*EHR moves forward with ADL 1.5, UCL CHIME has been working on tooling to deliver more capability to the *open*EHR users community, providing new and open source assets to leverage in systems development.
The *open*EHR Eiffel repository developed by Ocean Informatics has been providing a very mature, capable and tested open source code base for quite some time. In the context of the UCL Opereffa project, a major work item has been to provide support for the new features of ADL 1.5....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1330] Eclipse project for Java codebase](https://discourse.openehr.org/t/ref-impl-eiffel-1330-eclipse-project-for-java-codebase/15040)
> Revision: 1330
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1329] added null handling to getStringAttributeFromObj in ExperimentalApplicationEiffelAccessHelper .cpp](https://discourse.openehr.org/t/ref-impl-eiffel-1329-added-null-handling-to-getstringattributefromobj-in-experimentalapplicationeiffelaccesshelper-cpp/13880)
> Revision: 1329
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1328] C_PRIMITIVE set as visible in project settings, so that CECIL can use it](https://discourse.openehr.org/t/ref-impl-eiffel-1328-c-primitive-set-as-visible-in-project-settings-so-that-cecil-can-use-it/13879)
> Revision: 1328
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1327] Aom_visitor added, which is compliant with existing visitors, also Eiffel wrapper (experimental_app) has been modified to use this new visitor, which is driven by visitor iterator.](https://discourse.openehr.org/t/ref-impl-eiffel-1327-aom-visitor-added-which-is-compliant-with-existing-visitors-also-eiffel-wrapper-experimental-app-has-been-modified-to-use-this-new-visitor-which-is-driven-by-visitor-iterator/13878)
> Revision: 1327
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1326] Added helpers for java and Eiffel side management.](https://discourse.openehr.org/t/ref-impl-eiffel-1326-added-helpers-for-java-and-eiffel-side-management/15039)
> Revision: 1326
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1325] Set better default size for RM schema dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-1325-set-better-default-size-for-rm-schema-dialog/13876)
> Revision: 1325
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1324] Make it so that RM schemas that fail even parsing are listed in all_schemas , and visible in RM_SCHEMA_DIALOG.](https://discourse.openehr.org/t/ref-impl-eiffel-1324-make-it-so-that-rm-schemas-that-fail-even-parsing-are-listed-in-all-schemas-and-visible-in-rm-schema-dialog/13875)
> Revision: 1324
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1323] Add button for viewing RM schema validation report.](https://discourse.openehr.org/t/ref-impl-eiffel-1323-add-button-for-viewing-rm-schema-validation-report/13874)
> Revision: 1323
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1322] Correct problems in the RM schema dialog that prevented the user from setting the schema directory :](https://discourse.openehr.org/t/ref-impl-eiffel-1322-correct-problems-in-the-rm-schema-dialog-that-prevented-the-user-from-setting-the-schema-directory/13873)
> Revision: 1322
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1321] Correct bugs in BMM class validation; accept manual changes in RM schema dialog RM schema directory text box.](https://discourse.openehr.org/t/ref-impl-eiffel-1321-correct-bugs-in-bmm-class-validation-accept-manual-changes-in-rm-schema-dialog-rm-schema-directory-text-box/13872)
> Revision: 1321
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1320] Small fix to avoid Void-ref in BMM schema generic parameter validation.](https://discourse.openehr.org/t/ref-impl-eiffel-1320-small-fix-to-avoid-void-ref-in-bmm-schema-generic-parameter-validation/13867)
> Revision: 1320
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1319] MERGE of BMM upgrade changes to this branch from adl1.5-bmm branch.](https://discourse.openehr.org/t/ref-impl-eiffel-1319-merge-of-bmm-upgrade-changes-to-this-branch-from-adl1-5-bmm-branch/13866)
> Revision: 1319
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1318] Update dadl_test app for dadl-based .cfg files.](https://discourse.openehr.org/t/ref-impl-eiffel-1318-update-dadl-test-app-for-dadl-based-cfg-files/13865)
> Revision: 1318
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1317] Correct some broken semantics in reading and writing object values in the DT_* classes .](https://discourse.openehr.org/t/ref-impl-eiffel-1317-correct-some-broken-semantics-in-reading-and-writing-object-values-in-the-dt-classes/13864)
> Revision: 1317
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1316] Upgrade Basic meta-model (BMM) schema facility:](https://discourse.openehr.org/t/ref-impl-eiffel-1316-upgrade-basic-meta-model-bmm-schema-facility/13863)
> Revision: 1316
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1315] Fix compilation errors caused by the last four revisions.](https://discourse.openehr.org/t/ref-impl-eiffel-1315-fix-compilation-errors-caused-by-the-last-four-revisions/13862)
> Revision: 1315
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Playing with Open EHR-Gen](https://discourse.openehr.org/t/playing-with-open-ehr-gen/13861)
> [Cave: X-post, please reply to the thread on the implementation list or even better edit the wiki page]
Hey guys
I started a wiki page about my first experiences with Pablo's framework
Here is the link: [http://www.openehr.org/wiki/display/impl/Playing+with+Pablo%27s+Open+EHR-Gen+Framework](http://www.openehr.org/wiki/display/impl/Playing+with+Pablo%27s+Open+EHR-Gen+Framework)
Feel free to participate.
Cheers
-thilo
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Playing with Open EHR-Gen](https://discourse.openehr.org/t/playing-with-open-ehr-gen/13860)
> Hey guys
I started a wiki page about my first experiences with Pablo's framework
Here is the link: [http://www.openehr.org/wiki/display/impl/Playing+with+Pablo%27s+Open+EHR-Gen+Framework](http://www.openehr.org/wiki/display/impl/Playing+with+Pablo%27s+Open+EHR-Gen+Framework)
Feel free to participate.
Cheers
-thilo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1313] Two fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-1313-two-fixes/15015)
> Revision: 1313
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1312] Dadl config file for AWB now working, although needs heavier testing .](https://discourse.openehr.org/t/ref-impl-eiffel-1312-dadl-config-file-for-awb-now-working-although-needs-heavier-testing/13858)
> Revision: 1312
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Update from the openEHR Foundation Board](https://discourse.openehr.org/t/update-from-the-openehr-foundation-board/13857)
> [The following from prof. David Ingram, UCL]
At the end of August, the Foundation Board posted an announcement about progress of discussions with IHTSDO concerning governance of archetypes and SNOMED terminology, expecting to be in a position to report back by mid-October. We have been working along the lines set out in previous announcements, here, and the wiki consultation process with *open*EHR users, earlier this year. Although a detailed set of options has been drafted by IHTSDO and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GUI-directives/hints again (Was: Developing usable GUIs)](https://discourse.openehr.org/t/gui-directives-hints-again-was-developing-usable-guis/15029)
> Hi All!
There was a related discussion regarding GUI-directives/hints around june 2008, that I tried to summarize in the post [http://www.openehr.org/mailarchives/openehr-technical/msg03755.html](http://www.openehr.org/mailarchives/openehr-technical/msg03755.html)
As you will see that post is somewhere in the middle of the thread, so you can find other interesting things before and after that post in the archives.
Now, if I understand things correctly there is now implementatin experience...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Developing usable GUIs](https://discourse.openehr.org/t/developing-usable-guis/13852)
> Hi there,
Linked to this email you may find a GUI prototype of a clinical application.
The GUI includes various tabs, trees for presenting various categories of items and so on.
My very specific question is "Is it possible to create such GUIs applying existing tools/frameworks"?
[http://www.openehr.org/wiki/download/attachments/18284548/new.png](http://www.openehr.org/wiki/download/attachments/18284548/new.png)
For more information please visit the wiki...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1311] Rename CONFIG_FILE_ACCESS to INI_CONFIG_FILE_ACCESS, so as to distinguish it from new DADL config file class.](https://discourse.openehr.org/t/ref-impl-eiffel-1311-rename-config-file-access-to-ini-config-file-access-so-as-to-distinguish-it-from-new-dadl-config-file-class/16302)
> Revision: 1311
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [REST Based Services and Storage Interfaces for openEHR Implementations](https://discourse.openehr.org/t/rest-based-services-and-storage-interfaces-for-openehr-implementations/15778)
> Hi all\!
We had a poster titled "REST Based Services and Storage Interfaces for
openEHR Implementations" at a Swedish conference in September\. I have
now finally gotten around to reformatting it to be readable when read
on screen or printed as a three\-page booklet on normally sized \(A4\)
paper\. It is available at:
http://www.imt.liu.se/~erisu/2010/EEE-Poster-multipage.pdf
Some of you have already heard these ideas at Medinfo in Capetown\.
Questions and discussions are very...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1310] Version with modified BMM library to support nested BMM schema files .](https://discourse.openehr.org/t/ref-impl-eiffel-1310-version-with-modified-bmm-library-to-support-nested-bmm-schema-files/13851)
> Revision: 1310
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1309] Comment out a change that will be needed for EiffelStudio 6. 7 but that does not compile in EiffelStudio 6.6.](https://discourse.openehr.org/t/ref-impl-eiffel-1309-comment-out-a-change-that-will-be-needed-for-eiffelstudio-6-7-but-that-does-not-compile-in-eiffelstudio-6-6/13850)
> Revision: 1309
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Because it's only healthcare IT that is so screwed up....](https://discourse.openehr.org/t/because-its-only-healthcare-it-that-is-so-screwed-up/13853)
> http://laforge.gnumonks.org/weblog/2010/11/12/#20101112-history_of_a52_withdrawal
;\-\)
Grahame
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Shared software implementationl aspects of OpenEHR/HL7 RIMBAA implementations](https://discourse.openehr.org/t/shared-software-implementationl-aspects-of-openehr-hl7-rimbaa-implementations/15013)
> Like Laura, Ed, and others I do believe there are things that can be
learned by looking at the experiences of OpenEHR/HL7v3 implementations,
and by listening to the best practices of those implementers\. So allow
me to interject the following invitation into the fray:
The RIMBAA HL7 Workgroup \(see
http://wiki.hl7.org/index.php?title=RIMBAA) is effectively the HL7
Software Implementers community; and one with a special interest: the
use of the HL7 v3 reference model as a data model for in...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[534] include new components to the root pom.xml](https://discourse.openehr.org/t/534-include-new-components-to-the-root-pom-xml/13848)
> Revision: 534
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[533] introduce dadl-binding into the trunk](https://discourse.openehr.org/t/533-introduce-dadl-binding-into-the-trunk/13847)
> Revision: 533
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[532] introduce xml-binding component into the trunk](https://discourse.openehr.org/t/532-introduce-xml-binding-component-into-the-trunk/13846)
> Revision: 532
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[531] fixed the adl-parser pom so that project build works from root dir](https://discourse.openehr.org/t/531-fixed-the-adl-parser-pom-so-that-project-build-works-from-root-dir/13845)
> Revision: 531
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[530] minor fix in rm-builder](https://discourse.openehr.org/t/530-minor-fix-in-rm-builder/13844)
> Revision: 530
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[529] fixed a typo in pom](https://discourse.openehr.org/t/529-fixed-a-typo-in-pom/13843)
> Revision: 529
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[528] updated the room pom.xml to include three new components](https://discourse.openehr.org/t/528-updated-the-room-pom-xml-to-include-three-new-components/13842)
> Revision: 528
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[527] minor updates in adl-serializer](https://discourse.openehr.org/t/527-minor-updates-in-adl-serializer/13838)
> Revision: 527
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [University Leiria - Portugal](https://discourse.openehr.org/t/university-leiria-portugal/15027)
> I have a problem with the new version of openHER, this is part of the system
error log:
\[ERROR\]Failed to execute goal
org\.apache\.maven\.plugins:maven\-surefire\-plugin:2\.5:test \(default\-test\) on
project adl\-serializer: There are test failures\.
\[ERROR\]
\[ERROR\]Please refer to C:\\openehr\\adl\-serializer\\target\\surefire\-reports for
the individual test results\.
\[ERROR\]\-> \[Help 1\]
\[ERROR\]
\[ERROR\]To see the full stack trace of the errors, re\-run Maven with the \-e...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[526] introduce dadl-parser to the TRUNK](https://discourse.openehr.org/t/526-introduce-dadl-parser-to-the-trunk/13837)
> Revision: 526
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new openEHR-based framework](https://discourse.openehr.org/t/new-openehr-based-framework/13165)
> Hi,
I have send this same email to the last 21090 discussion, and Ian ask me if I can send it again in another thread, here it is.
Just yto give some context, this was written in response to Koray who asks for real-world implementations, and who is studying the complexity/time of building openEHR-based systems.
I should clarify that the framework is the core of the system, but not the whole system. The whole trauma application has also DICOM integration, external MPI integration via IHE...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[525] introduce archetype/ template-based RM instance skeleton generator to the TRUNK](https://discourse.openehr.org/t/525-introduce-archetype-template-based-rm-instance-skeleton-generator-to-the-trunk/13836)
> Revision: 525
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[524] introduce oet-template parser and flattener to the trunk](https://discourse.openehr.org/t/524-introduce-oet-template-parser-and-flattener-to-the-trunk/16301)
> Revision: 524
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Sweden’s noble e-Health strategy](https://discourse.openehr.org/t/sweden-s-noble-e-health-strategy/12043)
> Further to my last email, I said I would mention positive eHealth
developments that are unfolding in Sweden\.
You may be interested in this article and the links to recent Swedish
eHealth presentations\.
http://frectal.com/2010/11/15/swedens-noble-e-health-strategy/
The ambitions of the Swedish eHealth strategy are far seeing and
internationally leading, albeit with much work to do\.
You may already know that openEHR and archetypes feature significantly
within their plans\.
The openEHR...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 21090](https://discourse.openehr.org/t/iso-21090/15037)
> Hi All
I have been having a long discussion with Tom off the
list about ISO 21090, and we've come to agreement
about the general picture\.
When I teach ISO 21090 tutorials, and I get to the
implementation part, the first thing I say is that the
data types are completely denormalised, and that
I would never implement them as is inside my system
\(as anything but an object model for exchange\.\)
And Tom says that they are all designed wrong
to be used as data types inside a...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1307] Get the dadl_test project compiling successfully in EiffelStudio 6. 7 beta.](https://discourse.openehr.org/t/ref-impl-eiffel-1307-get-the-dadl-test-project-compiling-successfully-in-eiffelstudio-6-7-beta/16300)
> Revision: 1307
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1306] Fix a couple of more compilation errors in classes that are in the universe of classes for the dadl_test project , but not compiled into the system.](https://discourse.openehr.org/t/ref-impl-eiffel-1306-fix-a-couple-of-more-compilation-errors-in-classes-that-are-in-the-universe-of-classes-for-the-dadl-test-project-but-not-compiled-into-the-system/13835)
> Revision: 1306
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [World Peace](https://discourse.openehr.org/t/world-peace/14987)
> Dear all,
As Ed Hammond said it somewhere earlier in this discussion: It's like World Peace - a great idea but probably not achievable.
I agree with Ed if we think along the line of ‘one solution should fit all’ and I also think that if we create different solutions for different purposes World Peace is achievable after all. Please let me explain.
The 21090 standard is a fact, is here to stay and is not going to change (soon). As William G. said it has been a tremendous accomplishment and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1305] Fix compilation errors in many classes that are in the universe of classes but not compiled into the system .](https://discourse.openehr.org/t/ref-impl-eiffel-1305-fix-compilation-errors-in-many-classes-that-are-in-the-universe-of-classes-but-not-compiled-into-the-system/16299)
> Revision: 1305
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1304] Fix the dadl_test project so that it compiles again.](https://discourse.openehr.org/t/ref-impl-eiffel-1304-fix-the-dadl-test-project-so-that-it-compiles-again/16298)
> Revision: 1304
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templates, node identifiers and data instances](https://discourse.openehr.org/t/templates-node-identifiers-and-data-instances/15030)
> Dear all,
I have a doubt about templates defined as an archetype specialization. The updated specs say that templates are just a further specialized archetype. So, any change made at that level (remove or define mandatory nodes, slot filling, etc.) also means a new level at the node identifier. For example, if I have a node with "at0001" and I constraint something of it at the template level, we should generate a new "at0001.1" for that node.
The question is, data instances that will be...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[523] minor testcase change](https://discourse.openehr.org/t/523-minor-testcase-change/16297)
> Revision: 523
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[522] changes due to removal of immutable object pattern](https://discourse.openehr.org/t/522-changes-due-to-removal-of-immutable-object-pattern/16296)
> Revision: 522
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[521] changes due to AOM changes](https://discourse.openehr.org/t/521-changes-due-to-aom-changes/16295)
> Revision: 521
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[520] removed immutable object pattern to facilitate template flattening](https://discourse.openehr.org/t/520-removed-immutable-object-pattern-to-facilitate-template-flattening/16294)
> Revision: 520
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[519] removed immutable object pattern, added setters to classes](https://discourse.openehr.org/t/519-removed-immutable-object-pattern-added-setters-to-classes/16293)
> Revision: 519
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[518] added setters (removed immutable object pattern); added path-based value setting api](https://discourse.openehr.org/t/518-added-setters-removed-immutable-object-pattern-added-path-based-value-setting-api/14986)
> Revision: 518
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [upcoming commits](https://discourse.openehr.org/t/upcoming-commits/15036)
> Hi all,
I will soon start to check in recent improvements of the java
reference implementation performed in the context of a Swedish
archetype pilot project\. Just briefly, the main improvements/changes
are: 1\) OET template parsing and flattening; 2\) modifiable RM / AOM
objects; 3\) RM skeleton generator; 4\) improved archetype\-based RM
validation\.
Better documentation of these improvements will appear on openEHR wiki soon\.
Cheers,
Rong
Rong Chen
Cambio Healthcare Systems
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [More on ISO 21090 complexity](https://discourse.openehr.org/t/more-on-iso-21090-complexity/15031)
> It might be just me thinking that some of the 21090 types are not that simple, so am interested in reactions of others. Here is the documentation of the term-code representation type CD, which explains how the 'no exceptions' (CNE) and 'exceptions' (CWE) variants should be realised:
> A CD is a reference to a concept defined in an external code system, terminology, or ontology. A CD may contain a simple code - that is, a reference to a concept defined directly by the referenced code system,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [short presentation on openEHR Tool chain](https://discourse.openehr.org/t/short-presentation-on-openehr-tool-chain/15028)
> On the [Getting started page](http://www.openehr.org/shared-resources/getting_started/getting_started.html), a new presentation is available explaining the *open*EHR knowledge development tool chain. It is less than 10 slides, and since quite a few people have requested it after recent presentations, I have made it generally available.
Direct links: [PPT](http://www.openehr.org/openehr/304-OE/version/default/part/AttachmentData/data/openEHR_toolchain.pptx),...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [download archetype repository](https://discourse.openehr.org/t/download-archetype-repository/13840)
> Dear all,
I'm sure this question is very easily answered, but I can't find a way to download the whole archetype repository available at the CKM (openehr.org/knowledge). I imagine it might be available through svn.
I would like to do some testing in the context of semantic mediation (initial paper describing the idea available in the openEHR page,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 21090 data types too complex?: HL7 models are created with clinician ...](https://discourse.openehr.org/t/iso-21090-data-types-too-complex-hl7-models-are-created-with-clinician/13834)
> In a message dated 10-11-2010 8:41:09 W. Europe Standard Time, hugh.leslie@oceaninformatics.com writes:
> Hi William
>
> I didn't see anyone say that the hl7 models have been developed without clinical input. I am certain this isn't true.
>
> I don't completely agree with you about the ease of accessibility for clinicians of UML models and MIF models - it's not our experience.
>
> Regards Hugh
Let us then agree to that we have different experiences with clinicians appreciating...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Research Topic](https://discourse.openehr.org/t/research-topic/15038)
> Hi All,
I’m a PhD student at the University of Queensland in Brisbane, Australia. I’m currently performing research, in collaboration with other members of the team, on creating an ontology for depicting a health information system model for a heterogeneous group of genetic disorders affecting skeletal development.
I have recently come across openEHR archetypes. I have an interest in this area and would like to kindly ask for your help in finding a research topic which I may be able to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-13606 harmonization CR regarding CLUSTER/TABLE etc and ENTRY/OBSERVATION (Was: ISO 21090 data types too complex?)](https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515)
> Hi!
I hope you don't mind breaking out a side thread with a concrete harmonisation sugestion. First an openEHR change request, then an ISO 13606 change request.
1.
Regarding ITEM_TABLE (and the other classes in the openEHR item_structure package) there was a change request from Sam that went pretty unnoticed by a while ago, see:
[http://www.openehr.org/mailarchives/openehr-technical/msg04994.html](http://www.openehr.org/mailarchives/openehr-technical/msg04994.html)
I'm not saying we...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1303] added parameter names to ArchetypeVisitor method signatures](https://discourse.openehr.org/t/ref-impl-eiffel-1303-added-parameter-names-to-archetypevisitor-method-signatures/13833)
> Revision: 1303
Author: seref\.arikan
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 21090 data types too complex?: HL7 models are created with clinician inp](https://discourse.openehr.org/t/iso-21090-data-types-too-complex-hl7-models-are-created-with-clinician-inp/15019)
> They (the clinical models in HL7 v3 R-MIM format) are all part of extensive clinician input and review, sorry clinicians do understand the modeling in HL7 space, but indeed like any other modeling effort, need some education first.
Statements that this HL7 clinical content modeling is done without clinicians input is simply a lie.
Comments that clinicians are unable to read and understand and critique UML and/or HL7 RIM based class models is not consistent with my 8 year + experience with a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[517] Minor modification of the ADL Parser to support otherwise reserved words such as status and version as uncommon keys in an ArchetypeTerm .](https://discourse.openehr.org/t/517-minor-modification-of-the-adl-parser-to-support-otherwise-reserved-words-such-as-status-and-version-as-uncommon-keys-in-an-archetypeterm/13832)
> Revision: 517
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 21090 data types too complex? - (longish / CO challenge only)](https://discourse.openehr.org/t/iso-21090-data-types-too-complex-longish-co-challenge-only/16692)
> I see a kind of cooperation emerging here, which is fine and what I like most.
Eric points at one are that has my particular interest since I started to represent such assessment scales in HL7 v3 space in 2002. We where using the existing HL7 R1 datatypes then and found that for the calculation of the sumscore the INT could do all counting, but, the specification of each single score needed to be done with a CO that at that time did not "allow" for the calculation. It dit allow Eric's...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1302] more methods added to IArchetypeVisitor and ArchetypeVisitor.](https://discourse.openehr.org/t/ref-impl-eiffel-1302-more-methods-added-to-iarchetypevisitor-and-archetypevisitor/13830)
> Revision: 1302
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1301] IArchetypeVisitor extended with more methods to match bosphorus_visitor type .](https://discourse.openehr.org/t/ref-impl-eiffel-1301-iarchetypevisitor-extended-with-more-methods-to-match-bosphorus-visitor-type/13829)
> Revision: 1301
Author: seref\.arikan
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: Paper on archetypes and enterprise data integration](https://discourse.openehr.org/t/annc-paper-on-archetypes-and-enterprise-data-integration/14982)
> The following paper has been published; links on the openEHR website [Resource page](http://www.openehr.org/shared-resources/publications/archetypes.html):
- _**Archetype-based semantic mediation: Incremental provisioning of data services ([PDF](http://www.dtic.upf.edu/%7Ejbisbal/publications/Bisbal-155-CBMS2010.pdf))**_
- **Jesus Bisbal, Gerhard Engelbrecht, and Alejandro Frangi**
CISTIB - Universitat Pompeu Fabra, and CIBER-BBN, Barcelona,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 21090 data types too complex?](https://discourse.openehr.org/t/iso-21090-data-types-too-complex/15023)
> The NCI's take, from [this document ](https://wiki.nci.nih.gov/download/attachments/18941682/Policy_Guidelines_ISO_21090_Final+%28Approved%29.doc?version=1&modificationDate=1247258606000)available [here](https://wiki.nci.nih.gov/display/ISO21090/CBIIT+Guidelines+for+Using+the+ISO+21090+Standard) on the NCI wiki (blue emphasis mine):
~~~~~~~~~~~~~~~~~~~~~~~~~~ from NCI CBIIT Guidelines for Using the ISO 21090 Standard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
## Guidelines- The use of ISO...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1300] Clean up error db files and separate out official openEHR error code part.](https://discourse.openehr.org/t/ref-impl-eiffel-1300-clean-up-error-db-files-and-separate-out-official-openehr-error-code-part/13828)
> Revision: 1300
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Uppercase and lowercase at archetype nodes](https://discourse.openehr.org/t/uppercase-and-lowercase-at-archetype-nodes/14972)
> While working with archetypes for different reference models we have faced a problem regarding the uppercase/lowercase rules for naming archetype nodes at ADL.
The ADL specifications imposes the following rule: "A type name is any identifier with an initial upper case letter, followed by any combination of letters, digits and underscores. A generic type name (including nested forms) additionally may include commas and angle brackets, but no spaces, and must be syntactically correct as per...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1299] Fix a typo.](https://discourse.openehr.org/t/ref-impl-eiffel-1299-fix-a-typo/13825)
> Revision: 1299
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1298] logger type now checks for null pointer for stored c++ pointer to ILogger instance](https://discourse.openehr.org/t/ref-impl-eiffel-1298-logger-type-now-checks-for-null-pointer-for-stored-c-pointer-to-ilogger-instance/13824)
> Revision: 1298
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1297]](https://discourse.openehr.org/t/ref-impl-eiffel-1297/16292)
> Revision: 1297
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1296] ILogger. h and ArchetypeLogger were added to connect Eiffel output to C++.](https://discourse.openehr.org/t/ref-impl-eiffel-1296-ilogger-h-and-archetypelogger-were-added-to-connect-eiffel-output-to-c/13823)
> Revision: 1296
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1295] LOGGER type added to connect Eiffel output to C++/Java.](https://discourse.openehr.org/t/ref-impl-eiffel-1295-logger-type-added-to-connect-eiffel-output-to-c-java/16291)
> Revision: 1295
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1294] IArchetypeVisitor.cpp IArchetypeVisitor.h and ArchetypeVisitor. cpp and ArchetypeVisitor.h added.](https://discourse.openehr.org/t/ref-impl-eiffel-1294-iarchetypevisitor-cpp-iarchetypevisitor-h-and-archetypevisitor-cpp-and-archetypevisitor-h-added/16290)
> Revision: 1294
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1293] bosphorus_visitor class now accepts a c++ visitor, which it calls during visits.](https://discourse.openehr.org/t/ref-impl-eiffel-1293-bosphorus-visitor-class-now-accepts-a-c-visitor-which-it-calls-during-visits/13822)
> Revision: 1293
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1292] .suo file removed, since it is specific to user, not to project](https://discourse.openehr.org/t/ref-impl-eiffel-1292-suo-file-removed-since-it-is-specific-to-user-not-to-project/13821)
> Revision: 1292
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1291] Added bosphorus_visitor.e, which defines a visitor that is going to wrap C++ visitor.](https://discourse.openehr.org/t/ref-impl-eiffel-1291-added-bosphorus-visitor-e-which-defines-a-visitor-that-is-going-to-wrap-c-visitor/13820)
> Revision: 1291
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1290] Fix compilation errors in many classes that are in the universe of classes but not compiled into the system .](https://discourse.openehr.org/t/ref-impl-eiffel-1290-fix-compilation-errors-in-many-classes-that-are-in-the-universe-of-classes-but-not-compiled-into-the-system/13819)
> Revision: 1290
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1289] Remove local RM schemas app-specific directories, replaced by addition of SVN ext-ref to knowledge2 repository.](https://discourse.openehr.org/t/ref-impl-eiffel-1289-remove-local-rm-schemas-app-specific-directories-replaced-by-addition-of-svn-ext-ref-to-knowledge2-repository/14961)
> Revision: 1289
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1288] Add a Subversion external to the rm_schemas directory in the knowledge2 repository 's TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1288-add-a-subversion-external-to-the-rm-schemas-directory-in-the-knowledge2-repository-s-trunk/13818)
> Revision: 1288
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1287] When serialising a dADL node id, escape any double-quotes in the id with a backslash.](https://discourse.openehr.org/t/ref-impl-eiffel-1287-when-serialising-a-dadl-node-id-escape-any-double-quotes-in-the-id-with-a-backslash/13817)
> Revision: 1287
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1286] Make rm_schemas directory a settable option on RM_SCHEMA_DIALOG.](https://discourse.openehr.org/t/ref-impl-eiffel-1286-make-rm-schemas-directory-a-settable-option-on-rm-schema-dialog/13816)
> Revision: 1286
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1285] Correct bug in ADHOC_FILE_REPOSITORY - misplaced 'not' was causing archetypes with valid ids to be treated as having invalid ( old-style draft) ids.](https://discourse.openehr.org/t/ref-impl-eiffel-1285-correct-bug-in-adhoc-file-repository-misplaced-not-was-causing-archetypes-with-valid-ids-to-be-treated-as-having-invalid-old-style-draft-ids/13810)
> Revision: 1285
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1283] Correct bug in compilation from scratch mode (used by test page) where compilation timestamp was not reset properly.](https://discourse.openehr.org/t/ref-impl-eiffel-1283-correct-bug-in-compilation-from-scratch-mode-used-by-test-page-where-compilation-timestamp-was-not-reset-properly/13808)
> Revision: 1283
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1282] Changed omit default library names setting in the project setup.](https://discourse.openehr.org/t/ref-impl-eiffel-1282-changed-omit-default-library-names-setting-in-the-project-setup/13807)
> Revision: 1282
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1281] Visual studio solution file configuration fixes](https://discourse.openehr.org/t/ref-impl-eiffel-1281-visual-studio-solution-file-configuration-fixes/13806)
> Revision: 1281
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1280] Bosphorus directory contains a vc++ 2010 Express solution.](https://discourse.openehr.org/t/ref-impl-eiffel-1280-bosphorus-directory-contains-a-vc-2010-express-solution/13805)
> Revision: 1280
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1277] Correct the default editor commands for Mac OS X:](https://discourse.openehr.org/t/ref-impl-eiffel-1277-correct-the-default-editor-commands-for-mac-os-x/13796)
> Revision: 1277
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1276] Separate Options dialog into two - original contains just options and tool paths etc .](https://discourse.openehr.org/t/ref-impl-eiffel-1276-separate-options-dialog-into-two-original-contains-just-options-and-tool-paths-etc/13795)
> Revision: 1276
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-RM-LINK discussion - now also on mailing list :-)](https://discourse.openehr.org/t/openehr-rm-link-discussion-now-also-on-mailing-list/15018)
> Hi\!
I hear of a lot of interesting off\-line discussions regarding the
openEHR RM object named "LINK"\. I guess they have not yet reached the
mailing list because of time restrictions and/or the
exploratory/initial nature of the discussions\. But now let's get more
good brains involved\.\.\.
Just to make sure we talk about the same thing, it is the class LINK
described in section 3\.2\.4 in
http://www.openehr.org/releases/1.0.2/architecture/rm/common_im.pdf
and in XML...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1275] feature to compile arcetype was added to class which is used by CECIL](https://discourse.openehr.org/t/ref-impl-eiffel-1275-feature-to-compile-arcetype-was-added-to-class-which-is-used-by-cecil/13794)
> Revision: 1275
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1274] Compile archetype method added to openEHRManager class](https://discourse.openehr.org/t/ref-impl-eiffel-1274-compile-archetype-method-added-to-openehrmanager-class/13793)
> Revision: 1274
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1273] Compile archetype method added to openEHRManager class](https://discourse.openehr.org/t/ref-impl-eiffel-1273-compile-archetype-method-added-to-openehrmanager-class/16289)
> Revision: 1273
Author: seref\.arikan
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Question about ADL-syntax (1.4) archetypeslot](https://discourse.openehr.org/t/question-about-adl-syntax-1-4-archetypeslot/15022)
> Hi,
Please allow me this ignorant question\.
Below the "allow\_archetype", there are includes \(and excludes\)
Below the "include" are rules what is include\(d\)
Like this\.
\(examples from repository on OpenEhr website\)
1\) allow\_archetype CLUSTER occurrences matches \{0\.\.1\} matches \{
include
archetype\_id/value matches \{/change\\\.v1draft/\}
2\) allow\_archetype ITEM\_TREE occurrences...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1272] app_root does not discover rm_schemas and error_db directories from the executable name anymore .](https://discourse.openehr.org/t/ref-impl-eiffel-1272-app-root-does-not-discover-rm-schemas-and-error-db-directories-from-the-executable-name-anymore/16288)
> Revision: 1272
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1271] functions for setting up rm_schema dir location and error_db dir location were added .](https://discourse.openehr.org/t/ref-impl-eiffel-1271-functions-for-setting-up-rm-schema-dir-location-and-error-db-dir-location-were-added/16287)
> Revision: 1271
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1270] functions for setting up rm_schema dir location and error_db dir location were added .](https://discourse.openehr.org/t/ref-impl-eiffel-1270-functions-for-setting-up-rm-schema-dir-location-and-error-db-dir-location-were-added/13792)
> Revision: 1270
Author: seref\.arikan
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Articles on Healthcare, Complexity, Change, Process, IT and the role of openEHR etc](https://discourse.openehr.org/t/articles-on-healthcare-complexity-change-process-it-and-the-role-of-openehr-etc/15024)
> Tony,
This is very impressive piece of work. Every since I first came across openEHR I have intuitively felt that it is closer to the 'solution' than more static attempts at standardization. So why is progress so slow? I've appplied some lateral thinking to this, and come up with what many people on this list may (at best) think contrarian - but at the risk of being flamed....
The Case for NPfIT 2.0 www.nationalhealthexecutive.com page 52-53.
(I'll go get my hard hat now...)
Best...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Articles on Healthcare, Complexity, Change, Process, IT and the role of openEHR etc](https://discourse.openehr.org/t/articles-on-healthcare-complexity-change-process-it-and-the-role-of-openehr-etc/14935)
> Late last year I said I would work on some material to help explain openEHR in the wider context of healthcare change during 2010\.
It has taken me longer that I originally planned but I've recently shared some articles online towards that end\.
http://frectal.com/book/
The articles explore issues such as
Healthcare under pressure,
Complexity of healthcare\+management\+IT,
Change and the elements within
Aligning process improvement efforts with IT
In the final articles I explore...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Mindmap software](https://discourse.openehr.org/t/mindmap-software/15021)
> Hi,
Does anybody have a recommendation for a Java software package for drawing the kind of mindmaps
that are often seen in openEHR contexts like for instance the openEHR Clinical Knowledge Manager?
regards
Olof Torgersson
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_QUANTITY or DV_PROPORTION](https://discourse.openehr.org/t/dv-quantity-or-dv-proportion/15020)
> I'm wondering which is the correct use of DV\_PROPORTION and DV\_QUANTITY\.\.\.
When using DV\_QUANTITY with property attribute 'proportion' and when using
DV\_PROPORTION? Why can not we use always a DV\_PROPORTION for proportion\!?
Regards
leo
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Datastructures and unique](https://discourse.openehr.org/t/datastructures-and-unique/15017)
> Hi,
In the RM\-datastructures, like ItemList and itemTree, there is no
structure to implement a the effect of the ADL keyword "unique"\.
A Set is the Java\-way to enforce "unique"\.
But a Set is not allowed in the RM\-container\-datastructures\.
How can this be solved?
Thanks for any thoughts\.
Bert Verhees
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1269] Fix adl_parser to compile following changes in revision 1262.](https://discourse.openehr.org/t/ref-impl-eiffel-1269-fix-adl-parser-to-compile-following-changes-in-revision-1262/13790)
> Revision: 1269
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1268] Add missing quotes to the diff command lines.](https://discourse.openehr.org/t/ref-impl-eiffel-1268-add-missing-quotes-to-the-diff-command-lines/13789)
> Revision: 1268
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1266] Add buttons and options for launching a diff tool from the test page , enabling the user to conveniently see .adls and . adlf diffs generated by the test page tests.](https://discourse.openehr.org/t/ref-impl-eiffel-1266-add-buttons-and-options-for-launching-a-diff-tool-from-the-test-page-enabling-the-user-to-conveniently-see-adls-and-adlf-diffs-generated-by-the-test-page-tests/13784)
> Revision: 1266
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR EHR Extract - new proposal posted](https://discourse.openehr.org/t/openehr-ehr-extract-new-proposal-posted/13785)
> For those of you interested in EHR Extracts, a new proposed update to the openEHR EHR Extract has been posted at [http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract](http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract) .This describes a very flexible and completely archteypable Extract, in which all components, including the outer structure, clinical content and demographic and administrative content can be archetyped and templated using ADL/AOM 1.5. This proposal better...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1265] types in language libraries which must be exposed to c side of things, like STRING or ARRAY are now exported from the libraries section of settings .](https://discourse.openehr.org/t/ref-impl-eiffel-1265-types-in-language-libraries-which-must-be-exposed-to-c-side-of-things-like-string-or-array-are-now-exported-from-the-libraries-section-of-settings/13783)
> Revision: 1265
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1264] CECIL to C++ communication works now.](https://discourse.openehr.org/t/ref-impl-eiffel-1264-cecil-to-c-communication-works-now/13782)
> Revision: 1264
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1263] CECIL to C++ communication works now.](https://discourse.openehr.org/t/ref-impl-eiffel-1263-cecil-to-c-communication-works-now/16286)
> Revision: 1263
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1262] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1262-changes/16284)
> Revision: 1262
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical Significance" field in problem-diagnosis](https://discourse.openehr.org/t/clinical-significance-field-in-problem-diagnosis/16690)
> Is there any particular reason why the field "Clinical significance" of
openEHR\-EHR\-EVALUATION\.problem\.v1 is not present in the specialized archetype
openEHR\-EHR\-EVALUATION\.problem\-diagnosis\.v1??
Best regards
leo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1261] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1261-changes/16283)
> Revision: 1261
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1260] This is an Eclipse C++ project using Eclipse Helios and CDT under windows, with mingw (gcc 4.5) as its compiler.](https://discourse.openehr.org/t/ref-impl-eiffel-1260-this-is-an-eclipse-c-project-using-eclipse-helios-and-cdt-under-windows-with-mingw-gcc-4-5-as-its-compiler/13780)
> Revision: 1260
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1259] This is an Eclipse C++ project using Eclipse Helios and CDT under windows, with mingw (gcc 4.5) as its compiler.](https://discourse.openehr.org/t/ref-impl-eiffel-1259-this-is-an-eclipse-c-project-using-eclipse-helios-and-cdt-under-windows-with-mingw-gcc-4-5-as-its-compiler/13779)
> Revision: 1259
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1258] This is an Eclipse C++ project using Eclipse Helios and CDT on Windows XP.](https://discourse.openehr.org/t/ref-impl-eiffel-1258-this-is-an-eclipse-c-project-using-eclipse-helios-and-cdt-on-windows-xp/13778)
> Revision: 1258
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1257] This is an Eclipse C++ project using Eclipse Helios and CDT on Windows XP.](https://discourse.openehr.org/t/ref-impl-eiffel-1257-this-is-an-eclipse-c-project-using-eclipse-helios-and-cdt-on-windows-xp/13777)
> Revision: 1257
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1256]](https://discourse.openehr.org/t/ref-impl-eiffel-1256/13776)
> Revision: 1256
Author: seref\.arikan
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Passing of Hans Åhlfeldt](https://discourse.openehr.org/t/passing-of-hans-ahlfeldt/13781)
> ```
Professor Hans Åhlfeldt, head of the Department of Biomedical Engineering at
Linköping University in Sweden, died Friday the 24th of September due to
his rapidly worsening illness detected a few months ago. Hans will be
greatly missed by his family and colleagues in Sweden and all over the
world.
Please share memories of Hans on the memorial page at [http://hans.imt.liu.se/](http://hans.imt.liu.se/)
Your contribution of thoughts is appreciated by family and friends no matter
how short or...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1255]](https://discourse.openehr.org/t/ref-impl-eiffel-1255/16282)
> Revision: 1255
Author: seref\.arikan
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1254] branch for Java / C++ wrapping of libraries and components.](https://discourse.openehr.org/t/ref-impl-eiffel-1254-branch-for-java-c-wrapping-of-libraries-and-components/13772)
> Revision: 1254
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1253] The SConstruct now builds various projects that were recently added, including the static library wrapper for the compiler project and its test C wrapper program .](https://discourse.openehr.org/t/ref-impl-eiffel-1253-the-sconstruct-now-builds-various-projects-that-were-recently-added-including-the-static-library-wrapper-for-the-compiler-project-and-its-test-c-wrapper-program/13771)
> Revision: 1253
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1252] Create new ADL1.5 clean branch from TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1252-create-new-adl1-5-clean-branch-from-trunk/13770)
> Revision: 1252
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL Workbench beta 2 released](https://discourse.openehr.org/t/adl-workbench-beta-2-released/13763)
> A second beta of the ADL/AOM 1.5 Workbench has been released. The main feature added is support for **regression testing of archetypes**. A new SVN repository has been added at [http://www.openehr.org/svn/knowledge2/TRUNK/](http://www.openehr.org/svn/knowledge2/TRUNK/) that contains test archetypes as well as the object model schemas used to drive the ADL Workbench. Around 150 test archetypes are available, each now with a test result tag included in the description meta-data, covering most...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1251] The SConstruct now builds various projects that were recently added, including the static library wrapper for the compiler project and its test C wrapper program .](https://discourse.openehr.org/t/ref-impl-eiffel-1251-the-sconstruct-now-builds-various-projects-that-were-recently-added-including-the-static-library-wrapper-for-the-compiler-project-and-its-test-c-wrapper-program/13768)
> Revision: 1251
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1250] Correct date in release_notes.html](https://discourse.openehr.org/t/ref-impl-eiffel-1250-correct-date-in-release-notes-html/16281)
> Revision: 1250
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1249] Correct date in release_notes.html](https://discourse.openehr.org/t/ref-impl-eiffel-1249-correct-date-in-release-notes-html/13767)
> Revision: 1249
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1248] Don't install the release notes file.](https://discourse.openehr.org/t/ref-impl-eiffel-1248-dont-install-the-release-notes-file/13766)
> Revision: 1248
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1247] Merge SVN rev 1246 form specialsiation ( release notes - related adjustments)](https://discourse.openehr.org/t/ref-impl-eiffel-1247-merge-svn-rev-1246-form-specialsiation-release-notes-related-adjustments/13765)
> Revision: 1247
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1246] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1246-changes/13764)
> Revision: 1246
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1245] Merge rev 1244 from specialisation to TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1245-merge-rev-1244-from-specialisation-to-trunk/13762)
> Revision: 1245
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1244] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1244-changes/13759)
> Revision: 1244
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1243] Fix adl_parser.ecf to compile following changes in revision 1231, by passing the current language when serialising.](https://discourse.openehr.org/t/ref-impl-eiffel-1243-fix-adl-parser-ecf-to-compile-following-changes-in-revision-1231-by-passing-the-current-language-when-serialising/13758)
> Revision: 1243
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1242] Merge revs 1231-1241 from specialisation branch to TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1242-merge-revs-1231-1241-from-specialisation-branch-to-trunk/13757)
> Revision: 1242
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1241] Changes to documentation including:](https://discourse.openehr.org/t/ref-impl-eiffel-1241-changes-to-documentation-including/13756)
> Revision: 1241
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1240] Remove the resource file from the adl_compiler project.](https://discourse.openehr.org/t/ref-impl-eiffel-1240-remove-the-resource-file-from-the-adl-compiler-project/13755)
> Revision: 1240
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1239] Further improvements inn error reporting.](https://discourse.openehr.org/t/ref-impl-eiffel-1239-further-improvements-inn-error-reporting/14900)
> Revision: 1239
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [possible conflict in DvDateTime <-> ADL combination](https://discourse.openehr.org/t/possible-conflict-in-dvdatetime-adl-combination/15016)
> Hi,
In ADL is possible to defineDate\-Time pattern: yyyy\-??\-??T??:??:??
But there is no way, in the current DvDateTime to instantiate a class
with a string conform this ADL \- spec\.
I wonder if this is an error?
Thanks
Bert Verhees
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1238] EDT-634: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL , copy fixes from BRANCHES/ specialisation revision 1235 so that the OG_PATH parser can handle predicates (i.e.](https://discourse.openehr.org/t/ref-impl-eiffel-1238-edt-634-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-copy-fixes-from-branches-specialisation-revision-1235-so-that-the-og-path-parser-can-handle-predicates-i-e/13748)
> Revision: 1238
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1237] EDT-633: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL , copy the fix from BRANCHES/ specialisation revisions 1232 and 1236 that allows any URI to be accepted ( not just those c](https://discourse.openehr.org/t/ref-impl-eiffel-1237-edt-633-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-copy-the-fix-from-branches-specialisation-revisions-1232-and-1236-that-allows-any-uri-to-be-accepted-not-just-those-c/13745)
> Revision: 1237
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1236] Commit missed generated .e files from fix to dADL . l lexer file that allows any URI to be accepted (not just those containing //).](https://discourse.openehr.org/t/ref-impl-eiffel-1236-commit-missed-generated-e-files-from-fix-to-dadl-l-lexer-file-that-allows-any-uri-to-be-accepted-not-just-those-containing/13743)
> Revision: 1236
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1235] Add code to OG_PATH parser to handle predicates (i.e.](https://discourse.openehr.org/t/ref-impl-eiffel-1235-add-code-to-og-path-parser-to-handle-predicates-i-e/13742)
> Revision: 1235
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1234] EDT-634: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL , copy fixes from BRANCHES/ specialisation revision 1232 so that the ontology object treats some constraint and term bindi](https://discourse.openehr.org/t/ref-impl-eiffel-1234-edt-634-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-copy-fixes-from-branches-specialisation-revision-1232-so-that-the-ontology-object-treats-some-constraint-and-term-bindi/16277)
> Revision: 1234
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1233] Fix a typo in the last revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1233-fix-a-typo-in-the-last-revision/13740)
> Revision: 1233
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [State of the CKM!](https://discourse.openehr.org/t/state-of-the-ckm/13746)
> If you're interested, an update resides on the CKM part of the openEHR wiki... [http://www.openehr.org/wiki/display/healthmod/State+of+the+CKM](http://www.openehr.org/wiki/display/healthmod/State+of+the+CKM)!
I'm honestly blown away by the momentum and interest from all over the globe - 62 countries represented, from small to large. The current number of registrants and especially volunteers to review archetype content and translate are all purely from the existing community and through word...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1232] These changes change ARCHETYPE_ONTOLOGY and ADL_ENGINE so that the ontology object properly reports coded errors , currently only to do with constraint_ and term_bindings.](https://discourse.openehr.org/t/ref-impl-eiffel-1232-these-changes-change-archetype-ontology-and-adl-engine-so-that-the-ontology-object-properly-reports-coded-errors-currently-only-to-do-with-constraint-and-term-bindings/14875)
> Revision: 1232
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR and iPhone/iPad anyone?](https://discourse.openehr.org/t/openehr-and-iphone-ipad-anyone/15014)
> Hi,
Is there anyone who's done any work related to openEHR for the iPhone/iPad?
I guess one would need an implementation of the reference model etc in Objective\-C since that's the only supported language on the platform\.
If you are working on this or interested in the topic then I would be interested in knowing about it\.
regards
Olof Torgersson
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1231] Various changes due to bugs uncovered by regression testing...](https://discourse.openehr.org/t/ref-impl-eiffel-1231-various-changes-due-to-bugs-uncovered-by-regression-testing/13737)
> Revision: 1231
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medinfo2010 Clinical Modelling Tutorial](https://discourse.openehr.org/t/medinfo2010-clinical-modelling-tutorial/15004)
> Hi everyone,
Mission accomplished!! There was good representation of openEHR activity at Medinfo2010, and most of us should have arrived home this weekend.
There were over 1000 attendees with a small exhibition. We had openEHR devotees from UK, Sweden, Portugal, Japan, New Zealand, Germany, and Australia - hope I haven't missed anybody.
Shinji Kobayashi and I experienced some of South Africa's informal redistribution of wealth from our luggage in transit - Shinji parted from his camera; me...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1230] EDT-634: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL , Fix an endless loop that occurred if the archetype contained an invalid constraint binding .](https://discourse.openehr.org/t/ref-impl-eiffel-1230-edt-634-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-fix-an-endless-loop-that-occurred-if-the-archetype-contained-an-invalid-constraint-binding/13736)
> Revision: 1230
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [existence and assumed value](https://discourse.openehr.org/t/existence-and-assumed-value/15009)
> Hi all,
I noticed that the JAVA ADL\-parser marks a CObject existence as required
if it is not specified in ADL
If there is also an assumed value specified, then this is, in my opinion
conflicting, because the function of the assumed value is to use it when
there an attribute is not used
\(page 21 AOM\.pdf\)\.
Or am I wrong?
Thanks for your attention
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1229] Missed files from last merge.](https://discourse.openehr.org/t/ref-impl-eiffel-1229-missed-files-from-last-merge/13733)
> Revision: 1229
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1228] Missed files from last merge](https://discourse.openehr.org/t/ref-impl-eiffel-1228-missed-files-from-last-merge/13732)
> Revision: 1228
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1227] Missed files from last merge](https://discourse.openehr.org/t/ref-impl-eiffel-1227-missed-files-from-last-merge/13731)
> Revision: 1227
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1226] Update SConstruct from specialisation branch](https://discourse.openehr.org/t/ref-impl-eiffel-1226-update-sconstruct-from-specialisation-branch/13730)
> Revision: 1226
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1225] Correct error in documentation URL.](https://discourse.openehr.org/t/ref-impl-eiffel-1225-correct-error-in-documentation-url/13729)
> Revision: 1225
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1224] Correct error in documentation URL.](https://discourse.openehr.org/t/ref-impl-eiffel-1224-correct-error-in-documentation-url/16275)
> Revision: 1224
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1223] Correct error in documentation URL.](https://discourse.openehr.org/t/ref-impl-eiffel-1223-correct-error-in-documentation-url/14861)
> Revision: 1223
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1222] Second attempt at merge by manual means using 'export' from specialisation into TRUNK work area.](https://discourse.openehr.org/t/ref-impl-eiffel-1222-second-attempt-at-merge-by-manual-means-using-export-from-specialisation-into-trunk-work-area/13728)
> Revision: 1222
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1221] Merged revisions 1189 to 1220 changes from specialisation to TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1221-merged-revisions-1189-to-1220-changes-from-specialisation-to-trunk/13727)
> Revision: 1221
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1220] Various updates:](https://discourse.openehr.org/t/ref-impl-eiffel-1220-various-updates/13726)
> Revision: 1220
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1219] Add config files to C ADLC test project; add some README info.](https://discourse.openehr.org/t/ref-impl-eiffel-1219-add-config-files-to-c-adlc-test-project-add-some-readme-info/13725)
> Revision: 1219
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1218] Move Eiffel build of ADL Compiler lib to C directory, since it is a C lib build.](https://discourse.openehr.org/t/ref-impl-eiffel-1218-move-eiffel-build-of-adl-compiler-lib-to-c-directory-since-it-is-a-c-lib-build/13723)
> Revision: 1218
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1217] 2nd attempt - add C tester for ADL compiler lib](https://discourse.openehr.org/t/ref-impl-eiffel-1217-2nd-attempt-add-c-tester-for-adl-compiler-lib/13721)
> Revision: 1217
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1216] Fix a typo on the Mac installer help page.](https://discourse.openehr.org/t/ref-impl-eiffel-1216-fix-a-typo-on-the-mac-installer-help-page/13720)
> Revision: 1216
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1215] In the SConstruct, tweak the HTML that the Mac installer displays:](https://discourse.openehr.org/t/ref-impl-eiffel-1215-in-the-sconstruct-tweak-the-html-that-the-mac-installer-displays/13719)
> Revision: 1215
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1214] Upload rm_schemas and error_db dirs for adl_compiler deployable lib.](https://discourse.openehr.org/t/ref-impl-eiffel-1214-upload-rm-schemas-and-error-db-dirs-for-adl-compiler-deployable-lib/13718)
> Revision: 1214
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1213] In the Windows installer script, correct the handling of the release notes file.](https://discourse.openehr.org/t/ref-impl-eiffel-1213-in-the-windows-installer-script-correct-the-handling-of-the-release-notes-file/13717)
> Revision: 1213
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1211] Add ADL compiler simulator application.](https://discourse.openehr.org/t/ref-impl-eiffel-1211-add-adl-compiler-simulator-application/13715)
> Revision: 1211
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1210] Generalised the dadl_test application test framework further to include groups of tests .](https://discourse.openehr.org/t/ref-impl-eiffel-1210-generalised-the-dadl-test-application-test-framework-further-to-include-groups-of-tests/13714)
> Revision: 1210
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1209] Change directory for release_notes file to now point to doc/web/ release_notes.html.](https://discourse.openehr.org/t/ref-impl-eiffel-1209-change-directory-for-release-notes-file-to-now-point-to-doc-web-release-notes-html/13712)
> Revision: 1209
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1208] In the Windows installer script, adjust the path to the license file which was moved by the last revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1208-in-the-windows-installer-script-adjust-the-path-to-the-license-file-which-was-moved-by-the-last-revision/13707)
> Revision: 1208
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1207] In the SConstruct, adjust the path to the license file which was moved by the last revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1207-in-the-sconstruct-adjust-the-path-to-the-license-file-which-was-moved-by-the-last-revision/13706)
> Revision: 1207
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1206] Commit move and deletion](https://discourse.openehr.org/t/ref-impl-eiffel-1206-commit-move-and-deletion/13705)
> Revision: 1206
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1205] Add doc directory to adl_workbench directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1205-add-doc-directory-to-adl-workbench-directory/13704)
> Revision: 1205
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1204] Update documentation to include regression testing facility.](https://discourse.openehr.org/t/ref-impl-eiffel-1204-update-documentation-to-include-regression-testing-facility/13703)
> Revision: 1204
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1203] Correction in dadl_test application due to change to structured error reporting in dadl validator .](https://discourse.openehr.org/t/ref-impl-eiffel-1203-correction-in-dadl-test-application-due-to-change-to-structured-error-reporting-in-dadl-validator/13702)
> Revision: 1203
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1202] Minor corrections to logic of regression checking.](https://discourse.openehr.org/t/ref-impl-eiffel-1202-minor-corrections-to-logic-of-regression-checking/13701)
> Revision: 1202
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1201] Include the error_db files in the installers, and rebuild the installers whenever there is a change to the error_db files .](https://discourse.openehr.org/t/ref-impl-eiffel-1201-include-the-error-db-files-in-the-installers-and-rebuild-the-installers-whenever-there-is-a-change-to-the-error-db-files/13700)
> Revision: 1201
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1200] Added Regression test on/off toggle button to Test page.](https://discourse.openehr.org/t/ref-impl-eiffel-1200-added-regression-test-on-off-toggle-button-to-test-page/13699)
> Revision: 1200
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1199] Various changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1199-various-changes/13698)
> Revision: 1199
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1198] Remove IN_MEMORY_MESSAGE_DB ( the MESSAGE_DB class now handles both in_memory and file-based forms of error database ).](https://discourse.openehr.org/t/ref-impl-eiffel-1198-remove-in-memory-message-db-the-message-db-class-now-handles-both-in-memory-and-file-based-forms-of-error-database/13697)
> Revision: 1198
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1197] Various changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1197-various-changes/14835)
> Revision: 1197
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1196] Various cleanup on DT_OBJECT_CONVERTER and related code:](https://discourse.openehr.org/t/ref-impl-eiffel-1196-various-cleanup-on-dt-object-converter-and-related-code/16273)
> Revision: 1196
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1195] Safer type testing in STRING_UTILITIES. atomic_value_to_string function.](https://discourse.openehr.org/t/ref-impl-eiffel-1195-safer-type-testing-in-string-utilities-atomic-value-to-string-function/13696)
> Revision: 1195
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1194] Additional interval types for date/times in DADL_TEST classes.](https://discourse.openehr.org/t/ref-impl-eiffel-1194-additional-interval-types-for-date-times-in-dadl-test-classes/13694)
> Revision: 1194
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1193] Further changes to DT_OBJECT_CONVERTER.](https://discourse.openehr.org/t/ref-impl-eiffel-1193-further-changes-to-dt-object-converter/13693)
> Revision: 1193
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1192] EDT-518: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL , correct the pattern for matching ISO8601_DURATIONs to include decimals on seconds .](https://discourse.openehr.org/t/ref-impl-eiffel-1192-edt-518-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-correct-the-pattern-for-matching-iso8601-durations-to-include-decimals-on-seconds/13692)
> Revision: 1192
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1191] Fix APPLICATION_TEMPLATE to be compilable following recent changes to how the config file is accessed .](https://discourse.openehr.org/t/ref-impl-eiffel-1191-fix-application-template-to-be-compilable-following-recent-changes-to-how-the-config-file-is-accessed/13691)
> Revision: 1191
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Message from openEHR board re openEHR/IHTSDO](https://discourse.openehr.org/t/message-from-openehr-board-re-openehr-ihtsdo/16688)
> [from David Ingram, chair openEHR Foundation Board]
I am writing with good news about continuing progress of the dialogue with the IHTSDO. At a meeting at the end of last week, in London, the following was agreed as a joint announcement to our respective communities.
'The openEHR Foundation core team held a two-day meeting with senior representatives of the IHTSDO on August 26th-27th, in London. This was to continue the very constructive dialogue that has followed from the published MOU...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1189] Interim commit of DADL changes; compiles and executes correctly for all DT primitive types; some intervals still not working; container structures not yet tested.](https://discourse.openehr.org/t/ref-impl-eiffel-1189-interim-commit-of-dadl-changes-compiles-and-executes-correctly-for-all-dt-primitive-types-some-intervals-still-not-working-container-structures-not-yet-tested/13689)
> Revision: 1189
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Position as professor / associate professor in health informatics](https://discourse.openehr.org/t/position-as-professor-associate-professor-in-health-informatics/13688)
> See
http://www.jobbnorge.no/job.aspx?jobid=68992
regards
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1188] Fix the merge of adl_parser.ecf into the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1188-fix-the-merge-of-adl-parser-ecf-into-the-trunk/13687)
> Revision: 1188
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1187] Final file deletions from last merge.](https://discourse.openehr.org/t/ref-impl-eiffel-1187-final-file-deletions-from-last-merge/13686)
> Revision: 1187
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1186] Missed change to directories in SConstruct](https://discourse.openehr.org/t/ref-impl-eiffel-1186-missed-change-to-directories-in-sconstruct/14822)
> Revision: 1186
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1185] Commit missed changes to AWB .ecf files](https://discourse.openehr.org/t/ref-impl-eiffel-1185-commit-missed-changes-to-awb-ecf-files/13685)
> Revision: 1185
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1184] Further missed deletes/moves from last merge](https://discourse.openehr.org/t/ref-impl-eiffel-1184-further-missed-deletes-moves-from-last-merge/13682)
> Revision: 1184
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1183] Rename components/adl_parser directory to adl_compiler.](https://discourse.openehr.org/t/ref-impl-eiffel-1183-rename-components-adl-parser-directory-to-adl-compiler/16271)
> Revision: 1183
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1182] Manual additions / changes relating to directory moves/ deletions from 1159-1180 in specialisation branch.](https://discourse.openehr.org/t/ref-impl-eiffel-1182-manual-additions-changes-relating-to-directory-moves-deletions-from-1159-1180-in-specialisation-branch/13681)
> Revision: 1182
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1181] Merge specialisation revs 1159-1180](https://discourse.openehr.org/t/ref-impl-eiffel-1181-merge-specialisation-revs-1159-1180/13680)
> Revision: 1181
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1180] Correct a path in the NSIS script following the recent move of the vim files .](https://discourse.openehr.org/t/ref-impl-eiffel-1180-correct-a-path-in-the-nsis-script-following-the-recent-move-of-the-vim-files/13679)
> Revision: 1180
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1179] Correct paths in adl_parser. ecf and the SConstruct following the recent separation of the deployment and components directories .](https://discourse.openehr.org/t/ref-impl-eiffel-1179-correct-paths-in-adl-parser-ecf-and-the-sconstruct-following-the-recent-separation-of-the-deployment-and-components-directories/13678)
> Revision: 1179
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1178] Correct path in .ecf file; removed commented old lines from DT_OBJECT_CONVERTER.](https://discourse.openehr.org/t/ref-impl-eiffel-1178-correct-path-in-ecf-file-removed-commented-old-lines-from-dt-object-converter/13677)
> Revision: 1178
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1177] Rename adl_parser directory to adl_compiler.](https://discourse.openehr.org/t/ref-impl-eiffel-1177-rename-adl-parser-directory-to-adl-compiler/13676)
> Revision: 1177
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1176] Remove junk code from testing.](https://discourse.openehr.org/t/ref-impl-eiffel-1176-remove-junk-code-from-testing/13675)
> Revision: 1176
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1175] Move etc directory containing VI syntax config files to a more appropriate place .](https://discourse.openehr.org/t/ref-impl-eiffel-1175-move-etc-directory-containing-vi-syntax-config-files-to-a-more-appropriate-place/13674)
> Revision: 1175
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1174] Move etc directory containing VI syntax config files to a more appropriate place .](https://discourse.openehr.org/t/ref-impl-eiffel-1174-move-etc-directory-containing-vi-syntax-config-files-to-a-more-appropriate-place/13673)
> Revision: 1174
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1173] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1173-further-re-arrangements-in-separation-of-deployment-from-components-directory/13672)
> Revision: 1173
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1172] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1172-further-re-arrangements-in-separation-of-deployment-from-components-directory/14807)
> Revision: 1172
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1171] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1171-further-re-arrangements-in-separation-of-deployment-from-components-directory/13671)
> Revision: 1171
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1170] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1170-further-re-arrangements-in-separation-of-deployment-from-components-directory/13667)
> Revision: 1170
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1169] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1169-further-re-arrangements-in-separation-of-deployment-from-components-directory/13666)
> Revision: 1169
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1168] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1168-further-re-arrangements-in-separation-of-deployment-from-components-directory/13665)
> Revision: 1168
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1167] Further re-arrangements in separation of deployment from components directory](https://discourse.openehr.org/t/ref-impl-eiffel-1167-further-re-arrangements-in-separation-of-deployment-from-components-directory/13664)
> Revision: 1167
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1166] Add eiffel wrapper directory in C area](https://discourse.openehr.org/t/ref-impl-eiffel-1166-add-eiffel-wrapper-directory-in-c-area/13663)
> Revision: 1166
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1165] Further moves as part of adding deployment directory](https://discourse.openehr.org/t/ref-impl-eiffel-1165-further-moves-as-part-of-adding-deployment-directory/13662)
> Revision: 1165
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1164] Various directory moves to separate more cleanly the code, makefiles etc for the deployable forms of the code into each target tehcnology , such as Java, dotnet etc.](https://discourse.openehr.org/t/ref-impl-eiffel-1164-various-directory-moves-to-separate-more-cleanly-the-code-makefiles-etc-for-the-deployable-forms-of-the-code-into-each-target-tehcnology-such-as-java-dotnet-etc/13661)
> Revision: 1164
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1162] Add directories for deployment technologies](https://discourse.openehr.org/t/ref-impl-eiffel-1162-add-directories-for-deployment-technologies/13659)
> Revision: 1162
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1161] Add new directory](https://discourse.openehr.org/t/ref-impl-eiffel-1161-add-new-directory/13657)
> Revision: 1161
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [use_node](https://discourse.openehr.org/t/use-node/15003)
> Please allow me a small question, I think, just for formality reasons\.
Is a archetypeInternalRef always pointing to a node representing a
Locatable?
I haven't seen other way, but it is not explicitly mentioned in the ADL
1\.4 specs
Thanks
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [When to use branches in version tree?](https://discourse.openehr.org/t/when-to-use-branches-in-version-tree/14794)
> Hi all!
I have a question. In distrivuted ehr-change process, when I must to use branches?
For example, in common_im at Fig.13 system B creates new branch.
Why not just continue trunk?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ArchetypeNodeId of an archetypeslot](https://discourse.openehr.org/t/archetypenodeid-of-an-archetypeslot/15008)
> Hi,
Excuse me if \(I\) asked before, it stills keeps puzzling me\.
When we have this archetype\-definition \(this from Rong's repository from
test\-archetypes for the adl\-parser\)
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1160] File rename in dadl_test area.](https://discourse.openehr.org/t/ref-impl-eiffel-1160-file-rename-in-dadl-test-area/13653)
> Revision: 1160
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1159] Interim upload of dadl test app.](https://discourse.openehr.org/t/ref-impl-eiffel-1159-interim-upload-of-dadl-test-app/13652)
> Revision: 1159
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1158] Merge revisions 1152-1157 from BRANCHES/ specialisation into the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-1158-merge-revisions-1152-1157-from-branches-specialisation-into-the-trunk/13651)
> Revision: 1158
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1157] Fix adl_parser. ecf to compile following the reorganisation in revision 1144.](https://discourse.openehr.org/t/ref-impl-eiffel-1157-fix-adl-parser-ecf-to-compile-following-the-reorganisation-in-revision-1144/13650)
> Revision: 1157
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1156] Partial commit of merge of 1144-1151 to TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1156-partial-commit-of-merge-of-1144-1151-to-trunk/13649)
> Revision: 1156
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1155] Partial commit of merge of 1144-1151 to TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1155-partial-commit-of-merge-of-1144-1151-to-trunk/13648)
> Revision: 1155
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1154] Partial commit of merge of 1144-1151 to TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1154-partial-commit-of-merge-of-1144-1151-to-trunk/13647)
> Revision: 1154
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1153] Partial commit of merge of 1144-1151 to TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1153-partial-commit-of-merge-of-1144-1151-to-trunk/13646)
> Revision: 1153
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1152] Partial commit of merge of 1144-1151 to TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-1152-partial-commit-of-merge-of-1144-1151-to-trunk/13645)
> Revision: 1152
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1151] Update GUI and app framework classes to AWB structure so app launches properly .](https://discourse.openehr.org/t/ref-impl-eiffel-1151-update-gui-and-app-framework-classes-to-awb-structure-so-app-launches-properly/13644)
> Revision: 1151
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1150] Basic shell app for dADL testing.](https://discourse.openehr.org/t/ref-impl-eiffel-1150-basic-shell-app-for-dadl-testing/13643)
> Revision: 1150
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1149] Move ANY_VALIDATOR to a common location.](https://discourse.openehr.org/t/ref-impl-eiffel-1149-move-any-validator-to-a-common-location/13642)
> Revision: 1149
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1147] Various clean-up refactoring, no semantic changes.](https://discourse.openehr.org/t/ref-impl-eiffel-1147-various-clean-up-refactoring-no-semantic-changes/13640)
> Revision: 1147
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1146] Move window accelerators class to common lib area.](https://discourse.openehr.org/t/ref-impl-eiffel-1146-move-window-accelerators-class-to-common-lib-area/13638)
> Revision: 1146
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1145] Rename of PG's accelerators class prior to move](https://discourse.openehr.org/t/ref-impl-eiffel-1145-rename-of-pgs-accelerators-class-prior-to-move/13637)
> Revision: 1145
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1144] Perform move of ADL parser specific app framework files to component area.](https://discourse.openehr.org/t/ref-impl-eiffel-1144-perform-move-of-adl-parser-specific-app-framework-files-to-component-area/13636)
> Revision: 1144
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1143] Incorrect file move on TRUNK area.](https://discourse.openehr.org/t/ref-impl-eiffel-1143-incorrect-file-move-on-trunk-area/13635)
> Revision: 1143
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1142] Upload new files in TRUNK update.](https://discourse.openehr.org/t/ref-impl-eiffel-1142-upload-new-files-in-trunk-update/13634)
> Revision: 1142
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1141] Update trunk to current specialisation revision.](https://discourse.openehr.org/t/ref-impl-eiffel-1141-update-trunk-to-current-specialisation-revision/13633)
> Revision: 1141
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1140] Fix the unit tests so that they all compile and pass following the refactoring in recent revisions .](https://discourse.openehr.org/t/ref-impl-eiffel-1140-fix-the-unit-tests-so-that-they-all-compile-and-pass-following-the-refactoring-in-recent-revisions/13632)
> Revision: 1140
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1139] Correct old-style Ocean URL](https://discourse.openehr.org/t/ref-impl-eiffel-1139-correct-old-style-ocean-url/13631)
> Revision: 1139
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1138] Changes](https://discourse.openehr.org/t/ref-impl-eiffel-1138-changes/16270)
> Revision: 1138
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1137] Because SHARED_RESOURCES. show_in_system_browser uses the process library, adl_parser. ecf could not compile.](https://discourse.openehr.org/t/ref-impl-eiffel-1137-because-shared-resources-show-in-system-browser-uses-the-process-library-adl-parser-ecf-could-not-compile/13630)
> Revision: 1137
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1136] Adjust adl_parser. ecf to be able to compile now that the root class no longer has a creation procedure 'make'.](https://discourse.openehr.org/t/ref-impl-eiffel-1136-adjust-adl-parser-ecf-to-be-able-to-compile-now-that-the-root-class-no-longer-has-a-creation-procedure-make/13629)
> Revision: 1136
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1135] Upload missed class.](https://discourse.openehr.org/t/ref-impl-eiffel-1135-upload-missed-class/13628)
> Revision: 1135
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1134] Refactoring of SHARED_xx classes to clean up various things:](https://discourse.openehr.org/t/ref-impl-eiffel-1134-refactoring-of-shared-xx-classes-to-clean-up-various-things/13627)
> Revision: 1134
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1133] Remove a hack in ARCHETYPE_PARSER which was there in order to ensure that SHARED_ARCHETYPE_SERIALISERS .archetype_serialisers were initialised, but the hack is no longer is needed.](https://discourse.openehr.org/t/ref-impl-eiffel-1133-remove-a-hack-in-archetype-parser-which-was-there-in-order-to-ensure-that-shared-archetype-serialisers-archetype-serialisers-were-initialised-but-the-hack-is-no-longer-is-needed/14768)
> Revision: 1133
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Run-time name constraints and appropriate use of terminologies](https://discourse.openehr.org/t/run-time-name-constraints-and-appropriate-use-of-terminologies/14033)
> I have been having an email conversation with Sebastian Iancu of Code24 about some issues concerning the design of the Demographics PARTY_IDENTITY.person_name.v1
[http://www.openehr.org/knowledge/OKM.html#showArchetype_1013.1.477](http://www.openehr.org/knowledge/OKM.html#showArchetype_1013.1.477)
There were 2 key areas discussed:
1. In 'Person identifier' the concept name of the archetype has a 'run-time constraint' allowing the archetype concept to be re-defined at Template/tun-time. e.g...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1132] AWB-167: Update the developer project page for EiffelStudio 6.6.](https://discourse.openehr.org/t/ref-impl-eiffel-1132-awb-167-update-the-developer-project-page-for-eiffelstudio-6-6/13626)
> Revision: 1132
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1131] Provide more accurate documentation for installing ADL Workbench on Mac OS X , including details of the 10.6 (Snow Leopard) installer.](https://discourse.openehr.org/t/ref-impl-eiffel-1131-provide-more-accurate-documentation-for-installing-adl-workbench-on-mac-os-x-including-details-of-the-10-6-snow-leopard-installer/13625)
> Revision: 1131
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1130] Update the SConstruct for building an installer for Mac OS X 10.6 ( Snow Leopard).](https://discourse.openehr.org/t/ref-impl-eiffel-1130-update-the-sconstruct-for-building-an-installer-for-mac-os-x-10-6-snow-leopard/13623)
> Revision: 1130
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1129] AWB-167: Update our override of the . NET version of INTERNAL for EiffelStudio 6.6.](https://discourse.openehr.org/t/ref-impl-eiffel-1129-awb-167-update-our-override-of-the-net-version-of-internal-for-eiffelstudio-6-6/13622)
> Revision: 1129
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1128] Fix the ADL Parser to compile following the refactoring in revisions 1126 and 1127 .](https://discourse.openehr.org/t/ref-impl-eiffel-1128-fix-the-adl-parser-to-compile-following-the-refactoring-in-revisions-1126-and-1127/13621)
> Revision: 1128
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1127] Various renaming to establish a standardised approach to naming classes in an app framework .](https://discourse.openehr.org/t/ref-impl-eiffel-1127-various-renaming-to-establish-a-standardised-approach-to-naming-classes-in-an-app-framework/13620)
> Revision: 1127
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1126] Further directory refactoring](https://discourse.openehr.org/t/ref-impl-eiffel-1126-further-directory-refactoring/16686)
> Revision: 1126
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1125] Add back main dir under app dir](https://discourse.openehr.org/t/ref-impl-eiffel-1125-add-back-main-dir-under-app-dir/13619)
> Revision: 1125
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1124] Further re-organisation - rename main & control dirs under app directory as gui_xxx to allow a non-gui main directory as well .](https://discourse.openehr.org/t/ref-impl-eiffel-1124-further-re-organisation-rename-main-control-dirs-under-app-directory-as-gui-xxx-to-allow-a-non-gui-main-directory-as-well/13618)
> Revision: 1124
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1122] AWB-167: Update our override of the GTK version of EV_TREE_IMP for EiffelStudio 6.6 .](https://discourse.openehr.org/t/ref-impl-eiffel-1122-awb-167-update-our-override-of-the-gtk-version-of-ev-tree-imp-for-eiffelstudio-6-6/16268)
> Revision: 1122
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1121] Correct problem where if AWB is exited when minimised, it doesn' t not display on next invocation.](https://discourse.openehr.org/t/ref-impl-eiffel-1121-correct-problem-where-if-awb-is-exited-when-minimised-it-doesn-t-not-display-on-next-invocation/13616)
> Revision: 1121
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1120] Adjust how the SConstruct runs the Gobo gelex and geyacc tools:](https://discourse.openehr.org/t/ref-impl-eiffel-1120-adjust-how-the-sconstruct-runs-the-gobo-gelex-and-geyacc-tools/13615)
> Revision: 1120
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1119] Fix node map rendering problem where multiple value attributes with existence = 1 not showing up in red but pink.](https://discourse.openehr.org/t/ref-impl-eiffel-1119-fix-node-map-rendering-problem-where-multiple-value-attributes-with-existence-1-not-showing-up-in-red-but-pink/13614)
> Revision: 1119
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1118] Add profile chooser combo box on explorers.](https://discourse.openehr.org/t/ref-impl-eiffel-1118-add-profile-chooser-combo-box-on-explorers/13613)
> Revision: 1118
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1117] Correct HTML-saving bug introduced recently.](https://discourse.openehr.org/t/ref-impl-eiffel-1117-correct-html-saving-bug-introduced-recently/13609)
> Revision: 1117
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1116] Update the SCons Eiffel builder to work properly with EiffelStudio 6 .5 and higher.](https://discourse.openehr.org/t/ref-impl-eiffel-1116-update-the-scons-eiffel-builder-to-work-properly-with-eiffelstudio-6-5-and-higher/13608)
> Revision: 1116
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1115] Minor formatting fix.](https://discourse.openehr.org/t/ref-impl-eiffel-1115-minor-formatting-fix/16267)
> Revision: 1115
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1114] AWB-167: Update adl_workbench.ecf and adl_parser. ecf to work with EiffelStudio 6.6.](https://discourse.openehr.org/t/ref-impl-eiffel-1114-awb-167-update-adl-workbench-ecf-and-adl-parser-ecf-to-work-with-eiffelstudio-6-6/13607)
> Revision: 1114
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1113] Cleaned version of constants_imp ('is' removed)](https://discourse.openehr.org/t/ref-impl-eiffel-1113-cleaned-version-of-constants-imp-is-removed/13606)
> Revision: 1113
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1112] Small additions to AWB documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1112-small-additions-to-awb-documentation/13605)
> Revision: 1112
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1111] Improve the accuracy of the online help for the Mac installer.](https://discourse.openehr.org/t/ref-impl-eiffel-1111-improve-the-accuracy-of-the-online-help-for-the-mac-installer/13604)
> Revision: 1111
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [ADL 1.5 Workbench beta available](https://discourse.openehr.org/t/adl-1-5-workbench-beta-available/13610)
> It is a pleasure to announce a new beta of the ADL Workbench (AWB). This version of the tool has been greatly improved from previous versions and has many new features. It also implements most of the ADL / AOM 1.5 draft specifications, which completely replace the ADL and AOM 1.4 vintage. Note that the new specifications and tooling are backwardly compatible, so your existing archetypes are safe! Some of the new features of the tool:
- Improved validation, with code-based error messages...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1110] Missing image files for HTML help.](https://discourse.openehr.org/t/ref-impl-eiffel-1110-missing-image-files-for-html-help/16266)
> Revision: 1110
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1109] Small final corrections to HTML help.](https://discourse.openehr.org/t/ref-impl-eiffel-1109-small-final-corrections-to-html-help/13601)
> Revision: 1109
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1108] Add common nav & footer text back in since SSI not supported via SVN](https://discourse.openehr.org/t/ref-impl-eiffel-1108-add-common-nav-footer-text-back-in-since-ssi-not-supported-via-svn/13600)
> Revision: 1108
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1107] Corrected contents/footer html file; added 13606 file.](https://discourse.openehr.org/t/ref-impl-eiffel-1107-corrected-contents-footer-html-file-added-13606-file/13599)
> Revision: 1107
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1106] Update the online help with details of the Mac and Linux installers.](https://discourse.openehr.org/t/ref-impl-eiffel-1106-update-the-online-help-with-details-of-the-mac-and-linux-installers/13598)
> Revision: 1106
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1105] The SCons Eiffel builder' s scanner was not working on non-Windows platforms, because the locations of clusters and libraries in a . ecf file use backslash as the path separator.](https://discourse.openehr.org/t/ref-impl-eiffel-1105-the-scons-eiffel-builder-s-scanner-was-not-working-on-non-windows-platforms-because-the-locations-of-clusters-and-libraries-in-a-ecf-file-use-backslash-as-the-path-separator/13597)
> Revision: 1105
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1104] The link to the online help was wrong in the release notes and readme files .](https://discourse.openehr.org/t/ref-impl-eiffel-1104-the-link-to-the-online-help-was-wrong-in-the-release-notes-and-readme-files/13594)
> Revision: 1104
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1103] Test tool documentation partially complete.](https://discourse.openehr.org/t/ref-impl-eiffel-1103-test-tool-documentation-partially-complete/13593)
> Revision: 1103
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New Release of the Clinical Knowledge Manager](https://discourse.openehr.org/t/new-release-of-the-clinical-knowledge-manager/13592)
> Dear all,
we have uploaded a new release of CKM to [http://www.openehr.org/knowledge](http://www.openehr.org/knowledge)
You can find all release details at: [http://www.openehr.org/wiki/display/healthmod/CKM+release+1.1.2](http://www.openehr.org/wiki/display/healthmod/CKM+release+1.1.2)
Main changes include:
- **Termsets:** This release adds suppot for Termsets (or Teminology subset) to the resources managed by CKM. The usual CKM functionality for versioning, commenting, documenting, etc....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1102] Fix a usability problem on Windows (but not on GTK) when the user is doing a search in the archetype id combo box.](https://discourse.openehr.org/t/ref-impl-eiffel-1102-fix-a-usability-problem-on-windows-but-not-on-gtk-when-the-user-is-doing-a-search-in-the-archetype-id-combo-box/13591)
> Revision: 1102
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1101] Improve template component icons;](https://discourse.openehr.org/t/ref-impl-eiffel-1101-improve-template-component-icons/16265)
> Revision: 1101
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1100] When the user hits the key in the archetype id combo box, if there is more than one match for the archetype id pattern then drop down the combo box list to show all of the matches .](https://discourse.openehr.org/t/ref-impl-eiffel-1100-when-the-user-hits-the-enter-key-in-the-archetype-id-combo-box-if-there-is-more-than-one-match-for-the-archetype-id-pattern-then-drop-down-the-combo-box-list-to-show-all-of-the-matches/13590)
> Revision: 1100
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1099] Allow search string length to be only 3, since archetypes like 'ecg' , 'esr' etc have only 3 chars in their name anyway](https://discourse.openehr.org/t/ref-impl-eiffel-1099-allow-search-string-length-to-be-only-3-since-archetypes-like-ecg-esr-etc-have-only-3-chars-in-their-name-anyway/13589)
> Revision: 1099
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1098] AWB-167: ADL Workbench and the ADL Parser now compile in EiffelStudio 6. 6 as well as 6.4.](https://discourse.openehr.org/t/ref-impl-eiffel-1098-awb-167-adl-workbench-and-the-adl-parser-now-compile-in-eiffelstudio-6-6-as-well-as-6-4/13588)
> Revision: 1098
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1097] When the user clicks the search button, highlight the text in the archetype id combo box.](https://discourse.openehr.org/t/ref-impl-eiffel-1097-when-the-user-clicks-the-search-button-highlight-the-text-in-the-archetype-id-combo-box/13587)
> Revision: 1097
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1096] In the toolbar, shift the search button to the left, so that it' s right next to the archetype id combo box.](https://discourse.openehr.org/t/ref-impl-eiffel-1096-in-the-toolbar-shift-the-search-button-to-the-left-so-that-it-s-right-next-to-the-archetype-id-combo-box/13586)
> Revision: 1096
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1095] In adl_parser.ecf, adjust the assembly directives.](https://discourse.openehr.org/t/ref-impl-eiffel-1095-in-adl-parser-ecf-adjust-the-assembly-directives/13585)
> Revision: 1095
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1094] Simplify the ADL Parser to use just one namespace.](https://discourse.openehr.org/t/ref-impl-eiffel-1094-simplify-the-adl-parser-to-use-just-one-namespace/13584)
> Revision: 1094
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1093] ADL Workbench did not start up because it was looking for the search pixmap 's icon in a hard-coded location.](https://discourse.openehr.org/t/ref-impl-eiffel-1093-adl-workbench-did-not-start-up-because-it-was-looking-for-the-search-pixmap-s-icon-in-a-hard-coded-location/13582)
> Revision: 1093
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1092] Small fix to searching to make searches resulting in a single archetype go straight to it .](https://discourse.openehr.org/t/ref-impl-eiffel-1092-small-fix-to-searching-to-make-searches-resulting-in-a-single-archetype-go-straight-to-it/13581)
> Revision: 1092
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1091] Removed attached qualifier on ARCHETYPE_DIRECTORY. set_selected_item_from_id to deal with out of date continuous build version of Eiffel .](https://discourse.openehr.org/t/ref-impl-eiffel-1091-removed-attached-qualifier-on-archetype-directory-set-selected-item-from-id-to-deal-with-out-of-date-continuous-build-version-of-eiffel/13580)
> Revision: 1091
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1090] Clean up of old help pages.](https://discourse.openehr.org/t/ref-impl-eiffel-1090-clean-up-of-old-help-pages/13579)
> Revision: 1090
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1088] Add support link to nav menu](https://discourse.openehr.org/t/ref-impl-eiffel-1088-add-support-link-to-nav-menu/13577)
> Revision: 1088
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1087] Add a rudimentary search-by-id facility.](https://discourse.openehr.org/t/ref-impl-eiffel-1087-add-a-rudimentary-search-by-id-facility/13576)
> Revision: 1087
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[516] Archetype Validator: Add check for non-unique keys in ontology (e.g.](https://discourse.openehr.org/t/516-archetype-validator-add-check-for-non-unique-keys-in-ontology-e-g/13575)
> Revision: 516
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Occurences representation in instances](https://discourse.openehr.org/t/occurences-representation-in-instances/16689)
> In every element, cluster, slot and others in Archetype Editor there is Occurences attribute.
For my Element at0005 I set this attribute to 0..*
How will it be represented in instance of this archetype?
Blah-blah-1
Blah-blah-2
Value1
...
Revision: 1086
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1085] Correct URL in AWB help link.](https://discourse.openehr.org/t/ref-impl-eiffel-1085-correct-url-in-awb-help-link/13573)
> Revision: 1085
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1083] Add download link to index help page.](https://discourse.openehr.org/t/ref-impl-eiffel-1083-add-download-link-to-index-help-page/13571)
> Revision: 1083
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1082] Change text for slot view to 'supplier archetypes' and ' client archetypes'.](https://discourse.openehr.org/t/ref-impl-eiffel-1082-change-text-for-slot-view-to-supplier-archetypes-and-client-archetypes/13570)
> Revision: 1082
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1080] Further AWB documentation work;](https://discourse.openehr.org/t/ref-impl-eiffel-1080-further-awb-documentation-work/13567)
> Revision: 1080
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1079] On Windows, use the process library to launch the user's web browser .](https://discourse.openehr.org/t/ref-impl-eiffel-1079-on-windows-use-the-process-library-to-launch-the-users-web-browser/13566)
> Revision: 1079
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1078] Under the help menu:](https://discourse.openehr.org/t/ref-impl-eiffel-1078-under-the-help-menu/13565)
> Revision: 1078
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1077] A few cosmetic changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1077-a-few-cosmetic-changes/13564)
> Revision: 1077
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1076] AWB-69: Under the Help menu, rename "Online" to "Contents".](https://discourse.openehr.org/t/ref-impl-eiffel-1076-awb-69-under-the-help-menu-rename-online-to-contents/13563)
> Revision: 1076
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1075] Changes](https://discourse.openehr.org/t/ref-impl-eiffel-1075-changes/14707)
> Revision: 1075
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1074] Make it easier to run the ARCHETYPE_DIRECTORY unit tests by relying on the developer already having set up a repository profile for the test archetypes , rather than needing a special category in the config file.](https://discourse.openehr.org/t/ref-impl-eiffel-1074-make-it-easier-to-run-the-archetype-directory-unit-tests-by-relying-on-the-developer-already-having-set-up-a-repository-profile-for-the-test-archetypes-rather-than-needing-a-special-category-in-the-config-file/14706)
> Revision: 1074
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1073] Update to AWB documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1073-update-to-awb-documentation/13562)
> Revision: 1073
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1072] Update to AWB documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-1072-update-to-awb-documentation/13561)
> Revision: 1072
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1071] 2nd attempt to fix CSS file MIME type.](https://discourse.openehr.org/t/ref-impl-eiffel-1071-2nd-attempt-to-fix-css-file-mime-type/13560)
> Revision: 1071
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1070] Fix awb.css mime-type & other SVN properties.](https://discourse.openehr.org/t/ref-impl-eiffel-1070-fix-awb-css-mime-type-other-svn-properties/13559)
> Revision: 1070
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1069] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1069-changes/14695)
> Revision: 1069
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[514] extracted duration_pattern method and re-arranged c_duration grammar](https://discourse.openehr.org/t/514-extracted-duration-pattern-method-and-re-arranged-c-duration-grammar/13558)
> Revision: 514
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1068] Intermediate upload of AWB documentation](https://discourse.openehr.org/t/ref-impl-eiffel-1068-intermediate-upload-of-awb-documentation/13557)
> Revision: 1068
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1067] Remove an unnecessary file.](https://discourse.openehr.org/t/ref-impl-eiffel-1067-remove-an-unnecessary-file/13556)
> Revision: 1067
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1066] Fix a typo.](https://discourse.openehr.org/t/ref-impl-eiffel-1066-fix-a-typo/13555)
> Revision: 1066
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1065] revert old help page to original form for the moment while new help is being written .](https://discourse.openehr.org/t/ref-impl-eiffel-1065-revert-old-help-page-to-original-form-for-the-moment-while-new-help-is-being-written/13553)
> Revision: 1065
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1064] The Alt+Left and Alt+Right keyboard accelerators, which activate the history back and forward menu items, were not working.](https://discourse.openehr.org/t/ref-impl-eiffel-1064-the-alt-left-and-alt-right-keyboard-accelerators-which-activate-the-history-back-and-forward-menu-items-were-not-working/13552)
> Revision: 1064
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1063] When the user selects some archetypes, the Back button becomes enabled, and then clicking the Back button can enable the Forward button.](https://discourse.openehr.org/t/ref-impl-eiffel-1063-when-the-user-selects-some-archetypes-the-back-button-becomes-enabled-and-then-clicking-the-back-button-can-enable-the-forward-button/14694)
> Revision: 1063
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1062] Finalise release notes history](https://discourse.openehr.org/t/ref-impl-eiffel-1062-finalise-release-notes-history/14693)
> Revision: 1062
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1061] Upload of work to date on AWB user manual.](https://discourse.openehr.org/t/ref-impl-eiffel-1061-upload-of-work-to-date-on-awb-user-manual/13550)
> Revision: 1061
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[Re: Can openEHR help here?]](https://discourse.openehr.org/t/re-can-openehr-help-here/13549)
> Hi Derek,
I am presently working with others on research to embed a clinical
terminology amongst clinical students, practitioners and academics\.
There are synergies between this work and openEHR ontology neutral
archetypes\. Your project sounds fascinatng and I'd like to know more
about it as you progress\.
Cheers
Juanita
> Hi,
>
> I'm involved in a group that is looking at the development of
ePortfolios for students' clinical attachments\.
>
> One of the issues we are...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1060] Update the SConstruct and the NSIS installer to install release_notes.txt, which has replaced the old news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-1060-update-the-sconstruct-and-the-nsis-installer-to-install-release-notes-txt-which-has-replaced-the-old-news-txt/13548)
> Revision: 1060
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1059] Added info to release notes file](https://discourse.openehr.org/t/ref-impl-eiffel-1059-added-info-to-release-notes-file/13547)
> Revision: 1059
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1058] Fixes related to 'news' file:](https://discourse.openehr.org/t/ref-impl-eiffel-1058-fixes-related-to-news-file/13546)
> Revision: 1058
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1057] Exporting to HTML displayed strange characters in text for non-English languages .](https://discourse.openehr.org/t/ref-impl-eiffel-1057-exporting-to-html-displayed-strange-characters-in-text-for-non-english-languages/13545)
> Revision: 1057
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1056] Fix a failure of the 'attr_name_valid' precondition in DT_COMPLEX_OBJECT_NODE.remove_attribute, when called from C_DOMAIN_TYPE.synchronise_to_tree.](https://discourse.openehr.org/t/ref-impl-eiffel-1056-fix-a-failure-of-the-attr-name-valid-precondition-in-dt-complex-object-node-remove-attribute-when-called-from-c-domain-type-synchronise-to-tree/13544)
> Revision: 1056
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1055] Remove an out-of-date comment in "news.txt".](https://discourse.openehr.org/t/ref-impl-eiffel-1055-remove-an-out-of-date-comment-in-news-txt/13543)
> Revision: 1055
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1054] Move of image files to doc/web directory](https://discourse.openehr.org/t/ref-impl-eiffel-1054-move-of-image-files-to-doc-web-directory/13542)
> Revision: 1054
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1053] Add web directory prior to re-organising documentation](https://discourse.openehr.org/t/ref-impl-eiffel-1053-add-web-directory-prior-to-re-organising-documentation/13541)
> Revision: 1053
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1052] Correct sizing error which prevented status area being shrunk.](https://discourse.openehr.org/t/ref-impl-eiffel-1052-correct-sizing-error-which-prevented-status-area-being-shrunk/13538)
> Revision: 1052
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1051] Near final set of help text images.](https://discourse.openehr.org/t/ref-impl-eiffel-1051-near-final-set-of-help-text-images/13537)
> Revision: 1051
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1050] Reinstate 'diff' test, renamed to 'compare' - this does a string length and then byte-wise compare of serialised archetypes ; essentially useful for showing up existence of differences so user knows whether to bother looking at di](https://discourse.openehr.org/t/ref-impl-eiffel-1050-reinstate-diff-test-renamed-to-compare-this-does-a-string-length-and-then-byte-wise-compare-of-serialised-archetypes-essentially-useful-for-showing-up-existence-of-differences-so-user-knows-whether-to-bother-looking-at-di/13536)
> Revision: 1050
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1049] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1049-changes/13535)
> Revision: 1049
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1048] After the user closes the repository dialog, there were two problems :](https://discourse.openehr.org/t/ref-impl-eiffel-1048-after-the-user-closes-the-repository-dialog-there-were-two-problems/13534)
> Revision: 1048
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1047] The config file directory below the user' s home directory was being created as a side-effect of querying the config file path .](https://discourse.openehr.org/t/ref-impl-eiffel-1047-the-config-file-directory-below-the-user-s-home-directory-was-being-created-as-a-side-effect-of-querying-the-config-file-path/13533)
> Revision: 1047
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1046] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1046-changes/13532)
> Revision: 1046
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - ["type" attribute of DvProportion: ProportionKind or Integer??](https://discourse.openehr.org/t/type-attribute-of-dvproportion-proportionkind-or-integer/16685)
> Hi all,
I'd like to report a particular problem which is creating trouble\.\.\.
In class DvProportion: "type" attribute is defined as ProportionKind,
while in
http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf
is defined as Integer\. Also in archetype model, "type" attribute of a
C\_COMPLEX\_OBJECT of rm\-type DV\_PROPORTION is defined as...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1045] Relocate the ".status" file to the config file directory below the user's home directory, rather than writing it to the application directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1045-relocate-the-status-file-to-the-config-file-directory-below-the-users-home-directory-rather-than-writing-it-to-the-application-directory/13531)
> Revision: 1045
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1044] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1044-changes/13529)
> Revision: 1044
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1043] Revision 1039 was applied to the wrong branch.](https://discourse.openehr.org/t/ref-impl-eiffel-1043-revision-1039-was-applied-to-the-wrong-branch/13528)
> Revision: 1043
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1042] The HTML output directory was defaulting under Program Files on Windows, and to "/html" on Mac OS X.](https://discourse.openehr.org/t/ref-impl-eiffel-1042-the-html-output-directory-was-defaulting-under-program-files-on-windows-and-to-html-on-mac-os-x/13527)
> Revision: 1042
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1041] The path to the config file was not reliably generated.](https://discourse.openehr.org/t/ref-impl-eiffel-1041-the-path-to-the-config-file-was-not-reliably-generated/13525)
> Revision: 1041
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1040] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1040-changes/13524)
> Revision: 1040
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1039] The launcher script for Mac OS X used to create symbolic links from the user 's application support folder to all of files in the application directory.](https://discourse.openehr.org/t/ref-impl-eiffel-1039-the-launcher-script-for-mac-os-x-used-to-create-symbolic-links-from-the-user-s-application-support-folder-to-all-of-files-in-the-application-directory/13523)
> Revision: 1039
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1038] Use the shared instance of the execution environment, rather than creating a new object.](https://discourse.openehr.org/t/ref-impl-eiffel-1038-use-the-shared-instance-of-the-execution-environment-rather-than-creating-a-new-object/16264)
> Revision: 1038
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1037] Correct a fossilised comment.](https://discourse.openehr.org/t/ref-impl-eiffel-1037-correct-a-fossilised-comment/13522)
> Revision: 1037
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1036] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1036-changes/13521)
> Revision: 1036
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1035] Move the Statistics tab down the bottom next to the Status and Errors tab.](https://discourse.openehr.org/t/ref-impl-eiffel-1035-move-the-statistics-tab-down-the-bottom-next-to-the-status-and-errors-tab/13520)
> Revision: 1035
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [possible openEHR application?](https://discourse.openehr.org/t/possible-openehr-application/15007)
> Hi,
I'm involved in a group that is looking at the development of ePortfolios for students' clinical attachments.
One of the issues we are addressing is the cost of providing clinical assessment and feedback in the ePortfolio. Students complain that they labourously document their activities and observations on an attachment, but get very little feedback on whether the amount, quality and variety of their experience is suburb/good/bad/unacceptable for the particular attachment. However...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1034] On launching ADL Workbench for the first time, the user is asked to specify a repository profile, but once the user had done so it was not actually loaded because no RM schemas had been selected yet .](https://discourse.openehr.org/t/ref-impl-eiffel-1034-on-launching-adl-workbench-for-the-first-time-the-user-is-asked-to-specify-a-repository-profile-but-once-the-user-had-done-so-it-was-not-actually-loaded-because-no-rm-schemas-had-been-selected-yet/13519)
> Revision: 1034
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1033] Correct license text for installer.](https://discourse.openehr.org/t/ref-impl-eiffel-1033-correct-license-text-for-installer/13517)
> Revision: 1033
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1032] Make the binding statistics slightly less inefficient.](https://discourse.openehr.org/t/ref-impl-eiffel-1032-make-the-binding-statistics-slightly-less-inefficient/13516)
> Revision: 1032
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1031] Changes](https://discourse.openehr.org/t/ref-impl-eiffel-1031-changes/14655)
> Revision: 1031
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1030] AWB-110: In the Windows and Mac installers, replace the Ocean Informatics branding with openEHR, and make sure that the copyright year is 2010 and the version is 1.5.](https://discourse.openehr.org/t/ref-impl-eiffel-1030-awb-110-in-the-windows-and-mac-installers-replace-the-ocean-informatics-branding-with-openehr-and-make-sure-that-the-copyright-year-is-2010-and-the-version-is-1-5/13515)
> Revision: 1030
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1029] Fix a precondition failure that occurred if the user opened the Repository dialog and simply changed the name of the active profile .](https://discourse.openehr.org/t/ref-impl-eiffel-1029-fix-a-precondition-failure-that-occurred-if-the-user-opened-the-repository-dialog-and-simply-changed-the-name-of-the-active-profile/14654)
> Revision: 1029
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1028] Add better visual feedback for removed nodes.](https://discourse.openehr.org/t/ref-impl-eiffel-1028-add-better-visual-feedback-for-removed-nodes/13511)
> Revision: 1028
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1027] In the Repository dialog:](https://discourse.openehr.org/t/ref-impl-eiffel-1027-in-the-repository-dialog/13510)
> Revision: 1027
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1025] Fix typos.](https://discourse.openehr.org/t/ref-impl-eiffel-1025-fix-typos/16263)
> Revision: 1025
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1024] Further changes to handle the possible operations on the repository setting dialog .](https://discourse.openehr.org/t/ref-impl-eiffel-1024-further-changes-to-handle-the-possible-operations-on-the-repository-setting-dialog/13508)
> Revision: 1024
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1023] Further improvements to REPOSITORY_DIALOG functioning.](https://discourse.openehr.org/t/ref-impl-eiffel-1023-further-improvements-to-repository-dialog-functioning/16262)
> Revision: 1023
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1022] In the Repository dialog, removing the last profile now works.](https://discourse.openehr.org/t/ref-impl-eiffel-1022-in-the-repository-dialog-removing-the-last-profile-now-works/13507)
> Revision: 1022
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1021] Don't display an error if the working repository is empty.](https://discourse.openehr.org/t/ref-impl-eiffel-1021-dont-display-an-error-if-the-working-repository-is-empty/13506)
> Revision: 1021
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1020] Remove erroneous precondition on ARCH_REP_ARCHETYPE.compile_legacy, which used to protect against compiling legacy archetypes when there was a differential file available .](https://discourse.openehr.org/t/ref-impl-eiffel-1020-remove-erroneous-precondition-on-arch-rep-archetype-compile-legacy-which-used-to-protect-against-compiling-legacy-archetypes-when-there-was-a-differential-file-available/13505)
> Revision: 1020
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1019] Get removal partially working.](https://discourse.openehr.org/t/ref-impl-eiffel-1019-get-removal-partially-working/13503)
> Revision: 1019
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1018] Correct bug in REPOSITORY_DIALOG where add_new_profile would also trigger select_profile ; stop this by turning off events temporarily.](https://discourse.openehr.org/t/ref-impl-eiffel-1018-correct-bug-in-repository-dialog-where-add-new-profile-would-also-trigger-select-profile-stop-this-by-turning-off-events-temporarily/13502)
> Revision: 1018
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1017] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1017-changes/13500)
> Revision: 1017
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1016] In the Options dialog, initially set focus to the RM schemas list, since it is now the first widget in the dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-1016-in-the-options-dialog-initially-set-focus-to-the-rm-schemas-list-since-it-is-now-the-first-widget-in-the-dialog/14641)
> Revision: 1016
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1015] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1015-changes/13498)
> Revision: 1015
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[openEHR: IP, SNOMED CT, IHTSDO collaboration]](https://discourse.openehr.org/t/openehr-ip-snomed-ct-ihtsdo-collaboration/13499)
> Hi,
No feedback from the clinical list on this announcement yet\.
If you have any views please send them to me, as trying to pull together themes from related discussions\.\.
Thanks,
Tony
Dr\. Tony Shannon
Consultant in Emergency Medicine, Leeds Teaching Hospitals
Clinical Lead for Informatics, Leeds Teaching Hospitals
Chair, Clinical Review Board, openEHR Foundation
\+44\.789\.988 5068 tony\.shannon@nhs\.net
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1014] Changes (finally, a nice GUI trick!) - make the archetype tree show the currently chosen node in the template tree , in sync, so one can find things easily.](https://discourse.openehr.org/t/ref-impl-eiffel-1014-changes-finally-a-nice-gui-trick-make-the-archetype-tree-show-the-currently-chosen-node-in-the-template-tree-in-sync-so-one-can-find-things-easily/13496)
> Revision: 1014
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1013] Correct invariant for AUTHORED_RESOURCE.languages_available, and also small refactoring to use the more standard '_cache' style name for the stored version.](https://discourse.openehr.org/t/ref-impl-eiffel-1013-correct-invariant-for-authored-resource-languages-available-and-also-small-refactoring-to-use-the-more-standard-cache-style-name-for-the-stored-version/13495)
> Revision: 1013
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1012] Fix two unit tests that were failing because a precondition was failing.](https://discourse.openehr.org/t/ref-impl-eiffel-1012-fix-two-unit-tests-that-were-failing-because-a-precondition-was-failing/13494)
> Revision: 1012
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1011] TEST_DIFFERENTIAL_ARCHETYPE_ONTOLOGY was failing during instantiation because , now that we've enabled invariants, the invariants inherited from DIFFERENTIAL_ARCHETYPE were not being satisfied .](https://discourse.openehr.org/t/ref-impl-eiffel-1011-test-differential-archetype-ontology-was-failing-during-instantiation-because-now-that-weve-enabled-invariants-the-invariants-inherited-from-differential-archetype-were-not-being-satisfied/13493)
> Revision: 1011
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1010] Fixes](https://discourse.openehr.org/t/ref-impl-eiffel-1010-fixes/13492)
> Revision: 1010
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1009] Small fix to MAIN_WINDOW to ensure some reasonable first-time positions for GUI splitters .](https://discourse.openehr.org/t/ref-impl-eiffel-1009-small-fix-to-main-window-to-ensure-some-reasonable-first-time-positions-for-gui-splitters/13491)
> Revision: 1009
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1008] Refactor ARCHETYPE_ONTOLOGY.primary_language to original_language, to match the ARCHETYPE attribute from which it is set.](https://discourse.openehr.org/t/ref-impl-eiffel-1008-refactor-archetype-ontology-primary-language-to-original-language-to-match-the-archetype-attribute-from-which-it-is-set/14631)
> Revision: 1008
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - ["state" and "protocol" structures are mandatory, when defined?](https://discourse.openehr.org/t/state-and-protocol-structures-are-mandatory-when-defined/15005)
> Hi all,
I have a doubt in interpretating the archetype definition when there are
"state" or "protocol" structure\. For example, looking at "Blood
Pressure" in http://openehr.org/knowledge/, I'm wondering if "protocol"
structure is mandatory, as it seems looking at the archetype\. If I don't
know any details about the protocol, do I have to insert an empty tag
<protocol> however?
Best regards
leo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1007] Changes](https://discourse.openehr.org/t/ref-impl-eiffel-1007-changes/13486)
> Revision: 1007
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1006] Enable the Ctrl+C shortcut for the Source text box.](https://discourse.openehr.org/t/ref-impl-eiffel-1006-enable-the-ctrl-c-shortcut-for-the-source-text-box/13485)
> Revision: 1006
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1005] Correct use of adl_version for serialisation - if not set, the latest should be assumed.](https://discourse.openehr.org/t/ref-impl-eiffel-1005-correct-use-of-adl-version-for-serialisation-if-not-set-the-latest-should-be-assumed/13484)
> Revision: 1005
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1004] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-1004-changes/13483)
> Revision: 1004
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[513] Add parsing support for a mixed Pattern and Interval for a DV_DURATION.](https://discourse.openehr.org/t/513-add-parsing-support-for-a-mixed-pattern-and-interval-for-a-dv-duration/13482)
> Revision: 513
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1003] Changes in ARCHETYPE_PARSER, which is the root class for the ADL Parser DLL:](https://discourse.openehr.org/t/ref-impl-eiffel-1003-changes-in-archetype-parser-which-is-the-root-class-for-the-adl-parser-dll/13481)
> Revision: 1003
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [About parallel archetype editing](https://discourse.openehr.org/t/about-parallel-archetype-editing/15011)
> Hi Everyone!
We've regional openEHR project and now we develop archetypes for our regional repository.
My problem is: archetypes are developed by several organizations in parallel. Because of IDs of archetype nodes are coded with increment numbers like 'atxxxx' parallel editing by two or more people is impossible.
So, how parallel editing is realized in OpenEHR standart or why it is not supported?
Best regards and thank you for your answers
Igor Lizunov
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1002] In adl_workbench.ecf, enable all assertions, except for invariants in the three clusters (archetype_repository, common_libs and openehr) where the invariants of some of the classes would fail during instantiation by the deserialis](https://discourse.openehr.org/t/ref-impl-eiffel-1002-in-adl-workbench-ecf-enable-all-assertions-except-for-invariants-in-the-three-clusters-archetype-repository-common-libs-and-openehr-where-the-invariants-of-some-of-the-classes-would-fail-during-instantiation-by-the-deserialis/13480)
> Revision: 1002
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [DvDuration: Mixed Pattern and Interval not supported by ADL Parser](https://discourse.openehr.org/t/dvduration-mixed-pattern-and-interval-not-supported-by-adl-parser/13487)
> Hi Rong and all,
The ADLParser does not appear to support a mixed pattern and Interval for a DV_DURATION.
>From the ADL Specs
> `Mixed Pattern and Interval`
> `In some cases there is a need to be able to limit the allowed units as well as state a duration interval.`
> `This is common in obstetrics, where physicians want to be able to set an interval from say 0-50 weeks`
> `and limit the units to only weeks and days. This can be done as follows:`
> `PWD/|P0W..P50W| -- 0-50 weeks, expressed...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [1000] Cosmetic changes to compiler status reporting.](https://discourse.openehr.org/t/ref-impl-eiffel-1000-cosmetic-changes-to-compiler-status-reporting/14619)
> Revision: 1000
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [999] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-999-changes/16260)
> Revision: 999
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [998] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-998-changes/16259)
> Revision: 998
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [997] Fix a precondition failure caused by ARCHETYPE_DIRECTORY. initialise_ontology_prototype violating the same_rule precondition of ARRAYED_SET .merge, i.e.](https://discourse.openehr.org/t/ref-impl-eiffel-997-fix-a-precondition-failure-caused-by-archetype-directory-initialise-ontology-prototype-violating-the-same-rule-precondition-of-arrayed-set-merge-i-e/13473)
> Revision: 997
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [996] Fix a failing precondition when ARCH_REP_ARCHETYPE. add_slot_ids was changing the comparison criterion of a non-empty list.](https://discourse.openehr.org/t/ref-impl-eiffel-996-fix-a-failing-precondition-when-arch-rep-archetype-add-slot-ids-was-changing-the-comparison-criterion-of-a-non-empty-list/13472)
> Revision: 996
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [995] Remove an invariant that was failing.](https://discourse.openehr.org/t/ref-impl-eiffel-995-remove-an-invariant-that-was-failing/13471)
> Revision: 995
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [994] Add a missing postcondition to ARCH_REP_ARCHETYPE.flatten.](https://discourse.openehr.org/t/ref-impl-eiffel-994-add-a-missing-postcondition-to-arch-rep-archetype-flatten/13470)
> Revision: 994
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [993] Remove the obsolete "is" keyword.](https://discourse.openehr.org/t/ref-impl-eiffel-993-remove-the-obsolete-is-keyword/13469)
> Revision: 993
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [992] Various fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-992-various-fixes/13468)
> Revision: 992
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [991] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-991-changes/13467)
> Revision: 991
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [990] Add a unit test demonstrating a bugs in ARCHETYPE_DIRECTORY. add_adhoc_item:](https://discourse.openehr.org/t/ref-impl-eiffel-990-add-a-unit-test-demonstrating-a-bugs-in-archetype-directory-add-adhoc-item/13466)
> Revision: 990
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [987] Fix an error in the compilation state checking that was unnecessarily recompiling validated archetypes all the time .](https://discourse.openehr.org/t/ref-impl-eiffel-987-fix-an-error-in-the-compilation-state-checking-that-was-unnecessarily-recompiling-validated-archetypes-all-the-time/13460)
> Revision: 987
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [What does "Add reference" in Archetype Editor means](https://discourse.openehr.org/t/what-does-add-reference-in-archetype-editor-means/15012)
> Hi!
When right-clicking on any element in Archetype Editor there is link "Add reference" which adds a readonly element to definition.
So, what does it mean?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [proposed ADL 1.5 simplification](https://discourse.openehr.org/t/proposed-adl-1-5-simplification/15002)
> In all archetypes that I have ever seen, the 'concept' at the top of the archetype is always the at-code of the root object constraint of the archetype. It would make sense to turn this into a function, and remove this clause from archetypes & templates. In fact, the concept code is by definition the node_id of the root object. In ADL 1.5, the root object must hae a node_id, according to the following rule:
- VACCD: archetype definition code validity. The node identifier of the root node of...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR: IP, SNOMED CT, IHTSDO collaboration](https://discourse.openehr.org/t/openehr-ip-snomed-ct-ihtsdo-collaboration/13452)
> Posted on behalf of the openEHR Board
There have been recent additional suggestions posted on the openEHR
wiki in response to the consultation about future licensing
arrangements for openEHR IP, as part of the Foundation’s policy and
aim of transferring it under suitable and sustainable international
governance\. The context of this consultation was set out in the
announcement in April\.
It is timely to report that the openEHR core team and senior
representatives of IHTSDO are engaged in a...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [986] Strengthen some postconditions in C_ATTRIBUTE.](https://discourse.openehr.org/t/ref-impl-eiffel-986-strengthen-some-postconditions-in-c-attribute/13459)
> Revision: 986
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [985] Correct pre-condition of SOURCE_REPOSITORIES.set_reference_repository](https://discourse.openehr.org/t/ref-impl-eiffel-985-correct-pre-condition-of-source-repositories-set-reference-repository/13458)
> Revision: 985
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [984] Correct validation of reference repository path.](https://discourse.openehr.org/t/ref-impl-eiffel-984-correct-validation-of-reference-repository-path/13457)
> Revision: 984
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [983] Correct subtle validation error - when occurrences we redefined to same constraint (due to AE using .adl specialisations), VSONIR was being triggered, but it should have gone via the VSONCO path in the code, which in non-strict mod](https://discourse.openehr.org/t/ref-impl-eiffel-983-correct-subtle-validation-error-when-occurrences-we-redefined-to-same-constraint-due-to-ae-using-adl-specialisations-vsonir-was-being-triggered-but-it-should-have-gone-via-the-vsonco-path-in-the-code-which-in-non-strict-mod/13456)
> Revision: 983
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [982] Fix 'About' screen icon access.](https://discourse.openehr.org/t/ref-impl-eiffel-982-fix-about-screen-icon-access/13455)
> Revision: 982
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [981] Correct serialised flat output of C_ARCHETYPE_ROOTs](https://discourse.openehr.org/t/ref-impl-eiffel-981-correct-serialised-flat-output-of-c-archetype-roots/13454)
> Revision: 981
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [980] Improve path computation in template visualisation.](https://discourse.openehr.org/t/ref-impl-eiffel-980-improve-path-computation-in-template-visualisation/13453)
> Revision: 980
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [979] Added custom Template GUI tree control, this shows templates in the slot filler structure rather than the class ontology structure .](https://discourse.openehr.org/t/ref-impl-eiffel-979-added-custom-template-gui-tree-control-this-shows-templates-in-the-slot-filler-structure-rather-than-the-class-ontology-structure/13451)
> Revision: 979
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [977] Correct an error that was preventing template_component files from parsing properly , and another error that was preventing them being displayed properly in the explorer tree .](https://discourse.openehr.org/t/ref-impl-eiffel-977-correct-an-error-that-was-preventing-template-component-files-from-parsing-properly-and-another-error-that-was-preventing-them-being-displayed-properly-in-the-explorer-tree/13447)
> Revision: 977
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [976] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-976-changes/13446)
> Revision: 976
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [975] Add some missing pre- and postconditions to C_STRING.](https://discourse.openehr.org/t/ref-impl-eiffel-975-add-some-missing-pre-and-postconditions-to-c-string/13445)
> Revision: 975
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [974] Changes for the ADL Parser DLL:](https://discourse.openehr.org/t/ref-impl-eiffel-974-changes-for-the-adl-parser-dll/13444)
> Revision: 974
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [973] Correct a bug where initial compilation state of legacy file not reset properly when out of date detected .](https://discourse.openehr.org/t/ref-impl-eiffel-973-correct-a-bug-where-initial-compilation-state-of-legacy-file-not-reset-properly-when-out-of-date-detected/13443)
> Revision: 973
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [972] Various changes:](https://discourse.openehr.org/t/ref-impl-eiffel-972-various-changes/16258)
> Revision: 972
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR IP - further comments](https://discourse.openehr.org/t/openehr-ip-further-comments/16257)
> for those interested in the openEHR IP status, Martin van der Meer has posted some useful comments - see [http://www.openehr.org/wiki/display/oecom/openEHR+IP+License+Revision+Proposal?focusedCommentId=13959172#comment-13959172](http://www.openehr.org/wiki/display/oecom/openEHR+IP+License+Revision+Proposal?focusedCommentId=13959172#comment-13959172)
- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [MEDILIG - Health Information and Integration Platform ontology](https://discourse.openehr.org/t/medilig-health-information-and-integration-platform-ontology/15001)
> Dear openehr members
I have posted the following message to your lists and I received two
replies; the first saying it was rejected with no reason given and the
second gave the following reason for rejecting "Non\-members are not allowed
to post messages to this list"\.
As far as I know I am a registered user with the clinical knowledge manager
but I do not know if that entitles me to send email to your lists\. If not
can you register my email and allow this email to appear in your...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [971] Add a missing postcondition.](https://discourse.openehr.org/t/ref-impl-eiffel-971-add-a-missing-postcondition/13442)
> Revision: 971
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [970] Add postconditions and unit test assertions demonstrating that a new minimal differential archetype was created in an invalid state .](https://discourse.openehr.org/t/ref-impl-eiffel-970-add-postconditions-and-unit-test-assertions-demonstrating-that-a-new-minimal-differential-archetype-was-created-in-an-invalid-state/13441)
> Revision: 970
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [AQL query to archetype and it's specializations in slot](https://discourse.openehr.org/t/aql-query-to-archetype-and-its-specializations-in-slot/14581)
> Hi!
I have an archetype 'A' with slot named 'Slot In A'.
There is constraint for possible archetypes for this slot: "B and specializations of B".
I know that in archetype B (and in all of it's specializations) there is field 'at0003' named 'Field In B'
I know only about B and particular clients has their own independent specializations 'B-spec'.
Now I want to build a query like this:
...[openEHR-EHR-CLUSTER.a.v1] /items[openEHR-EHR-CLUSTER.b.v1] / items[at0003]/value
And I want...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [969] Correct ARCH_REP_ARCHETYPE.legacy_is_primary function.](https://discourse.openehr.org/t/ref-impl-eiffel-969-correct-arch-rep-archetype-legacy-is-primary-function/13440)
> Revision: 969
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [968] Add a unit test demonstrating a wrong postcondition when creating a new minimal differential archetype .](https://discourse.openehr.org/t/ref-impl-eiffel-968-add-a-unit-test-demonstrating-a-wrong-postcondition-when-creating-a-new-minimal-differential-archetype/13439)
> Revision: 968
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Decision Support Providers](https://discourse.openehr.org/t/decision-support-providers/14999)
> FYI\.\.
A thought provoking post from John Halamka on decision support providers as service\.
http://geekdoctor.blogspot.com/2010/06/decision-support-service-providers.html
Some of you might have complementary/alternative views as to how this might work within an openEHR enabled landscape\.\.\.
Rong
Would you like to comment?
Your recent work covered some of this key territory\.\.
Regards,
Tony
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Empty string for DV_TEXT](https://discourse.openehr.org/t/empty-string-for-dv-text/14990)
> In
http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf,
DV\_TEXT is defined as a text item\. Among "Invariants" \(page 29\), I found
that this data type is valid if it is not empty \(Value\_valid: value /=
void and then not value\.is\_empty and then not\(value\.has\(CR\) or
value\.has\(LF\)\)\)\.
Does this mean empty string is not a valid value for DV\_TEXT? If so, why
empty string cannot be a valid value? An empty string could be
meaningful, with a different...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Medinfo 2010 openEHR workshop](https://discourse.openehr.org/t/medinfo-2010-openehr-workshop/14997)
> Thanks Koray,
Been away for a bit but would be good to restart this thread\.\. as September is getting closer\.
Let me restart with a shout of hands as to how many on the list expect to be there?
Its coming time to look at flight arrangements soon\.\.
\(NB Welcome any other thoughts on workshop too\)\.\.\.
Regards,
Tony
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Modelling not-applicable fields](https://discourse.openehr.org/t/modelling-not-applicable-fields/14993)
> Hi all!
I'm modelling "Blood Circulation System Examination" archetype and it's components like "Arterial Pressure" archetype.
The arterial pressure measurement is required for every examination in my particular hospital.
So, I need to enforce constraint for this archetype from [0..*] to [1..*] in my template .
But I have counterargument for this.
Some of the hospital's patients are disabled armless people, so arterial pressure couldn't bee measured at examination. And this must became...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[512] Change null_flavor to null_flavour because of http://openehr.org/ issues/browse/SPEC-283](https://discourse.openehr.org/t/512-change-null-flavor-to-null-flavour-because-of-http-openehr-org-issues-browse-spec-283/13438)
> Revision: 512
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [966] Further corrections to Archetype mini-parse proceess according to PG' s analysis.](https://discourse.openehr.org/t/ref-impl-eiffel-966-further-corrections-to-archetype-mini-parse-proceess-according-to-pg-s-analysis/13437)
> Revision: 966
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [965] Corrections to ARCHETYPE_COMPILER and ARCH_REP_ARCHETYPE to make error messages function normally again .](https://discourse.openehr.org/t/ref-impl-eiffel-965-corrections-to-archetype-compiler-and-arch-rep-archetype-to-make-error-messages-function-normally-again/13436)
> Revision: 965
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [964] Fix a precondition failure in STRING.replace_substring_all, caused by MESSAGE_DB. create_message_content passing it a Void replacement string.](https://discourse.openehr.org/t/ref-impl-eiffel-964-fix-a-precondition-failure-in-string-replace-substring-all-caused-by-message-db-create-message-content-passing-it-a-void-replacement-string/13435)
> Revision: 964
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Java Reference Implementation - Issue reporting system](https://discourse.openehr.org/t/java-reference-implementation-issue-reporting-system/14989)
> Is there an issue reporting system \(Jira\) for Java Reference
Implementation project?
Regards
leo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [963] Fix mini-parsing problem; old-style parent ids in specialised archetypes are now detected.](https://discourse.openehr.org/t/ref-impl-eiffel-963-fix-mini-parsing-problem-old-style-parent-ids-in-specialised-archetypes-are-now-detected/16256)
> Revision: 963
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [962] Revision 956 added an override class for FORMAT_DOUBLE.](https://discourse.openehr.org/t/ref-impl-eiffel-962-revision-956-added-an-override-class-for-format-double/16255)
> Revision: 962
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [961] Fix a precondition failure when creating the parent id of a specialised archetype while populating the repository tree .](https://discourse.openehr.org/t/ref-impl-eiffel-961-fix-a-precondition-failure-when-creating-the-parent-id-of-a-specialised-archetype-while-populating-the-repository-tree/16254)
> Revision: 961
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [960] Fix a postcondition failure when flattening an archetype ontology.](https://discourse.openehr.org/t/ref-impl-eiffel-960-fix-a-postcondition-failure-when-flattening-an-archetype-ontology/13434)
> Revision: 960
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [959] Minor fixes to dependency compiler code that have no effect ( useless code in the wrong place).](https://discourse.openehr.org/t/ref-impl-eiffel-959-minor-fixes-to-dependency-compiler-code-that-have-no-effect-useless-code-in-the-wrong-place/13433)
> Revision: 959
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [958] Initial working form (not properly tested) of dependency-checking compiler changes.](https://discourse.openehr.org/t/ref-impl-eiffel-958-initial-working-form-not-properly-tested-of-dependency-checking-compiler-changes/13432)
> Revision: 958
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [957] Fix call to C_ATTRIBUTE.set_cardinality](https://discourse.openehr.org/t/ref-impl-eiffel-957-fix-call-to-c-attribute-set-cardinality/13431)
> Revision: 957
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Question about reference modelling](https://discourse.openehr.org/t/question-about-reference-modelling/14992)
> Hi!
I've a problem with openEHR archetypes modelling.
I am modelling "Patient hospitalization" usecase. So I have "Ward" archetype with different information about rooms like floor, TV existence etc. I think that instances of this archetype will be stored in Demographics servce. So, in "Patient hospitalization" archetype I need a some kind of reference to "Ward".
In addition I have some requirements for my "Patient Hospitaliation" archetype:
- I need interoperability between different...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [956] Add an override class for FORMAT_DOUBLE.](https://discourse.openehr.org/t/ref-impl-eiffel-956-add-an-override-class-for-format-double/13430)
> Revision: 956
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[511] Add HashCode and equals methods to some classes.](https://discourse.openehr.org/t/511-add-hashcode-and-equals-methods-to-some-classes/16253)
> Revision: 511
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [955] Remove useless statements in C_ATTRIBUTE (due to PG code review)](https://discourse.openehr.org/t/ref-impl-eiffel-955-remove-useless-statements-in-c-attribute-due-to-pg-code-review/13429)
> Revision: 955
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [954] Fix some compiler warnings (misnamed source files).](https://discourse.openehr.org/t/ref-impl-eiffel-954-fix-some-compiler-warnings-misnamed-source-files/13428)
> Revision: 954
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [953] The ADL Parser DLL did not compile because two attributes with the same name were inherited from different ancestors .](https://discourse.openehr.org/t/ref-impl-eiffel-953-the-adl-parser-dll-did-not-compile-because-two-attributes-with-the-same-name-were-inherited-from-different-ancestors/13427)
> Revision: 953
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [952] The ADL Parser DLL did not compile because a cluster was missing from the configuration .](https://discourse.openehr.org/t/ref-impl-eiffel-952-the-adl-parser-dll-did-not-compile-because-a-cluster-was-missing-from-the-configuration/13426)
> Revision: 952
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [951] The ADL Parser DLL did not compile because a reference to a renamed class had not been adjusted .](https://discourse.openehr.org/t/ref-impl-eiffel-951-the-adl-parser-dll-did-not-compile-because-a-reference-to-a-renamed-class-had-not-been-adjusted/13425)
> Revision: 951
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [950] Small fix to rendering of attributes in node map](https://discourse.openehr.org/t/ref-impl-eiffel-950-small-fix-to-rendering-of-attributes-in-node-map/13424)
> Revision: 950
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [949] AWB-167: EiffelStudio 6. 6 changes generating_type to be of type TYPE rather than STRING.](https://discourse.openehr.org/t/ref-impl-eiffel-949-awb-167-eiffelstudio-6-6-changes-generating-type-to-be-of-type-type-rather-than-string/13423)
> Revision: 949
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [948] Remove all cases of the obsolete "is" keyword that have crept back into the source code.](https://discourse.openehr.org/t/ref-impl-eiffel-948-remove-all-cases-of-the-obsolete-is-keyword-that-have-crept-back-into-the-source-code/13422)
> Revision: 948
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [946] Small visualisation fix for node map control.](https://discourse.openehr.org/t/ref-impl-eiffel-946-small-visualisation-fix-for-node-map-control/14553)
> Revision: 946
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 44, Issue 14](https://discourse.openehr.org/t/openehr-clinical-digest-vol-44-issue-14/13420)
> I guess you could say that in this case rubrics denote the possible set of
natural language translations of a term with a particular ID\.
OP
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [rubrics in openEHR terminology](https://discourse.openehr.org/t/rubrics-in-openehr-terminology/14991)
> Why are the terms in the openEHR terminology called rubrics? Does this word have a special meaning in the terminology world. It is commonly used to designate groups and in this case we have single terms.
Ognian Pishev
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [945] Bug fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-945-bug-fixes/13416)
> Revision: 945
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Demographics archetypes](https://discourse.openehr.org/t/demographics-archetypes/14996)
> Hi,
We have had a couple of Demographics model archetypes up for review on CKM for some time but with very little input from the community at large. This may reflect low demand for these archetypes, but there seemed to be quite a lot of interest prior to the reviews being opened. I appreciate everyone is pushed for time and it may be that the lack of comment reflects the overall high quality of the archetypes that Sergio and his colleagues have developed. Certainly we have been making use of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [944] Cosmetic change to rendering of attributes in GUI node map.](https://discourse.openehr.org/t/ref-impl-eiffel-944-cosmetic-change-to-rendering-of-attributes-in-gui-node-map/13415)
> Revision: 944
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [943] Various bug fixes](https://discourse.openehr.org/t/ref-impl-eiffel-943-various-bug-fixes/13414)
> Revision: 943
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [942] Correct errors:](https://discourse.openehr.org/t/ref-impl-eiffel-942-correct-errors/13413)
> Revision: 942
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [941] Correct an error that prevents templates from safely being displayable, due to the fact that they have multiple levels of specialisation in them, and cannot sensibly be 'rolled-up' in the GUI node control.](https://discourse.openehr.org/t/ref-impl-eiffel-941-correct-an-error-that-prevents-templates-from-safely-being-displayable-due-to-the-fact-that-they-have-multiple-levels-of-specialisation-in-them-and-cannot-sensibly-be-rolled-up-in-the-gui-node-control/13412)
> Revision: 941
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [940] Correct a bug in the message reporting system.](https://discourse.openehr.org/t/ref-impl-eiffel-940-correct-a-bug-in-the-message-reporting-system/16252)
> Revision: 940
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [939] Fix some subtle bugs in code and path related routines; Added new test cases to make sure they work.](https://discourse.openehr.org/t/ref-impl-eiffel-939-fix-some-subtle-bugs-in-code-and-path-related-routines-added-new-test-cases-to-make-sure-they-work/16251)
> Revision: 939
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [938] Changes:](https://discourse.openehr.org/t/ref-impl-eiffel-938-changes/16250)
> Revision: 938
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [937] Bugs:](https://discourse.openehr.org/t/ref-impl-eiffel-937-bugs/14542)
> Revision: 937
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Message from the Board - openEHR Intellectual Property](https://discourse.openehr.org/t/message-from-the-board-openehr-intellectual-property/14998)
> Posted on behalf of Professor David Ingram, chair of the board of the
openEHR Foundation:
Since initiating the consultation on the principles governing present
and future licensing of openEHR IP \(see wiki page
http://www.openehr.org/wiki/display/oecom/openEHR+IP+License+Revision+Proposal),
we have had positive responses, expressed on a personal basis\. As the
Board needs to begin to act on these proposals, from the end of June,
this is a request to hear from anyone in the community who may...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [936] Remove all cases of the obsolete "is" keyword that have crept back into the source code.](https://discourse.openehr.org/t/ref-impl-eiffel-936-remove-all-cases-of-the-obsolete-is-keyword-that-have-crept-back-into-the-source-code/14541)
> Revision: 936
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [935] Correct text of link in ADL workbench help page.](https://discourse.openehr.org/t/ref-impl-eiffel-935-correct-text-of-link-in-adl-workbench-help-page/16249)
> Revision: 935
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [934] Add referenced archetype index to ARCH_REP_ARCHETYPE;](https://discourse.openehr.org/t/ref-impl-eiffel-934-add-referenced-archetype-index-to-arch-rep-archetype/13411)
> Revision: 934
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [933] Corrected small bug to do with VCATU error checking in CADL parser, where it was testing if an attribute already existed under an object by name (e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-933-corrected-small-bug-to-do-with-vcatu-error-checking-in-cadl-parser-where-it-was-testing-if-an-attribute-already-existed-under-an-object-by-name-e-g/13410)
> Revision: 933
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [932] Interim commit on C_ARCHETYPE_ROOT semantics; basic validation seems ok; flattening next.](https://discourse.openehr.org/t/ref-impl-eiffel-932-interim-commit-on-c-archetype-root-semantics-basic-validation-seems-ok-flattening-next/13406)
> Revision: 932
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [931] Correct some GUI bugs; make C_ARCHETYPE_ROT display properly.](https://discourse.openehr.org/t/ref-impl-eiffel-931-correct-some-gui-bugs-make-c-archetype-rot-display-properly/13405)
> Revision: 931
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [930] Further refactoring; templates now working in a basic form in their own explorer.](https://discourse.openehr.org/t/ref-impl-eiffel-930-further-refactoring-templates-now-working-in-a-basic-form-in-their-own-explorer/13404)
> Revision: 930
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 - relaxing a conformance rule - feedback sought](https://discourse.openehr.org/t/adl-1-5-relaxing-a-conformance-rule-feedback-sought/14988)
> I am in the middle of ADL/AOM 1.5 testing. There is a validity rule I defined in the current draft specficatich reads as fllows:
VSONIR: specialised archetype object node redefinition: if it exists, the node identifier of an object node in a specialised archetype must be redefined into its specialised form if either reference model type or occurrences of the immediate object constraint is redefined.
Translation: change of occurrences or change of RM type (e.g. redefine into descendant type)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specialisation of archetype - Some doubts](https://discourse.openehr.org/t/specialisation-of-archetype-some-doubts/14995)
> When we specialize an archetype, we must keep in mind some rules as:
\- a specialised archetype can only further narrow existing constraints
in the parent \(but it may add its own\)
\- constraints are inherited, and can be overridden
\- overrides are “covariant”, i\.e\. the constraints are narrower than the
parent, also can be thought of as “subsumed”
\- new constraints can be added where allowed by the parent archetype and
reference model
Using Archetype Editor I noted some strange...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [929] Add RM schema configuration and associated functionality to options dialog .](https://discourse.openehr.org/t/ref-impl-eiffel-929-add-rm-schema-configuration-and-associated-functionality-to-options-dialog/13403)
> Revision: 929
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [928] Basic functionality to separate out archetypes and templates found in reference and work repositories , into two explorer controls.](https://discourse.openehr.org/t/ref-impl-eiffel-928-basic-functionality-to-separate-out-archetypes-and-templates-found-in-reference-and-work-repositories-into-two-explorer-controls/13402)
> Revision: 928
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [927] Handle missing meta-data in RM schema files](https://discourse.openehr.org/t/ref-impl-eiffel-927-handle-missing-meta-data-in-rm-schema-files/13401)
> Revision: 927
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [926] Further refactoring to ensure safe and correct references to the reference model schemas are used throughout the application .](https://discourse.openehr.org/t/ref-impl-eiffel-926-further-refactoring-to-ensure-safe-and-correct-references-to-the-reference-model-schemas-are-used-throughout-the-application/14527)
> Revision: 926
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Governance of terminology lists](https://discourse.openehr.org/t/governance-of-terminology-lists/13393)
> In a separate thread Koray suggested:
"... do you think it would also be a good time to discuss the cases where some custom defined/non included units need to be added for some properties in DV_QUANTITY. You may remember our discussions around 'French' as Gauge unit - which is not allowed currently. Although this may safely be added to terminology I think many more will follow when people really get into niche highly structured clinical modelling."
which raises a more general issue of...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL test archetypes - proposal to correct ids](https://discourse.openehr.org/t/adl-test-archetypes-proposal-to-correct-ids/16682)
> all,
I am working on the ADL 1\.5 implementation, and as part of this, I need
to regularise the test archetypes at
http://www.openehr.org/svn/knowledge/archetypes/dev/adl/test
These currently have ids that don't obey the rules, e\.g\. ids like
adl\-test\-SOME\_TYPE\.generic\_type\_use\_node\.v1 which should be
openehr\-adltest\-SOME\_TYPE\. The schema at
http://www.openehr.org/svn/ref_impl_eiffel/BRANCHES/specialisation/apps/adl_workbench/app/rm_schemas/openehr_adltest_100.dadl
will...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [925] Make RM visibility controls more consistent](https://discourse.openehr.org/t/ref-impl-eiffel-925-make-rm-visibility-controls-more-consistent/13398)
> Revision: 925
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [924] Correct minor error in UI where terminology tab was at wrong level.](https://discourse.openehr.org/t/ref-impl-eiffel-924-correct-minor-error-in-ui-where-terminology-tab-was-at-wrong-level/16248)
> Revision: 924
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [923] Further refactoring.](https://discourse.openehr.org/t/ref-impl-eiffel-923-further-refactoring/16247)
> Revision: 923
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [922] Various minor refactoring changes](https://discourse.openehr.org/t/ref-impl-eiffel-922-various-minor-refactoring-changes/13397)
> Revision: 922
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [921] Added dADL mini-parser, in preparation for adding schema manager, which will use meta-data from tops of schemas to display to user.](https://discourse.openehr.org/t/ref-impl-eiffel-921-added-dadl-mini-parser-in-preparation-for-adding-schema-manager-which-will-use-meta-data-from-tops-of-schemas-to-display-to-user/13396)
> Revision: 921
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [920] Various minor refactorings to support schema management](https://discourse.openehr.org/t/ref-impl-eiffel-920-various-minor-refactorings-to-support-schema-management/13395)
> Revision: 920
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [919] Experimental RM class visualiser - click on a class in explorer; if node map control is visible, it will display.](https://discourse.openehr.org/t/ref-impl-eiffel-919-experimental-rm-class-visualiser-click-on-a-class-in-explorer-if-node-map-control-is-visible-it-will-display/13392)
> Revision: 919
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [1 Ref_impl_eiffel moderator request(s) waiting](https://discourse.openehr.org/t/1-ref-impl-eiffel-moderator-request-s-waiting/13399)
> The Ref\_impl\_eiffel@openehr\.org mailing list has 1 request\(s\) waiting
for your consideration at:
http://lists.chime.ucl.ac.uk/mailman/admindb/ref_impl_eiffel
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending posts:
Cause: Message body is too big: 67147 bytes with a limit of 40 KB
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [918] Continued refactoring](https://discourse.openehr.org/t/ref-impl-eiffel-918-continued-refactoring/13391)
> Revision: 918
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [915] Various small usability improvements relating to the navigator pane.](https://discourse.openehr.org/t/ref-impl-eiffel-915-various-small-usability-improvements-relating-to-the-navigator-pane/13388)
> Revision: 915
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [914] Further small GUI correction](https://discourse.openehr.org/t/ref-impl-eiffel-914-further-small-gui-correction/13387)
> Revision: 914
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [913] Correct minor GUI error](https://discourse.openehr.org/t/ref-impl-eiffel-913-correct-minor-gui-error/13386)
> Revision: 913
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [912] Changed GUI so that terminology is in a different notebook tab.](https://discourse.openehr.org/t/ref-impl-eiffel-912-changed-gui-so-that-terminology-is-in-a-different-notebook-tab/13385)
> Revision: 912
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [911] Small corrections to do with meta-model.](https://discourse.openehr.org/t/ref-impl-eiffel-911-small-corrections-to-do-with-meta-model/13384)
> Revision: 911
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [909] Small corrections to do with HTML export; this is still causing an exception on openEHR-DEMOGRAPHIC-CLUSTER. identifier_other_details.v1](https://discourse.openehr.org/t/ref-impl-eiffel-909-small-corrections-to-do-with-html-export-this-is-still-causing-an-exception-on-openehr-demographic-cluster-identifier-other-details-v1/13382)
> Revision: 909
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [908] Rewrite of archetype class hierarchy, completely derived from RM structure.](https://discourse.openehr.org/t/ref-impl-eiffel-908-rewrite-of-archetype-class-hierarchy-completely-derived-from-rm-structure/13379)
> Revision: 908
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [907] Add C_ARCHETYPE_ROOT to model, remove ARCHETYPE_EXTERNAL_REF.](https://discourse.openehr.org/t/ref-impl-eiffel-907-add-c-archetype-root-to-model-remove-archetype-external-ref/13378)
> Revision: 907
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [906] Last state of old-style template model, before abandoning ---------------](https://discourse.openehr.org/t/ref-impl-eiffel-906-last-state-of-old-style-template-model-before-abandoning/13377)
> Revision: 906
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [904] properties updated for mime type and svn keywords](https://discourse.openehr.org/t/ref-impl-eiffel-904-properties-updated-for-mime-type-and-svn-keywords/13376)
> Revision: 904
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [903] EDT-592: In TAGS/Aug2007, fix the parsing of ISM_TRANSITION. careflow_step.existence, which was being set to 1..1 ( the default value for existence).](https://discourse.openehr.org/t/ref-impl-eiffel-903-edt-592-in-tags-aug2007-fix-the-parsing-of-ism-transition-careflow-step-existence-which-was-being-set-to-1-1-the-default-value-for-existence/13375)
> Revision: 903
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [902] Progressive update to template implementation](https://discourse.openehr.org/t/ref-impl-eiffel-902-progressive-update-to-template-implementation/13374)
> Revision: 902
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [901] checkpoint commit](https://discourse.openehr.org/t/ref-impl-eiffel-901-checkpoint-commit/13373)
> Revision: 901
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AMIA standards news source](https://discourse.openehr.org/t/amia-standards-news-source/14981)
> A new and useful resource relating to standards.....AMIA is now publishing a twice yearly newsletter as a resource of news from various SDOs. Dipak Kalra is the principal editor, and the first issue was published this weekend.
```
[https://www.amia.org/standards-standard-letter-from-the-editor](https://www.amia.org/standards-standard-letter-from-the-editor)
- thomas beale
```
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CR for openEHR RM - Clusters and Data structures](https://discourse.openehr.org/t/cr-for-openehr-rm-clusters-and-data-structures/13372)
> Dear All
As an involved clinician I have been thinking about advantages of using inheritance to relate DATA_STRUCTURES and CLUSTER. This arises from two things we have learned in clinical modelling:
1) At almost every point where a DATA_STRUCTURE is currently specified in the RM it would probably be inappropriate to model any structure other than a ITEM_TREE. This is because any change to this will invalidate existing data and we have learned that information models get more complex with...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Disjoint Merge algorithm](https://discourse.openehr.org/t/disjoint-merge-algorithm/13371)
> Hi,
I'd be very grateful if you could help me about a question connected to "Disjoint Merge" (section 6.4.3 of CommonIM - [http://www.openehr.org/releases/1.0.2/architecture/rm/common_im.pdf](http://www.openehr.org/releases/1.0.2/architecture/rm/common_im.pdf)).
In its third step the merge procedure states to "set the data in the new trunk Version to be a copy of the data from the most recent trunk Version from the source container".
What should I do if the most recent trunk Version from...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes and XML-Schemas](https://discourse.openehr.org/t/archetypes-and-xml-schemas/14980)
> XMLSerializer\.output\(\) \(xml\-serializer\-1\.0\.1\.jar\) produce XMLs that are
not compliant with openEHR XML\-Schemas
\(http://www.openehr.org/releases/1.0.2/its/XML-schema/index.html).
Also the xml representation taken from http://openehr.org/knowledge/ are
not valid XML instances respect to these schemas \(for...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Medinfo 2010 openEHR tutorial collision](https://discourse.openehr.org/t/medinfo-2010-openehr-tutorial-collision/14984)
> Hi\!
The recently published preliminary Medinfo 2010 programme at\.\.\.
http://www.medinfo2010.org/docs/Draft_Conference_Programme.pdf
\.\.\.lists two openEHR tutorials in parallel\.\.\.
1\. OpenEHR I \- IV \(Saturday 11 September 9:00\-17:00\)
2\. EHR implementation tips I\-II \(Saturday 11 September 9:00\-12:30\)
If I understand the content of the tutorials correctly, these are
renamed versions of the ones mentioned...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Ref_impl_Java mailing list archives](https://discourse.openehr.org/t/ref-impl-java-mailing-list-archives/16246)
> Hi Sebastian,
You've probably been playing around with the adl\.jj file\. Technically,
the solution could look something like this:
ArchetypeTerm archetype\_term\(\) :
\{
Token t;
String code;
String key;
String value = null;
ArchetypeTerm term;
\}
\{
"\["
code = local\_code\_value\(\)
\{ term = new ArchetypeTerm\(code\); \}
"\]" <SYM\_EQ> "<"
\(
<SYM\_TEXT> <SYM\_EQ> "<"
value = string\_value\(\) \{...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [uncommon keys in ArchetypeTerm](https://discourse.openehr.org/t/uncommon-keys-in-archetypeterm/16245)
> Hi all,
The current Java parser does not support keys other than text, description and comment for an archetype term in the ontology.
The specs do allow any key here (although they don't really talk about what kind of characters are supported in such a key as far as I can tell)
I.e. the following example would fail to parse:
`ontology`
`[...]`
`term_definitions = <`
`["en"] = <`
`items = <`
`["at0000"] = <`
`text = <"test">;`
`description = <"test">`
`**anotherkey = <"another key...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [IHTSDO meeting - term binding presentation available](https://discourse.openehr.org/t/ihtsdo-meeting-term-binding-presentation-available/14985)
> I attended the IHTSDO meeting just finished in Copenhagen. Things look pretty good for where SNOMED CT is going generally - the RF2 technical infrastructure seems relatively well designed. There is a lot of activity in content modeling, the IHTSDO workbench and many other areas relevant to openEHR. Converely, I believe openEHR will be very important to make SNOMED CT work in many places, since it will be via archetypes, templates and associated ref sets that information systems will be able...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Implementing an OpenEHR repositorium](https://discourse.openehr.org/t/implementing-an-openehr-repositorium/16244)
> Hi,
I'm trying to implement an OpenEHR repository can you point me some
tutorials or howtos, or projects where this is already developed\.
Thank you, best regards,
Tiago Pedrosa
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Cant build the project completely..](https://discourse.openehr.org/t/cant-build-the-project-completely/16684)
> Hi,
I had freshly imported the source files from ref_impl_java and did all required settings for maven. I am using eclipse as development tool.
But when I do clean build , I get a compile time error, "ADLParser cannot be resolved to a type".
After visiting the page for Jar download, It seems that in the adlparser. jar the ADLparser.class is there but it's not provided in the Trunk.
Can I gate all the required files for clean building the project... Also if not what all settings i have to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New Release of Clinical Knowledge Manager online](https://discourse.openehr.org/t/new-release-of-clinical-knowledge-manager-online/13370)
> Dear all,
We have deployed a new release of CKM to [http://www.openehr.og/knowledge](http://www.openehr.og/knowledge)
Some of the main additions are:
- **Terminology Reviews**: This release features a new type of review: Terminology reviews. Terminology editors can now use CKM to initiate reviews of the terminology bindings of an archetype.
- **Snomed CT and LOINC term display:** For any Snomed CT and LOINC codes in an archetype, the (fully specified) term is being displayed (instead of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [??? DV_CODEDQUANTITY](https://discourse.openehr.org/t/dv-codedquantity/14979)
> Assessment scales provide a rich seam of frustration for developers, with their seemingly limitless capacity for arbitrary scales and quantities.
Here is a current example about which I have been asked for advice - the Borgscale ([http://www.ac6v.com/karlaz2.htm](http://www.ac6v.com/karlaz2.htm)).
It is a scale from 0-10, so would be ideal to express as a DV_ORDINAL but includes 0.5 which makes this impossible.
There are a number of workarounds but is there a case for adding some form of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISO 18308 Conformance Statement](https://discourse.openehr.org/t/iso-18308-conformance-statement/13380)
> Dear all,
My name is Alberto Moreno from the University Hospitals Virgen del Rocio in Spain. In the *ISO 18308 Conformance Statement document*, the OpenEHR architecture is mapped against the EHR requirements identified in the 18308 standard. At the end of the document there is a list with the identified exceptions that don't satisfy the requirement. Some hese exceptiions may have only partial conformance, are going ot be incorporated in the future or remain as "to be done" tasks. In contrast...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [VS: test](https://discourse.openehr.org/t/vs-test/16242)
> Hi Thomas\.
Was it possible to change my mailing list old email address
<mailto:jaana.junttila@pp.inet.fi> jaana\.junttila@pp\.inet\.fi to my
University address jaana\.junttila@uta\.fi \(University of Tampere in Finland\)?
Or if I have to unsubscribe and then subscribe again what is the address for
subscribe? It´s so many years ago I subscribed into it
Best Records
Jaana Junttila
jaana\.junttila@uta\.fi
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Board announcement - openEHR IP License Revision Proposal](https://discourse.openehr.org/t/board-announcement-openehr-ip-license-revision-proposal/13356)
> A message from the board of the *open*EHR Foundation.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Referencing terminology in written literature - a linguistic convention](https://discourse.openehr.org/t/referencing-terminology-in-written-literature-a-linguistic-convention/16243)
> This is just a small thing, but at the moment there is as far as I know no published convention in IHTSDO or elsewhere for the lingustic referencing of coded terms in literature, including specifications and academic papers. To see what I mean, see [http://www.openehr.org/wiki/display/term/Proposal+for+linguistic+convention+for+referencing+coded+terms](http://www.openehr.org/wiki/display/term/Proposal+for+linguistic+convention+for+referencing+coded+terms)
Ed Cheetham at CFH pointed out the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to express multiple composers for a composition with an history of events](https://discourse.openehr.org/t/how-to-express-multiple-composers-for-a-composition-with-an-history-of-events/14977)
> Hi everybody,
looking at Apgar score \(openEHR\-EHR\-OBSERVATION\.apgar\.v1\) and Barthel
Index \(openEHR\-EHR\-OBSERVATION\.barthel\.v1\) archetypes in CKM
\(http://openehr.org/knowledge/), I undestand we can have several "event"
samples of this data within the same HISTORY structure\. So the same
Barthel Index composition could contain several samples taken during an
inpatient encounter\.
But in this way, how can we indicate that different sample are be taken
by different...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Re NEJM article: Can Electronic Clinical Documentation Help?](https://discourse.openehr.org/t/re-nejm-article-can-electronic-clinical-documentation-help/14978)
> For your interest\.\.\.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [pom BUILD ERROR scm:update-subprojects](https://discourse.openehr.org/t/pom-build-error-scm-update-subprojects/16238)
> Hi,
for the command
mvn scm:update-subprojects
I got a BUILD ERROR. I've added the lines below to the root pom and everything works fine after...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [a-path and values](https://discourse.openehr.org/t/a-path-and-values/16240)
> Hi there,
I'm trying to save and load archetype data for a sample observation which includes boolean and quantity as well.
.............
String cellDifferentiation = "/data[at0001]/events[at0002]/data[at0003]/items[at0006]/items[at0069]/value";
String ana = "/data[at0001]/events[at0002]/data[at0003]/items[at0006]/items[at0063]/value/value";
String ra =...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Implementation error?](https://discourse.openehr.org/t/implementation-error/14975)
> Dear Rong,
In Locatable class constructor, "links" *must not be null or empty*, otherwise error will be triggered.
if (links != null && links.isEmpty()) {
throw new IllegalArgumentException("empty links");
}
However, in Locatable subclasses such as Party, Actor, Person, etc., "links" can be *null if not specified.*
It is also stated in the specification that links will have the optionality of "0...1".
Is it an error or is intended?
Cheers,
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype was adopted for intractable disease surveillance](https://discourse.openehr.org/t/archetype-was-adopted-for-intractable-disease-surveillance/14974)
> Japan has intractable disease \(so called 'nanbyo' in Japanese\) surveillance
and subsidy program\. Intractable disease is defined as rare and chronically
progressive diseases, which cause patients disability and social and
financial burden\. eg\. Systemic lupus erythematosus, dermatomyositis,
myasthenia gravis, ulcerative colitis and so on\.
To get more outcome from this program, data repository will be reconstructed
with archetype technology\. We are now modeling the clinical...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Concerning the attribute CARE_ENTRY.protocol](https://discourse.openehr.org/t/concerning-the-attribute-care-entry-protocol/14474)
> Dear Everyone,
in quite some archetypes the optional attribute protocol of the CARE_ENTRY class is made mandatory (occurrence is 1..1) although the underlying ITEM_STRUCTURE may contain zero items (cardinality is 0..* e.g. in the inevitable BP archetype). What is the rationale for this mandatoriness and is it possible to relax this occurrence constraint in the relevant archetypes?
Regards,
Daniel
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Warning: old MERGED_VERSION class still in UML... + versioning question](https://discourse.openehr.org/t/warning-old-merged-version-class-still-in-uml-versioning-question/16683)
> Hi\!
I just wanted to warn people using UML linked or derived from\.\.\.
http://www.openehr.org/releases/1.0.2/architecture/computable/UML/uml.html
\.\.\.that the old class MERGED\_VERSION class still in UML files although
it has been removed from the specification documents \(and VERSION plus
subclasses are a bit different\)
The problem includes UML\-generation described at
http://www.openehr.org/wiki/display/dev/Experimental+generation+of+code+and+documentation+from+UML
\(same as tiny...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [opereffa wrappers](https://discourse.openehr.org/t/opereffa-wrappers/16236)
> Hi there,
Does anyone know if there exist any documentation for opereffa framework? The only thing I could find was the short tutorial on the website
Regards
Pariya
MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of Technology
[http://www.chalmers.se/cse/EN/people/kashfi-hajar](http://www.chalmers.se/cse/EN/people/kashfi-hajar)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SNOMED CT RF2 & ref sets - UML and meta-data diagrams](https://discourse.openehr.org/t/snomed-ct-rf2-ref-sets-uml-and-meta-data-diagrams/14976)
> As part of reviewing SNOMED CT Release Format 2 (RF2) and Reference Sets specifications, I have created some diagrams which are available here: [http://www.openehr.org/wiki/pages/viewpageattachments.action?pageId=10387459](http://www.openehr.org/wiki/pages/viewpageattachments.action?pageId=10387459)
So far I have a class diagram, and semantic net diagrams of the SNOMED meta-data hierarchy. The latter is really a meta-model hierarchy, used to define the model of other parts of Snomed.
I am...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL - grammar diagrams](https://discourse.openehr.org/t/aql-grammar-diagrams/16237)
> Mikael Nyström at Linköping has done some nice work on generating diagrams from the AQL grammar. I would expect this to be useful in helping us review and refine the grammar. See [http://www.openehr.org/wiki/display/spec/Archetype+Query+Language+Grammar](http://www.openehr.org/wiki/display/spec/Archetype+Query+Language+Grammar) ; this includes a link to tools and methods for performing this transformation.
- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templates and visualization](https://discourse.openehr.org/t/templates-and-visualization/14969)
> Dear all,
I understand that templates are only local constrains that are useful in our local implementation to display the information, but how would be the best way to display on a screen the information that we have received in an EHR_EXTRACT, if we don't have a template to show the information that comes within the archetype structure?
Kind Regards
Alberto
**Alberto Moreno Conde**
GIT-Grupo de Innovación Tecnológica
Hospitales Universitarios Virgen del Rocío
Edif. Centro de...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Term bindings in archetypes and templates](https://discourse.openehr.org/t/term-bindings-in-archetypes-and-templates/14966)
> Hi Rong \(All\),
\(I hope that this is the right mailing list\)
I am part of an Irish project called EHRland which is looking at
two\-level models for e\-health and trying to understand the openEHR
architecture as well\. I myself am looking at correspondences between
archetype nodes and clinical terms\. However I encountered some problems
when parsing the ADL files which I took from the openEHR svn repository
using the Java ADL parser\. The errors messages indicate that they are
caused by...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Google Summer of Code - Deadline March 12 (Now Accepting Applications from Mentoring Organizations)](https://discourse.openehr.org/t/google-summer-of-code-deadline-march-12-now-accepting-applications-from-mentoring-organizations/16233)
> Hi\!
I just wanted to remind the openEHR community that mentoring
organization applications for Google Summer of Code must be submitted
by Friday, March 12, 2010 at 23:00 UTC
I added a 2010 child page to\.\.\.
http://www.openehr.org/wiki/display/dev/Google-Summer-of-Code
\.\.\.in case anybody wants to present or coordinate openEHR related
project ideas\. \(Have a look at 2008 & 2009 if you need some
inspiration\.\)
Best regards,
Erik Sundvall
erik\.sundvall@liu\.se...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Concepts for Problems, Issues, Diagnoses etc.](https://discourse.openehr.org/t/concepts-for-problems-issues-diagnoses-etc/14968)
> On reviewing the very helpful comments on the existing Clinical
Knowledge Manager \(CKM\) Problem and Problem\-diagnosis archetypes, it
is clear that we need to resolve some concept definitions in this
difficult area, before we move on to the even more heated question of
how to name these concepts\.
As a start point, we have tried to tease out the various 'evaluative'
elements of a patient encounter and in problem\-orientated health
issue/concern threads and have posted an entry to...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [CKM update and call for more Demographic archetype reviewers](https://discourse.openehr.org/t/ckm-update-and-call-for-more-demographic-archetype-reviewers/16234)
> Dear colleagues,
Definitely time for another an update on CKM activity.
**Users**: [http://bit.ly/4f4QGg](http://bit.ly/4f4QGg)
Registered users: 457 from 56 countries
Reviewers: 153 from 36 countries
Translators: 56
**Archetypes:**
221 draft archetypes
17 in Team Review
8 Published
**EHR archetype reviews:**
> Don't underestimate the significance of agreeing the Top 10 - effectively they are probably the most difficult archetypes that we will ever have to work on, with many opinions,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Should ATTESTATION.reason datatype really be DV_TEXT or rather DV_CODED_TEXT (or perhaps CODE_PHRASE)?](https://discourse.openehr.org/t/should-attestation-reason-datatype-really-be-dv-text-or-rather-dv-coded-text-or-perhaps-code-phrase/14964)
> Hi\!
Here comes yet another possibly stupid question\.\.\.
Do we ever want the attribute ATTESTATION\.reason to be a DV\_TEXT
instead of a DV\_CODED\_TEXT?
Is this a possible improvement for the specification \(common IM rev
2\.1\.1 from release 1\.0\.2\) or is there an intention behind being that
liberal?
The spec says the value for ATTESTATION\.reason should come from the
terminology group "attestation reason"\.
A less important sidetrack:
Is the use of the more verbose...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [enumerated types in openEHR](https://discourse.openehr.org/t/enumerated-types-in-openehr/16681)
> **While reviewing the AOM spec, I realised that the enumerated type VALIDITY_KIND contains the constants 'optional', 'mandatory', 'disallowed'. The new class I have added ARTEFACT_TYPE contains constants 'archetype', 'template' etc. I realised that in typical implementations, certainly the ADL parser I maintain, such constant names are likely to be problematic, and probably should be adjusted in some way. In the kind of code I normally write, this would mean for teh VALIDITY_KIND ones -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest ADL / AOM 1.5 & template specification drafts](https://discourse.openehr.org/t/latest-adl-aom-1-5-template-specification-drafts/14965)
> I have uploaded the latest drafts of the archetype and template
specifications\. The page at
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
gives a summary of all changes, as well as the links to the
specification drafts\. I am hoping to have an upgraded version of the ADL
workbench in the coming weeks demonstrating the full template semantics
described in these documents\.
The main aim of this work has been to integrate emerging new...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype implementation for scheduling and financial information](https://discourse.openehr.org/t/archetype-implementation-for-scheduling-and-financial-information/14962)
> Dear all,
My name is Jesus Hernández .I'm trying to develop a template based in archetypes for a patient referral from our specialist in our hospital to a dialysis hospital. Although the patient would be treated in the dialysis hospital, we will continue taken care of him therefore we need to share information between both hospitals. The dialysis sessions are scheduled in the dialysis hospital, these sessions will keep ongoing maybe for years in the dialysis hospital but every month they...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template and Schema for the ASTM Continuity of Care Record (CCR) and HL7 CCD](https://discourse.openehr.org/t/template-and-schema-for-the-astm-continuity-of-care-record-ccr-and-hl7-ccd/14967)
> Dear all,
In the openEHR Specifications Strategic Directions for 2008 there was
the creation of templates and schemas for the Continuity of Care
Record \(CCR\) and HL7 CCD\. In what stage is this project and where can
I find more information about?
Kind Regards
Alberto
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ECG archetype ready for CKM review](https://discourse.openehr.org/t/ecg-archetype-ready-for-ckm-review/16231)
> Dear Colleagues,
The ECG archetype is ready to start a Team Review in CKM, likely to be initiated during the next couple of days.
If you would like to participate, please log in to CKM - [www.openEHR.org/knowledge](http://www.openEHR.org/knowledge) - and 'Adopt' the "ECG recording - 12 lead standard" archetype. At initiation of the Review round all adoptors will be included as part of the review team and be sent instructions on how to participate. Instructions for adopting an...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medinfo 2010 interim report](https://discourse.openehr.org/t/medinfo-2010-interim-report/16235)
> Dear colleagus,
As I notified to the related authours, our proposal for "The openEHR
developers' workshop' has been accepted but scientific demo "Archeytpe
connectathon" has NOT been accepted\.
The workshop will be accomodated in 90 minutes\. We should have
presentations including connectathon within 90 minutes\.
Best regards,
Shinji
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Clarified semantics of CONTRIBUTION.audit.change_type](https://discourse.openehr.org/t/clarified-semantics-of-contribution-audit-change-type/16232)
> Hi\!
I just want to share a \(to me\) clarifying implementation discussion to
the list so that it does not get lost in cyberspace :\-\)
I wondered if e\.g\. the contribution 1 in fig 25 on
http://www.openehr.org/releases/1.0.2/html/architecture/overview/Output/versioning.html#1126708
really was possible to record as single contribution or if it needed
two contributions \(with identical timestamps\) but different
AUDIT\_DETAILS\.change\_type \(one for creation and one for modification\)\.
I...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Setting up a common publication/resource library for openEHR](https://discourse.openehr.org/t/setting-up-a-common-publication-resource-library-for-openehr/14970)
> Hi All,
Whenever I start with a paper, report or presentation I find myself doing the same literature search and environment scan…And can only find the ones that I can or allowed to access. I am pretty sure this is the case for many of you out there. The current publications page on openEHR Website is quite limited and not frequently updated. What about creating a wiki page or a common bookmarking system?
If there is enough enthusiasm (if any), I also suggest that we look at the Zotero Open...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR UML Models](https://discourse.openehr.org/t/openehr-uml-models/14963)
> Hi,
I wonder if anyone might be able to help – it says on the openEHR Release 1.0.1 UML Models page ([http://www.openehr.org/releases/1.0.2/architecture/computable/UML/uml.html](http://www.openehr.org/releases/1.0.2/architecture/computable/UML/uml.html)) that there is an XMI 1.0 file output for the UML models. Does anyone know where I might be able to find a copy?
I’m not too concerned about the XMI or openEHR release version, I’m just looking for a resource that I can load into a UML tool...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Mutable java classes development kick-off](https://discourse.openehr.org/t/mutable-java-classes-development-kick-off/14959)
> Dear all,
I'd like to let you know that I've just started refactoring Rong Chen's RM implementation to create a mutable version of RM classes.
At the moment I can't say I am following a precise, well thought out method, the term shutgun surgery is more appropriate for the current process. When I feel that the mutable version is stable and clean enough to share, I'll immediately put it out so that others can benefit from it.
I'd like to thank Rong once again for his excellent work, which has...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [testParsingWithoutUTF8Encoding Error](https://discourse.openehr.org/t/testparsingwithoututf8encoding-error/13364)
> Hi,
the unit test testParsingWithoutUTF8Encoding fails on my Mac. After trying to make my Mac use UTF-8 by default instead of Mac Roman I gave up. However, i am not sure the test is right. The test should work even with a different default encoding, or not?
Thanks in advance.
Fábio
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Comment on openEHR-EHR-CLUSTER.inspection-skin-wound.v1 archetype](https://discourse.openehr.org/t/comment-on-openehr-ehr-cluster-inspection-skin-wound-v1-archetype/14955)
> Dear all,
I would like to ask you to consider the inclusion in the "type of wound" of "animal agression".
Because this kind of wound has proper features that should be differentiated of all the rest and so incluiding would avoid of making another archetype almost identical to openEHR-EHR-CLUSTER.inspection-skin-wound.v1 just to consider those wounds made by animals...
Thanks in advance,
Otavio
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage for software upgrades (11th Feb 2010)](https://discourse.openehr.org/t/openehr-site-outage-for-software-upgrades-11th-feb-2010/13363)
> Hi,
In order for us to carry out essential software upgrades to the openEHR
server there will be a period of service disruption next week\. We will
be upgrading the wiki software \(confluence\)\. Other services should be
unaffected by this upgrade, but it may be neccessary to restart the
server, so the whole site should be considered at risk during these periods\.
Thursday 11th February 2010 \- Wiki \(Confluence\)
08:00 \- 10:00 GMT \- Wiki software upgrade\. The Wiki will be...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Using LDAP-API's](https://discourse.openehr.org/t/using-ldap-apis/14957)
> Hi all,
Are there any thoughts about using LDAP\-API's in conjunction with OpenEHR\.
This question comes to me because of the desire of a customer to use
Google Apps
http://www.google.com/support/a/bin/answer.py?hl=en&answer=106368
With Google Apps Directory Sync, you can automatically provision users,
groups and non\-employee contacts based on the user data in a LDAP server
There are some possible solutions that come up\.
\- Create a layer of LDAP\-API's around the kernel...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about the specs about a reference to a version-container in Actor](https://discourse.openehr.org/t/question-about-the-specs-about-a-reference-to-a-version-container-in-actor/16230)
> Hi all,
About the Actor\-class which has "roles" which are a set of PartyRef's
containing a link to version\-containers having stored the role, instead
of directly linking to the role itself\.
This is inconsistent to the support\-specs, where a party\-ref is
described as being a link to a identify a party in a demographic service\.
Because we cannot know if a demographic service, has a versioning
container\-system which is build on ID's, maybe it is \(for example\)...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Questionnarie on learning openEHR](https://discourse.openehr.org/t/questionnarie-on-learning-openehr/16227)
> Hi!
Did you ever think the inner workings of openEHR were a bit tricky to learn? If you can help "my" master student Dominique by answering some of the questions below, then I hope we can give an even more useful report and tool back to the openEHR community.
Don't send your questionnarie reply to the mailinglist, we don't want your answer to bias other answers.
Send it to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Interoperability with HL7](https://discourse.openehr.org/t/interoperability-with-hl7/14960)
> I would like to address the interoperability with the HL7 standards. As I understand it is possible to map between OpenEHR to HL7 CDA, this allows us to create systems that are based on the openEHR reference model compatible HL7. This system would be able to send HL7 v2 and HL7 v3 messages from the CDA and EHR_EXTRACTS from the OpenEHR reference model.
I don't understand what consequences have that the HL7 RIM is still not fully compatible with the OpenEHR reference model if we can send...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR in 2010- where to focus our effort?](https://discourse.openehr.org/t/openehr-in-2010-where-to-focus-our-effort/16228)
> Dear Colleagues,
As we have now begun 2010 it might be useful to take a bit of stock of where we are, where we want to be\.\.
I commented in my last email of 2009 of where I felt progress had been made\.\.
http://www.openehr.org/mailarchives/openehr-clinical/msg01679.html
When looking forward this year, there appears a natural focal point of Medinfo in September 2010 in Cape Town\.
It appears to be a good place to be exploring openEHR progress together\.
With that in mind, last year Tim...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Can a single CONTRIBUTION ever affect two separate EHRs?](https://discourse.openehr.org/t/can-a-single-contribution-ever-affect-two-separate-ehrs/14952)
> Hi techies\!
A possibly stupid question:
Can a single CONTRIBUTION ever affect two separate EHRs?
I understand that a CONTRIBUTION normally only affects a set of
VERSIONED\_OBJECTs within a single EHR, but are there any exceptions?
Technically the class CONTRIBUTION can point to any OBJECT\_REF, but
what should be allowed for real?
A possible use case could be when moving some compositions between
records \(e\.g\. due to entry mistakes or temporary records for
unidentified patients\)\....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Presentation HL7 PC?](https://discourse.openehr.org/t/presentation-hl7-pc/13366)
> Dear Hugh,
Would it be possible to get a copy of your presentation and supporting files you presented at the PC WG meeting last week? Pdf would be fine. It is supporting the minutes.
Thank you,
William
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Adding a new method to the Archetype class](https://discourse.openehr.org/t/adding-a-new-method-to-the-archetype-class/12403)
> Hi,
I know that the nodeID attribute of CObject is used to distinguish between two sibling nodes, but when I create an archetype using the Ocean's Archetype Editor, each node in the ADL has a different nodeID value, so we can use the nodeID to distinguish between all nodes in the archetype. So, is it right to think of adding a new method to the Archetype class to get a node from it's nodeID? it's like the node(path) method but node(nodeID). I think it's easier to use nodeID instead of the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical Knowledge Manager: new version with template support](https://discourse.openehr.org/t/clinical-knowledge-manager-new-version-with-template-support/14956)
> Dear all,
We have uploaded a new version of the Clinical Knowledge Manager:
The CKM Release 1.1.0 adds initial support for templates within CKM.
Once uploaded, they are linked to the archetypes in CKM, so that an Operational template can be generated and displayed as a form at any time for any uploaded template.
Template version management principles are similar to those used for archetypes and you can comment on templates, export all templates, get a mindmap overview of all or a selected...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [How to define a Party-Relationship archetype?](https://discourse.openehr.org/t/how-to-define-a-party-relationship-archetype/16715)
> Hi all,
I am looking for how to define a PARTY_RELATIONSHIP archetype.
I found an example from the Brazilian Demographic-archetypes, which are very good examples, but this one is, in my opinion not complete/correct.
The definition part looks like this:
definition
PARTY_RELATIONSHIP[at0000] matches { -- Relações Pessoais
details matches {
ITEM_SINGLE[at0001] matches { -- Item
item matches {
ELEMENT[at0002] matches { -- Grau de parentesco
value matches {
DV_TEXT matches...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [getParent() allways null in ArchetypeSlot nodes?](https://discourse.openehr.org/t/getparent-allways-null-in-archetypeslot-nodes/13518)
> Hi,
I've a problem with my slots in archetypes, when I do a slot.getParent(), to get the parent CAttribute of this node, I get always null.
Any ideas?
Cheers,
Pablo Pazos.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Question about ArchetypeSlot.path()](https://discourse.openehr.org/t/question-about-archetypeslot-path/14954)
> Hi,
I've a SECTION archetype with 3 slots:
definition
SECTION[at0000] matches { -- Evaluación de vía aérea
items cardinality matches {0..*; unordered} matches {
allow_archetype EVALUATION[at0002] occurrences matches {0..1} matches { -- EVALUATION
include
archetype_id/value matches {/openEHR-EHR-EVALUATION\.via_aerea(-[a-zA-Z0-9_]+)*\.v1/}
}
allow_archetype ACTION[at0003] occurrences matches {0..1} matches { -- ACTION
include
archetype_id/value matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Meaningful use criteria](https://discourse.openehr.org/t/meaningful-use-criteria/14953)
> Is anybody following the current discussion in the US about the meaningful use citeri and/or is anybody actively involved?
The published criteria can be found here: [http://frwebgate5.access.gpo.gov/cgi-bin/PDFgate.cgi?WAISdocID=467405454267+0+2+0&WAISaction=retrieve](http://frwebgate5.access.gpo.gov/cgi-bin/PDFgate.cgi?WAISdocID=467405454267+0+2+0&WAISaction=retrieve)
Is just scanned it very quickly and one thing stroke me, this is just a pre-definition.: 'In order for an EHR technology to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Re openEHR and progress in 2009- a clinicians perspective](https://discourse.openehr.org/t/re-openehr-and-progress-in-2009-a-clinicians-perspective/13368)
> Dear Colleagues,
As 2009 draws to a close I wanted to reflect back on some of the themes we explored at the start of the year to gauge progress made this year\.
In doing so it seems important to mention the challenging times that 2009 has meant to lot of people all over the globe, which if anything has demonstrated how very interdependant we all now are\.
Earlier in the year I shared a view as to what the openEHR clinical community had expressed a want/need in pursuing in 2009 and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Problem with diagnosis](https://discourse.openehr.org/t/problem-with-diagnosis/14950)
> David Rowen brought up an issue with the modeling of Diagnosis as being a specialized Problem. I concur and the comments in CKM are shown below.
The question is how do these issues get resolved - or will they not get resolved - once modeled can an archetype never change due to architecture e.g. the AQL requires the diagnosis to be in a specific place in a specific archetype so there will be resistance to change?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [data types and structures questions](https://discourse.openehr.org/t/data-types-and-structures-questions/14949)
> >
Hi All,
I've got some questions about data types and structures. I was wondering if someone could help me.
1. Why an item_single can,t be empty but other structures may be. I mean 'items" attribute's cardinality in item_single is 1..1 (and this is logical. coz' an item_single without element is meanless). But in other structures, the cardinality of "items" attribute is 0..1. What's the point of having an empty list or tree or table (without ant item in it)?
2. What's...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in CObject.isRequired() method?](https://discourse.openehr.org/t/bug-in-cobject-isrequired-method/16226)
> Hi,
I think there is a bug in CObject.isRequired().
If I set a node in Archetype to have 1 and only 1 occurrence.
Java ADL parser will parse it with occurrence.lower = 1 and occurrence.upper = 1 (not occurrences == null)
But the code below assumed that the occurrences == null for the above condition.
Thus the method return false which should be true instead.
> public boolean isRequired() {
> if (occurrences == null) { // default {1..1} // occurrences parsed from ADL parser is not...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Update from the openEHR Board Chairman - D. Ingram](https://discourse.openehr.org/t/update-from-the-openehr-board-chairman-d-ingram/16224)
> I have today posted an [update](http://www.openehr.org/news_events/announcements/board_update_12dec2009.html) on progress of the *open*EHR Foundation over the past year on the web site.
This is both a report from the Board and some personal reflections on the stage it has reached and the inevitable growing pains it is experiencing.
I would like to say thank you to everyone working so hard to make things happen: in terms of the specifications, the growing repository of formative archetypes,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [latest archetype & template drafts](https://discourse.openehr.org/t/latest-archetype-template-drafts/13365)
> You can see the progress at
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
This page has updated explanations for changes in ADL/AOM 1\.5, and also
links to the most recent archetype and template drafts\. The template
draft still has major parts to be done, but the modelling is nearly
worked out\. The operational template section will be next to be completed\.
There are also a bunch of UML and other diagrams on the page which will
give people quick...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [AQL builder](https://discourse.openehr.org/t/aql-builder/14958)
> Hello,
somebody know how could I get the AQL builder? I have downloaded the Template designer tool becouse I I think it includes AQL, but an activation code is required. ¿Could I get one?
Thank you in advanced! Regards!
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Updated AOM and template model](https://discourse.openehr.org/t/updated-aom-and-template-model/16225)
> I have finally broken the back of the modelling required to templates work cleanly. The latest drafts are at:
- archetype model: [http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/aom1.5.pdf](http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/aom1.5.pdf)
- template model: [http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/tom.pdf](http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/tom.pdf)
Note -...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Wound care proto-archetype development on Google Wave](https://discourse.openehr.org/t/wound-care-proto-archetype-development-on-google-wave/16221)
> Hi,
As some already know, we have been experimenting with Google Wave as a mechanism for early collaborative development on archetype concepts.
We have started a Wave on Wound care at:
[https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BsliTddCQD](https://wave.google.com/wave/#restored:wave:googlewave.com%21w%252BsliTddCQD)
and have already amassed quite a lot of good source material but we need input, particularly from nursing colleagues.
The intention is to get the ideas...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR engagement](https://discourse.openehr.org/t/openehr-engagement/16223)
> Hi,
I am working on a paper which I hope to submit to the EFMI Special Topic Conference,Reykjavík, Iceland, 2-4 June 2010.
The working title is 'Getting a wider community to engage with openEHR: Reflections on teaching openEHR to undergraduates.'
I was wondering if anyone else has a specific interest in this area?
Best wishes,
Derek.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problems with archetype internal ref](https://discourse.openehr.org/t/problems-with-archetype-internal-ref/16222)
> Hi,
I'm trying to support Archetype Internal Refs on my degree thesis project but I think there is an error on the specs or on the oceans archetype Editor.
In the AOM specs, every CObject has a mandatory node_id attribute, included the ArchetypeInternalRef.
I make an archetype using Oceans Archetype Editor and the node with the reference looks like this:
CLUSTER[at0008] occurrences matches {0..1} matches { -- Pelvis
items cardinality matches {0..*; unordered} matches {
use_node ELEMENT...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Google Wave invitations](https://discourse.openehr.org/t/google-wave-invitations/13360)
> Hello Ian, please send me an invitation.
Best Regards,
Arturo Alvestegui
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [: informal poll: openEHR conference](https://discourse.openehr.org/t/informal-poll-openehr-conference/13361)
> I, along with other representatives from the American College of
Rheumatology are interested in attending\.
\-Itara
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Rong Chen PhD thesis online](https://discourse.openehr.org/t/rong-chen-phd-thesis-online/14951)
> Rong Chen, the original author of the openEHR Java implementation has
finally returned to mainstream humanity, after completing his Doctoral
dissertation\. The abstract and link can be found here:
http://www.openehr.org/shared-resources/publications/archetypes.html \.
An abstract from the abstract:
The key contribution of the thesis can be summarized as the validation
and further improvement
of the openEHR archetype formalism through software implementation and
the explorations on
clinical...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ADLParser cannot parse Archetype with Khmer Language translation](https://discourse.openehr.org/t/adlparser-cannot-parse-archetype-with-khmer-language-translation/13359)
> Dear all,
When I try to parse Archetype with Khmer language translation, the parser throwed an Exception.
I attach the Stack Trace below:
Exception in thread "main" java.lang.IllegalArgumentException: **unknown original language ISO_639-1, km**
at org.openehr.rm.common.resource.TranslationDetails.(TranslationDetails.java:53)
at se.acode.openehr.parser.ADLParser.translations(ADLParser.java:384)
at se.acode.openehr.parser.ADLParser.archetype(ADLParser.java:258)
at...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in openehr_terminology_en.xml](https://discourse.openehr.org/t/bug-in-openehr-terminology-en-xml/16676)
> Dear all,
In [openehr_terminology_en.xml](http://openehr.org/wsvn/ref_impl_java/TRUNK/mini-termserv/src/main/resources/openehr_terminology_en.xml), the section ****
does not include **
But 'archetypeBinder' is not declared in **faces-config.xml**
**faces-config.xml**
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Amnon Shabo is out of the office.](https://discourse.openehr.org/t/amnon-shabo-is-out-of-the-office/13352)
> I will be out of the office starting 22/11/2009 and will not return until
01/01/2010\.
For Hypergenes issues, please contact Ariel Farkash at arielf@il\.ibm\.com on
"data\-in" and Carmel Kent at carmelk@il\.ibm\.com on "data\-out"\.
Standards Issue:
• For IHE issues, please contact Karen Witting at witting@us\.ibm\.com
• For OHT, Continua and HL7 issues, please contact Rich Rogers at
rrogers@us\.ibm\.com
• For DICOM issues, please contact Eric Goodall at...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Ruby implementation version 0.5.0(Samos) released](https://discourse.openehr.org/t/ruby-implementation-version-0-5-0-samos-released/14438)
> Hi folks,
Today, we released version 0\.5\.0 \(Samos\), Ruby implementation of the openEHR
specification\.
This release is still experimental preview of our work based on openEHR
specification release 1\.0\.2\. We implemented ADL Parser and most of the
specifications of the openEHR\. This parser successfully parses 27 ADLs
and generates archetype instances\. The work is still in progress\.
Almost all classes passed the test constructed by rspec or
test/unit\. This test cases are under...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Why ISM_TRANSITION of an ACTION is mandatory?](https://discourse.openehr.org/t/why-ism-transition-of-an-action-is-mandatory/14947)
> Hi,
In the specs I see that ACTION has a mandatory relationship to ISM_TRANSITION.
In my project I only use the "description" field of ACTION to record information about the ACTION and I don't have information to fill the ISM_TRANSITION.
My question is: why the ISM_TRANSITION of the ACTION is mandatory instead of optional?
Thank you,
Pablo.
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Typo in Release 1.0.2 Release Note](https://discourse.openehr.org/t/typo-in-release-1-0-2-release-note/16220)
> Hi,
Just notice there is a typo in the Release Notes of Release 1\.0\.2\. In
the section of Impact Analysis, the 2nd sub title should be something
like "Reference Model implementations" instead of "Rerence Model
implementations"\.
Cheers,
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ITEM_TABLE archetypes and Oceans Archetype Editor](https://discourse.openehr.org/t/item-table-archetypes-and-oceans-archetype-editor/16218)
> Hi,
We are trying some GUI generation with a wide set of archetypes.
Now we are making some ITEM_TABLE test archetypes.
From the data_structure specification I understand that "Each row is encoded as a Cluster containing a number of Elements, each corresponding to
the value of a column in that row", but when I create an ITEM_TABLE archetype with Oceans Archetype Editor I get a structure that not match the specification.
If I have a table with 3 rows and 2 columns I spect to see 3 clusters...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Terminology / information model interface](https://discourse.openehr.org/t/terminology-information-model-interface/16219)
> I have published some initial notes on the issue of the interface
between the information model \(in openEHR, this is generally archetypes,
with a bit of reference model\) \- see
http://www.openehr.org/wiki/display/term/Information+Model+-+Terminology+Equivalence
I am interested to know in particular what others think about the Snomed
context model, including the Temporal context, Finding context,
Procedure context, and the problem of trying to represent values in Snomed\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[503] Add Template OET parser to the Java Sandbox.](https://discourse.openehr.org/t/503-add-template-oet-parser-to-the-java-sandbox/16217)
> Revision: 503
Author: sebastian\.garde
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR community on Google Wave](https://discourse.openehr.org/t/openehr-community-on-google-wave/14940)
> For anyone who is interested and has a Google Wave account, I have started an openEHR community Wave with the intent of it being a coordinating point - which we can use as a jumping off point to various conversations or waves on specific topics or projects. This may work, or it may result in total chaos - I don't know ;-)
>From this first wave I have set up two linked waves to kick it off - one for clinical modelling, particularly with trying to start to communicate and coordinate early...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CEN/ISO 13606 extract tools](https://discourse.openehr.org/t/cen-iso-13606-extract-tools/14946)
> Hi all,
I created some CEN/ISO extracts and I'd like to validate these files. I'm looking for tools to work with CEN/ISO13606 extracts (parsers, extract generator, ADL editors for this reference model, XML schemas etc.). Could anyone offer help or indicate to me some references?
Thanks,
Marcelo.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_DATE definition mismatch](https://discourse.openehr.org/t/dv-date-definition-mismatch/14941)
> Hello everybody,
I have detected what it seems a mismatch between the DV_DATE definition of the reference model and the ADL parser/AOM model specifications.
At the RM, the DV_DATE value is defined as a String constrained as an ISO8601 pattern. This is both at the RM specification and at the XML Schema.
Following the ADL/AOM specifications, something such as (this code has been generated by the Ocean Archetype Editor)
DV_DATE matches {
value matches {yyyy-??-XX}
}
will be parsed as a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [interesting blogs](https://discourse.openehr.org/t/interesting-blogs/16216)
> Various blogs mentioning openEHR\.\.\.
http://healthit.hhs.gov/blog/faca/index.php/2009/11/09/real-world-experience-standards/
http://adambosworth.net/2009/10/29/talking-to-dc/
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Cancer treatment archetypes](https://discourse.openehr.org/t/cancer-treatment-archetypes/14942)
> Hi,
I'm trying to archetype patient records in a prostate cancer
environment\. I see that there are currently no specific archetypes for
common cancer treatments such as radiotherapy, hormone therapy and
chemotherapy\. Could hormone therapy and chemotherapy be described as
specializations of the openEHR\-EHR\-INSTRUCTION\.medication\.v1
archetype? And could radiotherapy be described with a specialization
of openEHR\-EHR\-INSTRUCTION\.non\_drug\_therapy\.v1? Or should these be
described...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Te invito a unirte a Facebook](https://discourse.openehr.org/t/te-invito-a-unirte-a-facebook/16214)
>
# Te invito a unirte a Facebook
Hola, Ref_impl_java:
He creado un perfil en Facebook donde puedo publicar mis fotos, vídeos y eventos, y quiero añadirte a mis amigos para que puedas verlo. Para ello, necesitas registrarte en Facebook y, después, podrás crear también tu propio perfil.
Gracias,
Juan Miguel
Para registrarte en Facebook, sigue este...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM Demographics archetypes](https://discourse.openehr.org/t/ckm-demographics-archetypes/16215)
> As most of you will now know, a set of Demographics Model archetypes which are aligned to the ISO standards, has been uploaded to CKM and we started formally reviewing "Person name" and "Postal address" recently. The results of these reviews will be posted to CKM in the next few days and many thanks to those of you who have already contributed.
We know that there was considerable interest in the ISO-Demographics archetypes earlier in the year but this has not been reflected in the number of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Where can I download the OpenEHR terminology?](https://discourse.openehr.org/t/where-can-i-download-the-openehr-terminology/14944)
> I've tried the link from here: http://www.openehr.org/releases/1.0.2/architecture/computable/terminology/terminology.html
But points to: http://www.openehr.org/releases/architecture/computable/terminology/terminology.xml
And I get a 404.
Thanks a lot.
Pablo.
http://pablo.swp.googlepages.com/
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Check out my photos on Facebook](https://discourse.openehr.org/t/check-out-my-photos-on-facebook/16213)
>
[ ](http://www.facebook.com/p.php?i=100000384409189&k=Z6E3Y5TSQZ5N5JMJPB63QTUPPTJG2ZXNUWEVBG4EVW)
|
Mahdi Asgari has:
7 friends
0 photos
0 notes
1 wall post
0 groups
|
# Check out my photos on Facebook
Hi...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR service specification space](https://discourse.openehr.org/t/openehr-service-specification-space/14398)
> I have started to populate the wiki area with some initial service specification material. See [http://www.openehr.org/wiki/display/spec/openEHR+Service+Model](http://www.openehr.org/wiki/display/spec/openEHR+Service+Model)
This is rough for now, but in the spirit of early collaboration, I thought it would be enough to provide some ideas. The top-level page is just an informal description of basic design ideas, as I see them, and based on what we have learned in our Ocean implementation....
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [OpenEHR-ES](https://discourse.openehr.org/t/openehr-es/14396)
> Hi,
We're trying to build an spanish-speakers community about openEHR , I just create a google group: http://groups.google.com/group/openehr-es
We want to translate some docs and presentations to generate enough knowledge to spread the word about OpenEHR, and other EHR related concepts between latin-american and spanish people.
Best regards
Pablo Pazos Gutierrez
http://pablo.swp.googlepages.com/
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [How to contribute an archetype](https://discourse.openehr.org/t/how-to-contribute-an-archetype/14945)
> Hi,
I have translated the Glasgow Coma Scale archetype to spanish, how can I send it to the CKM?
Cheers,
Pablo Pazos
http://pablo.swp.googlepages.com/
[details="(attachments)"]
[openEHR-EHR-OBSERVATION.glasgow_coma.v1draft.adl|attachment](upload://rjF4OqTLrYoHMvx3Agg0ffBd87k.adl) (7.44 KB)
[/details]
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM Web Service : getDescriptionForArchetype](https://discourse.openehr.org/t/ckm-web-service-getdescriptionforarchetype/14437)
> On the wiki the description for getDescriptionForArchetype accepts a parameter called descriptionTerms[], which can reference description elements (properties) as specified in the ontology.
Is their a definitive list of these terms that have been implemented, these would be useful if explicitly stated within the wiki.
thanks
OP
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [connecting the information model to terminology: slideshow on SNOMED CT expression patterns from Bethesda](https://discourse.openehr.org/t/connecting-the-information-model-to-terminology-slideshow-on-snomed-ct-expression-patterns-from-bethesda/14439)
> Kent Spackman made a presentation on how SNOMED should be used to
represent complex clinical statements, using a design pattern approach\.
This idea is clearly important in our thinking in openEHR on how to
connect the information models \(archetypes\) to terminology\. See
http://www.openehr.org/wiki/pages/viewpage.action?pageId=5997269 for
this discussion; the slideshow \(PDF format\) is linked at the bottom\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Generic name of medication](https://discourse.openehr.org/t/generic-name-of-medication/14938)
> Dear all,
In the Swedish archetype project, we need to record medication
information with the medication archetype from the openEHR knowledge
repository\. We have difficulties to decide on which archetype node to
use in the medication archetype
\("openEHR\-EHR\-ITEM\_TREE\.medication\.v1"\) for the name of the medication
and the ATC code\. There are at least two possibilities here, both
"Name of the medication" and "Generic name of the medication" seems to
be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM Icons](https://discourse.openehr.org/t/ckm-icons/16714)
> I am struggling to understand what all the icons on CKM mean - is there a FAQ on that anywhere?
thanks
OP
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Demographic Archetypes](https://discourse.openehr.org/t/demographic-archetypes/14937)
> I am struggling to understand why CLUSTER archetypes can exists within the DEMOGRAPHICS area, yet the CLUSTER class does not seem to exists within the Demographics IM.
If CLUSTER is allowed does that mean ELEMENT is also allowed ?
many thanks
OP
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New wiki space](https://discourse.openehr.org/t/new-wiki-space/13343)
> I have created a 'Terminology' space on the wiki\. Initially I would like
to get material from the recent IHTSDO meeting up there\. The idea is to
create very clear guidelines for archetype design, and to ensure the
semantic congruence of archetypes and other aspects of openEHR with
terminology\. Remembering of course that openEHR is designed to work with
any terminology, we will nevertheless be able to use a lot of the
thinking coming from IHTSDO and SNOMED\-CT\.
See...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Sending a new object using the Contribution](https://discourse.openehr.org/t/sending-a-new-object-using-the-contribution/16212)
> Dear All,
According to the reference, common, and extract information models
changes made to an EHR, including "additions", should be sent through
a contribution\.
There is no implicit or explicit link to an EHR neither in
X\_CONTRIBUTION nor in CONTRIBUTION\.
So, would you please let me know what is the scenario to send new
objects \("addition change type"\) using contribution or x\_contribution
classes?
Bests,
Soheil
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [wiki organisation](https://discourse.openehr.org/t/wiki-organisation/14936)
> I have just been looking around the openEHR wiki, and while I respect the fact that wikis are a place of creative anarchy, I wonder if some of the following pages could be better placed:
- the MedInfo submission page is currently in the Health Information Models space ([http://www.openehr.org/wiki/display/healthmod/Draft+-+Medinfo+clinical+workshop+submission+2010](http://www.openehr.org/wiki/display/healthmod/Draft+-+Medinfo+clinical+workshop+submission+2010)) when a more obvious place...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM update](https://discourse.openehr.org/t/ckm-update/14948)
> Dear colleagues,
Just thought I'd send an update on CKM activity, with the main focus on the Emergency-related archetypes. We are anticipating that Medication review will be able to commence soon.
If you are interested in participating in any Team reviews please log in to CKM and adopt the archetype to register your interest. At initiation of each review round all adoptors will be included as part of the review team and be sent instructions on how to participate. Instructions for adopting an...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Modeling reference ranges](https://discourse.openehr.org/t/modeling-reference-ranges/14933)
> Hi,
I'm playing around with archetypes trying to model an observation and its reference ranges,
I mean something like "blood pressure" and some range to define what is "hypertension", but
I can't found an archetype that defines a reference range for an observation.
Any one has experience in modeling something like this?
An archetype is the correct place to define a reference range for an observation value?
Any ideas?
Thak you!
Cheers,
Pablo Pazos Gutierrez
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CKM Reviews of Demographics model archetypes imminent](https://discourse.openehr.org/t/ckm-reviews-of-demographics-model-archetypes-imminent/14925)
> Dear colleagues,
We are aware
Sorry for posting on both technical and clinical lists but I am aware that there has been considerable interest in both parts of the openEHR community regarding the ISO-compatible archetypes developed by our Brazilian colleagues, Sergio Friere and Rigoleta Dutra.
.
I am pleased to announce that we will start formal reviews via Clinical Knowledge Manager (CKM) of the Demographics model archetypes later this week, commencing with **'Person Name'** and **'Postal...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Draft - Medinfo clinical workshop submission 2010](https://discourse.openehr.org/t/draft-medinfo-clinical-workshop-submission-2010/13354)
> Hi all - 2nd try. Sent a draft submission for Medinfo as an attachment last Friday - just found it had been rejected - grrrrrrrr (why so long????)
So I've uploaded it to the openEHR Wiki: Draft - Medinfo clinical workshop submission 2010 - [http://bit.ly/8PmWj](http://bit.ly/8PmWj)
Time was short last Friday, and so now it is VERY short - so you can comment on the wiki page or via email and I'll try to draw it all together in time for submission.
H
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Broken link on openEHR web site](https://discourse.openehr.org/t/broken-link-on-openehr-web-site/14436)
> Hi,
Whilst checking the subversion upgrade Matthew and I came across a page
with a link to the old style svn URLs\.\.\.
http://www.openehr.org/shared-resources/developers/subversion/overview.html
"openEHR Change Management Plan" links to :
http://svn.openehr.org/specification/TRUNK/publishing/CM/CM_plan.pdf
and should link to:
http://www.openehr.org/svn/specification/TRUNK/publishing/CM/CM_plan.pdf
I have no experience in using Daisy to edit pages, so have not even
attempted...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage for software upgrade (tomorrow)](https://discourse.openehr.org/t/openehr-site-outage-for-software-upgrade-tomorrow/13350)
> Hi,
\*\*\*\*\* Tomorrow, 7th October 2009, 08:00 BST \*\*\*\*\*
In order for us to carry out an essential upgrade to the openEHR
Subversion server, there will be a short period of service disruption
tomorrow morning\.
The other services on the openEHR site should continue to be available
whilst the upgrade is being carried out, however the entire site should
be considered at risk during this period\.
Wednesday 7th October 2009 \- Subversion upgrade
08:00 \- 10:00 BST \- Subversion...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL - syntax highlight for Notepad++](https://discourse.openehr.org/t/adl-syntax-highlight-for-notepad/14930)
> I wonder if anyone has created themselves a syntax highlight file
for use with Notepad\+\+
http://notepad-plus.sourceforge.net/uk/site.htm
and would be willing to share it?
Gavin Brelstaff CRS4
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[501] fixed negative value support in DvOrdinal](https://discourse.openehr.org/t/501-fixed-negative-value-support-in-dvordinal/13349)
> Revision: 501
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problems running Release 1.0.1 of openEHR Java Reference Implementation](https://discourse.openehr.org/t/problems-running-release-1-0-1-of-openehr-java-reference-implementation/13346)
> Hi to all from Trinity College Dublin,
I'm a student in the university and I'm starting to work on OpenEHR,
so please forgive me if my question\(s\) is/are newbie ones, or if
I've asked it in the wrong place, please redirect me\.
I did check the mailing list archive and could find no discussion
about this problem\.
I downloaded the file openehr\_ref\_impl\_java\-1\.0\.1\.jar
from
http://www.openehr.org/wiki/display/projects/Java+Project+Download
However, when I tried to run...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Interim Statement on Copyright and Licensing of Archetypes](https://discourse.openehr.org/t/interim-statement-on-copyright-and-licensing-of-archetypes/12362)
> **Interim Statement on Copyright and Licensing of Archetypes**
Effective processes for the authoring, review, management and quality assurance of archetypes are of fundamental concern to the *open*EHR Foundation. They are needed to underpin the clinical value of the work of the *open*EHR community and contribute to its wider success in what is an increasingly complex environment.
Within the wider health and social care communities that *open*EHR was created to serve, quality and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Medinfo2010 workshop proposal, draft](https://discourse.openehr.org/t/medinfo2010-workshop-proposal-draft/16673)
> I'm confused as to why some people think it's a good idea to take these
discussions OFF LIST to only a handful of people that weren't even
invloved in the ON LIST discussions when this is SUPPOSED to be a
community?????
See the thread on the technical list Tue, 15 Sep 2009 23:18:03 \+0100
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Disruption to power supply for openEHR servers](https://discourse.openehr.org/t/disruption-to-power-supply-for-openehr-servers/13347)
> Hi,
I have just been informed by our local Estates & Facilities department
that statutary 5 yearly tests are to be carried out to the main
electrical supply to the building that hosts the openEHR services\.
We are in the process of trying to arrange alternative power supplies to
maintain the services during this period, but all openEHR services
should be considered at risk from 1st October 2009 18:00 \(BST\) until 2nd
October 2009 08:00 \(BST\)\.
I am very sorry about the short notice,...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage for software upgrade (next week)](https://discourse.openehr.org/t/openehr-site-outage-for-software-upgrade-next-week/16211)
> Hi,
In order for us to carry out an essential upgrade to the openEHR
Subversion server, there will be a short period of service disruption
next week\.
The other services on the openEHR site should continue to be available
whilst the upgrade is being carried out, however the entire site should
be considered at risk during this period\.
Wednesday 7th October 2009 \- Subversion upgrade
08:00 \- 10:00 BST \- Subversion software upgrade\. The...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [8th Medical Open Source Software Seminar (MOSS8) in Tokyo, Oct 31 2009](https://discourse.openehr.org/t/8th-medical-open-source-software-seminar-moss8-in-tokyo-oct-31-2009/16210)
> It is a pleasure for us to announce the 8th Medical Open Source Software Seminar (MOSS8) in Tokyo, Japan as follows:
*Date and Time*: October 31, 2009, from 13:00 to 18:00
*Location*: Waseda University, Building 19, Room 610
[http://www.waseda.jp/jp/campus/waseda.html](http://www.waseda.jp/jp/campus/waseda.html)
*Organized by*: Medical Open Source Software Council in Japan
*In cooperation with*: Kano laboratory, Waseda University
*Registration Fee*: free
*Fee for reception after the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Medinfo submission deadline extended](https://discourse.openehr.org/t/medinfo-submission-deadline-extended/16209)
> Not sure if this has been posted previously - Medinfo 2010 deadline for submissions has been extended to 15 October, 2009
[http://www.medinfo2010.org/](http://www.medinfo2010.org/)
Cheers
Heather
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [900] AWB-167: Eiffel Software is planning to remove the implicit conversions from STRING_32 to STRING_8 in EiffelStudio 6.5.](https://discourse.openehr.org/t/ref-impl-eiffel-900-awb-167-eiffel-software-is-planning-to-remove-the-implicit-conversions-from-string-32-to-string-8-in-eiffelstudio-6-5/16208)
> Revision: 900
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Java implementation error?](https://discourse.openehr.org/t/java-implementation-error/13348)
> Hi there,
I have tried to input value to build DvOrdinal.
RM Object Builder cannot accept "0" for value.
It says in the documentation that any value is ok.
[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/data_types_im.pdf](http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/data_types_im.pdf)
Page: 44
Is it a bug, or is intended?
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Documentation Desparation](https://discourse.openehr.org/t/documentation-desparation/14928)
> Hi All,
Over the past several years I have discussed this issue with Tom Beale;
on mailing lists, off mailing lists and in person\.
The issue is that Framemaker is a proprietary and basically non standard
document format\. I fully understand that Tom enjoys the desktop
publishing capabilities that it gives him and that he is familiar with
the application\.
However, we the "open content" community end up with a proprietary
format \(Framemaker\) and a dead\-end format \(PDF\) for...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage for software upgrade](https://discourse.openehr.org/t/openehr-site-outage-for-software-upgrade/13345)
> Hi,
In order for us to carry out an essential upgrade to the openEHR
Subversion server, there will be a short period of service disruption in
two weeks\.
The other services on the openEHR site should continue to be available
whilst the upgrade is being carried out, however the entire site should
be considered at risk during this period\.
Wednesday 7th October 2009 \- Subversion upgrade
08:00 \- 10:00 BST \- Subversion software upgrade\. The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Future of EXTRACT_SPEC](https://discourse.openehr.org/t/future-of-extract-spec/13337)
> Hi There,
We found that the EXTRACT\_SPEC in the Extract Information Model
\(Revision 2\.0\) has a manifest property for specification of entities
\(e\.g\. records\) to be included in the Extract\.
But, in the trunk version of the eiffel implementation, the
EXTRACT\_SPEC dos not have this field\.
Would you please let me know if the manifest field of EXTRACT\_SPEC
will be kept in the future extract information models?
If no, please let me know where can I find the final version of...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [LexBIG terminology server incorporated into the Opereffa framework.](https://discourse.openehr.org/t/lexbig-terminology-server-incorporated-into-the-opereffa-framework/13339)
> We are pleased to announce a major step forward for Opereffa, which covers another important aspect of openEHR implementation: terminology server integration.
The relationships between terminologies and information modeling for the EHR has been the subject of much ongoing discussion. The intrinsic complexity of these relationships and the
technical tooling requirements for examining them rigorously have been growing inexorably, with many and rapid developments in both...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Heart Rate archetype review just initiated](https://discourse.openehr.org/t/heart-rate-archetype-review-just-initiated/13341)
> Dear colleagues,
I have just initiated the first review for the Heart Rate archetype in the Clinical Knowledge Manager - [www.openEHR.org/knowledge](http://www.openEHR.org/knowledge). The specialisation, Pulse, is anticipated to follow on as soon as the Heart Rate archetype is finalised and published.
If you would like to participate, it is not too late - simply log in and 'Adopt' the Heart Rate archetype, and you will be added to the review team for this round.
Kind Regards
Heather
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [899] Create template branch as a copy of specialisation branch](https://discourse.openehr.org/t/ref-impl-eiffel-899-create-template-branch-as-a-copy-of-specialisation-branch/13336)
> Revision: 899
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [898] Small bug fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-898-small-bug-fixes/13335)
> Revision: 898
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - ["An IHE Profile Proposal for Document Templates"](https://discourse.openehr.org/t/an-ihe-profile-proposal-for-document-templates/13340)
> I'm not a CDA specialist, but seems that CDA has its own "archetypes" now
http://motorcycleguy.blogspot.com/2009/09/ihe-profile-proposal-for-document.html
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [OpenEHR / ISO 13606 converter](https://discourse.openehr.org/t/openehr-iso-13606-converter/14931)
> Hi,
I presented in the MIE conference at the end of August a poster ([http://www.hst.aau.dk/~ska/MIE2009/papers/MIE2009p0260.pdf](http://www.hst.aau.dk/~ska/MIE2009/papers/MIE2009p0260.pdf)) about a ISO 13606 to OpenEHR and vice-versa converter. Some people asked for me to post some information about it. You can try it at: [http://miuras.inf.um.es:9080/PoseacleConverter/](http://miuras.inf.um.es:9080/PoseacleConverter/),
there, in the archetypes tab, you can also find OpenEHR archetypes...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Off the subject a little- Would like to look around CHIME when in London in November this year](https://discourse.openehr.org/t/off-the-subject-a-little-would-like-to-look-around-chime-when-in-london-in-november-this-year/13334)
> Hi,
I'm coming to London between November 8 and 13 to present at for the
forthcoming e\-HISec
2009 conference \(The Elephant in the Room: Health Information System
Security and the User\-Level Environment\)\. I'm sorry this is off\-topic
but this list seems the most effective way to organise a visit, so I
wondered whether anyone be able to might help out? Ultimately, I'd like
to get to know people because I hope to organise a range of reciprocal
seminars between academic staff at...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Medinfo2010 workshop proposal, draft](https://discourse.openehr.org/t/medinfo2010-workshop-proposal-draft/14929)
> Hi All,
I'm not saying that these \(multiple workshops\) are bad ideas\. But here
is the reality\.
The next MedInfo is three years away\. People have heard about openEHR
for more than a decade\. They want to see it work\.
I see us right now having trouble focusing on an interoperability
demonstration\.
With \(probably\) more than 1000 members in the openEHR community and a
large percentage of them healthcare providers\. I want to ask you to
support Tony Shannon and simply spend...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [IHTSDO and openEHR Begin Collaborative Work Programme](https://discourse.openehr.org/t/ihtsdo-and-openehr-begin-collaborative-work-programme/13333)
> Since I can't reply to an openEHR announce mail, I'll do it here\.
This is great news\. Congratulations to David, Thomas and all the other
hard working people who made this possible\. Although undoubtably new
challenges will come up, this is a great opportunity to show the value
of openEHR, when it comes to level 4/ semantic interoperability and
decision support to 'the rest of the world'\.
Cheers,
Stef
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR and IHTSDO - memorandum from the openEHR board](https://discourse.openehr.org/t/openehr-and-ihtsdo-memorandum-from-the-openehr-board/16206)
> Today there was a press announcement on behalf of the *open*EHR Foundation and the IHTSDO, from the IHTSDO headquarters in , which has been copied to the openehr-announce list.
An agreement has been reached between the respective boards to collaborate in establishing a programme of practical efforts to take forward the harmonisation of *open*EHR clinical archetypes and SNOMED clinical terminology, as a contribution towards professionally assured clinical content for electronic health...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [IHTSDO and openEHR Begin Collaborative Work Programme](https://discourse.openehr.org/t/ihtsdo-and-openehr-begin-collaborative-work-programme/16207)
> *Organizations will explore how clinical terminologies and archetype-based record structures*
*can best be aligned to support electronic health records.*
**September 15, 2009** – IHTSDO and the *open*EHR Foundation are to work together on a harmonisation project where the overall goal is the practical development of effective and sustainable clinical content for the electronic health record. The project will explore how best to support those who wish to use *open*EHR™ archetypes and SNOMED...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [897] Separate out the notion of 'flat' archetypes that are generated, and 'legacy (flat)' archetype files.](https://discourse.openehr.org/t/ref-impl-eiffel-897-separate-out-the-notion-of-flat-archetypes-that-are-generated-and-legacy-flat-archetype-files/14360)
> Revision: 897
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [896] Add repository refresh (ctrl+R) and add ADL save version to option dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-896-add-repository-refresh-ctrl-r-and-add-adl-save-version-to-option-dialog/14359)
> Revision: 896
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR courses in Brazil - National Laboratory for Scientific Computing of Brasil - Jan/Feb 2010](https://discourse.openehr.org/t/openehr-courses-in-brazil-national-laboratory-for-scientific-computing-of-brasil-jan-feb-2010/13338)
> Petropolis, RJ, Brazil \- 2009\-09\-07
The National Laboratory for Scientific Computing of Brasil \(LNCC\) will
host its 8th annual Summer programme of mini\-courses in advanced topics
from 4 Jan \- 26 Feb, 2010\. The activities are developed by researchers
from LNCC and guests from other institutions\. The objectives of the
program are the generation of scientific exchange and dissemination of
the knowledge base and borders\. The target audience consists of students
at the end of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [895] Update the installers to get the RM schema files from their new location, and to install them into the application's rm_schemas subdirectory.](https://discourse.openehr.org/t/ref-impl-eiffel-895-update-the-installers-to-get-the-rm-schema-files-from-their-new-location-and-to-install-them-into-the-applications-rm-schemas-subdirectory/13332)
> Revision: 895
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [894] Commit missed ARCHETYPE_REXTERNAL_REF icon files](https://discourse.openehr.org/t/ref-impl-eiffel-894-commit-missed-archetype-rexternal-ref-icon-files/13331)
> Revision: 894
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [893] Simplification of RM schema directory structure and file-naming approach](https://discourse.openehr.org/t/ref-impl-eiffel-893-simplification-of-rm-schema-directory-structure-and-file-naming-approach/13330)
> Revision: 893
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [892] Further minor improvements to RM schema attribute naming](https://discourse.openehr.org/t/ref-impl-eiffel-892-further-minor-improvements-to-rm-schema-attribute-naming/13329)
> Revision: 892
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [891] Correct RM checking so that file contains a 'schema' and a schema can contain >= 1 'model'](https://discourse.openehr.org/t/ref-impl-eiffel-891-correct-rm-checking-so-that-file-contains-a-schema-and-a-schema-can-contain-1-model/13326)
> Revision: 891
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [890] Support new C_OBJECT type ARCHETYPE_EXTERNAL_REF;](https://discourse.openehr.org/t/ref-impl-eiffel-890-support-new-c-object-type-archetype-external-ref/13325)
> Revision: 890
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [889] Update the installers to get the RM schema files from their new location.](https://discourse.openehr.org/t/ref-impl-eiffel-889-update-the-installers-to-get-the-rm-schema-files-from-their-new-location/13324)
> Revision: 889
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [888] final renaming operation](https://discourse.openehr.org/t/ref-impl-eiffel-888-final-renaming-operation/13323)
> Revision: 888
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [887] further renaming operations for RM schema files](https://discourse.openehr.org/t/ref-impl-eiffel-887-further-renaming-operations-for-rm-schema-files/16205)
> Revision: 887
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [License and copyright of archetypes](https://discourse.openehr.org/t/license-and-copyright-of-archetypes/14934)
> Dear all,
These days I have been thinking about the legal issues involving the use of existing archetypes. I have seen that openEHR archetypes available on the Clinical Knowledge Manager are all "Copyright (c) 200X openEHR Foundation". But, what does this exactly implies? I can download them freely, but can I use them in a commercial environment? Must I make public specialized archetypes or adaptations from them? Obviously, "I" is not me but anybody :-)
I have searched the openEHR page and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [886] Move existing rm_schema to new directory](https://discourse.openehr.org/t/ref-impl-eiffel-886-move-existing-rm-schema-to-new-directory/16204)
> Revision: 886
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [885] Add directory for reference model schemas](https://discourse.openehr.org/t/ref-impl-eiffel-885-add-directory-for-reference-model-schemas/14346)
> Revision: 885
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [request AQL builder link](https://discourse.openehr.org/t/request-aql-builder-link/13322)
> hi dear all,
is there any AQL builder available to use, the AQL builder of ocean is
not available to evaluate, can any body send evaluate download link to
ocean AQL builder or any similar tools\.
best regards\.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[500] Fix VCACA validation for CAPABILITY/credentials attributes (which is 1..1) in demographics archetypes](https://discourse.openehr.org/t/500-fix-vcaca-validation-for-capability-credentials-attributes-which-is-1-1-in-demographics-archetypes/13321)
> Revision: 500
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in adl-parser](https://discourse.openehr.org/t/bug-in-adl-parser/14926)
> Hi There,
There is a bug in adl-parser project about the existence of archetypes nodes. If a node exists with cardinality {0..*}, it is implicit that the node is OPTIONAL, but the parser consider it as REQUIRED. For example relationships is not necessary as defined in the following line but the ADLParser mark it as required.
relationships cardinality matches {0..*; ordered} matches {
The problem can be solved simply. Please find the patch...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Where can I find LIST archetype?](https://discourse.openehr.org/t/where-can-i-find-list-archetype/14021)
> hi all,
In openehr-demographic-PERSON.person.v1.adl
allow_archetype LIST matches {
include
id matches {"openehr-list_s.person_name.*"}
}
where can we find this kind of archetype: openehr-list_s.person_name.* ?
Kruy Vanna
+81 90 8344-3697
+81 423971721-101
Graduate School of Global Information and Telecommunication Studies,
Waseda University
- - - - - - - - - - - - -
[http://kvanna.multiply.com](http://kvanna.multiply.com)
[http://vannit.blogspot.com](http://vannit.blogspot.com)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ACME terminology](https://discourse.openehr.org/t/acme-terminology/16203)
> Hi There,
Is there any other source instead of down http://free.terminology.org/
site to search the ACME terms?
Bests,
Soheil
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [OSHIP Gets DSE](https://discourse.openehr.org/t/oship-gets-dse/13320)
> ```
The Open Source Health Information Platform (OSHIP) has integrated the
“gold standard” forward chaining inference engine CLIPS in order to
support complex decision support requirements.
OSHIP is based on the Python reference implementation of the openEHR
specifications; adding proven open source components to provide a web
services based development base for any type of healthcare application.
OSHIP is heavily internationalized. There are 12 translations started
with 4 major ones...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [MIE 2009 - openEHR related activities](https://discourse.openehr.org/t/mie-2009-openehr-related-activities/13319)
> MIE 2009 is located in Sarajevo this year. Programme: [http://www.mie2009.org/programme.php](http://www.mie2009.org/programme.php)
openEHR-related activities include:
**PAPERS**
*Mon 31 Aug*
Track A - CONGRESS HALL
17:40 - Engaging Clinicians in Clinical Content: Herding Cats or Piece of Cake? - Heather LESLIE, Sam HEARD, Sebastian GARDE, Ian MCNICOLL
Track B - ROOM BOSNIA
17:30 - An openEHR-Based Clinical Decision Support System: A Case Study - Hajar KASHFI
*Tue 1 Sep*
Track A -...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [parent of composition](https://discourse.openehr.org/t/parent-of-composition/12325)
> Hi, I have a question:
Which entity is the parent of a composition
A quick answer would be, the EHR\.
But that is impossible, because an EHR does not inherit from Locatable\.
So, better is, I have two questions:
What is the purpose of the Parent\-attribute of Composition?
How can I link from a Composition to the EHR where it uniquely to
belongs?
Maybe I missed or misunderstood something in the documentation?
Thanks
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [request link to archetype grammar](https://discourse.openehr.org/t/request-link-to-archetype-grammar/13313)
> hello all
can any body send a link to archetype grammar file.
is this file exist? like AQL grammar file witch is at
[http://www.openehr.org/wiki/download/attachments/2949295/AQL_grammar.txt?version=1](http://www.openehr.org/wiki/download/attachments/2949295/AQL_grammar.txt?version=1)
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Publication of the Blood Pressure and the Body Mass Index archetypes today](https://discourse.openehr.org/t/publication-of-the-blood-pressure-and-the-body-mass-index-archetypes-today/13327)
> Dear Colleagues,
2 archetypes published today! - only our 5th and 6th archetypes, but we are gathering momentum, with the rest of the Top 10 still progressively coming over the next few months and the other key archetype following on soon after.
Body Mass Index was completed reasonably quickly and after 2 review rounds - involving 17 clinicians/informaticians from 9 countries
But WOW - I was beginning to think that this day might never come! After 8 review rounds we have been able to come...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Error on DvOrdered, ref impl or in specs?](https://discourse.openehr.org/t/error-on-dvordered-ref-impl-or-in-specs/13328)
> Hi Rong,
In DvOrdered from java ref impl I found a diference between the fields declared here and the fields in the specs from UML here> [http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/architecture/computable/UML/uml_start_view.html](http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/architecture/computable/UML/uml_start_view.html)
DvOrdered in java ref impl have>
List> otherReferenceRanges;
DvInterval normalRange;
But in...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Editor for the openEHR wiki](https://discourse.openehr.org/t/editor-for-the-openehr-wiki/16654)
> Hi,
There have been number of spam users registered on the openEHR wiki
recently, mainly drug related\. Currently these are being reported to me
and I remove the users\. Manageing the content \(including
self\-regsitered users\) is not really a sysadmin task, and I would like
to see somebody from the openEHR community take on the responsibility of
monitoring and manageing this sort of thing\.
Seref Arikan, a post grad student working with David in CHIME has
noticed many of these spam...
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [The DSE Sprint](https://discourse.openehr.org/t/the-dse-sprint/13314)
> Announcing the OSHIP Decision Support Engine \(DSE\) Sprint to be held at
UFF Niterói, RJ Brasil on 24 August, 2009\.
While the OSHIP DSE is fully functional at this point\.
During this one day sprint we will complete the demos for the decision
support engine and the developer instructions so that others can use the
CLIPS inference engine in their own applications\. We will also begin
work on the archetypes for the Epidemiologic Surveillance Support System
\(EpiS3\), a decision support...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Planning the MedInfo Connectathon](https://discourse.openehr.org/t/planning-the-medinfo-connectathon/14932)
> Hi All,
There doesn't seem to be much momentum for finishing up the openEHR
Extract and using that as a document format to build a true SOA for
openEHR; but we need some formal framework for a document and a
transport mechanism\.
I recently spoke to Sam Heard and he said that Ocean Informatics would
release the scripts that they have been using for CDA \(r1 & r2\)\. This
sounds to me to be the most reasonable solution\. Select one of them
\(r2?\)
As far as transport goes I...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[499] Bug fixes for advanced specialised archetype validation, including test cases](https://discourse.openehr.org/t/499-bug-fixes-for-advanced-specialised-archetype-validation-including-test-cases/13312)
> Revision: 499
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Developing OpenEHR teaching material.](https://discourse.openehr.org/t/developing-openehr-teaching-material/13315)
> Hi,
I am developing teaching material on openEHR for our undergraduate course\.
Most approaches to teaching openEHR tend to be high level \- explaining
the need and advantages of using archetypes, guiding principles and so
on\. I am hoping to get away from this and to offer a more hands\-on
approach\. My aim is to develop material that leads my students to an
understanding of the problems of developing EHRs first, before
demonstrating how openEHR attempts to overcome these difficulties\.
I...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers Digest, Vol 32, Issue 13](https://discourse.openehr.org/t/openehr-implementers-digest-vol-32-issue-13/14927)
> > Hi Greg,
>
> The Answers you seek are in understanding of the overview and of the
> reference model. Without them; archetypes have no meaning.
>
> --Tim
>
> >
> > I agree that extract is a dull word.
> >
> > The problem we still seem to be missing key pieces. The xml e.g.
> >
> > [http://www.openehr.org/svn/ref_impl_java/SANDBOX/ehr-bank/src/res/xml/blood-glucose-sample.xml](http://www.openehr.org/svn/ref_impl_java/SANDBOX/ehr-bank/src/res/xml/blood-glucose-sample.xml)
> >
> > does not seem...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[498] Add initial validation for specialised archetypes (most error types)](https://discourse.openehr.org/t/498-add-initial-validation-for-specialised-archetypes-most-error-types/13311)
> Revision: 498
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Loading archetypes referenced by ArchetypeSlots](https://discourse.openehr.org/t/loading-archetypes-referenced-by-archetypeslots/16202)
> Hi,
I'm doing some archetype modeling and loading tests with Java Ref Impl\.
I have two ACTION archetypes and a COMPOSITION archetype that
references the two ACTION archetypes:
content cardinality matches \{0\.\.\*; unordered\} matches \{
allow\_archetype ACTION occurrences matches \{0\.\.1\} matches \{
include
archetype\_id/value matches...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [We Are Implementing the Wrong Specs -- Humor](https://discourse.openehr.org/t/we-are-implementing-the-wrong-specs-humor/16201)
> Hi Tim,
I was on the lecture of Dr John Halamka at August 7\. It was very
stimulating and related 'http://www.hitsp.org/'. The streaming video of
the lecture will be available soon\. I will announce to this list to
share\.
Chees,
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Loading archetypes referenced by ArchetypeSlots](https://discourse.openehr.org/t/loading-archetypes-referenced-by-archetypeslots/16655)
> Hi,
I'm doing some archetype modeling and loading tests with Java Ref Impl\.
I have two ACTION archetypes and a COMPOSITION archetype that references the
two ACTION archetypes:
content cardinality matches \{0\.\.\*; unordered\} matches \{
allow\_archetype ACTION occurrences matches \{0\.\.1\} matches \{
include
archetype\_id/value matches...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [DADL Implementation](https://discourse.openehr.org/t/dadl-implementation/13309)
> Hi Soheil,
You can find it in the sandbox area:
http://www.openehr.org/svn/ref_impl_java/SANDBOX/dadl-parser/
Cheers,
Rong
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [OSHIP Update](https://discourse.openehr.org/t/oship-update/13310)
> Hi All,
It has been awhile since I've sent out an update but that doesn't mean
things are not happening\.
First of all the translators are working hard\. Especially Eduardo and
Roberto\.
https://translations.launchpad.net/oship/trunk/+pots/oship I have just
update the trunk with the latest translations\.
Also I'm work on adding the decision support engine \(dse\) to OSHIP\. It
consists on the "gold standard" inference engine CLIPS using the PyClips
wrapper\. It...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Please review your mailing list subscriptions (recent DNS problems)](https://discourse.openehr.org/t/please-review-your-mailing-list-subscriptions-recent-dns-problems/13303)
> Dear all,
due to the recent DNS problem at the provider where the openEHR\.org
domain name is managed, some community members may have been
unsubscribed from lists due to 'excessive bounces'\. If you suspect you
have been unsubscribed I recommend you visit the list management site \-
the links are here: http://www.openehr.org/community/mailinglists.html
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [request DADL project link](https://discourse.openehr.org/t/request-dadl-project-link/16652)
> hi dear sir
i am tring the java implementation of openehr and i am looking for the
**org.openehr.am.parser.DADLParser** and the **DADLBinding**
but i cant find them in the
**[http://www.openehr.org/svn/ref_impl_java/](http://www.openehr.org/svn/ref_impl_java/)** source repository
would you please help me to find the correct downloaded link
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [First release of a new Eclipse plugin for the Opereffa framework](https://discourse.openehr.org/t/first-release-of-a-new-eclipse-plugin-for-the-opereffa-framework/13308)
> \(Sent on behalf of serefarikan@kurumsalteknoloji\.com, please do not
reply to this address\)
Dear members of the openEHR community,
We would like to announce the first release of a new Eclipse plugin for
the Opereffa framework\. This contains all the current tooling provided
by Opereffa and is expected to become the focus of all our tooling work
in the Eclipse environment\.
The plugin utilises the current codebase of Opereffa and can be used to
work on any archetypes which stay within...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [884] AWB-166: Override PLATFORM for the .NET ADL Parser DLL, to avoid calling an external C function to figure out whether it's running on .NET.](https://discourse.openehr.org/t/ref-impl-eiffel-884-awb-166-override-platform-for-the-net-adl-parser-dll-to-avoid-calling-an-external-c-function-to-figure-out-whether-its-running-on-net/13307)
> Revision: 884
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Next archetypes for review in CKM](https://discourse.openehr.org/t/next-archetypes-for-review-in-ckm/16200)
> Many thanks for those who voted in the 'Top 10 archetypes for use in an Emergency' poll.
Following up from the [results](http://www.openehr.org/wiki/display/healthmod/Poll+Results+-+Top+10+archetypes+for+use+in+an+Emergency) of the Poll for the next 10 archetype concepts for review in CKM, I propose that the next archetypes that will be initiated for review are:
- [Heart Rate](http://openehr.org/knowledge/OKM.html#showArchetype_1013.1.170) (and this will be closely followed by it's...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [883] AWB-146: Update documentation to EiffelStudio 6.4.](https://discourse.openehr.org/t/ref-impl-eiffel-883-awb-146-update-documentation-to-eiffelstudio-6-4/16199)
> Revision: 883
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[497] Added VCACA validation to the Archetype Validator.](https://discourse.openehr.org/t/497-added-vcaca-validation-to-the-archetype-validator/16198)
> Revision: 497
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issues around UI technologies and bindings to back end (gjb)](https://discourse.openehr.org/t/issues-around-ui-technologies-and-bindings-to-back-end-gjb/13304)
> > 1. Re: Issues around UI technologies and bindings to back end (gjb)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Jul 2009 17:16:18 +0200
> From: gjb <[gjb@crs4.it](mailto:gjb@crs4.it)>
> Subject: Re: Issues around UI technologies and bindings to back end
> To: For openEHR technical discussions <[openehr-technical@openehr.org](mailto:openehr-technical@openehr.org)>
> Message-ID:...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [question about Party](https://discourse.openehr.org/t/question-about-party/14924)
> PERSON inherits from Locatable, and Locatable has the attribute ownerId\.
It is not allowed to leave it empty\.
Who is the owner of a PERSON \(f\.e\. representing a patient\)
If someone knows the answer\.
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [881] Minor corrections to do with VATDF and VACDF validity rules.](https://discourse.openehr.org/t/ref-impl-eiffel-881-minor-corrections-to-do-with-vatdf-and-vacdf-validity-rules/16197)
> Revision: 881
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[495] fixed two duplicated openehr concept ids in the terminology xml file](https://discourse.openehr.org/t/495-fixed-two-duplicated-openehr-concept-ids-in-the-terminology-xml-file/16196)
> Revision: 495
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [880] Corrections to previous changes:](https://discourse.openehr.org/t/ref-impl-eiffel-880-corrections-to-previous-changes/13306)
> Revision: 880
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [879] Various validation improvements:](https://discourse.openehr.org/t/ref-impl-eiffel-879-various-validation-improvements/13297)
> Revision: 879
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from timothywayne.cook@gmail.com requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-timothywayne-cook-gmail-com-requires-approval/14310)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@openehr\.org
Reason: Message body is too big: 43155 bytes with a limit of 40 KB
At your convenience, visit:
http://lists.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
to approve or deny the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM - 250th registered user](https://discourse.openehr.org/t/ckm-250th-registered-user/16651)
> Hi everyone,
We just had our 250th user register in the Clinical Knowledge Manager today! Seems like a pretty good milestone to share and celebrate to me!
Seem more [user stats](http://openehr.org/knowledge/#userstatistics) here: 95 reviewers, 24 translators, 42 countries
[www.openehr.org/knowledge](http://www.openehr.org/knowledge)
Regards
Heather
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Results of the openEHR poll - Top archetypes/concepts for use in an Emergency](https://discourse.openehr.org/t/results-of-the-openehr-poll-top-archetypes-concepts-for-use-in-an-emergency/14309)
> The Poll closed last Friday - see the full results on the [openEHR wiki](http://www.openehr.org/wiki/display/healthmod/Poll+Results+-+Top+10+archetypes+for+use+in+an+Emergency).
The Top 11 concepts voted by the community were:
1. Medication
1. Problem/Diagnosis
1. Adverse Reaction
1. Vital Signs group
1. Laboratory report
1. Alert
1. Blood Group
1. Procedure
1. Admission/Episode
1. Clinical Synopsis
As a direct result of the poll, there are more than 10 archetypes that will need to be...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[494] improved utf-8 bom support](https://discourse.openehr.org/t/494-improved-utf-8-bom-support/13295)
> Revision: 494
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-EHR-OBSERVATION.body_weight.v1 has been published](https://discourse.openehr.org/t/openehr-ehr-observation-body-weight-v1-has-been-published/14916)
> Dear colleagues,
The Weight archetype (openEHR-EHR-OBSERVATION.body_weight.v1) has completed a team review process and has been published in the Clinical Knowledge Manager today.
Reviews for its' specialisations - Adjusted weight and Birth weight - will be initiated shortly.
As a reminder, the other archetypes that are currently in Team Review are:
> **Concept** | **Archetype ID** |
> - | - |
> Blood Pressure
| openEHR-EHR-OBSERVATION.blood_pressure.v1 |
> Height/Length
|...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [More expressivity needed](https://discourse.openehr.org/t/more-expressivity-needed/14920)
> Hi All,
I have a use case which I am having quite hard time to model. The thing is in fact very simple to express with a tabular list, spreadsheet or XML - which we do not fancy much because ADL is claimed to have much more expressive power (well in general yes)!
Here is the use-case:
A CLUSTER archetype for depicting the anatomical sites of a finding for a given organ. The clinical domain is digestive endoscopy but this applies to others I think.
So we have an organ, then list of sites...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [IP Issues in medical practice](https://discourse.openehr.org/t/ip-issues-in-medical-practice/13299)
> Dear members of the list,
I'd like share with you an interesting lawsuit, which you may find interesting. It is not directly related to focus of this group, and but regarding current work around licencing issues of archetypes, the future may hold some nasty surprizes, especially when people realize the actual value of this community's joint work. Even if the lawsuit is not about our type of effort, it would be a mistake to underestimate the creativity of...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR terminology - wiki page](https://discourse.openehr.org/t/openehr-terminology-wiki-page/14913)
> various people have \(justifiably\) complained about the openEHR
terminology file currently in the official release\. It has been
suggested that the Java project one should be used to replace this\. I
have created a wiki page help discuss this \- see
http://www.openehr.org/wiki/display/spec/openEHR+Terminology
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issues around UI technologies and bindings to back end](https://discourse.openehr.org/t/issues-around-ui-technologies-and-bindings-to-back-end/14010)
> Hi,
Even if it feels a little bit too implementation related I'd like to get your opinions about the various UI implementation ideas/practices you may have, especially about web based applications.
I've written an initial set of things here : [http://www.openehr.org/wiki/display/projects/Technology+and+architecture+challenges+in+UI+implementation](http://www.openehr.org/wiki/display/projects/Technology+and+architecture+challenges+in+UI+implementation). based on Opereffa, but I'd really like...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Inger Wejerfelt är inte på kontoret/not in office......](https://discourse.openehr.org/t/inger-wejerfelt-ar-inte-pa-kontoret-not-in-office/13294)
> Jag kommer att vara borta från kontoret fr.o.m. 2009-07-20 och kommer inte tillbaka förrän 2009-08-24.
Jag kommer då att ta hand om alla inkomna mail.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - ['10 archetypes that could save a life' - poll closes this Friday, July 24](https://discourse.openehr.org/t/10-archetypes-that-could-save-a-life-poll-closes-this-friday-july-24/14921)
> Hi Everyone,
It has been proposed that the priorities and focus of the next [Clinical Knowledge Manager](http://www.openEHR.org/knowledge) archetype reviews be on achieving agreement and consensus on the 10 key archetypes that would support healthcare provision in a typical crisis situation. Effectively these archetypes would contain clinical content that the openEHR community regard as the most important components of any Emergency Summary. More colloquially, we could refer to them as '10...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [home page modifications](https://discourse.openehr.org/t/home-page-modifications/14912)
> Dear all,
I have made some slight changes on the right hand side of the openEHR Home page. It seems I have to publish them live (I know this is evil, but if you don't do that, Daisy does something really stupid - it puts a huge yellow banner across the top of the page saying 'this is not the latest'..... maybe it can be done with 'variants'? Don't have the time to work it out...).
Anyway, the links are the same as the used to be, but now:
- better organised, easier to see?
- there are two...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Clinical Knowledge Manager - new version](https://discourse.openehr.org/t/clinical-knowledge-manager-new-version/16195)
> Dear all,
We have uploaded a new version of the Clinical Knowledge Manager (CKM) to [http://www.openehr.org/knowledge](http://www.openehr.org/knowledge)
As you can see from the new User Statistics (which is directly available at [http://openehr.org/knowledge/#userstatistics](http://openehr.org/knowledge/#userstatistics) or via the Reports/User Statistics menu), we already have an amazing diversity of users' countries, professions and health domains.
It is now even easier to adopt an...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [878] Correct a comment which was no longer applicable.](https://discourse.openehr.org/t/ref-impl-eiffel-878-correct-a-comment-which-was-no-longer-applicable/16194)
> Revision: 878
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [877] Minor corrections to error processing of cardinality etc; currently the compiler is strict on everything.](https://discourse.openehr.org/t/ref-impl-eiffel-877-minor-corrections-to-error-processing-of-cardinality-etc-currently-the-compiler-is-strict-on-everything/16193)
> Revision: 877
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [876] Change INTERVAL.is_equal to equal_interval, and make all comparisons between INTERVAL[INTEGER] objects and also between MULTIPLICITY_INTERVAL objects use this instead of the standard is_equal.](https://discourse.openehr.org/t/ref-impl-eiffel-876-change-interval-is-equal-to-equal-interval-and-make-all-comparisons-between-interval-integer-objects-and-also-between-multiplicity-interval-objects-use-this-instead-of-the-standard-is-equal/14297)
> Revision: 876
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in CDvQuantity implementation?](https://discourse.openehr.org/t/bug-in-cdvquantity-implementation/14917)
> In Java Reference Implementation, class
org\.openehr\.am\.openehrprofile\.datatypes\.quantity\.CDvOrdinal should
specifying constraints on instances of DV\_ORDINAL\.
Similarly org\.openehr\.am\.openehrprofile\.datatypes\.quantity\.CDvQuantity
represents constrain instances of DV\_QUANTITY\.
While CDvQuantity extends and uses DvQuantity class of RM model,
CDvOrdinal extends and uses Ordinal class of AOM model\! Instead of
Ordinal class, I expected to have DvOrdinal, as indicated in...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [875] Make occurrences, cardinality and existence optional.](https://discourse.openehr.org/t/ref-impl-eiffel-875-make-occurrences-cardinality-and-existence-optional/16186)
> Revision: 875
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR / ISO 13606 archetypes - licensing and copyright .... again!](https://discourse.openehr.org/t/openehr-iso-13606-archetypes-licensing-and-copyright-again/16189)
> There have been many debates over the years about licensing and copyright for archetypes. Now the ADL 1.4 and related specifications are art of CEN and ISO 13606, and archetypes (as well as templates) are being created all over the world.
There is still no consensus on how they should be licensed - more specifically, what the guidelines should be to determine licensing. What copyright and licenses should be applied may well differ based on who creates them, what their purpose is, and also...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [openEHR Wiki permissions](https://discourse.openehr.org/t/openehr-wiki-permissions/14914)
> Dear all,
I have altered the wiki permissions such that there is a new group called 'editors', currently with members myself, Tony Shannon and Heather Leslie. I have added this group to the groups permissions in the 'education', 'health information models' and 'healthcare' spaces, and made the permissions slightly greater than normal users, by adding the ability to 'restrict' view and edit rights to a page within the space.
The idea is that someone (the current requestor was Tony) would...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Vote on the next archetypes for review in CKM](https://discourse.openehr.org/t/vote-on-the-next-archetypes-for-review-in-ckm/16187)
> Dear Colleagues,
It has been proposed that the priorities and focus of the next Clinical Knowledge Manager[](http://www.openEHR.org/knowledge) archetype reviews be on achieving agreement and consensus on the 10 key archetypes that would support healthcare provision in a typical crisis situation. Effectively these archetypes would contain clinical content that the openEHR community regard as the most important components of any Emergency Summary. More colloquially, we could refer to them as...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Quero que você entre no Facebook](https://discourse.openehr.org/t/quero-que-voce-entre-no-facebook/16185)
>
[ ](http://www.facebook.com/p.php?i=1014909081&k=Z6EU64UXV66DUCD1QB63Y4X2UWEE)
|
Jussara Macedo Rötzsch tem:
42 amigos
0 fotos
0 notas
2 mensagens no mural
2 grupos
|
# Quero que você entre no Facebook
Olá...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EHR and its versioned objects](https://discourse.openehr.org/t/ehr-and-its-versioned-objects/16191)
> Hi there,
I was reading the documents and specifications of OpenEHR EHR. As far as I read, EHR class has some fields of type OBJECT_REF (e.g. status, compositions, ...).
These fields are all **versioned** and the details of each version can be found in the contributions of the EHR.
So, there are two possibilities hear that I can not get which one is corret:
1. The OBJECT_REF points to an object that is a real object, not a version one. For example the reference points to an object of type...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Simple tutorial to save and load data from DB using Opereffa.](https://discourse.openehr.org/t/simple-tutorial-to-save-and-load-data-from-db-using-opereffa/16653)
> For those who asked for a leaner sample of Opereffa, the wiki has a simple tutorial, based on a class submitted into SVN.
It performs the very basic task of entering data using an archetype, saving it to DB, loading it back and printing values to console.
Pablo, and few others who asked for such an example will hopefully find this...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR in £1.1m Wellcome Trust Sintero project](https://discourse.openehr.org/t/openehr-in-1-1m-wellcome-trust-sintero-project/16188)
> The *open*EHR health computing platform will be used as the basis of the core clinical repository for the Sintero project ([http://www.cs.cf.ac.uk/newsandevents/wellcome.html](http://www.cs.cf.ac.uk/newsandevents/wellcome.html)), funded by a £1.1m grant from the Wellcome Trust. The central aim of Sintero is to provide a reliable means of solving a key problem in medical research: the difficulty (often an economic impossibility) of semantically aggregating data from multiple sources, and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [governance and identification - new draft available](https://discourse.openehr.org/t/governance-and-identification-new-draft-available/16190)
> For those interested in artefact governance and identification issues,
there is a new draft of the identification document available\. See
http://www.openehr.org/wiki/display/spec/Development+and+Governance+of+Knowledge+Artefacts
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [874] AWB-146: Upgrade to EiffelStudio 6.4 on non-Windows platforms: one of the classes that is not compiled on Windows was still using "attached" as an assertion tag.](https://discourse.openehr.org/t/ref-impl-eiffel-874-awb-146-upgrade-to-eiffelstudio-6-4-on-non-windows-platforms-one-of-the-classes-that-is-not-compiled-on-windows-was-still-using-attached-as-an-assertion-tag/14283)
> Revision: 874
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [next clinical steps in openEHR? SOAP+/-Emergency Summary via Opereffa+CKM?](https://discourse.openehr.org/t/next-clinical-steps-in-openehr-soap-emergency-summary-via-opereffa-ckm/14919)
> Dear all,
Many thanks Stef and others for the recent encouraging emails since the
Opereffa announcement\.
Now that folk has have a little time to digest that news, I wanted to
follow up with an email probing about next steps for the openEHR
clinical community to take\.
\#Recap on direction of travel\- need for an openEHR showcase
I have made the case in the past that the focus of our work must be
about helping healthcare staff improve their services with better
information and better...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CKM update](https://discourse.openehr.org/t/ckm-update/13301)
> Dear Colleagues,
The archetype team review and communication process has been refined and enhanced over the past couple of months since the formal launch of CKM. In that time we have agreed and published the clinical content for two archetype specifications, and we currently have 8 archetypes undergoing content review.
It has been a somewhat slow and gentle start to all appearances, but I assure you that there has been much activity happening 'under the surface'.
The Statistics page, found...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Adverse Reaction archetype - review round initiated](https://discourse.openehr.org/t/adverse-reaction-archetype-review-round-initiated/14922)
> Dear Colleagues,
A review round for the Adverse Reaction archetype was initiated today. This is a significant archetype that requires careful and considered collaboration and I would like to ensure that we have the best team reviewing the specs as we can.
Current reviewers comprise the openEHR Archetype Editorial Group plus existing adopters of the archetype, however we welcome broader expertise from the broader openEHR community.
If you, or one of your colleagues, would like to...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [proposal for better slot semantics](https://discourse.openehr.org/t/proposal-for-better-slot-semantics/13984)
> I have put up a new wiki page at
http://www.openehr.org/wiki/display/spec/Towards+a+definition+of+%27slot%27+semantics
on how to better understand slot semantics\. The idea is to a\) fix some
existing problems in archetypes and b\) get as much as possible of the
template semantics into the ADL/AOM formalism\.
reactions welcome\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [LinkingIn, Facebooking and Twittering openEHR](https://discourse.openehr.org/t/linkingin-facebooking-and-twittering-openehr/13300)
> Dear colleagues,
There is no doubt that one of the strengths of openEHR is the activity and connectedness within the openEHR community. I'm also intrigued by the social networking tools that have arisen in recent years.
So, slightly orthogonal to the usual list content and at the risk of preaching to those who are far more advanced than I, thought I might share some tools and sites that I've been exploring - with the intent to connect openEHR community members in other ways and to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [LinkingIn, Facebooking and Twittering openEHR](https://discourse.openehr.org/t/linkingin-facebooking-and-twittering-openehr/14918)
> Dear colleagues,
There is no doubt that one of the strengths of openEHR is the activity and connectedness within the openEHR community. I'm also intrigued by the social networking tools that have arisen in recent years.
So, slightly orthogonal to the usual list content and at the risk of preaching to those who are far more advanced than I, thought I might share some tools and sites that I've been exploring - with the intent to connect openEHR community members in other ways and to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [optional existence, cardinality and occurrences.](https://discourse.openehr.org/t/optional-existence-cardinality-and-occurrences/14915)
> Dear all,
as part of the specialisation semantics, which are nearly all
implemented in the ADL workbench, we have made existence, cardinality
and occurrences all optional\. This is sensible for 'source' form
archetypes \- i\.e\. it is natural that only overridden constraints be
stated in an archetype, if there is no override of either the reference
model or a specialisation parent archetype, where the latter is
relevant, then no constraint is needed\.
The change is described in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [cADL assertion, invariant, validity - any practical examples of use?](https://discourse.openehr.org/t/cadl-assertion-invariant-validity-any-practical-examples-of-use/14270)
> Hi
I'm considering how I might constrain layout in an EHR GUI depending
on constraint made in an adl file\.
cADL assertions look a plausible way to go\.
But I don't see anyone using the invariant keyword in their ADL files
\- has anyone got any practical examples of doing so?
Any help gratefully accepted\.
Gavin Brelstaff
Sardinia
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [{Disarmed} editor: no object orientation features](https://discourse.openehr.org/t/disarmed-editor-no-object-orientation-features/13957)
> Dear all,
I wonder you experience the same experience that if you are creating a more complex cluster based archetype you want to copy and paste a small structure from one cluster into another, but the editor does not allow this.
(on behalf of DCM work I am trying to see if the HL7 allergy and intolerance model can be transformed into an archetype).
Any tricks to be able to reuse small archetype strucetures into creating a new one? Now I have to create each single structure over and over...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [873] Initial working version of 'has_path' fnction for Basic meta-model - checks if a path can exist in reference model, taking into account any possible object structure, including dynamic attachment of subtypes.](https://discourse.openehr.org/t/ref-impl-eiffel-873-initial-working-version-of-has-path-fnction-for-basic-meta-model-checks-if-a-path-can-exist-in-reference-model-taking-into-account-any-possible-object-structure-including-dynamic-attachment-of-subtypes/13293)
> Revision: 873
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [872] Improve the test that loads and compiles the validation test archetype repository.](https://discourse.openehr.org/t/ref-impl-eiffel-872-improve-the-test-that-loads-and-compiles-the-validation-test-archetype-repository/16182)
> Revision: 872
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Next archetype reviews in CKM](https://discourse.openehr.org/t/next-archetype-reviews-in-ckm/16184)
> I will be initiating some archetype review rounds in CKM over the next few days.
Archetypes:
> **Concept** | **Archetype ID** | **Review round about to commence**
|
> - | - | - |
> Blood Pressure | openEHR-EHR-OBSERVATION.blood_pressure.v1 | Round 7 |
> Height/Length | openEHR-EHR-OBSERVATION.height.v1 | Round 4 |
> Body Mass Index | openEHR-EHR-OBSERVATION.body_mass_index.v1 | Initial |
If you are interested in participating in any of these reviews please adopt the archetype to...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [871] Add a test that loads the test archetype repository and then compiles all of the validation test archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-871-add-a-test-that-loads-the-test-archetype-repository-and-then-compiles-all-of-the-validation-test-archetypes/16181)
> Revision: 871
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [test archetypes](https://discourse.openehr.org/t/test-archetypes/12321)
> hi,
as most of you know, there are test archetypes at [http://www.openehr.org/svn/knowledge/archetypes/dev/adl/test/](http://www.openehr.org/svn/knowledge/archetypes/dev/adl/test/)
We have made some attempts in the past to get these better organised, but have not been very systematic about it. To improve on the current situation, I propose the following that we adopt a regression testing approach. This means having both the input archetype and the expected output in each case. Given that we...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Improving Translation_details and other_contributors ?](https://discourse.openehr.org/t/improving-translation-details-and-other-contributors/14907)
> Dear all,
Ian, Heather and I have raised an issue at [http://www.openehr.org/issues/browse/SPECPR-24](http://www.openehr.org/issues/browse/SPECPR-24) for improving the Translation_details and other_contributors.
What seems to be current practice is that a translation will be done by more than one person and documenting this is not really supported by the model:
**TRANSLATION_DETAILS**
> accreditation :...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers subscription notification](https://discourse.openehr.org/t/openehr-implementers-subscription-notification/14903)
> Zanifa <zanifa\.omary@gmail\.com> has been successfully subscribed to
openEHR\-implementers\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [870] Add is_regexp to C_STRING](https://discourse.openehr.org/t/ref-impl-eiffel-870-add-is-regexp-to-c-string/14261)
> Revision: 870
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Get an instance of the RM from an Archetype](https://discourse.openehr.org/t/get-an-instance-of-the-rm-from-an-archetype/14902)
> Hi,
I see that the parsed definition section of an archetype is instanced to the constraint model, but the definition section is (in some way) also a description of the RM instance.
Is there some way to get an instance of the OpenEHR RM from a parsed archetype?
Thank you!
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [request for updates on commercial openEHR offerings](https://discourse.openehr.org/t/request-for-updates-on-commercial-openehr-offerings/14260)
> The page [http://www.openehr.org/shared-resources/usage/commercial.html](http://www.openehr.org/shared-resources/usage/commercial.html) gives information on commercial products and services offered based on *open*EHR, including open source products. The only qualification to be on this page is having products or services available use in a production environments on a general basis (this does not include academic offerings which may be embedded in e.g. teaching hospitals - these are included...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Announcement of the release of Opereffa by the openEHR Foundation](https://discourse.openehr.org/t/announcement-of-the-release-of-opereffa-by-the-openehr-foundation/14910)
> Dear Tony, David and Seref,
Congratulations to you (and to the openEHR community).
This is truly very good news, great work and a major milestone for the openEHR community.
I'm confident that this will boost many efforts that are out there a helps to focus our energy as well as to show the outside world what really can be done with openEHR.
Cheers,
Stef
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Opereffa - an openEHR reference application](https://discourse.openehr.org/t/opereffa-an-openehr-reference-application/16179)
> Announcement of the release of Opereffa by the *open*EHR Foundation
The *open*EHR Foundation is pleased to announce the early release of **Opereffa** – *open*EHR REFerence Framework and Application, under development at .
As healthcare systems are under increasing pressure, internationally, they are exploring improvements in health information systems, as a key way to survive and thrive in the 21st century. As a means to support these efforts, members now working under the umbrella of the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [abstract data types](https://discourse.openehr.org/t/abstract-data-types/14905)
> > Hi All,
Could it be possible to use an abstract data type (like DV_ORDERED, DV_AMOUNT, ...) as a type for any data?
Regards
Masoumeh
|
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DATA_VALUE](https://discourse.openehr.org/t/data-value/16170)
> > Dear All,
I have a question about DATA_VALUE class in data types:
Why all of the data types should be inherited from DATA_VALUE? What's the usefulness of this pattern?
Thanks in Advance
Masoumeh
|
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new masters thesis - openEHR case study at Australian hospital](https://discourse.openehr.org/t/new-masters-thesis-openehr-case-study-at-australian-hospital/12301)
> A masters thesis by Murat Gök from 2008 is now available at [http://www.openehr.org/shared-resources/publications/archetypes.html](http://www.openehr.org/shared-resources/publications/archetypes.html)
*Abstract*: this thesis reports a case study of an *open*EHR system at the Emergency Department, Austin Health, Melbourne, and arose from the collaboration with Austin Health, the Austin Centre for Applied Clinical Informatics (ACACI), the Nursing Informatics Group, the Biomedical Engineering...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [-- PatientOS OpenEHR Demo II @ HIMSS Virtual Conference](https://discourse.openehr.org/t/patientos-openehr-demo-ii-himss-virtual-conference/13291)
> Right they are two PatientOS demo systems. Basically one setup as a hospital which will pass results to the one setup as the Primary Care Clinic.
Of course it would be much more powerful (from an interoperability standpoint) if there was another vendor that had an online demo environment that could receive results - but the transport and parsing of the messages is less important than watching archetyped data being used in two very different applications - but with the same semantic context...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [-- PatientOS OpenEHR Demo II @ HIMSS Virtual Conference](https://discourse.openehr.org/t/patientos-openehr-demo-ii-himss-virtual-conference/13290)
> Right they are two PatientOS demo systems. Basically one setup as a hospital which will pass results to the one setup as the Primary Care Clinic.
Of course it would be much more powerful (from an interoperability standpoint) if there was another vendor that had an online demo environment that could receive results - but the transport and parsing of the messages is less important than watching archetyped data being used in two very different applications - but with the same semantic context...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [distributed development, governance and artefact identification for openEHR](https://discourse.openehr.org/t/distributed-development-governance-and-artefact-identification-for-openehr/14904)
> I have completed drafts of two documents I believe will come to be
important in openEHR in the near future\. The first describes a model of
distributed development and governance of knowledge artefacts, including
archetypes and templates\. The second defines an identification system
for these artefacts\. The first document is a rewrite of a document
called the 'Archetype System' from previous releases of openEHR, the
second is new\. A detailed description of a governance structure and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [-- PatientOS OpenEHR Demo II @ HIMSS Virtual Conference --](https://discourse.openehr.org/t/patientos-openehr-demo-ii-himss-virtual-conference/13289)
> We are going to have a live, hands on demo at the HIMSS Virtual Conference June 9-10 where in response to [Tony Shannons call to action](http://www.nabble.com/openEHR-in-2009-and-beyond..-a-view-of-the-way-forward-td21623065.html) we will
1) Provide a live Physician Office environment
2) Provide a live Hospital environment
3) Demonstrate various workflows in both (office visit, hospital closed loop medication management)
4) Demonstrate a patient portal with a consolidated view of the two...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Concept Overload Caution](https://discourse.openehr.org/t/concept-overload-caution/14909)
> Hi All,
The past 3 or 4 subjects on this list takes me back to conversations
that we had before \(maybe several years ago?\) when we were discussing
slots and links\. Maybe they were here maybe they were on the ARB list\.
I do not recall now\.
But my feeling in both of these areas are that there is a tendency for
archetype developers to create archetypes that are more than one
clinical concept\. IIRC, that is about the time that templates were
being thought of/designed to alleviate the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Item_Tree](https://discourse.openehr.org/t/item-tree/14908)
> Hi all,
Where can I use an Item_Tree class? There are some existing Item-Tree s that I want to reuse, but it sounds that I cannot embed them in observation,sections or clusters. What's the aim of creating Item_Tree?
Regards
Pariya
MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of Technology
[http://www.chalmers.se/cse/EN/people/kashfi-hajar](http://www.chalmers.se/cse/EN/people/kashfi-hajar)
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [869] AWB-146: Upgrade to EiffelStudio 6.4.78984.](https://discourse.openehr.org/t/ref-impl-eiffel-869-awb-146-upgrade-to-eiffelstudio-6-4-78984/16171)
> Revision: 869
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetyping links](https://discourse.openehr.org/t/archetyping-links/14906)
> Dear Everyone,
what are the possibilites of constraining the LINK\.target attribute
\(DV\_EHR\_UIR datatype\) in an archetype? This was possible in earlier
versions of the Ocean Archetype Editor \(although its use never was clear
to me\)\. Let's say that I want to constrain a link from an archetype to
only allow linkage to instances conforming a specific set of archetypes
\(e\.g\. allowing linkage only to Diagnosis\-archetype instances for links
with "complication of"...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Medinfo 2010](https://discourse.openehr.org/t/medinfo-2010/14994)
> Hi, all
In the next year 2010, Medinfo 2010 will be held in Captown, South
Africa\.\(http://medinfo2010.org/)
I would like to have a workshop in the openEHR implementation in Eiffel,
Java, Python and Ruby to examine the universality and availability of
openEHR specification\. It is interesting that each implementation has
its own feature in contrast\.
Fortunately our Ruby implementation is progressing step by step, some
demo will be shown in the session\.
I would like to hear comments by...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Representing knowledge in Archetypes/Templates or external rules](https://discourse.openehr.org/t/representing-knowledge-in-archetypes-templates-or-external-rules/15571)
> Dear All,
I have encountered a question regarding knowledge representation during archetype designing.
Let's say a list of some special drugs that patient has used is important for Evaluation. I have two options here: First, to apply one external rule during the data entry, and mark the patient as e.g X-affected. Secondly, to represent this knowledge in Templates/Archetypes I am designing. It can be in the form of an Item-Tree-Medication-List using internal codes ( to specify medications that...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [data types XML representation](https://discourse.openehr.org/t/data-types-xml-representation/16169)
> >
Hi All,
I have a question about XML representation of data types:
in an XML file, each attribute of a data type has to be a tag and if the data type has one or many parent, the parents' attributes should be included as different tags. The point is that in some data types, the type of an attribute is another data type and when you want to represent it in an XML, there would be confusion. For example, this is an XML part for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Enquiry - status of academic work on openEHR / archetypes / related](https://discourse.openehr.org/t/enquiry-status-of-academic-work-on-openehr-archetypes-related/16172)
> The page http://www.openehr.org/shared-resources/usage/academic.html
shows what we currently know of academic \(including university hospital\)
work with openEHR, archetypes etc\.
This is a request for updates and additions to these pages\. One of the
goals of these pages is to help other people in academia, government or
elsewhere look at your work, so up to date and precise contact
information and web\-site URLs are important for this\. In order to
maintain privacy, I suggest that email...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SLots in archetypes](https://discourse.openehr.org/t/slots-in-archetypes/14897)
> Hello,
In archetype-editor one item type is Slot which only accepts archetypes in form of Cluster or Element as constraint on that slot. Is there any way to put a slot for including one Observation in another? Is the only way of putting two Observations together is using templates?
Regards
Pariya
MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [data types XML representation](https://discourse.openehr.org/t/data-types-xml-representation/16168)
> >
Hi All,
I have a question about XML representation of data types:
in an XML file, each attribute of a data type has to be a tag and if the data type has one or many parent, the parents' attributes should be included as different tags. The point is that in some data types, the type of an attribute is another data type and when you want to represent it in an XML, there would be confusion. For example, this is an XML part for...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [868] Add a test demonstrating a bug in INTERVAL.is_equal.](https://discourse.openehr.org/t/ref-impl-eiffel-868-add-a-test-demonstrating-a-bug-in-interval-is-equal/13288)
> Revision: 868
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [866] AWB-146: Run all classes have been run through the Eiffel Syntax Updater (http://www.eiffelroom.com/tool/eiffel_syntax_updater).](https://discourse.openehr.org/t/ref-impl-eiffel-866-awb-146-run-all-classes-have-been-run-through-the-eiffel-syntax-updater-http-www-eiffelroom-com-tool-eiffel-syntax-updater/13286)
> Revision: 866
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [864] AWB-146: Upgrade to EiffelStudio 6.4.78765:](https://discourse.openehr.org/t/ref-impl-eiffel-864-awb-146-upgrade-to-eiffelstudio-6-4-78765/13284)
> Revision: 864
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XSD incompatibilites with XSLT code](https://discourse.openehr.org/t/xsd-incompatibilites-with-xslt-code/14896)
> Hello,
we have created a template with the Template Designer \(Version 2\.4\)\. It
contains the Report archetype \(openEHR\-EHR\-COMPOSITION\.report\.v1\) that
is built as a composition that allows to put generic content in it\. We
put e\.g\. some Lab\-Data in\.
When we export the "Template Data Schema" we get a schema file that
seems not to be compatible with the openEHR information model\.
Please have a look at the code snippet i provide below the text\!
A compostition must have...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[493] Fixed missing nodeId in archetype_slot parsing.](https://discourse.openehr.org/t/493-fixed-missing-nodeid-in-archetype-slot-parsing/13282)
> Revision: 493
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [continuum upgrade](https://discourse.openehr.org/t/continuum-upgrade/13281)
> Hi all,
The java project's continuous integration server is currently off line
for upgrade\. I will let you know once it's back online\.
Cheers,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[492] Adjusted pom files due to url change of Svn repository](https://discourse.openehr.org/t/492-adjusted-pom-files-due-to-url-change-of-svn-repository/13280)
> Revision: 492
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[491] Correct parsing of Translator Accreditations.](https://discourse.openehr.org/t/491-correct-parsing-of-translator-accreditations/16167)
> Revision: 491
Author: sebastian\.garde
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Reminder: openEHR site outage for software upgrades](https://discourse.openehr.org/t/reminder-openehr-site-outage-for-software-upgrades/13275)
> REMINDER of service outage
The first of the scheduled upgrades will be taking place this Wedneday
\(13th May 2009\) between 08:00 and 12:00 BST, further details below\.
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [[ Notice of closure of svn.openehr.org]](https://discourse.openehr.org/t/notice-of-closure-of-svn-openehr-org/16166)
> Hi,
The change detailed below has now been implemented\. Any requests to
svn\.openehr\.org will start to generate errors, please use the
instructions below to change your local repositories\.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [new download page for the java project](https://discourse.openehr.org/t/new-download-page-for-the-java-project/14895)
> Hi all,
I just created a new download page for the java project on the openEHR
wiki\. You can now find jar files from the Release 1\.0\.1 build there\.
The URL to this page is
http://www.openehr.org/wiki/display/projects/Java+Project+Download
The project page has been updated to reflect this change\.
Cheers,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[490] Archetype-Validator: Add missing support for DV_EHR_URI (with testcase)](https://discourse.openehr.org/t/490-archetype-validator-add-missing-support-for-dv-ehr-uri-with-testcase/16165)
> Revision: 490
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reverse_relationships](https://discourse.openehr.org/t/reverse-relationships/13918)
> I've been working through the demographic AT's that were provided by Sergio. It's probably due to my lack of technical knowlegde but I can't find where reverse_relationships are defined in these archetypes. Or it must be in openEHR-DEMOGRAPHIC-ROLE.health_consumer.v1 under:
relationships matches {
PARTY_RELATIONSHIP[at0010] matches { -- relationship between a health consumer and a third-party payer
details matches { -- we gaan er klaarblijkelijk vanuit dat er maar 1 relatie kan bestaan met...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Adjustment of the adl-parser license](https://discourse.openehr.org/t/adjustment-of-the-adl-parser-license/14202)
> Dear all,
The Java ADL\-parser was released under GPL in the past\. Due to recent
requests for a more liberal OSS license for the parser, it is now
released under Mozilla tri\-license, i\.e MPL 1\.1/GPL 2\.0/LGPL 2\.1\.
This also means that now all java components from the openEHR Java
reference implementation project are released under the Mozilla
tri\-license\. I think this move will ease the nerve of some commercial
developers who are using our java components\. ;\-\)
Cheers,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[489] Adjusted the license of adl-parser to Mozila tri-license](https://discourse.openehr.org/t/489-adjusted-the-license-of-adl-parser-to-mozila-tri-license/13274)
> Revision: 489
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Folders in Demographic Items](https://discourse.openehr.org/t/folders-in-demographic-items/14889)
> Hi,
I am reading the document
http://www.openehr.org/releases/1.0.1/architecture/rm/common_im.pdf
In there, Chapter 5, page 39 I read:
"It provides a means of versioning FOLDER structures over
time, which is useful in the EHR, Demographics service or anywhere else
where Folders are used to group things\."
But the only location I found in the Reference Model where it is
possible to start a directory is the EHR\.
Maybe I missed the other locations, can someone please help me out...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New version of the Clinical Knowledge Manager (CKM)](https://discourse.openehr.org/t/new-version-of-the-clinical-knowledge-manager-ckm/14201)
> Dear all,
we have uploaded a new version of the Clinical Knowledge Manager at [http://www.openehr.org/knowledge](http://www.openehr.org/knowledge)
Please note that when you are logged in, you have more functionality available. For example, you can always right-click on an archetype to "Adopt" it. Please do so - you will then be invited to be a reviewer for this archetype when it is up for review. This will also help us to work out the order of reviewing of archetypes, the more interest...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [863] AWB-146: Update adl_parser.ecf to build with EiffelStudio 6.4.78382.](https://discourse.openehr.org/t/ref-impl-eiffel-863-awb-146-update-adl-parser-ecf-to-build-with-eiffelstudio-6-4-78382/13273)
> Revision: 863
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage for software upgrades](https://discourse.openehr.org/t/openehr-site-outage-for-software-upgrades/13283)
> Hi,
In order for us to carry out essential software upgrades to the openEHR
server\. There will be two periods of service disruption this month\.
Although each session will be upgrading a single service, and the other
parts of the site should continue to be available, it may be neccessary
to restart other parts of the servive, so the site should be considered
at risk during these periods\.
Wednesday 13th May 2009 \- Wiki \(Confluence\)
08:00 \- 10:00 BST \- Wiki software upgrade\. The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SVN problem fixed](https://discourse.openehr.org/t/svn-problem-fixed/13277)
> The problem with accessing some repositories yesterday has been fixed\.
The old URL http://svn.openehr.org has been turned off\. If you have an
error when doing an SVN operation on a local repository, check if this
is the initial part of the URL\. If it is, just do a Subversion
'relocate' operation \- in TortoiseSVN, this is very easy \- right click
on the repository root > Tortoise SVN > Relocate\. You can then enter the
new URL, according to the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Specification Problem Report issue tracker](https://discourse.openehr.org/t/openehr-specification-problem-report-issue-tracker/13269)
> In a recent post I mentioned that we would create a new public Problem Report
\(PR\) tracker on openEHR\.org for the purpose of raising issues on the
specifications\.
This has now been done \- see http://www.openehr.org/issues/browse/SPECPR
A number of existing PRs from the existing SPEC Jira project have been moved
to this tracker\. In future, the SPECPR project will be restricted to CRs
\(change requests\) of work actually done on the specifications\.
The permissions scheme in Jira can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SVN problems](https://discourse.openehr.org/t/svn-problems/13276)
> We appear to be experiencing technical difficulties with the Subversion site
on openEHR\.org right now \- this is being addressed right now\. Sorry for the
inconvenience \- we will post an update as soon as we know the source of the
problem\.
\- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Notice of closure of svn.openehr.org](https://discourse.openehr.org/t/notice-of-closure-of-svn-openehr-org/13272)
> Hi,
In December 2007 a notice was posted informing all users of the openEHR
Subversion repository that the URL was changing\. The old URL will now
be disabled, all subversion users should now be using the new URL as
detailed below\.
The original message is in the archives at:
http://www.openehr.org/mailarchives/openehr-announce/msg00050.html
And copied below\.\.\.
"To: all users of openEHR Subversion repositories\.
All openEHR Subversion repositories have been relocated in a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Release 1.0.1 of the Java Implementation](https://discourse.openehr.org/t/release-1-0-1-of-the-java-implementation/13271)
> Dear all,
The version 1\.0\.1 of the Java implementation is just released\. All the
sub\-components have the same version number as this release number,
which is 1\.0\.1 now\.
The release branch is here:
http://svn.openehr.org/ref_impl_java/BRANCHES/Release-1.0.1
And the tag: http://svn.openehr.org/ref_impl_java/TAGS/Release-1.0.1
This clears the way for new development on the ADL 1\.5 and Template on
the trunk\.
Please report on the list any anomalies that might be introduced by
this...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[488] Tag release 1.0.1](https://discourse.openehr.org/t/488-tag-release-1-0-1/13270)
> Revision: 488
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[487] Increase the trunk version number](https://discourse.openehr.org/t/487-increase-the-trunk-version-number/16164)
> Revision: 487
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[486] Increase the trunk version number](https://discourse.openehr.org/t/486-increase-the-trunk-version-number/16163)
> Revision: 486
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[485] Create 1.0.1 release branch.](https://discourse.openehr.org/t/485-create-1-0-1-release-branch/16161)
> Revision: 485
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[484] Prepare the trunk for 1.0.1 release](https://discourse.openehr.org/t/484-prepare-the-trunk-for-1-0-1-release/14185)
> Revision: 484
Author: rong\.chen
Log Message:
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [GELLO v.1 as a candidate openEHR CDS language - message reduced to <40kb, RESEND](https://discourse.openehr.org/t/gello-v-1-as-a-candidate-openehr-cds-language-message-reduced-to-40kb-resend/14890)
> Dear CDSSers
I am a newbie on this list but have followed and worked with archetypes
for a little while now\. I would like to talk about the strongly typed,
OO, declarative CDS language called GELLO\. This is a HL7 standrd that
wasn't really ever implemented\. OpenClinical gives a fair treatment of
the topic\. Our group \(Medical Objects\) has implemented it after some
work on resolving ambiguities in the BNF and the development of various
editors and interpreters such as a GELLO v\.1 ...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Issue rasied with content](https://discourse.openehr.org/t/issue-rasied-with-content/16162)
> Hi,
Just logged into Jira to modify some issues, noticed that people had
been adding issues that I wasn't aware of\. This one is not a sysadmin
problem, so I have closed the issue, but someone should probably look at
it\. What is the correct location for reporting these kind of things?
http://www.openehr.org/issues/browse/SYSADMIN-5
"1\) The document seems to have a property 'Title', which has the value
'main\.book' in stead of 'Archetype Principles' or...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[[JIRA] Created: (SPEC-302) Translations embedded in the ADL are not efficient and should instead use 'gettext' catalogs.]](https://discourse.openehr.org/t/jira-created-spec-302-translations-embedded-in-the-adl-are-not-efficient-and-should-instead-use-gettext-catalogs/15654)
> Hi All,
I raised the below CR and I wanted to open up discussion on this issue\.
Actually I brought it up a few years ago but I don't have a record of
where/when; now\.
I know that this have a major impact on implementers but I think the
current way we handle translations in ADL is a monster that is only
going to get worse\.
Thoughts?
\-\-Tim
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Java Ref Impl SVN password request](https://discourse.openehr.org/t/java-ref-impl-svn-password-request/15198)
> Hi,
Yesterday I have downloaded the java reference implementation from the svn site, but today I'm getting a password request:
# Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
The SVN has no more free access?
Thanks.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problems with java archetype parser](https://discourse.openehr.org/t/problems-with-java-archetype-parser/14888)
> Hi everyone,
I've downloaded the java parser jar from openehr site ([http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm](http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm)) and made a simple application to try it, but when I want to parse an archetype I get:
Exception in thread "main" java.lang.NoClassDefFoundError: org/openehr/rm/support/measurement/SimpleMeasurementService
at se.acode.openehr.parser.ADLParser.(ADLParser.java:49)
at...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [862] AWB-146: Migrate to building with EiffelStudio 6.4.78382.](https://discourse.openehr.org/t/ref-impl-eiffel-862-awb-146-migrate-to-building-with-eiffelstudio-6-4-78382/13266)
> Revision: 862
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [861] AWB-146: Migrate to building with EiffelStudio 6.4.78090:](https://discourse.openehr.org/t/ref-impl-eiffel-861-awb-146-migrate-to-building-with-eiffelstudio-6-4-78090/13260)
> Revision: 861
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Inspection vs Observation](https://discourse.openehr.org/t/inspection-vs-observation/14894)
> Hi all,
Considering these questions:
1- (asking patient) : Have you noticed any swelling of your salivary glands?
2- Inspection of salivary glands (Actually for this one, based on a suggestion from Ian I intend to create Cluster: Inspection- Salivary glands)
Should one just create one Observation or Cluster to use it for both cases or do you suggest another way of modeling these two concepts?
As you may notice, the first question is info. that the clinician receive from the patient by just...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - ["So semantic interoperability is a kind of philosopher's stone...."](https://discourse.openehr.org/t/so-semantic-interoperability-is-a-kind-of-philosophers-stone/13263)
> I have re\-posted this from the openEHR Technical list as I think
Seref's original technical post, prompted the beginnings of a
discussion which is decidedly more clinical and may run on, swamping
Seref's original query\.
I have tidied up the various responses to date below and included
Seref's original post, don't worry if this seems very technical \- the
key to this discussion is to read Derek Meyer's reply and this
paragraph in particular\.\.
"So semantic...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Layers of interoperability, OWL and openEHR](https://discourse.openehr.org/t/layers-of-interoperability-owl-and-openehr/13891)
> Dear members of the list,
I'd appreciate your opinions and guidance about a particular topic. As most of you probably know, the work in the ontology domain has been the flagship of semantic interoperability for many projects now, and there is a large amount of researchers active in the field.
I've been involved in use of ontologies for semantic interoperability for the first time in 2002, and since then, ontologies have become a frequently pronounced solution for a large set of...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Microsoft Connected Health Framework (CHF) uses archetypes](https://discourse.openehr.org/t/microsoft-connected-health-framework-chf-uses-archetypes/13255)
> The latest edition of Microsoft's Connected Health Framework \- a
strategy based on the idea of 'knowledge\-driven health' \(see
http://www.microsoft.com/industry/healthcare/technology/HealthFramework.mspx)
\- includes openEHR \(ISO 13606\-2\) archetypes as part of its domain
knowledge architecture\. There is much worth reading in this set of
documents, including a good analysis of the problem space, deployment
scenarios and issues, semantic and services architecture and much...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [proposed web home page change](https://discourse.openehr.org/t/proposed-web-home-page-change/13261)
> Dear all,
a few people have been thinking about changing the home page title \-
below the blue strip\. The suggestion is to change the 'Welcome to
openEHR' to "Welcome to openEHR \- specifications, tools and clinical
content to support e\-health"\. This is Tony Shannon's suggestion\. Others
may have other suggestions\.\.\.
thoughts?
\- thomas
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [[GELLO, archetypes and SNOMED-CT]](https://discourse.openehr.org/t/gello-archetypes-and-snomed-ct/13268)
>
[details="(attachments)"]
[GELLO, archetypes and SNOMED-CT.eml|attachment](upload://8I5vbsC21TjSKLcmP6j46ZfpUza.eml) (176 KB)
[/details]
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype-triggered events for CDSS](https://discourse.openehr.org/t/archetype-triggered-events-for-cdss/14893)
> Hi all,
In the paper "Archetype 101" by Heather and Sam, there's a short discussion about CDSS, here comes a quote from it:
"Intelligent generic decision support programs can rely on archetype-triggered events and for the
first time operate in real-time."
I wonder what is the exact meaning of Archetype-triggered events.
IS any research done in this area before or has any implementation based on that been used in a CDSS so far?
Regards
Pariya
PhD Student
Department of Computing Science and...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [maybe strange code-construct in DvOrdered used with DvDateTime? (also other combinations are possible)](https://discourse.openehr.org/t/maybe-strange-code-construct-in-dvordered-used-with-dvdatetime-also-other-combinations-are-possible/13267)
> Hi Rong, Ik would be happy, if you can spare some time coming days to
look at following question
Thanks,
Bert
When DvDateTime is constructed with only a string, which is possible\!
Then normalstatus and normalrange will not be set\.
When function "isNormal" is used an exception will be raised: "Both
normalRange and normalStatus null"
I wonder if that is a good combination, allowing to construct an object
in one way, but then raising an exception when it is used in its...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [possible error small error in BaseTypes.xsd (version 1.0.1)](https://discourse.openehr.org/t/possible-error-small-error-in-basetypes-xsd-version-1-0-1/14606)
> According to the documentation
\(http://www.openehr.org/releases/1.0.1/architecture/rm/data_types_im.pdf) should
<xs:complexType name="DV\_AMOUNT">
be marked abstract\.
Bert
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Update on requirements for openEHR clinical reference framework/application](https://discourse.openehr.org/t/update-on-requirements-for-openehr-clinical-reference-framework-application/13262)
> Dear Colleagues,
Further to our recent announcement of the very important release of the openEHR Clinical Knowledge Manager \(http://www.openehr.org/knowledge/)... I wanted to give you an update on the requirements for an openEHR clinical reference framework/application that have recently been collated from the clinical community\.
The feedback to my request for folks "top 5" clinical requirements for this solution generated very positive and interesting ideas\. Having now...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [problems and solutions for grouping and ordering in ADL / AOM](https://discourse.openehr.org/t/problems-and-solutions-for-grouping-and-ordering-in-adl-aom/14409)
> A number of problems have surfaced over the last couple of years of
archetype modelling that the tools and sometimes the underlying
formalism do not adequately deal with\. Many of these are to do with
being able to control the items within a container attribute, such as
inside SECTIONs, CLUSTERs, and the many other places in the openEHR
reference model where attributes can have multiple members\. It has taken
quite some time to understand the problems and come up with an analysis
which deals...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR Clinical Knowledge Manager offers means of collaboration to international Health IT community](https://discourse.openehr.org/t/openehr-clinical-knowledge-manager-offers-means-of-collaboration-to-international-health-it-community/13264)
> openEHR Clinical Knowledge Manager announcement
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 33, Issue 3](https://discourse.openehr.org/t/openehr-technical-digest-vol-33-issue-3/13259)
> >
> Message: 5
> Date: Thu, 2 Apr 2009 10:53:04 \+0200
> From: Rong Chen <rong\.acode@gmail\.com>
> Subject: Re: Question about the item property of Item\_Tree
> To: For openEHR technical discussions <openehr\-technical@openehr\.org>
> Message\-ID:
> <ebd0d070904020153y4bac0b48yb794a8b7fa2885d8@mail\.gmail\.com>
> Content\-Type: text/plain; charset=ISO\-8859\-1
>
> Hi Seref,
>
> Interesting thought\! I think this comes down to a design choice, which
> is whether we...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about the item property of Item_Tree](https://discourse.openehr.org/t/question-about-the-item-property-of-item-tree/14354)
> Hi,
Why is "item" field of Item_tree of type List- ? I feel that it is causing a litle bit of overlap betwen Item_tree and item_table. Item_table has a rows property with type List, which is nice for representing multi column tables, but when it comes to a single column table, item_tree also seem to allow it, by using a List given that items property is List
-
Would not it be better to enforce semantics of a tree structure by making item property of Item_tree a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Information Model vs AOM](https://discourse.openehr.org/t/information-model-vs-aom/14282)
> Hi,
I've three basic questions about IM and AOM:
Assuming that a connection between GUI forms and templates( consequently Archetypes) has been established, still the connection between Information Model and Archetype Model is not clear for me. The only connection I could find between these two models is based on Locatable class which has been inereited in both categories: AOM and IM. Does it mean that after data entry, validation will be done using archetype object in memory, and then data...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [859] Add Mac and Linux installation instructions to AWB area (copied from Ocean wiki).](https://discourse.openehr.org/t/ref-impl-eiffel-859-add-mac-and-linux-installation-instructions-to-awb-area-copied-from-ocean-wiki/16160)
> Revision: 859
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 Workbench - new release, including Reference Model checking](https://discourse.openehr.org/t/adl-1-5-workbench-new-release-including-reference-model-checking/12253)
> We are pleased to announce a new release of the ADL Workbench ('AWB') based on the [latest ADL / AOM 1.5 draft specifications](http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes). This release includes Reference Model checking and visualisation, i.e. validation of archetypes against a machine representation of the openEHR reference model, and numerous improvements in validation, and specialisation-related functionality. It is available for Windows, Mac...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [858] Further cleanup of AWB specialisation help page](https://discourse.openehr.org/t/ref-impl-eiffel-858-further-cleanup-of-awb-specialisation-help-page/16159)
> Revision: 858
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [857] Small improvements to ADL workbench help.](https://discourse.openehr.org/t/ref-impl-eiffel-857-small-improvements-to-adl-workbench-help/16158)
> Revision: 857
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [856] Updated readme file for AWB](https://discourse.openehr.org/t/ref-impl-eiffel-856-updated-readme-file-for-awb/13258)
> Revision: 856
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [855] Add some caveats to news.txt](https://discourse.openehr.org/t/ref-impl-eiffel-855-add-some-caveats-to-news-txt/13257)
> Revision: 855
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [854] Adjust the layout of the Options dialog so that all fields are fully visible on Linux.](https://discourse.openehr.org/t/ref-impl-eiffel-854-adjust-the-layout-of-the-options-dialog-so-that-all-fields-are-fully-visible-on-linux/13256)
> Revision: 854
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [853] Add rm_schema.adl to the SConstruct so that it will be included in the Mac and Linux installation.](https://discourse.openehr.org/t/ref-impl-eiffel-853-add-rm-schema-adl-to-the-sconstruct-so-that-it-will-be-included-in-the-mac-and-linux-installation/13254)
> Revision: 853
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [851] Reinstate the i18n library, which was accidentally removed in revision 849.](https://discourse.openehr.org/t/ref-impl-eiffel-851-reinstate-the-i18n-library-which-was-accidentally-removed-in-revision-849/13253)
> Revision: 851
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [850] Fix an unhandled exception "No such file or directory" when RM checking was on but rm_schema.dadl was missing.](https://discourse.openehr.org/t/ref-impl-eiffel-850-fix-an-unhandled-exception-no-such-file-or-directory-when-rm-checking-was-on-but-rm-schema-dadl-was-missing/13251)
> Revision: 850
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [849] Update the version to 1.5.0 and the copyright year to 2009 in the Macintosh installer and application packages.](https://discourse.openehr.org/t/ref-impl-eiffel-849-update-the-version-to-1-5-0-and-the-copyright-year-to-2009-in-the-macintosh-installer-and-application-packages/13250)
> Revision: 849
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [848] Minor punctuation fix in news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-848-minor-punctuation-fix-in-news-txt/13249)
> Revision: 848
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 32, Issue 14](https://discourse.openehr.org/t/openehr-technical-digest-vol-32-issue-14/13166)
> It makes sense, but I will have to find time to dig into the
differences between the EHR and Demographic reference model classes
and understand why they need to be different\.
And then determine once we have added one more reference model class,
how many more will need to be added to achieve a standalone HIS to
address administrative processes \- billing, admission, discharge etc\.
At this point it doesn't seem to make sense to build a new
administrative reference model for the non\-EHR...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [847] Update news prior to release](https://discourse.openehr.org/t/ref-impl-eiffel-847-update-news-prior-to-release/13248)
> Revision: 847
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [846] Make help page link depend on path of build.](https://discourse.openehr.org/t/ref-impl-eiffel-846-make-help-page-link-depend-on-path-of-build/13247)
> Revision: 846
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [845] AWB-162: Fix a void target call that occurred when re-selecting a specialised archetype in the repository tree, where the specialisation parent is missing.](https://discourse.openehr.org/t/ref-impl-eiffel-845-awb-162-fix-a-void-target-call-that-occurred-when-re-selecting-a-specialised-archetype-in-the-repository-tree-where-the-specialisation-parent-is-missing/16157)
> Revision: 845
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [844] Correct minor synchronisation error with validity flag.](https://discourse.openehr.org/t/ref-impl-eiffel-844-correct-minor-synchronisation-error-with-validity-flag/14146)
> Revision: 844
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [843] Small functional addition to file system reader - if an archetype of same id but more recent version than an existing one is found, use it.](https://discourse.openehr.org/t/ref-impl-eiffel-843-small-functional-addition-to-file-system-reader-if-an-archetype-of-same-id-but-more-recent-version-than-an-existing-one-is-found-use-it/13246)
> Revision: 843
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [842] Correct various errors in the RM checking.](https://discourse.openehr.org/t/ref-impl-eiffel-842-correct-various-errors-in-the-rm-checking/14144)
> Revision: 842
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[483] Put back a testcase that verifies the problem with a slash char in comment is fixed](https://discourse.openehr.org/t/483-put-back-a-testcase-that-verifies-the-problem-with-a-slash-char-in-comment-is-fixed/14143)
> Revision: 483
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[482] Update parser to support a slash in a comment after a regex (such as in use_node)](https://discourse.openehr.org/t/482-update-parser-to-support-a-slash-in-a-comment-after-a-regex-such-as-in-use-node/13245)
> Revision: 482
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[481] fixed a deprecated tag in the root pom file](https://discourse.openehr.org/t/481-fixed-a-deprecated-tag-in-the-root-pom-file/13244)
> Revision: 481
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[480] removed a testcase that is not relevant](https://discourse.openehr.org/t/480-removed-a-testcase-that-is-not-relevant/16156)
> Revision: 480
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[479] added a testcase related to a bug triggered by slash char in trailing comments after path syntax](https://discourse.openehr.org/t/479-added-a-testcase-related-to-a-bug-triggered-by-slash-char-in-trailing-comments-after-path-syntax/13243)
> Revision: 479
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[478] validator: Add validation for unknown codes and paths in the term bindings: WITB=Warning: The path/code referenced in the term binding does not exist in the archetype.](https://discourse.openehr.org/t/478-validator-add-validation-for-unknown-codes-and-paths-in-the-term-bindings-witb-warning-the-path-code-referenced-in-the-term-binding-does-not-exist-in-the-archetype/13238)
> Revision: 478
Author: sebastian\.garde
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR Concept Ids](https://discourse.openehr.org/t/openehr-concept-ids/14892)
> Hi All,
I'd like feedback on what other implementers think of the fact that we
have duplicate concept ids in the openEHR terminology\.
For example:
In the version lifecycle state group deleted is 523
In the audit change type deleted is 523
Now one can certainly argue that 'deleted' is the same no matter what
group it is in\. But in archetypes the concept id will appear as just
\[openehr::523\]
Having duplicate concept ids unnecessarily complicates the application
code because...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Mentoring Organization Applicant - tcrc](https://discourse.openehr.org/t/mentoring-organization-applicant-tcrc/13237)
> No sooner said than done\!\!\!\!\!
We are proud to announce our association with Northwestern University
Biomedical Informatics Center/NUCATS on project ideas \# 10 \- 13\.
Please revisit our ideas page, start making your selections for
projects\. Even if we are not selected as an organization we still need
your input to make FOSS healthcare applications, real, reliable and
interoperable\.
The OSHIP ideas page is at:
http://timothywayne.cook.googlepages.com/GSoC2009_ideas.html
Cheers,
Tim
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[477] Archetype Validator:](https://discourse.openehr.org/t/477-archetype-validator/14131)
> Revision: 477
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Why is the editor not opening ADL files? demographics is EHR core](https://discourse.openehr.org/t/why-is-the-editor-not-opening-adl-files-demographics-is-ehr-core/13235)
> Hi all,
it is sometimes good to deal with the basics again.
ISO 18308 defines the EHR as a virtual collection of patient related data.
It assumes the data are stored for an identifyable individual in more than one technical system (virtual).
ISO 18308 also assumes that the data can be used accross the continuum of healthcare, including continuity of care, management information, epidemiology etc.
Sincerely yours,
dr. William TF Goossen
director
Results 4 Care b.v.
De Stinse 15
3823 VM...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 29, Issue 3 Classifications](https://discourse.openehr.org/t/openehr-clinical-digest-vol-29-issue-3-classifications/16155)
> Yes, I had to search again to find them - but the classifications are perfect - is there a way to search or browse by them? As I said not a big deal now but as the number of archetypes increase I would imagine the long tree height per technical type will grow unwieldy.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 29, Issue 3](https://discourse.openehr.org/t/openehr-clinical-digest-vol-29-issue-3/14891)
> I would prefer to see the archetypes categorized by clinical domain rather than than the technical 'type' of archetype.
I actually do that inside our tools but it would be nice to have a consistent organization.
Not as important as getting more content into CKM though.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [840] Correct differential path analysis and generation - replaced the ARCHETYPE_CONSTRAINT.is_congruent notion by a slightly different one - is_mergeable, which means that the node should be overlaid piecemeal rather than used as a tota](https://discourse.openehr.org/t/ref-impl-eiffel-840-correct-differential-path-analysis-and-generation-replaced-the-archetype-constraint-is-congruent-notion-by-a-slightly-different-one-is-mergeable-which-means-that-the-node-should-be-overlaid-piecemeal-rather-than-used-as-a-tota/14130)
> Revision: 840
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Confusing naming of OBSERVATION and EVALUATION?](https://discourse.openehr.org/t/confusing-naming-of-observation-and-evaluation/14883)
> Hi\!
I just want to get some more global response to a little discussion
some of us had here at LiU\. So here comes some provocations\.\.\. :\-\)
In contact with clinicians we have discovered that the naming of the
openEHR reference model classes OBSERVATION and EVALUATION \(and of
course the corresponding archetype families\) is confusing partly
because of the class names themselves\. The distinction in practical
clinical documentation cases is often far from obvious when just
looking at...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Why is the editor not opening ADL files?](https://discourse.openehr.org/t/why-is-the-editor-not-opening-adl-files/13890)
> Dear all,
I am browsing through the existing archetypes from Ocean, obviously created by the Ocean Archetype Editor given the file name.
E.g.
openehr-demographic-person.person.draft.adl
When I try to open it with the AE, I do get continuously error messages similar to:
Is there anything wrong with the archetypes, or is this an error in the archetype...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Eclipse tooling for OpenEHR.](https://discourse.openehr.org/t/eclipse-tooling-for-openehr/13239)
> As discussed previously on this group, NHS CFH have developed an Eclipse
model viewer for openEHR models\. The viewer uses the XML representation of
the models \(not the ADL\) and is purely for displaying the model\.
\(See http://img147.imageshack.us/img147/5690/openehrviewer.png \)
More information and source code available Open Health Tools here :
https://openehr-model-browser.projects.openhealthtools.org/
regards
Richard Kavanagh
Head of Interoperability Specifications
Data Standards...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[476] Added testcase for internal reference VUNT/VUNP checking that would have failed previously due to a wrong check (it was not testing the target)](https://discourse.openehr.org/t/476-added-testcase-for-internal-reference-vunt-vunp-checking-that-would-have-failed-previously-due-to-a-wrong-check-it-was-not-testing-the-target/13233)
> Revision: 476
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [839] Improve processing in flattener.](https://discourse.openehr.org/t/ref-impl-eiffel-839-improve-processing-in-flattener/14118)
> Revision: 839
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [838] Correct errors in ARCHETYPE_FLATTENER.expand_definition_use_nodes which resulting in failure to clone subtrees due to differential paths (routine worked originally with fully structured archetypes).](https://discourse.openehr.org/t/ref-impl-eiffel-838-correct-errors-in-archetype-flattener-expand-definition-use-nodes-which-resulting-in-failure-to-clone-subtrees-due-to-differential-paths-routine-worked-originally-with-fully-structured-archetypes/13232)
> Revision: 838
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL/AOM 1.5, Templates progress](https://discourse.openehr.org/t/adl-aom-1-5-templates-progress/13230)
> I have updated the wiki page at
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
to explain the changes in the specifications due to the move to 'proper'
openEHR specification of the 'template' notion, and the related changes
to ADL and the AOM, particularly to do with specialisation and a higher
level of formality\. The wiki page is not yet finished, but explains in
quite a lot of detail all the new elements, changes, and some analysis
of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Seeking recent archetype research](https://discourse.openehr.org/t/seeking-recent-archetype-research/14885)
> Hi All
My name is Dennis Wollersheim; I lecture in Health Information Management
at La Trobe University in Bundoora, Melbourne, Australia\. I am currently
co\-authoring a health archetype literature review\. Evelyn Hovenga
suggested that the inhabitants of this list might have some suggestions\.
I have already gathered publications from Pubmed, computer science
journals, and those pointed to by the OpenEHR website\. My question is, do
you know of recent \(or unpublished\) archetype...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [837] Correct some workflow issues to do with cleaning generated files.](https://discourse.openehr.org/t/ref-impl-eiffel-837-correct-some-workflow-issues-to-do-with-cleaning-generated-files/13231)
> Revision: 837
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [836] Correct the interface of AUTHORED_RESOURCE.add_translation, which used to permissively allow a translation object to have a different language from the Hash key it was lsted under, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-836-correct-the-interface-of-authored-resource-add-translation-which-used-to-permissively-allow-a-translation-object-to-have-a-different-language-from-the-hash-key-it-was-lsted-under-e-g/14117)
> Revision: 836
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [835] Add missed execution path where grafted sub-tree clones are put into the child_grafted_path_list to be avoided in later processing.](https://discourse.openehr.org/t/ref-impl-eiffel-835-add-missed-execution-path-where-grafted-sub-tree-clones-are-put-into-the-child-grafted-path-list-to-be-avoided-in-later-processing/13227)
> Revision: 835
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[475] - correct handling of Internal References in the validator - sometimes too strict for VACMI, VUNT, VUNP errors](https://discourse.openehr.org/t/475-correct-handling-of-internal-references-in-the-validator-sometimes-too-strict-for-vacmi-vunt-vunp-errors/13226)
> Revision: 475
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [834] Correct a bug whereby cloned sub-hierarchies that had already been grafted into the output flat structure were still being descended into in the child differential, causing multiple cloning & grafting of sub-items.](https://discourse.openehr.org/t/ref-impl-eiffel-834-correct-a-bug-whereby-cloned-sub-hierarchies-that-had-already-been-grafted-into-the-output-flat-structure-were-still-being-descended-into-in-the-child-differential-causing-multiple-cloning-grafting-of-sub-items/13225)
> Revision: 834
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [833] Correct two errors found by AML:](https://discourse.openehr.org/t/ref-impl-eiffel-833-correct-two-errors-found-by-aml/13224)
> Revision: 833
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [832] Fix a dumb recursion error in archetype parsing loop.](https://discourse.openehr.org/t/ref-impl-eiffel-832-fix-a-dumb-recursion-error-in-archetype-parsing-loop/13223)
> Revision: 832
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [831] Missed new file](https://discourse.openehr.org/t/ref-impl-eiffel-831-missed-new-file/13222)
> Revision: 831
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [830] Small refactoring plus correct 'bug' where differential files were being serialised in ADL 1.4 if the adl_version_for_flat_output .cfg fle option was being used - but there is no point doing that.](https://discourse.openehr.org/t/ref-impl-eiffel-830-small-refactoring-plus-correct-bug-where-differential-files-were-being-serialised-in-adl-1-4-if-the-adl-version-for-flat-output-cfg-fle-option-was-being-used-but-there-is-no-point-doing-that/13221)
> Revision: 830
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [1 openEHR-implementers moderator request(s) waiting](https://discourse.openehr.org/t/1-openehr-implementers-moderator-request-s-waiting/14105)
> The openEHR\-implementers@openehr\.org mailing list has 1 request\(s\)
waiting for your consideration at:
http://lists.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending posts:
Cause: Message body is too big: 268910 bytes with a limit of 40 KB
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [829] Remove the class ARCHETYPE_PARSER; the functionality is now in ARCH_REP_ARCHETYPE, allowing better capability to assess out of date files, other changes that require various kinds of recompilation.](https://discourse.openehr.org/t/ref-impl-eiffel-829-remove-the-class-archetype-parser-the-functionality-is-now-in-arch-rep-archetype-allowing-better-capability-to-assess-out-of-date-files-other-changes-that-require-various-kinds-of-recompilation/13220)
> Revision: 829
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Definition of persistence for a composition](https://discourse.openehr.org/t/definition-of-persistence-for-a-composition/14882)
> Hi all,
I'd like to define persistence for a composition dinamically \(and not
statically in an archetype\), because this property changes depending on
application or application context\.
If I'd like to define a composition as persistent, could I define this into
a template? Is this the correct way to use templates? Moreover, in some
particular case, I don't exclude to change persistence attribute for a
compositon at run\-time, depending of application context\.
Any other...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [java downloads page not working](https://discourse.openehr.org/t/java-downloads-page-not-working/13711)
> Hi there,
At the moment, the download links reached via [http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm](http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm) do not work for me.
Due to some unfortunate events, I do need the jars immediately. Are there any other mirrors etc?
Kind regards
Seref
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [828] Two initial performance enhancements based on inspection of Eiffel profiling output on Finalised build...](https://discourse.openehr.org/t/ref-impl-eiffel-828-two-initial-performance-enhancements-based-on-inspection-of-eiffel-profiling-output-on-finalised-build/13215)
> Revision: 828
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [826] Correct a bug that caused a Void reference violation for a C_ATTRIBUTE that should have been declared with a cardinality but wasn't](https://discourse.openehr.org/t/ref-impl-eiffel-826-correct-a-bug-that-caused-a-void-reference-violation-for-a-c-attribute-that-should-have-been-declared-with-a-cardinality-but-wasnt/13213)
> Revision: 826
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Open source IDE to use Ocean's Archetype editor code](https://discourse.openehr.org/t/open-source-ide-to-use-oceans-archetype-editor-code/13217)
> Hi there,
For those who are interested in Ocean's Archetype editor code, SharpDevelop works quite fine. ( [http://www.icsharpcode.net/OpenSource/SD/](http://www.icsharpcode.net/OpenSource/SD/) )
It is an open source .NET development environment. I've just checked out the TRUNK branch from svn, and SharpDevelop loaded the solution without any problems.
I've compiled and executed it, and it works. So if you do not have access to [vs.net](http://vs.net), but want to take a peek, you may find...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [825] This is a slightly less awful hack for the purpose of managing different ADL versions in serialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-825-this-is-a-slightly-less-awful-hack-for-the-purpose-of-managing-different-adl-versions-in-serialisation/13212)
> Revision: 825
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [824] Introduce a basic and somewhat ugly capability to handle more than one version of ADL syntax on serialised output:](https://discourse.openehr.org/t/ref-impl-eiffel-824-introduce-a-basic-and-somewhat-ugly-capability-to-handle-more-than-one-version-of-adl-syntax-on-serialised-output/13211)
> Revision: 824
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [823] Remove unnecessary inheritance](https://discourse.openehr.org/t/ref-impl-eiffel-823-remove-unnecessary-inheritance/13210)
> Revision: 823
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [822] Improve VSONIR error message](https://discourse.openehr.org/t/ref-impl-eiffel-822-improve-vsonir-error-message/13209)
> Revision: 822
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [820] Correct inherited subtree removal logic to include all kinds of C_OBJECTs](https://discourse.openehr.org/t/ref-impl-eiffel-820-correct-inherited-subtree-removal-logic-to-include-all-kinds-of-c-objects/14090)
> Revision: 820
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [819] Correct combo-box default selection on start-up in repository dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-819-correct-combo-box-default-selection-on-start-up-in-repository-dialog/13208)
> Revision: 819
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [818] Make repository chooser a combo_box that remembers previously chosen repository paths.](https://discourse.openehr.org/t/ref-impl-eiffel-818-make-repository-chooser-a-combo-box-that-remembers-previously-chosen-repository-paths/16152)
> Revision: 818
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [OpenEHR'ED](https://discourse.openehr.org/t/openehred/14878)
> Hi,
I'm thinking about teaching some aspects of openEHR to our BSc
Biomedical Informatics undergraduates\.
In the spirit of open Source I was thinking of doing this by developing
open Courseware \- or enhancing existing course ware, if any exists\.
Does anyone know if any course ware on openEHR exists, and if not, would
be interested in developing some?
BWs
Derek
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL queries and one-many relationships](https://discourse.openehr.org/t/aql-queries-and-one-many-relationships/14877)
> Hello\. I am currently investigating AQL and would like to know how the following queries would be answered by a conformant AQL query engine\. I understand that the structure of AQL query results are not standardized yet in the AQL specifications, so if the spec cannot give a definitive answer what would Ocean's AQL query engine implementation do?
1\. SELECT
o/data\[at0001\]/events\[at0031\]/data\[at0003\]/items\[at0004\]/value AS...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [817] Fix a typo in news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-817-fix-a-typo-in-news-txt/13207)
> Revision: 817
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [816] Correct approach to doing RM validation so that unknown class nodes are not descended into](https://discourse.openehr.org/t/ref-impl-eiffel-816-correct-approach-to-doing-rm-validation-so-that-unknown-class-nodes-are-not-descended-into/13206)
> Revision: 816
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [815] Simplify specialisation build help page](https://discourse.openehr.org/t/ref-impl-eiffel-815-simplify-specialisation-build-help-page/13205)
> Revision: 815
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [814] Updated news.txt in specialisation branch](https://discourse.openehr.org/t/ref-impl-eiffel-814-updated-news-txt-in-specialisation-branch/13204)
> Revision: 814
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [813] Various changes to do with relaxing strictness of compiling for the moment:](https://discourse.openehr.org/t/ref-impl-eiffel-813-various-changes-to-do-with-relaxing-strictness-of-compiling-for-the-moment/13203)
> Revision: 813
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [812] Add missed icon files.](https://discourse.openehr.org/t/ref-impl-eiffel-812-add-missed-icon-files/16151)
> Revision: 812
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [811] Correct VACMI error reporting](https://discourse.openehr.org/t/ref-impl-eiffel-811-correct-vacmi-error-reporting/13202)
> Revision: 811
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [810] Correct errors in staging archetype building](https://discourse.openehr.org/t/ref-impl-eiffel-810-correct-errors-in-staging-archetype-building/13201)
> Revision: 810
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [809] Use proper constants for "adl" and "html" in format argument of archetype_parser calls.](https://discourse.openehr.org/t/ref-impl-eiffel-809-use-proper-constants-for-adl-and-html-in-format-argument-of-archetype-parser-calls/13200)
> Revision: 809
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [808] Improve semantics of multiplicity_interval and cardinality classes.](https://discourse.openehr.org/t/ref-impl-eiffel-808-improve-semantics-of-multiplicity-interval-and-cardinality-classes/14076)
> Revision: 808
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [805] Support mandatory in node map visualisation - uses two variants of attribute icons.](https://discourse.openehr.org/t/ref-impl-eiffel-805-support-mandatory-in-node-map-visualisation-uses-two-variants-of-attribute-icons/16149)
> Revision: 805
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [804] Correct bugs in test routines identified by Peter Gummer - make test_diff work properly.](https://discourse.openehr.org/t/ref-impl-eiffel-804-correct-bugs-in-test-routines-identified-by-peter-gummer-make-test-diff-work-properly/13196)
> Revision: 804
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [caBIG](https://discourse.openehr.org/t/cabig/13191)
> Yesterday we were doing a demo for a hospital client of ours and I
thought it quick cool that they recognized OpenEHR and became excited
that our product had the ability to configure against a clinical
standard \(I should the archetype import and how we can build content
suited for AQL querying\)\.
The reason being is they had interests in caBIG which is very similar
and \(with my limited understanding\) if you have a system that conforms
to their data model you can \(theoretically with the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[474] fixed a dadl-parser bug triggered by typed object block with keyed attributes](https://discourse.openehr.org/t/474-fixed-a-dadl-parser-bug-triggered-by-typed-object-block-with-keyed-attributes/13639)
> Revision: 474
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [803] AWB-158: Revision 801 was causing a void target call on the Tests page if the "Save ADLS" check box is off.](https://discourse.openehr.org/t/ref-impl-eiffel-803-awb-158-revision-801-was-causing-a-void-target-call-on-the-tests-page-if-the-save-adls-check-box-is-off/13189)
> Revision: 803
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem with using DADL-parser?](https://discourse.openehr.org/t/problem-with-using-dadl-parser/13188)
> I have a simple DADL file, I copy it here
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Syntax - highlighting DADL for Kate (KDE)](https://discourse.openehr.org/t/syntax-highlighting-dadl-for-kate-kde/13854)
> I created a \(quick/dirty\) simple syntax\-highlighting definition file for
the editor Kate, which is part of the KDE environment, it is also loaded
in KDevelop\.
It recognizes blocks/regions \(<>\), and datatypes \(strings, numeric
types\)
For me it is useful, so if you want it, I hope attachments arrive on the
mailinglist\.
Just put it somewhere on your computer \(best is in cache directory
\(below\) where all the other syntax files are\) and add the lines
\[Cache /home/YOUR...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype validation report](https://discourse.openehr.org/t/archetype-validation-report/13190)
> I was playing a bit the archetype validator in the Zilics models, and I decided to try validating the archetypes available for download here:
[http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html](http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html)
I downloaded everything there: 212 archetypes.
103 of them are draft (*draft.adl) and most failed validation because of missing or empty properties: original_author and purpose.
Among the other 109, 1 failed...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[473] Updated javadoc.](https://discourse.openehr.org/t/473-updated-javadoc/16148)
> Revision: 473
Author: tony\.lampada
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [802] AWB-148: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, apply changes from TRUNK revision 691:](https://discourse.openehr.org/t/ref-impl-eiffel-802-awb-148-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-apply-changes-from-trunk-revision-691/13187)
> Revision: 802
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [801] AWB-158: On the Tests page, make it explicit to the user that running the tests is going to overwrite their .adl and .adls files.](https://discourse.openehr.org/t/ref-impl-eiffel-801-awb-158-on-the-tests-page-make-it-explicit-to-the-user-that-running-the-tests-is-going-to-overwrite-their-adl-and-adls-files/14064)
> Revision: 801
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[472] remove escape from special strings in adl parsing](https://discourse.openehr.org/t/472-remove-escape-from-special-strings-in-adl-parsing/14063)
> Revision: 472
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR @ Google Summer of Code 2009?](https://discourse.openehr.org/t/openehr-google-summer-of-code-2009/14881)
> Hi\!
Now the FAQ for Google Summer of Code 2009 has been published at
http://code.google.com/opensource/gsoc/2009/faqs.html.
> From the FAQ: "We'll begin accepting applications from open source
mentoring organizations on Monday, March 9, 2009; we'll stop accepting
organization applications on Friday, March 13th\."
Maybe it's time for people involved in openEHR implementation projects
etc\. to discuss if/how their openEHR projects want to apply\. 2008 we
made a...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [800] Update the year that appears in the splash window to 2009.](https://discourse.openehr.org/t/ref-impl-eiffel-800-update-the-year-that-appears-in-the-splash-window-to-2009/13186)
> Revision: 800
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] adl_workbench, 64 bit, and small wish-list](https://discourse.openehr.org/t/ref-impl-eiffel-adl-workbench-64-bit-and-small-wish-list/13194)
> I compiled it on 64 bit Linux, on 64 bit Eiffel\-compiler, it compiles
and runs fine\. Maybe someone wants to know\.
I have a small wish\-list\.
\- I would appreciate an internal text\-editor with syntax highlighting
\- Autodetection if a file has changed on disk, and ask for parsing again
\- In splashscreen the date and version of latest code \(indicates now,
somewhere in 2008\)
Thanks, and congratulations with this multi\-platform\-compilable tool
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [798] Implemented existence and cardinality reference model checking.](https://discourse.openehr.org/t/ref-impl-eiffel-798-implemented-existence-and-cardinality-reference-model-checking/13184)
> Revision: 798
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [797] Correct a couple of type-checking errors to do with generics.](https://discourse.openehr.org/t/ref-impl-eiffel-797-correct-a-couple-of-type-checking-errors-to-do-with-generics/16147)
> Revision: 797
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [796] Added reference model attributes to node visualisation, switchable on GUI;](https://discourse.openehr.org/t/ref-impl-eiffel-796-added-reference-model-attributes-to-node-visualisation-switchable-on-gui/16146)
> Revision: 796
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CQuantityItem.units not empty](https://discourse.openehr.org/t/cquantityitem-units-not-empty/14880)
> Hi all.
I´m working in the archetype validation alghoritm of the zilics models (more on this thread --> [http://www.openehr.org/mailarchives/ref_impl_java/msg00975.html](http://www.openehr.org/mailarchives/ref_impl_java/msg00975.html)).
I ran into a little problem, and I´d like to hear your thoughts.
The specification for the C_QUANTITY_ITEM class states that the "units" field is valid when:
units_valid: units /= Void and not units.is_empty, in other (java) words: units != null &&...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL internal references change proposal](https://discourse.openehr.org/t/adl-internal-references-change-proposal/13747)
> Hello to everybody.
We have detected an issue in the ADL grammar related to the node_id (atXXXX value) of Internal References. An Internal Reference node, as any other C_OBJECT, inherits the node_id attribute. But its ADL grammar does not allow to define this value in a textual representation.
archetype_internal_ref:
SYM_USE_NODE type_identifier c_occurrences object_path
> SYM_USE_NODE type_identifier error
We think it is necessary to allow the introduction of this information in some...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [795] Make it compile!](https://discourse.openehr.org/t/ref-impl-eiffel-795-make-it-compile/13182)
> Revision: 795
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [794] RM checking - basic form looks correct for reasonable selection of archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-794-rm-checking-basic-form-looks-correct-for-reasonable-selection-of-archetypes/13181)
> Revision: 794
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [792] Various improvements and changes to RM checker:](https://discourse.openehr.org/t/ref-impl-eiffel-792-various-improvements-and-changes-to-rm-checker/14050)
> Revision: 792
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Existence of attributes (ADL, AOM)](https://discourse.openehr.org/t/existence-of-attributes-adl-aom/14049)
> Dear All
I have, as a clinician, undertaken to raise an issue on the list about our current handling of existence of attributes in archetypes. At Ocean we have discovered a ‘sleeping’ problem that needs to be addressed. In a nutshell, the existence of attributes is not handled correctly and requires changes in the ADL parser, the XML archetypes and in the AOM. Constraints on existence are not used at present and should not be heeded until the next release. I have put a full explanation here....
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [how to determine that a variable has PQ according to ISO 21090](https://discourse.openehr.org/t/how-to-determine-that-a-variable-has-pq-according-to-iso-21090/14876)
> Dear all,
We are currently working on several archetypes and encounter difficulties in finding the right approach in the Ocean archetype editor.
For instance, a pain scale (VAS type, or numeric 0 -10). According to ISO datatypes 21090 this is a Physical Quantity.
How can this be determined in the editor? We get the option Q to set that it is a quantity. Then there is a wealth of specific units, but not a simple way of stating this is a PQ.
Am I missing the point here?
Sincerely...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [791] The basic class and attribute checks appear to be working, based on current archetypes, including specialised ones.](https://discourse.openehr.org/t/ref-impl-eiffel-791-the-basic-class-and-attribute-checks-appear-to-be-working-based-on-current-archetypes-including-specialised-ones/13176)
> Revision: 791
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [790] Updates to RM schema](https://discourse.openehr.org/t/ref-impl-eiffel-790-updates-to-rm-schema/13175)
> Revision: 790
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [789] Initial basic checking now working.](https://discourse.openehr.org/t/ref-impl-eiffel-789-initial-basic-checking-now-working/13174)
> Revision: 789
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [RES: Demographic archetypes,](https://discourse.openehr.org/t/res-demographic-archetypes/13171)
> My point was not related to the data, just that filing an address
archetype under a branch called 'clusters' did not seem intuitive when
the branch next to it is called 'Demographic'\. Though perhaps
'Demographic' is the odd one out\.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ADL parser license](https://discourse.openehr.org/t/adl-parser-license/13183)
> Hi Rong.
We´ve just realised that the license for the ADL parser is GPL, unlike the rest of OpenEHR which is MPL (Is this correct or did I misunderstand?)
Was this really Acode´s intention?
If so, here at Zilics we won´t be able to use it in the commercial software that we´re building (bummer!)
btw, I still haven´t heard your thoughts about the merge...
Thanks!
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [788] Corrected and compiling BMM classes (again; -)](https://discourse.openehr.org/t/ref-impl-eiffel-788-corrected-and-compiling-bmm-classes-again/13173)
> Revision: 788
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [787] partial (non-compiling) changes to ensure SVN filename changes handled correctly](https://discourse.openehr.org/t/ref-impl-eiffel-787-partial-non-compiling-changes-to-ensure-svn-filename-changes-handled-correctly/13172)
> Revision: 787
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [786] Corrections to basic meta-model, now compiling properly](https://discourse.openehr.org/t/ref-impl-eiffel-786-corrections-to-basic-meta-model-now-compiling-properly/16145)
> Revision: 786
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [785] BMM class now back to compiling](https://discourse.openehr.org/t/ref-impl-eiffel-785-bmm-class-now-back-to-compiling/16144)
> Revision: 785
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [784] Improved meta-model, based on proper separation of 'type specifiers' and 'class definitions'.](https://discourse.openehr.org/t/ref-impl-eiffel-784-improved-meta-model-based-on-proper-separation-of-type-specifiers-and-class-definitions/16143)
> Revision: 784
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [RES: Demographic archetypes,](https://discourse.openehr.org/t/res-demographic-archetypes/16141)
> Hi Sergio,
Is it possible to zip and send me a copy of your demographic
archetypes caultonpos@gmail\.com
I don't see them on CKM yet and I would like to see the breadth so I
can figure out what is or isn't there\. As far as I can tell there are
no other demographic archetypes being shared \( well apart from address
lol which is a cluster not sure why\)\.
Greg
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [783] EDT-458: In BRANCHES/specialisation, reinstate most of the changes originally done in revision 759, which were reverted in revision 780 due to their performance impact when assertions are enabled.](https://discourse.openehr.org/t/ref-impl-eiffel-783-edt-458-in-branches-specialisation-reinstate-most-of-the-changes-originally-done-in-revision-759-which-were-reverted-in-revision-780-due-to-their-performance-impact-when-assertions-are-enabled/16142)
> Revision: 783
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Wisdom of the Crowds](https://discourse.openehr.org/t/wisdom-of-the-crowds/14879)
> Hi All,
\[This posting is related to Tony Shannon's great email regarding the
future of openEHR in 2009\. I think some of it relates to the technical
list members as well so I have CC'd them\.\]
Not wanting to hi\-jack Tony's thread I started this one where I hope I
have a few positive and possibly helpful suggestions\. Some of them may
need funding to help protect some people's time and others are virtually
cost free\.
I do have one negative comment and I'll get that...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [782] Initial cut of reference model checker.](https://discourse.openehr.org/t/ref-impl-eiffel-782-initial-cut-of-reference-model-checker/16140)
> Revision: 782
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [780] Reverse change 759 - causes serious performance impact problem.](https://discourse.openehr.org/t/ref-impl-eiffel-780-reverse-change-759-causes-serious-performance-impact-problem/16138)
> Revision: 780
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RM Versions](https://discourse.openehr.org/t/rm-versions/13839)
> This is really an implementer's question but I'd like opinions from
everyone on it\.
ADL files carry the adl version as well as the reference model name that
the archetype was built against\.
With the ARB starting on release 1\.1 and it looks like there may be
changes that impact software\. I wonder if we should raise a CR for 1\.1
that adds the RM version number to the ADL as well?
While I know that the ARB will do everything possible to not break
backwards compatibillity\. It...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [I Thought I Knew What I was Doing!](https://discourse.openehr.org/t/i-thought-i-knew-what-i-was-doing/13504)
> Well, at least the reference model makes sense to me\.
I can build EHR structures like no problem now in my demo\.
But reading the Archetypes \(definition\) makes me think so much is
missing from the ADL\. Let's take a simple case study\.
Compositions are the primary data container in an EHR\.
openEHR\-EHR\-COMPOSITION\.encounter\.v1
as shown in the definition:
26 definition
27 COMPOSITION\[at0000\] matches \{ \-\- Encounter
28 category matches \{
29 DV\_CODED\_TEXT...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [OpenEHR: PhD Case Study](https://discourse.openehr.org/t/openehr-phd-case-study/14865)
> >
All,
I am in the final stages of a PhD in Applied Information Security and am investigating different options for demonstrating my research offering. I have had a interest in Medical Informatics, in particular EHR's, for some time now. To give you a very brief synopsis of my research: I have developed an abstract access control module which uses logic (OWL + Rules) to determine access to protected information. I then use the decision results to expose or hide relevant...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [International representation of decimal magnitude in DV_QUANTITY](https://discourse.openehr.org/t/international-representation-of-decimal-magnitude-in-dv-quantity/14864)
> Hi all,
Our.NET implementation of the openEHR RM DV_QUANTITY is dependent on the regional setting on the system, for example a magnitude of 1.0 on a system with ‘en’ regional settings will be represented as 1,0 on a system with ‘de’ regional settings.
Thilo has recently identified an issue where our serialisation of these RM objects when in the ‘de’ culture produces an XML instance of DV_QUNATITY as follows:
Revision: 779
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [New member in the OpenEHR community](https://discourse.openehr.org/t/new-member-in-the-openehr-community/13169)
> Hi everyone. Finally I can post to this list :-)
My name is Tony, I work with Humberto Naves at Zilics, and from now on I too will contribute to the OpenEHR community (hopefully!)
Cheers
Tony Lampada
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [778] AWB-52: Merge OPENEHR_VERSION from the TRUNK into TAGS/Aug2007, from which the live version of the ADL Parser is built, so that we get an accurate report of the version.](https://discourse.openehr.org/t/ref-impl-eiffel-778-awb-52-merge-openehr-version-from-the-trunk-into-tags-aug2007-from-which-the-live-version-of-the-adl-parser-is-built-so-that-we-get-an-accurate-report-of-the-version/13168)
> Revision: 778
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New member on the OpenEHR community](https://discourse.openehr.org/t/new-member-on-the-openehr-community/13170)
> Hi everyone.
My name is Tony, I work with Humberto Naves at Zilics, and from now on I too will contribute to the OpenEHR community (hopefully!)
Cheers
Tony Lampada
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR in 2009 and beyond.. a view of the way forward](https://discourse.openehr.org/t/openehr-in-2009-and-beyond-a-view-of-the-way-forward/14873)
> Dear Stef,
Many thanks for the kick into action\. Apologies for the long radio
silence\. I have a tendency to listen>talk>write, been quiet for long
enough while delving into the issues the clinical community have raised
\(inc\. exploring your own issue\) while preparing a draft of this email
for some time now\.
You asked for my view on how developments in openEHR may unfold in 2009
and beyond \(inc archetype governance etc\)\. I'm still not sure this email
is quite ready \(some...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parser Versions](https://discourse.openehr.org/t/parser-versions/13167)
> I am using the ADL parser library from within a C\# application\. I want
the application to be able to report on which version of the parser is
being used\.
Using the following code :
openehr\.version\.OPENEHR\_VERSION adl\_parser\_version =
openehr\.version\.Create\.OPENEHR\_VERSION\.default\_create\(\);
EiffelSoftware\.Library\.Base\.kernel\.STRING\_8 parserVersion =
adl\_parser\_version\.version\(\);
This seems work and I get a version back, the version reported is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DLL files and licensing.](https://discourse.openehr.org/t/dll-files-and-licensing/14863)
> The current Archetype editor makes use of two external libraries , one
for ADL parsing, one for XML parsing\.
What is the licence on these libraries?, can they be used in other applications\.
regards
OP
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Leaving openEHR](https://discourse.openehr.org/t/leaving-openehr/14862)
> Dear members,
First of all, I want to thank you for all the support shown and all the help given me in this forum, particularly Rong Chen for your prompt assistance. I want to announce that I am leaving Zilics and the openEHR community for now because I am going to start my PhD in Mathematics next month. Tony França (a newcomer in this list) will be the official representative of Zilics from now on and he will answer all questions regarding the "Zilics Models" in my place.
Tahnk you and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Editor source code](https://discourse.openehr.org/t/archetype-editor-source-code/14013)
> Looking at the beta version of the archetype editor at
https://wiki.oceaninformatics.com/confluence/display/TTL/Archetype+Editor+Beta+Release
Can someone let me know which "release" this corresponds to from the
SVN code repository\.
many thanks
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [New member on the OpenEHR community](https://discourse.openehr.org/t/new-member-on-the-openehr-community/13162)
> Hi everyone
My name is Tony, I work with Humberto Naves at Zilics, and I would also like to contribute to the OpenEHR community.
I have tried to subscribe to the following mailing lists:
openehr-technical
openehr-implementers
ref_impl_java
but I fear the subscriptions did not work (it seems my emails are not making to the list archives).
Can someone give me a hand? :-)
Thanks a lot!
Cheers
Tony Lampada
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [2009 and beyond](https://discourse.openehr.org/t/2009-and-beyond/16136)
> Dear Tony,
You're the new chair now for almost 6 months\. Can you provide us with
some views/ outlooks of what is going to happen in 2009 and beyond\.
Are there any plans/ ideas to set up an official \(top level?\)
archetype repository so that one unified set of archetypes is being
created\. If such a thing isn't installed quickly we run into a big
risk that everbody starts using their 'home brewed' archetypes\. In
that case interoperability will be lost and if one wants to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [a model for medication strengths](https://discourse.openehr.org/t/a-model-for-medication-strengths/13826)
> I was wondering if anyone had any experience or knowledge of
a useable model for storing computable medication strengths
\(and medications forms etc\)?
Now I realise this is pretty complex \- for instance these are
some of the medication strengths strings listed for some Australian
medications\.\.
0\.3mg/mL \(0\.03%\)
0\.4mg\-10\.0mg\-2\.0mg/mL
0\.54g\-1\.28g/10mL
0\.375mg
1% w/w
1 Million KIU/100mL
10 dose
100mcg/capsule
However I actually think that it would be possible to construct
a...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Disruption to openEHR online services this weekend - [Power Outage and Update on Electrical Works]](https://discourse.openehr.org/t/disruption-to-openehr-online-services-this-weekend-power-outage-and-update-on-electrical-works/14012)
> There will be disruption to the openEHR online services from 17:30GMT
today \(16th Jan 2009\) until late Saturday evening, this is due to
essential works to the electrical supply to the building which hosts the
openEHR services\. This work will replace the ancient electrical
distribution equipment which handles the distribution of the main
electrical supply from our supplier\.
The services will be shut down normally by the UPS when the power is cut
off and all services should return...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Top health IT issues in US: interoperability & privacy](https://discourse.openehr.org/t/top-health-it-issues-in-us-interoperability-privacy/16135)
> Hi All,
I got this very interesting link to a video from my colleague Dr\. Chris
Paton today and watched it \(70\+ min\)\. There are guys from Kaiser
Permanente and Microsoft also\. I am impressed\. Even if this becomes a
failure, I am impressed in the way how non health IT people, especially
politicians, take things to that level\. Coupled with Obama's health IT
speeches, it gives a very clear picture of the consensus that has been
reached among all that interoperability is the \#1...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Problems with the OpenEHR service this weekend](https://discourse.openehr.org/t/problems-with-the-openehr-service-this-weekend/16028)
> Hi,
You may have noticed that the OpenEHR web site was unavailable for parts
of yesterday and this morning\. The full service is up and running now\.
There seems to have been a power failure yesterday between about 10:30
and 15:10 yesterday\. This was long enough that the UPS initated
automatic shutdowns of the servers in our server room\. When the power
returned the servers automatically restarted\.
The OpenEHR web site appeared to failed to start up\. On closer
investigation many...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [is OpenEHR.org down?](https://discourse.openehr.org/t/is-openehr-org-down/14874)
> Hi there,
I can not access to [openehr.org](http://openehr.org) from Turkey at the moment, and I've also tried a proxy in USA. Is it me only, or is the site down?
Kind Regards
Seref
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [777] Strict archetype id regex checking in ADL scanner.](https://discourse.openehr.org/t/ref-impl-eiffel-777-strict-archetype-id-regex-checking-in-adl-scanner/16134)
> Revision: 777
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [775] Updated text on ADL workbench help page](https://discourse.openehr.org/t/ref-impl-eiffel-775-updated-text-on-adl-workbench-help-page/13160)
> Revision: 775
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Release 1.0.2 published](https://discourse.openehr.org/t/openehr-release-1-0-2-published/13153)
> The *open*EHR Foundation is pleased to announce Release 1.0.2 of the specifications. In what appears to be a strong sign of stability, only 15 Change Requests were needed, of which only 7 had any effect on the formal specifications, and no impact on existing schemas or data. [Specification home page](http://www.openehr.org/releases/1.0.2/roadmap.html); [release notes](http://www.openehr.org/releases/1.0.2/release_notes_1.0.2.htm). Thanks to everyone in the community who contributed to this...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [A toy Java "workbench"](https://discourse.openehr.org/t/a-toy-java-workbench/14867)
> Hi,
To learn more about openEHR programming and using the Java implementation, I've
written what could be called a toy Java openEHR Workbench.
The feature list is not long but includes
- Possibility to view a tree presentation of an Archetype and the corresponding Adl or XML code at the same time.
Can be useful for understanding Adl
- Localized in English and Swedish.
The application can be downloaded from
[http://www.medview.se/openehr](http://www.medview.se/openehr)
While very...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [774] Improved scanner rules to allow fractional seconds be indicated by , or .](https://discourse.openehr.org/t/ref-impl-eiffel-774-improved-scanner-rules-to-allow-fractional-seconds-be-indicated-by-or/13159)
> Revision: 774
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [772] Update to allow fractional seconds in time durations.](https://discourse.openehr.org/t/ref-impl-eiffel-772-update-to-allow-fractional-seconds-in-time-durations/14000)
> Revision: 772
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[471] Added multimedia mediatypes to the openehr terminology](https://discourse.openehr.org/t/471-added-multimedia-mediatypes-to-the-openehr-terminology/13156)
> Revision: 471
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [{Disarmed} OpenEHR evaluation](https://discourse.openehr.org/t/disarmed-openehr-evaluation/14871)
> Hi,
I've started working on an EHR project at national level in my country. The people here knows only about HL7 and IHE, but OpenEHR is not so popular. I've been follow OpenEHR since 2006, when with Rodrigo Filgueira we made a prototype of an ICU system with the OpenEHR Information Model.
This is the first email of a list of emails I have to send to you to make a correct evaluation of OpenEHR and to have solid information to propose it to my coleagues on the project (I don't make the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [770] The Eiffel builder's utility functions files() and eiffel_classes_in_cluster() are now added to the environment, so that the main script can call them in a more object-oriented way rather than importing them individually.](https://discourse.openehr.org/t/ref-impl-eiffel-770-the-eiffel-builders-utility-functions-files-and-eiffel-classes-in-cluster-are-now-added-to-the-environment-so-that-the-main-script-can-call-them-in-a-more-object-oriented-way-rather-than-importing-them-individually/13155)
> Revision: 770
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [769] The Eiffel builder no longer assumes that C compilation must be done.](https://discourse.openehr.org/t/ref-impl-eiffel-769-the-eiffel-builder-no-longer-assumes-that-c-compilation-must-be-done/16132)
> Revision: 769
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Code error or redundant code?](https://discourse.openehr.org/t/code-error-or-redundant-code/12712)
> In the following code
[http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor/BusinessLogic/openEHR/History/RmEvent.vb](http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor/BusinessLogic/openEHR/History/RmEvent.vb)
there exists the following
Public Overrides Function Copy() As RmStructure
Dim ae As New RmEvent(Me.NodeId)
ae.cOccurrences = Me.cOccurrences
ae.mType = mType
ae.sNodeId = Me.sNodeId
ae.mRunTimeConstraint = Me.mRunTimeConstraint
ae.iOffset =...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[470] added validation for codes from openehr terminology](https://discourse.openehr.org/t/470-added-validation-for-codes-from-openehr-terminology/16131)
> Revision: 470
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[469] added two new testcases to simple terminology service](https://discourse.openehr.org/t/469-added-two-new-testcases-to-simple-terminology-service/16130)
> Revision: 469
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[468] added support for validation with generics](https://discourse.openehr.org/t/468-added-support-for-validation-with-generics/16129)
> Revision: 468
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[467] added support for fractional seconds in duration parsing](https://discourse.openehr.org/t/467-added-support-for-fractional-seconds-in-duration-parsing/13151)
> Revision: 467
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [768] Correct pattern for matching ISO8601_DURATIONs to include decimals on seconds.](https://discourse.openehr.org/t/ref-impl-eiffel-768-correct-pattern-for-matching-iso8601-durations-to-include-decimals-on-seconds/13150)
> Revision: 768
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[466] Added VCATU validation (uniquely named sibling attributes)](https://discourse.openehr.org/t/466-added-vcatu-validation-uniquely-named-sibling-attributes/13149)
> Revision: 466
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[465] minor fix in the test archetypes](https://discourse.openehr.org/t/465-minor-fix-in-the-test-archetypes/13148)
> Revision: 465
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[464] Updated slot test archetypes (previous ones had an empty purpose)](https://discourse.openehr.org/t/464-updated-slot-test-archetypes-previous-ones-had-an-empty-purpose/13987)
> Revision: 464
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[463] Fix bug with test adl files (multimedia and uri)](https://discourse.openehr.org/t/463-fix-bug-with-test-adl-files-multimedia-and-uri/13986)
> Revision: 463
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[462] Added VDFAI validation.](https://discourse.openehr.org/t/462-added-vdfai-validation/13147)
> Revision: 462
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [4.5.1.2 has a legacy string typo](https://discourse.openehr.org/t/4-5-1-2-has-a-legacy-string-typo/13146)
> 4\.5\.1\.2 still using ISO/IEC 10646 escape
sequences in the example string but these have
now been removed from ADL strings \(the text
refers to the ISO 10646 as well\)
Andrew
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [3.2 special character sequences](https://discourse.openehr.org/t/3-2-special-character-sequences/13145)
> I know that these aren't used much at the moment,
but section 3\.2 of the ADL draft is wrong
because it suggests that
\\uHHHH
\\uHHHHHHHH
are both acceptable quotation forms for unicode
character points\. However, I think that the long
form \(HHHHHHHH\) must have a capital U
to distinguish it\. It is not possible to distinguish
the forms based on the number of H characters
because the H characters could legitimately
be part of the actual string\.
For instance, to express 1000 euros I...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [767] AWB-154: In TAGS/Aug2007 and BRANCHES/specialisation, OceanInformatics.AdlParser.dll is now strongly named.](https://discourse.openehr.org/t/ref-impl-eiffel-767-awb-154-in-tags-aug2007-and-branches-specialisation-oceaninformatics-adlparser-dll-is-now-strongly-named/13144)
> Revision: 767
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [questions about ASSERTION](https://discourse.openehr.org/t/questions-about-assertion/14869)
> The EXPR\_LEAF of assertion has an 'Item'
of type ANY\.\.
The AOM says that 'Item' can be either a
a\) a manifest constant of any primitive type \(Integer, Real, Boolean, String,
Character, Date, Time, Date\_time, Duration\),
b\) a path
c\) a constraint, expressed in the form of concrete subtype of C\_OBJECT; most
often this will be a C\_PRIMITIVE\_OBJECT\.
What are the actual types that should be assigned
to 'Item' for each of these? \(c\) seems like it should be
a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Rules in sections](https://discourse.openehr.org/t/rules-in-sections/13143)
> Hi,
In Zilics API one can find getRule method both in Section and TemplateLocatable.
Invoking that method, I get some out put like this:
{/data[at0001]/events[at0026]/data[at0003]/items[at0007]=br.com.zilics.archetypes.models.am.template.openehrprofile.TemplateStatement@7f4d3272, /data[at0001]=br.com.zilics.archetypes.models.am.template.openehrprofile.TemplateStatement@5698c507}
But what I wonder is whether these kinds of paths mean just this part from the referenced Archetype should be...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [766] EDT-428: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, restore the revision 761 changes that were partially reverted by revision 764, because Archetype Editor 2.0 is not affecte](https://discourse.openehr.org/t/ref-impl-eiffel-766-edt-428-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-restore-the-revision-761-changes-that-were-partially-reverted-by-revision-764-because-archetype-editor-2-0-is-not-affecte/13142)
> Revision: 766
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [765] AWB-153: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, copy changes from BRANCHES/specialisation revision 763, to fix the way quoting is done on C_STRINGs and also correct the i](https://discourse.openehr.org/t/ref-impl-eiffel-765-awb-153-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-copy-changes-from-branches-specialisation-revision-763-to-fix-the-way-quoting-is-done-on-c-strings-and-also-correct-the-i/13140)
> Revision: 765
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [764] EDT-428: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, partially revert revision 761, because it is too soon for Archetype Editor to be correcting the spelling of term_bindings](https://discourse.openehr.org/t/ref-impl-eiffel-764-edt-428-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-partially-revert-revision-761-because-it-is-too-soon-for-archetype-editor-to-be-correcting-the-spelling-of-term-bindings/13135)
> Revision: 764
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [763] Fix the way quoting is done on C_STRINGs and also correct the implementation (no change to the outcome) for DT_PRIMITIVE_OBJECTs (the objects of dadl strings).](https://discourse.openehr.org/t/ref-impl-eiffel-763-fix-the-way-quoting-is-done-on-c-strings-and-also-correct-the-implementation-no-change-to-the-outcome-for-dt-primitive-objects-the-objects-of-dadl-strings/13134)
> Revision: 763
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Rules in statements](https://discourse.openehr.org/t/rules-in-statements/13133)
> Hi,
In Zilics API one can find getRule method both in Section and TemplateLocatable.
Invoking that method, I get some out put like this:
{/data[at0001]/events[at0026]/data[at0003]/items[at0007]=br.com.zilics.archetypes.models.am.template.openehrprofile.TemplateStatement@7f4d3272, /data[at0001]=br.com.zilics.archetypes.models.am.template.openehrprofile.TemplateStatement@5698c507}
But what I wonder is whether these kinds of paths mean just this part from the referenced Archetype should be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [list_open](https://discourse.openehr.org/t/list-open/14868)
> I have a vague recollection of discussing this before,
but I can't for the life of me work out what the
"list\_open" field in AOM C\_STRING class is
for\. It is described as being for when a
constraint is "non\-exhaustive" but I don't know what
this means in practical terms\. I also can't
work out how the "non\-exhaustive" lists would be
specified in ADL \- I was guessing
"a","b", \.\.\.
but the ADL explanation says that these...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [definition of object_path](https://discourse.openehr.org/t/definition-of-object-path/13129)
> The grammar \(pasted in the spec\) for the use\_node
slot refers to object\_path which is not actually
defined in the path grammar\. Furthermore, I can't
actually tell from the spec whether use\_node
is restricted to absolute paths, or whether it can
also accept relative paths\.
archetype\_internal\_ref:
SYM\_USE\_NODE type\_identifier c\_occurrences object\_path
So obviously the grammar needs to be updated to
use the right path rule, but I am also thinking that
perhaps the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EHR for some billion people in India](https://discourse.openehr.org/t/ehr-for-some-billion-people-in-india/13137)
> Hi to All,
I was thinking about the feasibility of a single consolidated EHR
repository for Turkey \(70\+ million people\)\.\.\.And it seemed ridiculous to
me\. I am now in New Zealand \(appx 4 million I guess\) and this is still
a hot issue whether to acquire Epic here and forget about
interoperability\.\.\.BUT even in such a tiny country authorities here
have started to turn away from this\.\.\. Just when I was thinking about
this I came across the following...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Q on openEHR XML-schema versioning](https://discourse.openehr.org/t/q-on-openehr-xml-schema-versioning/14870)
> We are about to publish Release 1\.0\.2 of the openEHR specifications\. The
CRs in this release have necessitated some very small \(non\-data
affecting\) changes in the schema BaseTypes\.xsd \(impact statement of
Release 1\.0\.2 at
http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candidate/publishing/release_notes_1.0.2.htm
; published Release 1\.0\.1 schemas at
http://www.openehr.org/releases/1.0.1/its/XML-schema/index.html)
The question has come up as to how changes in...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [762] AWB-146: Make compilable in EiffelStudio 6.3 (final release) by fixing the two remaining cases where an assignment attempt was being made to an attached local variable in ARCHETYPE_VALIDATOR.specialised_node_validate.](https://discourse.openehr.org/t/ref-impl-eiffel-762-awb-146-make-compilable-in-eiffelstudio-6-3-final-release-by-fixing-the-two-remaining-cases-where-an-assignment-attempt-was-being-made-to-an-attached-local-variable-in-archetype-validator-specialised-node-validate/13132)
> Revision: 762
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[461] minor improvments in the equals() and related testcase of CDomainType](https://discourse.openehr.org/t/461-minor-improvments-in-the-equals-and-related-testcase-of-cdomaintype/13131)
> Revision: 461
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[460] Add Validation for assumed values (VOBAV error)](https://discourse.openehr.org/t/460-add-validation-for-assumed-values-vobav-error/13126)
> Revision: 460
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[459] added validation for ontology code specialisation level](https://discourse.openehr.org/t/459-added-validation-for-ontology-code-specialisation-level/13125)
> Revision: 459
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[458] Added VASID validation check](https://discourse.openehr.org/t/458-added-vasid-validation-check/13124)
> Revision: 458
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[457] fixed a few bugs and added several more validations](https://discourse.openehr.org/t/457-fixed-a-few-bugs-and-added-several-more-validations/13123)
> Revision: 457
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[456] add new constructor of ArchetypeID with correct specialisation type](https://discourse.openehr.org/t/456-add-new-constructor-of-archetypeid-with-correct-specialisation-type/13122)
> Revision: 456
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [761] EDT-428: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, support openEHR change SPEC-284 to correct the spelling of term_bindings and constraint_bindings.](https://discourse.openehr.org/t/ref-impl-eiffel-761-edt-428-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-support-openehr-change-spec-284-to-correct-the-spelling-of-term-bindings-and-constraint-bindings/13121)
> Revision: 761
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[455] fix bug in constructing the base of an ArchetypeId and added testcase](https://discourse.openehr.org/t/455-fix-bug-in-constructing-the-base-of-an-archetypeid-and-added-testcase/16128)
> Revision: 455
Author: sebastian\.garde
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [grammar ambiguity with / character](https://discourse.openehr.org/t/grammar-ambiguity-with-character/16127)
> Now that arithmetic leaf in the assertion grammar
can take absolute paths, we have a lot of
/ characters possible in the expressions \- most
noticeably the path separators and the 'divides'
operator\.
So as of 1\.5
arithmetic\_leaf:
\( arithmetic\_expression \)
> integer\_value
> real\_value
> absolute\_path
Which means we can have expressions like\.\.
which should be valid\.\.
I suppose this can be worked around, but it
seems to be too complex for my parser to handle
\- so I...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[454] fixed validation error on EVENT; added check for specialisation depth](https://discourse.openehr.org/t/454-fixed-validation-error-on-event-added-check-for-specialisation-depth/13120)
> Revision: 454
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[453] Minor adjustment of Event constructor; Changed the signature of specialisation function of ArchetypeID](https://discourse.openehr.org/t/453-minor-adjustment-of-event-constructor-changed-the-signature-of-specialisation-function-of-archetypeid/13119)
> Revision: 453
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [poor version management in archetype editor / clinicians content](https://discourse.openehr.org/t/poor-version-management-in-archetype-editor-clinicians-content/14866)
> In a message dated 3-12-2008 14:57:33 W. Europe Standard Time, thomas.beale@oceaninformatics.com writes:
> I still don't quite get
> what way DCM is going - I thought it was going with archetypes, based on
> the meeting a year ago, but in any case, I think the job of
> standardising clinical models must be done by clinical people, and on a
> far more agile basis than any of the official standards organisations.
DCM is about standardising clinical models done by clinicians. Archetypes are...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[452] Additions to the Archetype Validator](https://discourse.openehr.org/t/452-additions-to-the-archetype-validator/16125)
> Revision: 452
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[451] fixed translation validation without contraint defs](https://discourse.openehr.org/t/451-fixed-translation-validation-without-contraint-defs/16124)
> Revision: 451
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Creating GUI](https://discourse.openehr.org/t/creating-gui/16123)
> Hi,
I wonder whether there exists any document or hints explaining creating of GUI( I mean forms for data entry by end user) or not.
I can parse templates to get used archetypes and continue parsing until reaching to leaf nodes and C_Primitive types then create form entries based on them, but I guess it should be another way to do that uses resolveArchetypes method and finally XSD file created.
Regards
Pariya
PhD Student
Department of Computing Science and Engineering
Chalmers University of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Creating GUI based on template xsd file](https://discourse.openehr.org/t/creating-gui-based-on-template-xsd-file/13229)
> Hi,
I wonder whether there exists any document or hints explaining creating of GUI( I mean forms for data entry by end user) or not.
I can parse templates to get used archetypes and continue parsing until reaching to leaf nodes and C_Primitive types then create form entries based on them, but I guess it should be another way to do that uses resolveArchetypes method and finally XSD file created.
Regards
Pariya
PhD Student
Department of Computing Science and Engineering
Chalmers University of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [760] Correct error of VACMI, VACMM error code mixup.](https://discourse.openehr.org/t/ref-impl-eiffel-760-correct-error-of-vacmi-vacmm-error-code-mixup/16122)
> Revision: 760
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL workbench - specialisation beta](https://discourse.openehr.org/t/adl-workbench-specialisation-beta/16126)
> We unfortunately recently uploaded an installer for the specialisation
version of the ADL Workbench that contained a bug which makes it hang
for locales other than "en" locales\. Anyone who has downloaded this
please download the latest version now there instead \(see
http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm).
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [HL7 too expensive, too complex and inconsistent](https://discourse.openehr.org/t/hl7-too-expensive-too-complex-and-inconsistent/14860)
> Says the European Commission
\(report:\)
http://www.ebusiness-watch.org/studies/special_topics/2007/documents/Special-study_01-2008_ICT_health_standards.pdf
\(sorry previous was the bad english\)
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [non-inclusive intervals in ADL](https://discourse.openehr.org/t/non-inclusive-intervals-in-adl/13812)
> I was dusting off the old parser and running it over the sample
test files on the openehr subversion site
dev/adl/test
My parser didn't handle the new 1\.4 non\-inclusive
intervals, or the new duration stuff \- fair enough, so I
have updated it to pass the test archetypes\. However, I
have now realise that the location of the > character
in the test archetypes is actually different than the
location in the ADL specs \(in some spots\)\.
4\.5\.2 has the explanation of ranges and does...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [schema for 1.0.2](https://discourse.openehr.org/t/schema-for-1-0-2/13127)
> Hi all, I have only vaguely been following various 1\.0\.2
related posts over the past few months, but am now back
on deck \(development wise\) and have a few questions
that I don't think have been covered, but apologies if they
have\.
Is there a pre\-release of the 1\.0\.2 AOM xsd files available?
Are there any AOM changes that require any
significant changes to the XSD, and if so how are
we handling XSD versioning\.
Related to the MONTH\_VALIDITY etc, I am happy for the
changes you...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [759] EDT-458: Fix a bug on saving an ADL file in .NET: wherever a carriage return was already present in the in-memory serialisation of the archetype, the ADL file was saved with another carriage return inserted.](https://discourse.openehr.org/t/ref-impl-eiffel-759-edt-458-fix-a-bug-on-saving-an-adl-file-in-net-wherever-a-carriage-return-was-already-present-in-the-in-memory-serialisation-of-the-archetype-the-adl-file-was-saved-with-another-carriage-return-inserted/13946)
> Revision: 759
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[450] initial import of archetype-validator](https://discourse.openehr.org/t/450-initial-import-of-archetype-validator/16121)
> Revision: 450
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL Parsing using the reference parser](https://discourse.openehr.org/t/adl-parsing-using-the-reference-parser/14857)
> I have seen on the website that there is a reference ADL parser available\. When Googling for more details I notice that there used to be documentation that described how to use this parser, this does not seem to be around any more\.
Does anyone know of any publicly accessible information that shows how to read an ADL file using the reference parser\. I am looking for examples of usage within a \.NET language \( i\.e C\~ or VB\.NET \)
any help appreciated
OxfordPartnership
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [poor version management in archetype editor](https://discourse.openehr.org/t/poor-version-management-in-archetype-editor/14855)
> Dear all,
Currently underway in making archetypes using the Ocean archetype editor we encounter a major flaw in the tool.
It is impossible to maintain version management, which leads to many inconsistencies in the archetypes.
Also, while participating in the review of archetypes such as blood pressure, the old (before review) and the new (after review) have the same version.
I think this is a very urgent matter to solve, otherwise we will end up with heaps of archetypes on the same...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML Schema spec improvements wiki](https://discourse.openehr.org/t/xml-schema-spec-improvements-wiki/16120)
> Dear All,
Please browse:
http://www.openehr.org/wiki/display/spec/XML+Schemas
Where we are trying to tighten up and rationalize the OpenEHR XML
Spec/Schemas\. It is a Wiki so feel free to edit, discuss etc\.etc\.
In short, the usage of XML will grow & it should be consistent,compact
and as simple as possible from templates to archetypes especially as the
concept of operational templates takes hold\.
There is a huge scope for simplification and compression in the
archetype XML so that...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [758] AWB-146: Compiling in EiffelStudio 6.3 release candidate found 3 cases where an assignment attempt was being made to attached local variables, all in ARCHETYPE_VALIDATOR.specialised_node_validate.](https://discourse.openehr.org/t/ref-impl-eiffel-758-awb-146-compiling-in-eiffelstudio-6-3-release-candidate-found-3-cases-where-an-assignment-attempt-was-being-made-to-attached-local-variables-all-in-archetype-validator-specialised-node-validate/13118)
> Revision: 758
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [text and description](https://discourse.openehr.org/t/text-and-description/14851)
> Hi,
In openEHR there are two labels 'text' and 'description' used.
For instance
text = "Increased bowel sounds"
description="Bowel sounds are more intense than normal"
In the tools I have tested 'text' is used as a label to input fields.
To me it would have been more natural to have 3 items, let's say 'term', 'text' and 'description' where term could be some agreed
upon language independent code and text and description are localised into different languages.
I guess this has been...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [757] AWB-152: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, don't escape backslashes when serialising regular expression patterns, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-757-awb-152-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-dont-escape-backslashes-when-serialising-regular-expression-patterns-e-g/13113)
> Revision: 757
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [756] AWB-152: Don't escape backslashes when serialising regular expression patterns, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-756-awb-152-dont-escape-backslashes-when-serialising-regular-expression-patterns-e-g/13112)
> Revision: 756
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Top 10 of Detailed Clinical Models](https://discourse.openehr.org/t/top-10-of-detailed-clinical-models/14852)
> Dear all,
A while ago in discussions on Detailed Clinical Models we determined a Top 10 to start with. In practice these are only 9 examples.
My suggestion is to include the Braden Scale for pressure ulcer risk as number 10.
The other 9 items are:
1 weight
2 lenght
3 heart rate
4 temperature
5 blood pressure
6 breathing (frequency)
7 Apgar score
8 Barthel index
9 Glasgow Coma Scale.
Note that the blood pressure archetype that includes a lot of information that is in the DCM is currently...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [755] EDT-446: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, add ADL commenting to internal references.](https://discourse.openehr.org/t/ref-impl-eiffel-755-edt-446-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-add-adl-commenting-to-internal-references/13111)
> Revision: 755
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [754] Add ADL commenting to internal references.](https://discourse.openehr.org/t/ref-impl-eiffel-754-add-adl-commenting-to-internal-references/16118)
> Revision: 754
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[449] Bug corrected in "for" statement](https://discourse.openehr.org/t/449-bug-corrected-in-for-statement/16116)
> Revision: 449
Author: humberto\.naves
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XmlPaser.parseXml](https://discourse.openehr.org/t/xmlpaser-parsexml/13919)
> Hi,
I am trying to parse a Template using Zilics donated code
but for almost all of templates, at least ones which I tried, that exist in OceanInformatics Template folder I receive this parsing error
br.com.zilics.archetypes.models.rm.exception.XmlParserException: Invalid namespaces at ....
Does anyone have any idea about it? Is it a problem with templates or should I change something is settings
I've tried Parser for Archetypes and it seems there's no problem there
Regards
Pariya
PhD...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [small data types clarification](https://discourse.openehr.org/t/small-data-types-clarification/13114)
> > From 5\.1\.5\.2
> A further situation in which text values \- this time
> plain text \- is mapped to equivalent terms is when
> natural language processing is used to generate
> coded terms for existing free\-text prose\. The aim of
> such processing is to detect word phrases and
> associate them with a coded term of the same meaning,
> without obliterating the original text\. In this case,
> an instance of DV\_CODED\_TEXT is associated with
> an instance of DV\_TEXT via the mappings...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Lifecycle of an archetype](https://discourse.openehr.org/t/lifecycle-of-an-archetype/14859)
> Hi,
The term lifecycle may not be appropriate for archetypes, and suggestions for a better term are more than welcommed.
Assuming that we constrain our interest only to a set of information encapsulated in a single archetype, would you provide the technical lifecycle you can imagine, for an archetype? The scenario is very simple: an archetype is loaded from disk, displayed on screen, and after data is provided by user, data is saved on disk, later loaded and edited, and saved again. That's...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Latest archetype ADL 1.5 + AOM drafts available](https://discourse.openehr.org/t/latest-archetype-adl-1-5-aom-drafts-available/16119)
> Dear all,
I have uploaded drafts of the ADL 1\.5 and corresponding AOM
specification\. These provide support for the last remaining major
semantic gap in templates, namely rules and conditions \(of the kind
required by the NHS CUI project and various other template authors\)\. In
the current release of openEHR, assertions are only partially specified
and practically never used to my knowledge,although the reference parser
does in fact implement them\. However, more powerful syntax and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Location info for zilincs-donated (mutable AM/RM)](https://discourse.openehr.org/t/location-info-for-zilincs-donated-mutable-am-rm/14856)
> Hi there,
What is the location of the zilincs-donated (__**mutable**__ AM/__**RM**__) implemenation in the java ref. impl svn repository? I guess it is accompanied by a reference parser for templates too?
I'd be really delighted to get a source tree for this implementation. Sorry if I am failing to see what is in front of me.
Kind regards
Seref
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XSLT converting Composition->HTML available?](https://discourse.openehr.org/t/xslt-converting-composition-html-available/14854)
> Hi\!
Does anybody want to share their XSLT\-script for converting openEHR
Compositions \(in XML form\) to a simple HTML view?
We're taking the lazy way of asking for this before sitting down to
create one ourselves :\-\)
Best regards,
Erik Sundvall
erisu@imt\.liu\.se http://www.imt.liu.se/~erisu/ Tel: \+46\-13\-227579
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [NodeID has to have a value?](https://discourse.openehr.org/t/nodeid-has-to-have-a-value/13074)
> Hi, i am wondering if NodeID for all CObjects is something that has to have a value? In the AOM documentation it says: "Semantic id of this node, used to differentiate sibling nodes of the same type. [Previously called 'meaning']. Each node_id must be defined in the archetype ontology as a term code."
According to the soruce code of LinkEHR NodeID has to exist. I am just trying to make sure that is the case.
Cheers
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [753] EDT-399: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, always backslash-quote the '\' and '"' characters, compliant with the ADL specification.](https://discourse.openehr.org/t/ref-impl-eiffel-753-edt-399-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-always-backslash-quote-the-and-characters-compliant-with-the-adl-specification/13110)
> Revision: 753
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [752] Correct code for quote insertion, to always backslash-quote '\' and '"' characters, since in non-serialised form of text there is by definition no 'quoting' (it is only a concept that applies to serialised form of an archetype on a](https://discourse.openehr.org/t/ref-impl-eiffel-752-correct-code-for-quote-insertion-to-always-backslash-quote-and-characters-since-in-non-serialised-form-of-text-there-is-by-definition-no-quoting-it-is-only-a-concept-that-applies-to-serialised-form-of-an-archetype-on-a/13109)
> Revision: 752
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[448] Added support for plural form of constraint_binding(s) and terminology_binding(s) and added test case](https://discourse.openehr.org/t/448-added-support-for-plural-form-of-constraint-binding-s-and-terminology-binding-s-and-added-test-case/13106)
> Revision: 448
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [751] In BRANCHES/specialisation, fix the external link to a specific revision of the i18n library so that it will build with EiffelStudio 6.2.](https://discourse.openehr.org/t/ref-impl-eiffel-751-in-branches-specialisation-fix-the-external-link-to-a-specific-revision-of-the-i18n-library-so-that-it-will-build-with-eiffelstudio-6-2/13105)
> Revision: 751
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [750] Improved version of quoting changes, handles lists of strings in dADL properly.](https://discourse.openehr.org/t/ref-impl-eiffel-750-improved-version-of-quoting-changes-handles-lists-of-strings-in-dadl-properly/13104)
> Revision: 750
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [749] Changes to support openEHR change SPEC-284.](https://discourse.openehr.org/t/ref-impl-eiffel-749-changes-to-support-openehr-change-spec-284/13103)
> Revision: 749
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [748] Upgrade invariants in C_DATE, etc types.](https://discourse.openehr.org/t/ref-impl-eiffel-748-upgrade-invariants-in-c-date-etc-types/13102)
> Revision: 748
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [747] Handle \\ and \" quoting properly.](https://discourse.openehr.org/t/ref-impl-eiffel-747-handle-and-quoting-properly/13908)
> Revision: 747
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [746] AWB-151 - output error message for missing parent archetype; generate reasonable message on reparse attempt.](https://discourse.openehr.org/t/ref-impl-eiffel-746-awb-151-output-error-message-for-missing-parent-archetype-generate-reasonable-message-on-reparse-attempt/13101)
> Revision: 746
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Final stages of Release 1.0.2](https://discourse.openehr.org/t/final-stages-of-release-1-0-2/16115)
> It is nearly there\! Have a look at
http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candidate/publishing/roadmap.html
and in particular the release notes \(link is a few lines down\) and let
me know if you think anything is missing or incorrect\. You can of course
look directly at the Jira project as well to see the CRs in this release
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[447] Modified Parser to allow any order of items of the TRANSLATION_DETAILS, e.g.](https://discourse.openehr.org/t/447-modified-parser-to-allow-any-order-of-items-of-the-translation-details-e-g/16114)
> Revision: 447
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Java Parser: Problem with using Translation_details' Accreditation in ADL](https://discourse.openehr.org/t/java-parser-problem-with-using-translation-details-accreditation-in-adl/13907)
> Dear all,
the current java parser doesn't seem to allow changes to order of the
TRANSLATION\_DETAILS \(other than the order of language and author\)\.
For example the following would fail:
translations = <
\["de"\] = <
author =...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [745] Correct error where IN_MEMORY_MESSAGES_DB can't find messages for language of the locale.](https://discourse.openehr.org/t/ref-impl-eiffel-745-correct-error-where-in-memory-messages-db-cant-find-messages-for-language-of-the-locale/16110)
> Revision: 745
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [inconsistencies in naming of term_bindings and constraint_bindings attributes in XML-schema and PDF specs](https://discourse.openehr.org/t/inconsistencies-in-naming-of-term-bindings-and-constraint-bindings-attributes-in-xml-schema-and-pdf-specs/16112)
> Alessandro Torrisi (Unusual Visions, implementing at the Medical Centre Alkmaar, The Netherlands) reported the following inconsistency.
- The ADL 1.4 specification mentions subsections under the archetype ontology section named term_binding and constraint_binding (both singular). In the AOM specification, these attributes are not defined (already raised as an issue), although there are invariants that imply the presence of attributes term_bindings and constraint_bindings (both plural).
- In...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR news from IHTSDO meeting, Denmark](https://discourse.openehr.org/t/openehr-news-from-ihtsdo-meeting-denmark/13916)
> posted on behalf of professor David Ingram, Head of CHIME, UCL and chair of the openEHR Foundation.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Detailed Clinical Modelling for EHR Development and deployment and for HL...](https://discourse.openehr.org/t/detailed-clinical-modelling-for-ehr-development-and-deployment-and-for-hl/14853)
> In a message dated 10-11-2008 0:30:48 W. Europe Standard Time, hugh.leslie@oceaninformatics.com writes:
> Hi William
>
> I think that the biggest problem I have with DCM is this bit -
> "Purposes of DCM include:
> 1] to allow quality of clinical content to be discussed and verified by clinicians, "
>
> Most of the formalisms that you have mentioned including UML and V3 RIM and OWL and Gello are very technical - how do you propose that these can be used by clinicians to discuss and verify...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [{Disarmed} Interpretation of occurrence in multivalued attributes](https://discourse.openehr.org/t/disarmed-interpretation-of-occurrence-in-multivalued-attributes/16109)
> Hi,
In section [**MailScanner has detected a possible fraud attempt from "5.3.5.1" claiming to be** **MailScanner warning: numerical links are often malicious:** 5.3.5.1](http://5.3.5.1) of Adl spec 1.5, draft 4, examples to both single and multi valued attributes are given within the context of subtype constraints.
It is explicitly stated in the doc that lack of occurrence in a single valued attribute where multiple options are given (with different node ids) this represents alternatives for...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Detailed Clinical Modelling for EHR Development and deployment and for H...](https://discourse.openehr.org/t/detailed-clinical-modelling-for-ehr-development-and-deployment-and-for-h/14850)
> Dear Eric, Tom,
I will answer in the sections.
In a message dated 8-11-2008 10:31:58 W. Europe Standard Time, eric.browne@montagesystems.com.au writes:
> Regarding coded ordinals, ADL provides for both the ordinal value and the
> corresponding text. If we use the Barthel Index archetype ( e.g.
> http://www.openehr.org/svn/knowledge/archetypes/dev/html/en/openEHR-EHR-OBSERVATION.barthel.v1.html
> ) as an example, then you can see that both the ordinal ( assessment score
> ) and the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - ['null flavour' in the reference model](https://discourse.openehr.org/t/null-flavour-in-the-reference-model/14858)
> It has been recently discovered that the null flavour attribute in the
ELEMENT class was spelled in US english\. This contradicts the
XML\-schema, which uses the international english used elsewhere in
openEHR\. See the CR describing the proposed change
http://www.openehr.org/issues/browse/SPEC-283 \- essentially, the change
would correct the spelling in the reference model\. The XML\-schema, and
existing data will remain the same\. Some software might need a change,
but it seems far...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Detailed Clinical Modelling for EHR Development and deployment and for HL7 v3](https://discourse.openehr.org/t/detailed-clinical-modelling-for-ehr-development-and-deployment-and-for-hl7-v3/12242)
> In a message dated 7-11-2008 9:24:56 W. Europe Standard Time, thomas.beale@oceaninformatics.com writes:
> William,
>
> I don't know what DCM is 'using' - is there are new formalism?
>
> - thomas
Detailed Clinical Modelling is currently using multiple formats:
1. For legacy systems to extract clinical knowledge, and to come up with an expression that 2 and 3 below at least can use: UML
2. For messaging HL7 v3: template formalism (i.e. HL7 v3 XML and schematron)
3. For 13606 RIM based...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Please respond by Nov. 5th: Known Free/Open Source EHR/EMR Deployment Cou...](https://discourse.openehr.org/t/please-respond-by-nov-5th-known-free-open-source-ehr-emr-deployment-cou/16113)
> I find it quite peculiar that the debate surfaces once again now all parties have agreed to use detailed clinical models to capture the knowledge and data details and from there make archetypes and clinical statements.
I would like to see all our passion move into creating the DCM :-)
Sincerely yours,
dr. William TF Goossen
director
Results 4 Care b.v.
De Stinse 15
3823 VM Amersfoort
the Netherlands
email: Results4Care@cs.com
phone + 31654614458
fax +3133 2570169
www.results4care.nl
Dutch...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Representing constraints in Java reference implementation](https://discourse.openehr.org/t/representing-constraints-in-java-reference-implementation/16111)
> Ok,
I'll try to ask this as brief and clear as possible: How do you represent a constraint defined on an information model entity in an archetype, in the java ref. implementation? (in an ITS friendly way)
Ocean's archetype editor has a nice hierarchy of Constraint classes, which are constructed as [vb.net](http://vb.net) code walks over the adl object representation returned from eiffel parser wrapping dll.
Unless I'm missing something, the java ref implementation has classes in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Please respond by Friday Nov 7th: Deployment, Version, PATIENTS IN SYSTEM.](https://discourse.openehr.org/t/please-respond-by-friday-nov-7th-deployment-version-patients-in-system/14849)
> Hello all,
The un\-official, Draft 8 of the upcoming American Medical Informatics
Association Open Source Working Group white paper to be voted on
November 9th can be found http://ignaciovaldes.com/amia. It will be
voted on for ratification on November 9th\-11th or so\. Action is needed
on your part to answer the question: If open source is so great why is
no one using it? There is no aggregate data that I can find to counter
this opinion\. If you know of a Free/Open Source EHR/EMR...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [parser syntax in Time_specification package](https://discourse.openehr.org/t/parser-syntax-in-time-specification-package/16108)
> Which syntax is used in the parse specifications in the time\_specification
Package? \(For example Data Types Information Model Rev 2\.1\.0 in section
8\.2\.2\.1\)
I have seen that BackusNaur form \(BNF\) is used in some other places in
the specification\. However, the parse specifications in the
Time\_specification package does not look like BNF\.
/Björn
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Description of files from Template Designer?](https://discourse.openehr.org/t/description-of-files-from-template-designer/14844)
> Hi,
Sorry if this is the wrong forum.
Is there a description somewhere of the oet-files produced by the Ocean Informatics Template Designer?
I would like to use the templates in an application as a basis for input forms, but then I need
a specification of the file-contents.
Regards
Olof Torgersson
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Is originalAuthor required?](https://discourse.openehr.org/t/is-originalauthor-required/14840)
> Dear All,
Running the Java ADL > XML & I get a fair few errors of the type:
Error Class: java\.lang\.IllegalArgumentException Message: null or empty
originalAuthor
Is originalAuthor a required structure?
If so then the Ocean ADL > XML is not picking that up\.
If not then could the Java code be amended to not error if it is not
present\.
TIA
Adam
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Time in Observation](https://discourse.openehr.org/t/time-in-observation/14839)
> Hi All
I got a question about the time in the observations, like blood pressure, Heart_rate, etc. There is no item in a Archetype that contains the time of the event.So, how it would be saved (i e time of the blood pressure or herat rate that is measured ). I know that in the HISTORY class there are some attributes for saving the time of the event. But as the Archetypes are our model for making templates and inserting data and there is no item to save the time in the observation,so how it...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Please respond by Nov. 5th: Known Free/Open Source EHR/EMR Deployment Count.](https://discourse.openehr.org/t/please-respond-by-nov-5th-known-free-open-source-ehr-emr-deployment-count/14838)
> The un\-official, Draft 7 of the upcoming American Medical Informatics
Association Open Source Working Group white paper to be voted on
November 9th can be found http://ignaciovaldes.com/amia. It will be
voted on for ratification on November 9th\-11th or so\. Action is needed
on your part to answer the question: If open source is so great why is
no one using it? There is no aggregate data that I can find to counter
this opinion\. If you know of a Free/Open Source EHR/EMR deployment and
could...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Please respond by Nov. 5th: Known Free/Open Source EHR/EMR Deployment Count.](https://discourse.openehr.org/t/please-respond-by-nov-5th-known-free-open-source-ehr-emr-deployment-count/14836)
> The un\-official, Draft 7 of the upcoming American Medical Informatics
Association Open Source Working Group white paper to be voted on
November 9th can be found http://ignaciovaldes.com/amia. It will be
voted on for ratification on November 9th\-11th or so\. Action is needed
on your part to answer the question: If open source is so great why is
no one using it? There is no aggregate data that I can find to counter
this opinion\. If you know of a Free/Open Source EHR/EMR deployment and
could...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[446] start a branch to merge the trunk with the new zilics model](https://discourse.openehr.org/t/446-start-a-branch-to-merge-the-trunk-with-the-new-zilics-model/13099)
> Revision: 446
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[445] New Zilics Models](https://discourse.openehr.org/t/445-new-zilics-models/13098)
> Revision: 445
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[444] New models will be here](https://discourse.openehr.org/t/444-new-models-will-be-here/14847)
> Revision: 444
Author: humberto\.naves
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ocean Archetype Editor source code?](https://discourse.openehr.org/t/ocean-archetype-editor-source-code/12608)
> Hi,
My attempts to check out Ocean's archetype editor fail with a request for a username/password for [svn.oceaninformatics.com](http://svn.oceaninformatics.com)
I can omit externals in my svn client (should I?), however when I do that only beryllium directory in releases contains a project I can compile and run. Others, including the one in the trunk do not compile due to a missing project or an undefined type.
I'm a little bit lost here, can someone help me out to get the up to date source...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [744] Update news file.](https://discourse.openehr.org/t/ref-impl-eiffel-744-update-news-file/13097)
> Revision: 744
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [743] Missed interval->range renamings.](https://discourse.openehr.org/t/ref-impl-eiffel-743-missed-interval-range-renamings/13096)
> Revision: 743
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [742] Change names of 'interval' attribute and corresponding make routines in C_XXX primitive classes to conform to standard AOM.](https://discourse.openehr.org/t/ref-impl-eiffel-742-change-names-of-interval-attribute-and-corresponding-make-routines-in-c-xxx-primitive-classes-to-conform-to-standard-aom/13093)
> Revision: 742
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL/AOM 1.5 - proposed change to representation of date/time constraints](https://discourse.openehr.org/t/adl-aom-1-5-proposed-change-to-representation-of-date-time-constraints/12046)
> Dear all,
in the current AOM spec ([http://www.openehr.org/releases/1.0.1/architecture/am/aom.pdf](http://www.openehr.org/releases/1.0.1/architecture/am/aom.pdf) section 6), the C_DATE class is defined as follows:
class C_DATE
month_validity[0..1]: VALIDITY_KIND
day_validity[0..1]: VALIDITY_KIND
timezone_validity[0..1]: VALIDITY_KIND
range[0..1]: Interval
assumed_value[0..1]: Date
class VALIDITY_KIND - enum with values mandatory, optional, disallowed
However, in the current...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype](https://discourse.openehr.org/t/archetype/14846)
> Hi All
I have a question about some of the openehr Archetypes.
Why some of them(like Encounter,Discharge) doesn't have any thing in it, not evevn other Archetypes included? I can't get the point .How they can be used?
Could anybody help me please.
Thanks in advance
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [740] Refactoring - rename all 'compressed_path' calls to 'differential_path' or related names.](https://discourse.openehr.org/t/ref-impl-eiffel-740-refactoring-rename-all-compressed-path-calls-to-differential-path-or-related-names/13882)
> Revision: 740
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [739] Change file repository scanning method so that most recent versions of archetypes are always used, not olderst ones.](https://discourse.openehr.org/t/ref-impl-eiffel-739-change-file-repository-scanning-method-so-that-most-recent-versions-of-archetypes-are-always-used-not-olderst-ones/13881)
> Revision: 739
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Byte Order Marks](https://discourse.openehr.org/t/byte-order-marks/14842)
> Byte Order Marks
What is the default CharSet for OpenEHR ADL?
ASCII? UTF\-8?
I ask because ADL itself does not anywhere declare a character set & we
have had a number of adl files which have failed \(either to be opened or
to be transformed into XML\) & in each occasion the reason has been the
presence of a byte order mark \(hex bytes EF BB BF\) e\.g\.
Exception in thread "main" se\.acode\.openehr\.parser\.TokenMgrError:
Lexical error at line 1, column 1\. Encountered:...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Inspections & Examinations](https://discourse.openehr.org/t/inspections-examinations/16105)
> For the inspection and examination archetypes we have
Normal statements
Clinical description
Findings
\.\.\.
Should we have an optional boolean indicator for 'presence of the
finding' so we can document the absence of a finding like
'no rigidity of the abdomen'
or is this somehow addressed by 'normal statements' ?
thanks\!
Greg
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [738] Improve and fix some bugs in handling of .vNdraft style archetype ids.](https://discourse.openehr.org/t/ref-impl-eiffel-738-improve-and-fix-some-bugs-in-handling-of-vndraft-style-archetype-ids/16104)
> Revision: 738
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [737] Fix a couple of edge-case bugs found by full pass over openEHR archetypes in full assertion mode.](https://discourse.openehr.org/t/ref-impl-eiffel-737-fix-a-couple-of-edge-case-bugs-found-by-full-pass-over-openehr-archetypes-in-full-assertion-mode/13092)
> Revision: 737
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [AHRQ indicators and OpenEHR](https://discourse.openehr.org/t/ahrq-indicators-and-openehr/14837)
> Hello all,
I'm working in a project to build a system for clinicals data capture and data analisys refers at some indicators which you can find at [http://www.qualityindicators.ahrq.gov/](http://www.qualityindicators.ahrq.gov/)
This indicators, defined by AHRQ (Agency for Healthcare Research and Quality) can indicate for example "Diabetes short-term complication admission rate" with specifics like: "all non-maternal/non-neonatal discharges of age 18 years and older with ICD-9-CM principal...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Symposium on CCR](https://discourse.openehr.org/t/symposium-on-ccr/13091)
> Hello all,
looking for news about the CCR Standard i discovered that there took
place "/A Symposium on Present and Future Uses" of/ Continuity of Care
Record \(CCR\) in September in the US\.
The presentations are available at the following website:
http://www.massmed.org/AM/Template.cfm?Section=Calendar&Template=/Conference/ConferenceDescription.cfm&ConferenceID=145
I found most interesting Kibbe's Screenshots of real implementations of
the CCR and the information given by...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [General examination archetype](https://discourse.openehr.org/t/general-examination-archetype/12583)
> I have an Archetype question on openEHR\-EHR\-CLUSTER\.exam\.v1
The archetype appears to be designed such that the findings can only
be expressed with a limited set of attributes \- color, location,
shape, etc\. \- things specific to the archetypes Inspection,
Auscultation, Percussion and Palpation
This is the hierarchy \(or part of it\)
exam
\-\- normal statements
\-\-\-\-\- normal statement
\-\- clinical...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [family medical history archetype](https://discourse.openehr.org/t/family-medical-history-archetype/14845)
> I was looking for an archetype which contained data elements for
family medical history, specifically
\- medical condition \(coded or free text\)
\- relation to patient \(relative\)
\- presence of condition \(present/not present\)
There is an archetype called 'Risk of condition based on family
history' which seems to have everything I need \- except that its usage
is to evaluate the risk\.
Do you think this could be a specialization of a more general
archetype for family history \-...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [736] Increment OPENEHR_VERSION to 1.5.](https://discourse.openehr.org/t/ref-impl-eiffel-736-increment-openehr-version-to-1-5/13870)
> Revision: 736
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [735] Fix bug where code_list is void (which is legal)](https://discourse.openehr.org/t/ref-impl-eiffel-735-fix-bug-where-code-list-is-void-which-is-legal/13090)
> Revision: 735
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [734] Implement compressed paths within OG_PATH objects, to allow path-finding within archetypes with compressed attributes to work properly.](https://discourse.openehr.org/t/ref-impl-eiffel-734-implement-compressed-paths-within-og-path-objects-to-allow-path-finding-within-archetypes-with-compressed-attributes-to-work-properly/13089)
> Revision: 734
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Unhandled exception parsing ADL](https://discourse.openehr.org/t/unhandled-exception-parsing-adl/16106)
> I've built an ant task for generating XML from ADL & running it against
out adl archetypes dies when an unhandled error pops up\.
Exception in thread "main" se\.acode\.openehr\.parser\.TokenMgrError:
Lexical error at line 1, column 1\. Encountered: "\\u00ef" \(239\), after :...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [733] EDT-369: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, make comments in ordinals and coded text items safe (no newlines, length-limited).](https://discourse.openehr.org/t/ref-impl-eiffel-733-edt-369-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-make-comments-in-ordinals-and-coded-text-items-safe-no-newlines-length-limited/13088)
> Revision: 733
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [732] Make comments in ordinals and coded text items safe (no newlines, length-limited).](https://discourse.openehr.org/t/ref-impl-eiffel-732-make-comments-in-ordinals-and-coded-text-items-safe-no-newlines-length-limited/13087)
> Revision: 732
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [731] Support for 'compressed paths' in differential archetypes, needed for templates as well.](https://discourse.openehr.org/t/ref-impl-eiffel-731-support-for-compressed-paths-in-differential-archetypes-needed-for-templates-as-well/16103)
> Revision: 731
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ADL syntax problem, the new ADLParser finds a problem that an old version of the ADLParser didnt find.](https://discourse.openehr.org/t/adl-syntax-problem-the-new-adlparser-finds-a-problem-that-an-old-version-of-the-adlparser-didnt-find/14848)
> Hi,
i am not very good at ADL syntax so i am wondering if some of you could help me find whats wrong with the ADL file. The ADL file is from openLinkEHR and they use an old version of the ADLParser. I would like to update the file so the new ADLParser accepts it since i want to use it in my project.
The ADLParser returns the text:
se.acode.openehr.parser.ParseException: Encountered "/" at line 297, column 48.
Was expecting one of:
"}" ...
"c_dv_quantity" ...
...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Supporting image in data entry](https://discourse.openehr.org/t/supporting-image-in-data-entry/14841)
> Hi everybody,
As you may know, one of the most important information inputs for clinicians in oral medicine, or maybe other domains as well, is images of infected area, teeth, ....
In our Clinical information system([MedView](http://medview.se/)) dentists has the ability to take pictures of patients' mouth and enter it to the system, share in with their colleagues and extract more information by investigating it.
I was just wondering whether in openEHR specification this kind of inputs has...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[443] changes due to adjustment of language valiation in TranslationDetails](https://discourse.openehr.org/t/443-changes-due-to-adjustment-of-language-valiation-in-translationdetails/16102)
> Revision: 443
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[442] fixed language validation issue in TranslationDetails](https://discourse.openehr.org/t/442-fixed-language-validation-issue-in-translationdetails/16101)
> Revision: 442
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[441] adjusted the type of defaultValue of CDvOrdinal](https://discourse.openehr.org/t/441-adjusted-the-type-of-defaultvalue-of-cdvordinal/16100)
> Revision: 441
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[440] implemented validValue() in CDvQuantity](https://discourse.openehr.org/t/440-implemented-validvalue-in-cdvquantity/16099)
> Revision: 440
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [CDvOrdinal class, quick question about defaultValue and assumedValue.](https://discourse.openehr.org/t/cdvordinal-class-quick-question-about-defaultvalue-and-assumedvalue/15897)
> Hi,
I have a question about the constuctor in the CDvOrdinal class, it looks like this:
public CDvOrdinal(String path, Interval occurrences,
String nodeID, CAttribute parent, Set list,
DvOrdinal defaultValue, Ordinal assumedValue) {
super(list == null, path, "DvOrdinal", occurrences, nodeID, null,
assumedValue, parent);
if (list != null && list.isEmpty()) {
throw new IllegalArgumentException("list is empty");
}
this.list = list == null ? null : new...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[439] commented out assembly-plugin in adl-parser pom](https://discourse.openehr.org/t/439-commented-out-assembly-plugin-in-adl-parser-pom/13086)
> Revision: 439
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[438] updated subclasses of CObject according to the sepcs](https://discourse.openehr.org/t/438-updated-subclasses-of-cobject-according-to-the-sepcs/13856)
> Revision: 438
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [SimpleTerminologyTest XML file, possible error in the XML file or in the constructor of the class TranslationDetails](https://discourse.openehr.org/t/simpleterminologytest-xml-file-possible-error-in-the-xml-file-or-in-the-constructor-of-the-class-translationdetails/13085)
> Hi,
I am trying to create an Archetype using the constructor in org.openehr.am.archetype.Archetype.java and i use the SimpleTerminology implementation that uses the XML file openehr_terminology_en.xml as terminology. When i create TranslationDetails which is one of the arguments to the Archetype constructor i get IllegalArgumentException("unknown language ").
The code that throws this exception looks like this:
if (terminologyService != null &&...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [new CEN standards page](https://discourse.openehr.org/t/new-cen-standards-page/14843)
> Dipak Kalra has supplied new content for the first section of the page
on CEN \- http://www.openehr.org/standards/cen.html
let me know if anyone wants this modified, improved etc\.
\- thomas
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [730] Missed new class to support commonality in ARCHETYPE_ID and TEMPLATE_ID](https://discourse.openehr.org/t/ref-impl-eiffel-730-missed-new-class-to-support-commonality-in-archetype-id-and-template-id/13084)
> Revision: 730
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [729] Support old-style Archetype ids, official ADL 1.4 archetype ids, and a draft form of template ids.](https://discourse.openehr.org/t/ref-impl-eiffel-729-support-old-style-archetype-ids-official-adl-1-4-archetype-ids-and-a-draft-form-of-template-ids/13082)
> Revision: 729
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [728] Small improvements in coding of path logic and ARCHETYPE_CONSTRAINT.safe_deep_twin.](https://discourse.openehr.org/t/ref-impl-eiffel-728-small-improvements-in-coding-of-path-logic-and-archetype-constraint-safe-deep-twin/16096)
> Revision: 728
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [modelling question on AOM](https://discourse.openehr.org/t/modelling-question-on-aom/16097)
> this a question for those who have implemented the AOM\. I am currently
finalising the draft model of AOM for ADL 1\.5, to accommodate the
various things need to support specialisation and templates properly\.
One of the harder parts of the model is to cleanly support attributes
'at a path', which happens when a redefinition is somewhere deep inside
the structure\. You will have seen how in the current \.oet template XML
format, all 'rules' \(which are overrides\) are keyed by...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[437] initial import of archetype based rm-validator component to sandbox area](https://discourse.openehr.org/t/437-initial-import-of-archetype-based-rm-validator-component-to-sandbox-area/16095)
> Revision: 437
Author: rong\.chen
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR.org unavailable 10-Oct-2008 18:00 - 12-Oct-2008 17:00 (GMT+1)](https://discourse.openehr.org/t/openehr-org-unavailable-10-oct-2008-18-00-12-oct-2008-17-00-gmt-1/16098)
> Unfortunately due to maintenance of the power supply at UCL's Archway
campus, where the openEHR\.org server is housed, network equipment will
be without power for this weekend\.
Apologies for the inconvenience\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Insight into the choices to be made in standards for the electronic exchange of health record information](https://discourse.openehr.org/t/insight-into-the-choices-to-be-made-in-standards-for-the-electronic-exchange-of-health-record-information/12498)
> For those of you interested: here \(http://www.vivici.nl/
insight\_into\_choices\_to\_be\_made/ \) you can download the translated
version of the document we've created within the Dutch mirror group
on information models & messages\.
This document will be presented at the joint ISO/TC 215 Health
Informatics and CEN/TC 251 Health Informatics meeting in Instanbul
later this month\. Hopefully it contributes to an even better
discussion about choices to be made in the various CEN/ISO...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [727] Tabular presentation for download links.](https://discourse.openehr.org/t/ref-impl-eiffel-727-tabular-presentation-for-download-links/16094)
> Revision: 727
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Ontologies as archetype inspiration (Was: Chief Complaint)](https://discourse.openehr.org/t/ontologies-as-archetype-inspiration-was-chief-complaint/13841)
> Hi\!
I agree with Knut's points\. It's probably often a good idea least have
a look in Snomed CT for inspiration, sometimes you will find that
things are well modelled and in other cases that another modelling
would be desirable\. The archetypes should be usable no matter if a
country is an IHTSDO\-member or not\. The same probably goes for other
ontologies like FMA \(http://fma.biostr.washington.edu/) or in some
areas other OBO ontologies \(http://www.obofoundry.org/). We don't...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [726] Add specialisation build links for Mac and Linux.](https://discourse.openehr.org/t/ref-impl-eiffel-726-add-specialisation-build-links-for-mac-and-linux/13081)
> Revision: 726
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [725] Remove a mapping that was added to adl_workbench.ecf in revision 721, apparently by accident.](https://discourse.openehr.org/t/ref-impl-eiffel-725-remove-a-mapping-that-was-added-to-adl-workbench-ecf-in-revision-721-apparently-by-accident/13080)
> Revision: 725
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL Workbench specialisation build available](https://discourse.openehr.org/t/adl-workbench-specialisation-build-available/14831)
> Dear all,
an interim build of the ADL workbench that implements far improved and
stricter validation is available here
http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
This is a pre\-cursor to a complete specialisation semantics, and also
template semantics defined in the forthcoming Template Object Model\. The
developers of other archetype parsers may like to have a look\. The
validation checks should now all correspond with the validity rules in
the ADL...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [724] Add specialisation build link](https://discourse.openehr.org/t/ref-impl-eiffel-724-add-specialisation-build-link/13079)
> Revision: 724
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[436] added support for empty attribute list block in dadl binding](https://discourse.openehr.org/t/436-added-support-for-empty-attribute-list-block-in-dadl-binding/13078)
> Revision: 436
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[435] added a new testcase to dadl-parser](https://discourse.openehr.org/t/435-added-a-new-testcase-to-dadl-parser/13827)
> Revision: 435
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[434] added a new test for empty attri block parsing in dadl](https://discourse.openehr.org/t/434-added-a-new-test-for-empty-attri-block-parsing-in-dadl/13077)
> Revision: 434
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 24, Issue 4](https://discourse.openehr.org/t/openehr-clinical-digest-vol-24-issue-4/15829)
> >>
>> Right, I am writing an open source HIS which hopefully will start
>> hospital deployments in the spring\. I am loading the official
>> archetypes to provide the core content and then anything I cannot map
>> I will assign a LOINC or SNOMED code and then map it to an archetype
>> later\.
>>
>> thanks for the info \!
>>
>> Greg
>>
>
> I would have thought that it would be better to do it the other way
> around i\.e\. map everything to archetypes and worry about the coding
> later?...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [723] Fix some bugs in conformance logic;](https://discourse.openehr.org/t/ref-impl-eiffel-723-fix-some-bugs-in-conformance-logic/13076)
> Revision: 723
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [chief complaint](https://discourse.openehr.org/t/chief-complaint/14824)
> Hi,
I am working on building a basic progress note with archetype data
elements\. I am looking for the most appropriate archetype for the
standard 'Chief Complaint' that the patient presents with, perhaps in
the patients words, perhaps defaulting with the registration reason
for visit\.
The best I can find is the "Clinical Description" under
openEHR\-EHR\-CLUSTER\.health\_event\.v1
Let me know if this is not the right place for basic mapping questions
thanks\!
Greg
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [adding contact to party](https://discourse.openehr.org/t/adding-contact-to-party/16091)
> I am happy to read in a book, that there are no dumb questions \(Head
First\-books\)
Let's try this one,
This is an example, there maybe better examples, but i hope my question
is clear:
What happens if a Contact is added to a Party in code?
This is easy to do, but what are the consequences?
How will the path look?
Suppose the Party to which the Contact is added had no contact\-list in
its archetype?
So what will be the path of the Contact which is then added in code to
the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL querying by internal code](https://discourse.openehr.org/t/aql-querying-by-internal-code/15831)
> Will the AQL queries qualifying on Archetype internal codes do so
using the value of the code and if so will it use the full path to
that value\.
For example if we wanted to find all patients with pupils observed to
be sluggish/slow would the query be:
Select pupils
> From EHR e CONTAINS Composition anyComposition CONTAINS Observation
pupils\[openEHR\-EHR\-OBSERVATION\.pupils\.v1\]
Where
pupils/data/events\[at0002\]/data/rows\[at0013\]/items\[at0015\]/value...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.5 draft 4 now available](https://discourse.openehr.org/t/adl-1-5-draft-4-now-available/16093)
> Dear all,
I have been hard at work on the ADL 1.5 specification, which will underpin the forthcoming openEHR template specification. A new draft of this specification is now available on the page
[http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes](http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes) . The exact URL for the PDF is...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [721] Further refinements to the validation code.](https://discourse.openehr.org/t/ref-impl-eiffel-721-further-refinements-to-the-validation-code/16090)
> Revision: 721
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [AQL queries](https://discourse.openehr.org/t/aql-queries/16092)
> > Currently you can get the paths from the Archetype workbench \- path
> view\. See
> http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
>
> \- thomas beale
Oh oh, now I am more confused :\-\)
So looking at body weight node structure I would have parsed a path
that would have included AT0004 in it to identify the discrete weight
data element \(as in mass\) \.
http://www.patientos.org/forum_temp/archetype.png
But the query path shown in the tool suggests that...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [openEHR-technical Digest, Vol 27, Issue 1](https://discourse.openehr.org/t/openehr-technical-digest-vol-27-issue-1/14830)
> > Currently you can get the paths from the Archetype workbench \- path
> view\. See
> http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
>
> \- thomas beale
Oh oh, now I am more confused :\-\)
So looking at body weight node structure I would have parsed a path
that would have included AT0004 in it to identify the discrete weight
data element \(as in mass\) \.
http://www.patientos.org/forum_temp/archetype.png
But the query path shown in the tool suggests that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL queries](https://discourse.openehr.org/t/aql-queries/14829)
> I still think it is unfortunate that none of the existing tools nor
the web based CKM show the appropriate AQL path for each data element\.
It is near impossible to manually build
\.\.\.
WHERE openEHR\-EHR\-OBSERVATION\.blood\_pressure\.v1/data\[at0001\]/events\[at0006\]/data\[at0003\]/items\[at0004\]/value/value
> = 140
the only way I can do it is to write code to parse the ADL and build
the path but I have nothing to validate that my implementation was
correct
it would be nice to have a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [commitAudit](https://discourse.openehr.org/t/commitaudit/14828)
> Please allow me a simple question.
The VERSION class has a commit-audit, in the specs description: Audit trail corresponding to the committal of this version to the VERSIONED_OBJECT. This cannot be void.
The VERSION class has also a contribution: a reference to a contribution in which this version was added. Also this cannot be void.
The CONTRIBUTION class has also a audit, in the specs description: Audit trail corresponding to the committal of this contribution, also may not be void.
I don...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AQL-parser in Java? + AQL response format (using the AS operator)](https://discourse.openehr.org/t/aql-parser-in-java-aql-response-format-using-the-as-operator/13724)
> Hi\!
1\. Has anybody planned, or started, to create an AQL\-parser in Java?
Maybe the basics from AQL to parse tree could be common for several
different persistence implementations and then the rest of the
implementation will be different for different persistence mechanisms\.
Our first interest will be in transforming AQL queries to queries
against an XML\-database containing versioned Compositions\. \(It's for
an educational system where performance isn't crucial\.\)
2\. Are...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [SNOMED/LOINC mapping](https://discourse.openehr.org/t/snomed-loinc-mapping/14827)
> Hi,
One of the things that has been holding me up is the conundrum around
coded clinical documentation\.
I would use OpenEHR exclusively but as I delve into the depths of
integration I am getting nervous that the archetypes have not yet been
mapped to LOINC or SNOMED\.
As an example comparison take a patients \(non\-birth\) weight for
example\. In pediatric hospitals and for patients receiving chemo it
has always been critical to differentiate between a carefully measured
weight suitable...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ArchetypeOntology](https://discourse.openehr.org/t/archetypeontology/14826)
> Hi All,
While attempting to implement the ArchetypeOntology I have ran into some
confusion\.
The attributes term\_codes and constraint\_codes are documented as being a
List of strings\.
However, it seems to me that they should be a List of ArchetypeTerms\. So
that the code is associated with the Hash \(or Tuple\) of the
text/description etc\.
how is everyone else implementing this?
\-\-Tim
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Using adl-parser from jar-file](https://discourse.openehr.org/t/using-adl-parser-from-jar-file/14825)
> Hi,
I downloaded and tested the ADL-parser jar-file from
[http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm](http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm)
I got the following error
Exception in thread "main" java.lang.NoClassDefFoundError: org/openehr/rm/support/measurement/SimpleMeasurementService
at se.acode.openehr.parser.ADLParser.(ADLParser.java:49)
at se.acode.openehr.parser.ADLParser.(ADLParser.java:56)
at...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [720] EDT-344: In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, prevent a Void target call when serialising a term code that does not exist in the ontology.](https://discourse.openehr.org/t/ref-impl-eiffel-720-edt-344-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-prevent-a-void-target-call-when-serialising-a-term-code-that-does-not-exist-in-the-ontology/13073)
> Revision: 720
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [In praise of things that work....](https://discourse.openehr.org/t/in-praise-of-things-that-work/12110)
> Dear all,
I was just contemplating this weekend about our choice of website technology (i.e. Helma's recommendation of Daisy/Cocoon). After a few initial hiccups and reservations, I remember her saying, just give it a year and see how it goes. I am pleased to say I think it has after all been a great choice. It's not the most exciting website in the world, but in terms of effort to keep it going, it has been absolutely minimal, and far less time-consuming than our previous situation. And it...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [719] AWB-147: Changes copied from revision 715 in BRANCHES/specialisation:](https://discourse.openehr.org/t/ref-impl-eiffel-719-awb-147-changes-copied-from-revision-715-in-branches-specialisation/13072)
> Revision: 719
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [718] In TAGS/Aug2007, which contains the source code for the current public build of the ADL Parser DLL, add files that the SConstruct needs for building the ADL Workbench installer.](https://discourse.openehr.org/t/ref-impl-eiffel-718-in-tags-aug2007-which-contains-the-source-code-for-the-current-public-build-of-the-adl-parser-dll-add-files-that-the-sconstruct-needs-for-building-the-adl-workbench-installer/13069)
> Revision: 718
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [717] Remove a couple of obsolete files that have somehow been left behind in BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-717-remove-a-couple-of-obsolete-files-that-have-somehow-been-left-behind-in-branches-specialisation/13814)
> Revision: 717
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [716] Missed validity message.](https://discourse.openehr.org/t/ref-impl-eiffel-716-missed-validity-message/13068)
> Revision: 716
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [715] Set of changes to fix bug reported in AWB-147:](https://discourse.openehr.org/t/ref-impl-eiffel-715-set-of-changes-to-fix-bug-reported-in-awb-147/13067)
> Revision: 715
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [714] Further adjustments to specialised archetype validation and flattening - some bugs removed and code cleaned up in cADL parser;](https://discourse.openehr.org/t/ref-impl-eiffel-714-further-adjustments-to-specialised-archetype-validation-and-flattening-some-bugs-removed-and-code-cleaned-up-in-cadl-parser/13066)
> Revision: 714
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[433] minor change in CDvOrdinal so the order of ordinals is kept](https://discourse.openehr.org/t/433-minor-change-in-cdvordinal-so-the-order-of-ordinals-is-kept/13065)
> Revision: 433
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[432] changes due to renaming of attribute in CDvQuantityItem](https://discourse.openehr.org/t/432-changes-due-to-renaming-of-attribute-in-cdvquantityitem/13064)
> Revision: 432
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[431] renamed the attribute of CDvQuantityItem according to the specs](https://discourse.openehr.org/t/431-renamed-the-attribute-of-cdvquantityitem-according-to-the-specs/13063)
> Revision: 431
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[430] added a convenience method to get termDefinition from onology for the primary language](https://discourse.openehr.org/t/430-added-a-convenience-method-to-get-termdefinition-from-onology-for-the-primary-language/16088)
> Revision: 430
Author: rong\.chen
Log Message:
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [AQL for Decision Support](https://discourse.openehr.org/t/aql-for-decision-support/14833)
> Dear All,
I’d like to this message could kick off the discussion about AQL - a common query language - for decision support.
Archetype Query Language (AQL) is a semantic query language. It is archetype specific, but neutral to system design/implementation. It can be used to query archetype-based data at any level of granularity within a system, cross system boundaries or enterprise-wide. It can retrieve all compositions of a particular EHR , all compositions specific to archetypes for a...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Link error to release 1.0.1](https://discourse.openehr.org/t/link-error-to-release-1-0-1/14834)
> Hi\!
Now when RC 1\.0\.2 has been added to the side menu on openEHR\.org there
are two ways to get to version 1\.0\.1, the SVN one should not be used:
Specification Project
\- Current Release <\- This link is correct\. \(/releases/1\.0\.1/\)
\- Release 1\.0\.2 candidate \(OK in SVN until release\)
\- Release 1\.0\.1 <\- Wrong link target \(in SVN\)
The links to released specifications we want people to bookmark, cite
in papers/webpages and indexed by search engines should start...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [713] More improvements to validation of specialised archetypes, including implementation of conformance checking for more primitive types - the C_DATE, C_TIME and C_DATE_TIME types.](https://discourse.openehr.org/t/ref-impl-eiffel-713-more-improvements-to-validation-of-specialised-archetypes-including-implementation-of-conformance-checking-for-more-primitive-types-the-c-date-c-time-and-c-date-time-types/16087)
> Revision: 713
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Building RMObject objects from Archetype objects](https://discourse.openehr.org/t/building-rmobject-objects-from-archetype-objects/14823)
> Hi all,
I looked at the packages in the TRUNK folder\. After using the ADLParser
class to get an Archetype object from an adl file, my next wish was to
build a RMObject from that Archetype\. I looked at the org\.openehr\.build
package but it does not seem to be using Archetype objects\.
Basically I wonder if there is something like this class \(that I called
RMArchetypedObjectBuilder\) currently:
Archetype myArchetype = \.\.\.\.;
RMObject rmObject =...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[429] minor pom change in dadl-parser](https://discourse.openehr.org/t/429-minor-pom-change-in-dadl-parser/13802)
> Revision: 429
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [eHealth-INTEROP Report in response to EU Mandate/403-2007](https://discourse.openehr.org/t/ehealth-interop-report-in-response-to-eu-mandate-403-2007/14817)
> Dear all,
Today the final draft of the eHealth-INTEROP Report in response to EU Mandate/403-2007 was published. The report can be downloaded from: [http://www.ehealth-interop.nen.nl](http://www.ehealth-interop.nen.nl)/
Comments and suggestions to this document can be made to NEN untill october 22th.
**Scope:**
The European Commission has issued in 2007 a mandate to the European Standardization Organizations (ESOs), CEN, CENELEC, and ETSI, to develop a coordinated work programme for...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [712] Fix a typo in the last commit.](https://discourse.openehr.org/t/ref-impl-eiffel-712-fix-a-typo-in-the-last-commit/13801)
> Revision: 712
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [711] The SConstruct now depends on SCons 1.0 or higher.](https://discourse.openehr.org/t/ref-impl-eiffel-711-the-sconstruct-now-depends-on-scons-1-0-or-higher/13061)
> Revision: 711
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [710] Slight refactoring of validation logic to improve maintainability.](https://discourse.openehr.org/t/ref-impl-eiffel-710-slight-refactoring-of-validation-logic-to-improve-maintainability/13060)
> Revision: 710
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [709] Add the i18n library to the ADL parser DLL project so that it will build.](https://discourse.openehr.org/t/ref-impl-eiffel-709-add-the-i18n-library-to-the-adl-parser-dll-project-so-that-it-will-build/13059)
> Revision: 709
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [708] Refinements to validity error codes and messages for adding child objects to attributes](https://discourse.openehr.org/t/ref-impl-eiffel-708-refinements-to-validity-error-codes-and-messages-for-adding-child-objects-to-attributes/13058)
> Revision: 708
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Demographics Archetypes](https://discourse.openehr.org/t/demographics-archetypes/13811)
> >
All,
When I try to pull the demographics archetype from the following link on the OpenEHR website, I get a 404 error. Can someone test to see if they get the same error?
[http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr/demographic/openehr-demographic-person.person.draft.html](http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr/demographic/openehr-demographic-person.person.draft.html)
Thanks,
Eddy Rospide
|
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Tool for validation of archetyped RM instance against corresponding archetypes?](https://discourse.openehr.org/t/tool-for-validation-of-archetyped-rm-instance-against-corresponding-archetypes/12624)
> Dear all,
I am looking for a tool that allows to validate an instance of the reference model, which complies with one or more archetypes, against these archetypes. Is such a tool available?
Thank you for any help,
Georg
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [707] Remaining error message conversion changes.](https://discourse.openehr.org/t/ref-impl-eiffel-707-remaining-error-message-conversion-changes/13787)
> Revision: 707
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [705] Initial (unfinished) pass at converting all AWB messages to strings within the Message database (IN_MEMORY_MESSAGE_DB class).](https://discourse.openehr.org/t/ref-impl-eiffel-705-initial-unfinished-pass-at-converting-all-awb-messages-to-strings-within-the-message-database-in-memory-message-db-class/13053)
> Revision: 705
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Contribution](https://discourse.openehr.org/t/contribution/13062)
> Hi,
I hope this is a simple question
What do I do with a contribution in a version where a contribution is not needed (there are no logical changes to connect)
For example, imagine a Party object which is stored in a version in a versionedparty, and that party has no other related information, so the Contribution is useless.
The problem is that in a Version an Objectref to a Contribution may not be void, and that in a Contribution a set of ObjectRefs may not be empty.
How is this to be...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Using the jar-files](https://discourse.openehr.org/t/using-the-jar-files/13057)
> Hi,
I downloaded and tested using the openehr-rm-core from
[http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm](http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm)
It appears that this requires packages Apache Commons to work.
Perhaps this should be mentioned on the download page?
Regards
Olof
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[428] fixed unnecessary depenedency on the order of language and author elements in the archetype language translations parsing](https://discourse.openehr.org/t/428-fixed-unnecessary-depenedency-on-the-order-of-language-and-author-elements-in-the-archetype-language-translations-parsing/16086)
> Revision: 428
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem with ADL Parser and unusual order in translation details](https://discourse.openehr.org/t/problem-with-adl-parser-and-unusual-order-in-translation-details/15689)
> Dear Rong, Thomas, and all
The Java ADL Parser seems to expect that a translation details are always in a given order...
For example the following will lead to a parser error because the parser expects language instead of author first:
> ```
> language
> original_language = <[ISO_639-1::en]>
> translations = <
> ["de"] = <
> author = <
> ["organisation"] = <"Central Queensland University, University of Heidelberg">
> ["name"] = <"Sebastian Garde, Jasmin Buck">
> >
>...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[427] added a testcase on archetype_id with concept_name in Swedish](https://discourse.openehr.org/t/427-added-a-testcase-on-archetype-id-with-concept-name-in-swedish/16085)
> Revision: 427
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Representing templates](https://discourse.openehr.org/t/representing-templates/13775)
> Hi,
I'm new to this list but has been working with information systems aimed at medicine for some time.
I'm involved in a project where we would like to use openEHR for modelling clinical data for decision support.
This means that we need to create and use some archetypes and templates.
From these we could then create a user interface for our application.
Now, my question:
I've looked at the Java-doc but do not find anything related to templates.
Before we start writing code to manage...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new presentation avialable on openEHR, open source, strategic issues](https://discourse.openehr.org/t/new-presentation-avialable-on-openehr-open-source-strategic-issues/16084)
> I gave a presentation the other day at the EFMI special topic conference
organised here in London by the British Computer Society\. It contains
some observations about how to understand the structure of the health
ICT domain, and what openEHR's role can be\. See
http://www.openehr.org/downloads/presentations/EFMI_2008_openEHR.zip
\- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from bert.verhees@rosa.nl requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-bert-verhees-rosa-nl-requires-approval/13052)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@openehr\.org
Reason: Message body is too big: 71920 bytes with a limit of 40 KB
At your convenience, visit:
http://lists.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
to approve or deny the request\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [704] Minor but important improvements to path processing correctness;](https://discourse.openehr.org/t/ref-impl-eiffel-704-minor-but-important-improvements-to-path-processing-correctness/13051)
> Revision: 704
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [10 Dutch hospitals choose for EPD from Google or Microsoft](https://discourse.openehr.org/t/10-dutch-hospitals-choose-for-epd-from-google-or-microsoft/14816)
> This announced yesterday, together they form 20% of the market\. There is
a lot of press attention, even from non\-traditional ICT/healthcare press\.
Seems a important move, after seven years designing, hospiutals choose
something completely different\.
Some links for the Dutch readers\. \(others can translate them with...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [XML Focus Group for openehr](https://discourse.openehr.org/t/xml-focus-group-for-openehr/14815)
> Dear All,
After the series of posts on "Re: Archetyping Methodology\-Mind Mapping" back in July and \(see below\) on Mind Mapping Archetypes\. I raised a question to a group within Ocean Informatics which later included others listed below:
Sebastian Garde; Lisa Thurston; Thomas Beale; Heather Leslie; Adam Flinton; Heath Frankel;Federici Massimilliano; Olusegun Odujebe; Sam Heard
The proposal is to have an XML Focus Group and/or List within openehr to look and work at...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [VERSIONED_OBJECT uid question](https://discourse.openehr.org/t/versioned-object-t-uid-question/14812)
> Hi all,
I am implementing some of the versioned document
semantics and have a quick query\.
VERSIONED\_OBJECT<T> has a 'uid' attribute
that is meant to represent a unique identifier
for all versions of this object \- so kind of like
the master identifier for this document set\.
It is of type HIER\_OBJECT\_ID
VERSION<T> is a particular instance of a
document version \- so many VERSION<T>
documents may be part of one overall
VERSIONED\_OBJECT \(amendments etc\)\.
It...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [702] Corrections to properly handle object node redefined into multiple sibling nodes, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-702-corrections-to-properly-handle-object-node-redefined-into-multiple-sibling-nodes-e-g/13049)
> Revision: 702
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [701] The CruiseControl server now has SCons 1.0 installed, which developer_page.htm now mentions as being the minimum requirement.](https://discourse.openehr.org/t/ref-impl-eiffel-701-the-cruisecontrol-server-now-has-scons-1-0-installed-which-developer-page-htm-now-mentions-as-being-the-minimum-requirement/13048)
> Revision: 701
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [700] Correct logic for insertion of sibling nodes prior to 'after' ordering marker - now they go before the last insert_object in the flat parent.](https://discourse.openehr.org/t/ref-impl-eiffel-700-correct-logic-for-insertion-of-sibling-nodes-prior-to-after-ordering-marker-now-they-go-before-the-last-insert-object-in-the-flat-parent/13047)
> Revision: 700
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [699] Additions for the case of multiple sibling redefinitions of a single node in the parent (classic example - lab-lipids redefinition of node at0013 into at0013.1, at0013.2).](https://discourse.openehr.org/t/ref-impl-eiffel-699-additions-for-the-case-of-multiple-sibling-redefinitions-of-a-single-node-in-the-parent-classic-example-lab-lipids-redefinition-of-node-at0013-into-at0013-1-at0013-2/13046)
> Revision: 699
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Python/openEHR workshop, XVIII IEA World Congress of Epidemiology, Porto Alegre, Brazil](https://discourse.openehr.org/t/python-openehr-workshop-xviii-iea-world-congress-of-epidemiology-porto-alegre-brazil/16082)
> Hi All,
This is really an announcement but I was invited to send it to this list
in case there are interested parties reading these emails and not the
announce list\.
There will be a 1\.5 day workshop on openEHR using the Python
implementation \(aka\. OSHIP\) at the XVIII IEA World Congress of
Epidemiology in Porto Alegre,Brazil
http://www.epi2008.com.br/ingles/index.php on 20 & 21 September, 2008\.
The workshop registration link...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[426] Updating files](https://discourse.openehr.org/t/426-updating-files/13045)
> Revision: 426
Author: leonardo\.lezcano
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[425] Updating sources](https://discourse.openehr.org/t/425-updating-sources/13044)
> Revision: 425
Author: leonardo\.lezcano
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[424]](https://discourse.openehr.org/t/topic/13043)
> Revision: 424
Author: leonardo\.lezcano
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [698] Add a postcondition.](https://discourse.openehr.org/t/ref-impl-eiffel-698-add-a-postcondition/16083)
> Revision: 698
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [697] AWB-128: In the TRUNk and in BRANCHES/specialisation, complete the upgrade to EiffelStudio 6.2 by copying changes from EiffelStudio 6.2's .NET implementation of INTERNAL to our override of it.](https://discourse.openehr.org/t/ref-impl-eiffel-697-awb-128-in-the-trunk-and-in-branches-specialisation-complete-the-upgrade-to-eiffelstudio-6-2-by-copying-changes-from-eiffelstudio-6-2s-net-implementation-of-internal-to-our-override-of-it/13036)
> Revision: 697
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [696] In BRANCHES/specialisation, add the new reference_model_checker cluster to adl_parser.ecf so that it will compile.](https://discourse.openehr.org/t/ref-impl-eiffel-696-in-branches-specialisation-add-the-new-reference-model-checker-cluster-to-adl-parser-ecf-so-that-it-will-compile/13034)
> Revision: 696
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [695] First working version of proper archetype flattening.](https://discourse.openehr.org/t/ref-impl-eiffel-695-first-working-version-of-proper-archetype-flattening/13761)
> Revision: 695
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [possible bug in VersionedObject.java](https://discourse.openehr.org/t/possible-bug-in-versionedobject-java/16680)
> Please correct me if I am wrong, but I think I found a bug in the Java-code.
In this source we find following code snippet
`// in order to skip map timeVersionMap to table`
`void setVersions(Set> versions) {`
`idVersionMap = new HashMap>();`
`timeVersionMap = new TreeMap>();`
`for(Version version : versions) {`
`addVersion(version);`
`}`
`}`
I discover unpredictable behavior ot this, and in some cases leading to an...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ehr2ont Joints the openEHR Java project](https://discourse.openehr.org/t/ehr2ont-joints-the-openehr-java-project/13035)
> (sorry about the previous post without body text)
Dear all,
I am glad to announce that the team behind the software ehr2ont, which is a translator from ADL to OWL, has accepted the invitation to join the openEHR Java project and continue to maintain the software through the common infrastructure of the java project. This move would not only make it easy to synchronize the ehr2ont components with other components released by the Java project, but also make the software more accessible to the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [versioning](https://discourse.openehr.org/t/versioning/14814)
> Hi
I have a question about versioning.I'm afraid I haven't get it.
Regarding the openEHR common doc.it seems that any changes in an object usch as composition, cause creating a new version in its version container.Am I right.Or changes records in an audit?
And if it is true so why we save contribution objects too?I mean there will be overlapping 'cos' as I understood contributions will cause creating nwe versions.
Couls someone help me please?
Besr Regards
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[423] Updating files](https://discourse.openehr.org/t/423-updating-files/16081)
> Revision: 423
Author: leonardo\.lezcano
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[422] Updating files](https://discourse.openehr.org/t/422-updating-files/16080)
> Revision: 422
Author: leonardo\.lezcano
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[421] Updating files](https://discourse.openehr.org/t/421-updating-files/16079)
> Revision: 421
Author: leonardo\.lezcano
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Slots, naming and merging](https://discourse.openehr.org/t/slots-naming-and-merging/16078)
> Dear All
I have started a Wiki page on Slots as we are definitely finding issues with different approaches. Please have a look at:
[http://www.openehr.org/wiki/display/spec/Slots%2C+naming+and+merging](http://www.openehr.org/wiki/display/spec/Slots%2C+naming+and+merging)
and comment on the solution that is proposed - edit it, comment and embellish.
Cheers, Sam
[details="(attachments)"]
[/details]
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ehr2ont Joints the openEHR Java project](https://discourse.openehr.org/t/ehr2ont-joints-the-openehr-java-project/16076)
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [automatic generation of templates](https://discourse.openehr.org/t/automatic-generation-of-templates/14813)
> Hi Nancy
We don't see the proliferation of Templates as an issue because they should be ALL based on a much smaller number of shared archetypes. That means that if two different labs use a slightly different request format (or even different departments in the same institution), as long as the underlying archetypes are the same, then the data created is shareable and means the same thing. This approach allows for the semantics to be rigidly captured, while giving the flexibility to allow for...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [feeder_audit <> audit_details](https://discourse.openehr.org/t/feeder-audit-audit-details/13039)
> Hi,
I'm trying to understand how the auditing is recorded in the openEHR model,
and I'm a bit confused\.
As I understand it, changes to a Composition can occur either due to
somebody changing something locally, or due to changes that come from some
external system\. Local changes are traced using AUDIT\_DETAILS instances that
come together with versioned objects \(in the case that the composition is
versioned\)\. But changes coming from external parties are recorded in
FEEDER\_AUDIT...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[420] initial import of ehr2ont component to the sandbox area](https://discourse.openehr.org/t/420-initial-import-of-ehr2ont-component-to-the-sandbox-area/16075)
> Revision: 420
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Chair of openEHR Clinical Review Board (CRB) announced](https://discourse.openehr.org/t/chair-of-openehr-clinical-review-board-crb-announced/14884)
> \[this is a repost of an announcement made a week ago, for those on the clinical list but not on the announce list\]
from Prof David Ingram, CHIME department, University College London:
I am delighted to announce that Dr Tony Shannon has accepted an
invitation, on behalf of the openEHR Foundation Board, to take over the
chair of the Clinical Review Board\. Tony has long experience and
interest in clinical information management, as Clinical Lead for the
Clinical Content Service of NHS...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR training course, London 29, 30 September](https://discourse.openehr.org/t/openehr-training-course-london-29-30-september/16077)
> The CHIME department, University College London, is hosting a 2-day training course on openEHR and SNOMED CT at the Whittington campus, Archway London on 29 and 30 September.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is there a UML class diagram for templates?](https://discourse.openehr.org/t/is-there-a-uml-class-diagram-for-templates/14811)
> Preferably in Eclipse UML2\.\.\.?
If so does it then include the archetypes class model as well?
Adam
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Differential display](https://discourse.openehr.org/t/differential-display/14819)
> Dear All (cross post)
We are working in an environment where many applications and CDA messages have information that is displayed as text and repeated information in structured form. This also arises in applications which have a formatted document plus structured information (typically in primary care).
I am proposing that we have a section archetype to manage this. The archetype display script would not display any information about the section itself (it would be invisible) and would...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [proposed improvement in Resource menu](https://discourse.openehr.org/t/proposed-improvement-in-resource-menu/14810)
> Dear all,
the current 'Who is using it' menu uption under 'Resources' has the following sub-items
- Who is using it
- openEHR - commercial- openEHR - governments- openEHR - academic- GeHR Australia- GEHR + CEN- GEHR (original)- Related Projects
In the interests of clarity, being more up to date, and also being able to handle a new group of 'who's using it' - non-profits - I propose the following:
- Who is using it
- Commercial- Government- Academic
- Non-profit- GEHR
- GeHR Australia-...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Chair of openEHR Clinical Review Board (CRB) announced](https://discourse.openehr.org/t/chair-of-openehr-clinical-review-board-crb-announced/13040)
> from Prof David Ingram, CHIME department, University College London:
I am delighted to announce that Dr Tony Shannon has accepted an
invitation, on behalf of the openEHR Foundation Board, to take over the
chair of the Clinical Review Board\. Tony has long experience and
interest in clinical information management, as Clinical Lead for the
Clinical Content Service of NHS Connecting for Health and as Consultant
in Emergency Medicine at Leeds Teaching Hospitals\.
My UCL colleague, Dr Dipak...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes and terminologies.](https://discourse.openehr.org/t/archetypes-and-terminologies/14809)
> What happens if an end\-user wants to create a template and use a terminology as often as possible, and the archetypes are constrained to be free text instead of terminology?
Shouldn't all archetypes enable the use of a terminology?
For example: In the well\-known observation\.blood\_pressure the person state position is constrained to internal codes and one of them is "sitting"\. What if the template creator wants to use the SNOMED term 33586001 instead of an internal...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [archetype as ontology](https://discourse.openehr.org/t/archetype-as-ontology/14808)
> Hello there,
I am looking for "openEHR.org/knowledge site" within openEHR.org . Has this site live now? Could you please provide me link?
Regards,
**Pratima P. Acharya**
6/459 Remuera Rd,
Remuera, Auckland
Cell +6421823126
Home +6495224976
Skype praima.acharya
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes for EN13606 RM](https://discourse.openehr.org/t/archetypes-for-en13606-rm/14802)
> Hi, I'm starting a research on EN13606. In many places mention that EN13606 defines archetypes to constraint it RM, but I can't find the spec of such archetypes.
Anyone knows if there is a spec for EN13606 archetypes?
If I make an archetype with the OpenEHR archetype editor, this archetype is compatible with the EN13606 RM? I see in OEHR website that OEHR is compatible with EN13606, but I don't know if this compatibility extends to the archetypes too.
Thanks a lot!
Pablo.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [694] AWB-133: Minor correction to a comment in the cADL lexer.](https://discourse.openehr.org/t/ref-impl-eiffel-694-awb-133-minor-correction-to-a-comment-in-the-cadl-lexer/13033)
> Revision: 694
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [693] Merge trunk versions 664 - 692 to specialisation branch](https://discourse.openehr.org/t/ref-impl-eiffel-693-merge-trunk-versions-664-692-to-specialisation-branch/13032)
> Revision: 693
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [692] Correct the use of the build_completed flag.](https://discourse.openehr.org/t/ref-impl-eiffel-692-correct-the-use-of-the-build-completed-flag/13031)
> Revision: 692
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [691] Correct an existing error in conformance of tool to ADL 1.4 standard - type names in dADL, including dADL sections in cADL now parse with ().](https://discourse.openehr.org/t/ref-impl-eiffel-691-correct-an-existing-error-in-conformance-of-tool-to-adl-1-4-standard-type-names-in-dadl-including-dadl-sections-in-cadl-now-parse-with/13030)
> Revision: 691
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ehr2ont: An open source translator from ADL to OWL](https://discourse.openehr.org/t/ehr2ont-an-open-source-translator-from-adl-to-owl/13029)
> Dear openehr\-technical users,
This message is to announce the release of a Java\-based implementation of a translator of OpenEHR archetypes to OWL, which may be of interest for the users of this list\. The translator uses an OWL ontology of the reference model that is linked in the OpenEHR pages, and the APIs of the Java reference implementation of OpenEHR\.
The code is LGPL and it is now hosted in:
http://code.google.com/p/ehr2ont/
This is an early release and of course feedback and bug...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Release 1.0.2 - SPEC-268 - Correct missing parentheses in dADL type identifiers.](https://discourse.openehr.org/t/release-1-0-2-spec-268-correct-missing-parentheses-in-dadl-type-identifiers/16073)
> Implementers of ADL/dADL and related XML software should have a look at
this CR which has been accepted for the next minor release \-
http://www.openehr.org/issues/browse/SPEC-268
Make sure you have a look at the 'Raise CR' and 'Analysis' tabs\.
The main thing to consider is a time interval over which you would make
this correction in your tools, and also allow the previous \(quite
common\) non\-parenthesised form of ADL archteypes to exist\. Please post
any reactions on...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Hello [ffehr]](https://discourse.openehr.org/t/hello-ffehr/16071)
> Hello thomas,
ffehr is using XUL of mozilla and run's preferably under the xulrunner engine\. Part of the goal is to have it under a small USB device and need not have any network access\. Ffehr should be able to serve in areas where net access is not reliable or non\-existent\.
Upon googling for HL7 specs I have stumbled upon openEHR, which I find to have it's specs open for the public to download\. However, my expertise is not so much in this area but I am doing my best to...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Hello](https://discourse.openehr.org/t/hello/14805)
> Hello all,
I am nathaniel b\. jayme the lead developer of ffehr \- ffehr\.freefeathers\.org
I would like to advance the project by adopting the specifications of openEHR via XSLT\. However, my knowledge in openEHR specs is somewhat limited\. I sure could use more help from develpers in this list\.
If you know of technical persons interested in ffehr and willing to contribute their time please link them up with my email\.
Thanks in...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [multiple questions: database, archetypes, templates](https://discourse.openehr.org/t/multiple-questions-database-archetypes-templates/14803)
> Hi,
In the last couple of weeks I've been studying a bunch of openEHR documents
to see whether or not we want to use it in our own project, but I stumble
upon some questions\. Perhaps somebody in this community is able to direct me
to the right direction for answering these\.\.\.
1\. openEHR has a quite solid model, but at the end of the day you always
need some form of persistance\. I've read about some suggested ways of
working on the openEHR website, but I'm not convinced any...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [chile update](https://discourse.openehr.org/t/chile-update/13735)
> Dear Thomas,
Just got your update in openehr, just to let you know that we are working at the academic level with Erika Caballero in this open source tool for educational purposes and publication in SPANISH.
Also, with Dra Rojas together with our colleague Fernanda from the Ministry of Health , we are creating working groups to create a road map of implementation of open ehr as a standard of care in short and long term basis. Lots of networking work.
The projects will be presented in...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [690] Fix a bug caused by the recent change that made clean_generated_files reliant on the build status of the archetype repository.](https://discourse.openehr.org/t/ref-impl-eiffel-690-fix-a-bug-caused-by-the-recent-change-that-made-clean-generated-files-reliant-on-the-build-status-of-the-archetype-repository/16072)
> Revision: 690
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updating government, commercial and academic use of openEHR](https://discourse.openehr.org/t/updating-government-commercial-and-academic-use-of-openehr/16074)
> On the pages
http://www.openehr.org/shared-resources/usage/governments.html
http://www.openehr.org/shared-resources/usage/commercial.html
http://www.openehr.org/shared-resources/usage/academic.html
there is information about current use of openEHR\. We would like to hear
from anyone with updates for these pages\.
\- thomas beale
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [keeping 'who's using it' up to date](https://discourse.openehr.org/t/keeping-whos-using-it-up-to-date/13041)
> Dear all,
the page http://www.openehr.org/shared-resources/usage/academic.html is
becoming out of date \- both some non\-current research, and requests for
new items to go on there\. I would propose to rearrange the page a bit:
put it into 2 blocks, 'current research' and 'past research'\. Then in
each block, I would suggest to alphabetically sort the rows on country\.
thoughts?
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DADL optional rm-type](https://discourse.openehr.org/t/dadl-optional-rm-type/13038)
> Hi,
I wrote another message before, earlier this week, but that was addresses to
the Java\-list, but I now think it is a problem of specification\.
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [AQL](https://discourse.openehr.org/t/aql/14806)
> Dear All
Ocean's proposal for an Archetype Query Language has been around for a year now:
For a general time line and introduction see:
[http://www.openehr.org/wiki/display/spec/openEHR+Query+Specifications](http://www.openehr.org/wiki/display/spec/openEHR+Query+Specifications)
The AQL Specifications:
[http://www.openehr.org/wiki/display/spec/Archetype+Query+Language+(AQL)](http://www.openehr.org/wiki/display/spec/Archetype+Query+Language+(AQL))
Queries will be required to based elements...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [findMatchingRMClass](https://discourse.openehr.org/t/findmatchingrmclass/14799)
> Hi Rong,
It took me some time before I discovered what this method is for, it is used
in dadl\-binding\.
It doesn't work reliable for me, often retunring the wrong RMtype, when
stepping hrough the code, I can always explain why\.
Isn't it a shortcoming of the dadl\-specs, to allow data without rm\-type
specification?
I ask this, because, the findMatchingRMClass\-method, does not work very
reliable \(for me\), and also, if this method is used in large amounts of data\-
processing,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new draft of ADL 1.5 available](https://discourse.openehr.org/t/new-draft-of-adl-1-5-available/12032)
> See ADL heading at [http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes](http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes)
The latest draft includes quite a lot of changes in the cADL section that hopefully resolve a number of anbiguities present in ADL and archetype semantics in general. The new Specialisatoin section is also improved, although not yet finished.
The changes for ADL 1.5 include:
- the semantics of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [689] Small refactoring + slight correction of inheritance status of C_DV_ORDINAL and C_CODE_PHRASE to propagated rather than inherited.](https://discourse.openehr.org/t/ref-impl-eiffel-689-small-refactoring-slight-correction-of-inheritance-status-of-c-dv-ordinal-and-c-code-phrase-to-propagated-rather-than-inherited/13026)
> Revision: 689
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.2 change - SPEC-260 - Correct the regex published for the ARCHETYPE_ID type (due date 304/Aug/08)](https://discourse.openehr.org/t/release-1-0-2-change-spec-260-correct-the-regex-published-for-the-archetype-id-type-due-date-304-aug-08/14804)
> Dear all,
The CR SPEC\-260 \(http://www.openehr.org/issues/browse/SPEC-260) being
processed for Release\-1\.0\.2 proposes an updated regular expression and
syntax to match Archetype identifiers\. The changes are visible in
section 4\.3\.10 of the Support IM document at
http://www.openehr.org/svn/specification/BRANCHES/Release-1.0.2-candidate/publishing/architecture/rm/support_im.pdf
Any feedback on the proposed regular expression would be appreciated\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem building java-impl: missing acode:adl-parser:jar:1.0.5-SNAPSHOT](https://discourse.openehr.org/t/problem-building-java-impl-missing-acodejar-1-0-5-snapshot/14798)
> I try to build the java\-impl project \- almost went thru but building the ADL
Serializer fails with the message below\.
\(Alternatively I tried to look for the adl\-serializer\.jar on the project
page \(http://www.openehr.org/svn/ref_impl_java/TRUNK/docs/download.htm) to
download the binary, but couldn't find it there, only the adl\-parser is
there\.\)
My environment:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[419] removed redundant parent attribute in the Event class and added equality check for Event](https://discourse.openehr.org/t/419-removed-redundant-parent-attribute-in-the-event-class-and-added-equality-check-for-event/13025)
> Revision: 419
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Request fort commit](https://discourse.openehr.org/t/request-fort-commit/13027)
> Hi Rong,
TRUNK code is mixed up with referenceUid and referenceID \(in
small/uppercase\)\. The referenceID is legacy\. It exists in some files,
and other have the referenceUid\.
I cleaned it up in my code according the specifications \(changed all
referenceID to referenceUid, also getters setters, etc\.\)\. I occured more
than I suspected, also in all inherited objects of version,
folderversion, etc\. in testfiles\.\.\.\.
I also changed it in my local copy of the svn TRUNK code, and I...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[418] changed version->rightBrace-location to value.lastIndexOf (instead](https://discourse.openehr.org/t/418-changed-version-rightbrace-location-to-value-lastindexof-instead/13722)
> Revision: 418
Author: bert\.verhees
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Where is the Archetype spec?](https://discourse.openehr.org/t/where-is-the-archetype-spec/16679)
> Dear All,
I have been poking about the openEhr site looking for something which
definitively says what an archetype is, preferably in a computable form\.
is there a UML model/adl/XML schema which is downloaded & which is the
definative/normative definition\.
Adam
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[417] referenceRanges to otherReferenceRanges (forgot in a spot)](https://discourse.openehr.org/t/417-referenceranges-to-otherreferenceranges-forgot-in-a-spot/16069)
> Revision: 417
Author: bert\.verhees
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[416] changed referenceRanges to otherReferenceRanges in constructor,](https://discourse.openehr.org/t/416-changed-referenceranges-to-otherreferenceranges-in-constructor/16068)
> Revision: 416
Author: bert\.verhees
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [double parent-attribute in Event/Pathable](https://discourse.openehr.org/t/double-parent-attribute-in-event-pathable/16070)
> Excuse me if this has been discussed before, I must have missed it then\.
In Event \(which inherits from Pathable\) we have an attribute called
parent of type History<T> \(which inherits from Pathable\)
In Pathable we also have an attribute parent, which is made invisible,
but gets a value at the constructor of Event \(by calling super\(\)\)\.
It caused confusion, and I think it is not necessary, or is it?
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[415] since it is now possible to to instantiate InstructionDetails using](https://discourse.openehr.org/t/415-since-it-is-now-possible-to-to-instantiate-instructiondetails-using/16067)
> Revision: 415
Author: bert\.verhees
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[414] added the constructor annotation (the attribute-annotations were already](https://discourse.openehr.org/t/414-added-the-constructor-annotation-the-attribute-annotations-were-already/16066)
> Revision: 414
Author: bert\.verhees
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Is there an OpenEHR technical commitee?](https://discourse.openehr.org/t/is-there-an-openehr-technical-commitee/14801)
> 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...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes including inherited content](https://discourse.openehr.org/t/archetypes-including-inherited-content/14800)
> Dear All,
Given we have a lot of archetypes which are then further versioned etc
moving archetypes from one version to another can become a real pain
based on their inherited content\.
i\.e\. if B\.v1 specializes A\.v1 then it includes the content of A\.v1
If we then create an A\.v2 & wish to create a B\.v2 which specialises A\.v2
\(or even we have a b\.v1draft which we we to change to
specializing/extending A\.v2\) a manual process must ensue so that the
content brought in from A\.v2...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Regex in Archetypes must include TYPE](https://discourse.openehr.org/t/regex-in-archetypes-must-include-type/14796)
> Dear All,
The regex locator used to get an archetype from another archetype is too
loose\. Given the Archetype ID is something like :
openEHR\-EHR\-CLUSTER\.address\.v1
instead of :
archetype\_id/value matches \{/address\\\.v1/\}
we should have \(at the very least\):
archetype\_id/value matches \{/CLUSTER\\\.address\\\.v1 /\}
or \(preferably\)
archetype\_id/value matches \{/openEHR\-EHR\-CLUSTER\\\.address\\\.v1 /\}
\(A\) address\\\.v1 matches no particular string exactly as the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [I cann't running form](https://discourse.openehr.org/t/i-cannt-running-form/16713)
> Hi all\.
What should I do, to run the form created in template designer ?
can someone help me?
kyung ja \( in Seoul, Korea\)
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [relationship between change type and lifecycle state](https://discourse.openehr.org/t/relationship-between-change-type-and-lifecycle-state/14797)
> I think there is some ambiguity around the 'change type' in a
version's audit, and the lifecycle state of the version\.
To recap, change type has the following terminology entries
creation
ammendment
modification
synthesis
deleted
attestation
unknown
And lifecycle state can be
complete
incomplete
deleted
Firstly, I think the 'synthesis' and 'unknown' change types aren't
well defined so until they are it might be better if they weren't in
the list of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetypes - distniguishing multiple alternative constraints of a single-valued attribute](https://discourse.openehr.org/t/archetypes-distniguishing-multiple-alternative-constraints-of-a-single-valued-attribute/14789)
> Here is a technical problem which is so far very rare, but probably requires a better solution than we have now. In the current release of the ADL specification, section 5.3.3 describes rules for constraints on a single-valued attribute:
5.3.3 Single-valued Attributes
Repeated blocks of object constraints of the same class (or its subtypes) can have two possible meanings in cADL, depending on whether the cardinality is present or not in the containing attribute block. With no cardinality,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [archetypes for genomic data](https://discourse.openehr.org/t/archetypes-for-genomic-data/14788)
> Hi Nicola,
It is great that someone from genomic society is involved with openEHR
:\) As an M\.D\. who has done \(thesis not submitted\) Ph\.D\. work in
Molecular Biology & Genetics and worked on Genomic Databases \(I am still
the curator of Turkish Human Mutation Database \- a former HUGO MDI
initiative and now HGVS\) my primary problem was to associate phenotypic
\(i\.e\. clinical\) data with genomic data\. It was 1997\-1998 and openEHR did
not exists\! However I found out that the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [687] Correct broken link.](https://discourse.openehr.org/t/ref-impl-eiffel-687-correct-broken-link/13709)
> Revision: 687
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [686] Change the way that AWB behaves with respect to .adl and .adls files:](https://discourse.openehr.org/t/ref-impl-eiffel-686-change-the-way-that-awb-behaves-with-respect-to-adl-and-adls-files/13009)
> Revision: 686
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Building Archetypes](https://discourse.openehr.org/t/building-archetypes/14785)
> Hi All,
I am currently attempting to build Instruction archetypes and I'm a bit
confused\.
From the NHS tree there are two:
openEHR\-EHR\-INSTRUCTION\.haemodialysis\_prescription\.v1draft
and
openEHR\-EHR\-INSTRUCTION\.disposition\.v2draft
That have ITEM\_TREEs that do not have openEHR datatypes in them\.
They contain a 0 \(zero\) where I expect to find a datatype
\(DV\_TEXT,DV\_COUNT,etc\.\)
The definition section of the first one is below:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [proposal for managing migration to .adls (source form) archetypes](https://discourse.openehr.org/t/proposal-for-managing-migration-to-adls-source-form-archetypes/14790)
> Dear all,
as some at least have noticed from previous posts, there is the
intention to move toward what we call 'source form' or 'differential'
archetypes, whereby archetypes contain only changes with respect to a
specialisation parent archetype\. This move has no effect on the majority
of archetypes \(since they are top\-level archetypes\) but specialised
archetypes are changed from being 'flat\-form' archetypes \(where
inherited, unchanged elements are repeated in...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [UK openEHR training 24/25 July CHIME, UCL (Archway, London)](https://discourse.openehr.org/t/uk-openehr-training-24-25-july-chime-ucl-archway-london/14783)
> Dear all,
there is an openEHR training course at CHIME, UCL, in London on 24/25
July\. This course will run for 2 days, and will be presented by myself,
Dr Ian McNicoll of NHS Scotland and Dr Dipak Kalra of CHIME\. See
http://www.chime.ucl.ac.uk/news/latest/news-20080616a.htm for details\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Template Designing](https://discourse.openehr.org/t/template-designing/12981)
> Hi all,
well, after spending some days on Archetypes and their relations to Templates, now, I want to start creating a sample Template using the Template Designer.
We discussed about the methodology before , and since I have a previously designed form -however not based on openEHR- in hand, I'll start mapping this form to a Template. So, I don't need Brain Storming or even organizing data, I guess I just should find appropriate Archetypes, and of course the main one for this template
my...
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [CDSS and openEHR](https://discourse.openehr.org/t/cdss-and-openehr/12982)
> Hi there,
up to now, I've just found a little infor regarding Clinical Decision Support systems and their relation to openEHR.
in Archetupes 101 by Hether and Sam there's one paragraph indicationg that we canhave Arcehtype-Triggered events also computer tracking of clinical workflow using instruction status.
Do you know if there's any other resources related to CDSS?
has any one done any effort in this area? I mean combining CDSS and openEHR ?
Paria
PhD Student
IDC | Interaction Design...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templated Designing](https://discourse.openehr.org/t/templated-designing/12945)
> Hi all,
well, after spending some days on Archetypes and their relations to Templates, now, I want to start creating a sample Template using the Template Designer.
We discussed about the methodology before , and since I have a previously designed form -however not based on openEHR- in hand, I'll start mapping this form to a Template. So, I don't need Brain Storming or even organizing data, I guess I just should find appropriate Archetypes, and of course the main one for this template
my...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[NEW][ARCHETYPE][BRAINSTORM] Fracture](https://discourse.openehr.org/t/new-archetype-brainstorm-fracture/14793)
> Hi there,
This is my first try at creating an archetype\. I have read the Building
Archetypes PDF Heather kindly posted a couple of days ago \(what great
timing\!\)\. Tried to read the Reference Model and all that but find it rather
techinical\.
So here I am dwelving into the unknown\.
Background: I'm currently involved in an orthopaedic study: Open Fracture of
the Long Bones with a local university where they enter a set of data into a
paper\-based performa\. Any patient that comes...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [685] Changes to enable specialised archetypes in flat form (i.e.](https://discourse.openehr.org/t/ref-impl-eiffel-685-changes-to-enable-specialised-archetypes-in-flat-form-i-e/13596)
> Revision: 685
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Python Reference Implementation News](https://discourse.openehr.org/t/python-reference-implementation-news/12924)
> The openEHR Python reference implementation is under active development\.
While Python developers will be able to extract only the openehr package
and use it in any Python application\. The Open Source Health
Information \(OSHIP\) project includes many additional modules like,
webservers, object database, security, auto\-widget creation and
documentation\.
The source code is available via anonymous SVN at
http://www.openehr.org/svn/ref_impl_python/TRUNK/
Installation instructions are...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reusable Archetypes](https://discourse.openehr.org/t/reusable-archetypes/14787)
> Hi there,
I feel the most important thing in developing suitable templates is to understand the openEHR reference model and its basic concepts very well and to be able to analyze the case and extract required information that may help finding proper archetype clues while designing. It may sounds simple at first glance but is a tedious task.
It seems to me that one should be aware of all existing Archetypes and their ingredients ( data section at least) to be able to recognizing Archetypes...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetyping Methodology](https://discourse.openehr.org/t/archetyping-methodology/14792)
> Thank you Heather for the Link and Congrats for the new born website!
As far as I remember form the tutorial session, you-Heather- started creating an archetype by a brain storming of what any clinician may ask about smoking or what She may examine during the caring process of a smoker patient,..., (I'm not sure about the kind of disease we discussed that day but surely you remember that example)
is it what you-or any other researchers in openEHR area- wanted to show us or I just understood...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetyping Methodology](https://discourse.openehr.org/t/archetyping-methodology/12908)
> > Thank to Heather for the Link and Congrats for the new born website!
> As far as I remember form the tutorial session, Heather- started creating an archetype by a brain storming of what any clinician may ask about smoking or what She may examine during the caring process of a smoker patient,..., (I'm not sure about the kind of disease we discussed that day but surely you remember that example)
>
> is it what she-or any other researchers in openEHR area- wanted to show us or I just...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Redux: Circular Imports (Tim Cook)](https://discourse.openehr.org/t/redux-circular-imports-tim-cook/12907)
> There's nothing wrong with a class defining a reference to another \(or
the same\) instance of that class \- that's how most hierarchical OO
implementations would work\.
I don't know Python \- but other languages certainly won't worry about
this \- it's not a circular reference in as much as the reference is \(at
run time\) to an instance of a class of the same type which may be the
same object, but generally would not be\.
In the case of the thumbnail attribute it does...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Email Clients (was Redux: Circular Imports)](https://discourse.openehr.org/t/email-clients-was-redux-circular-imports/12890)
> >
> Message: 5
> Date: Fri, 04 Jul 2008 10:18:48 \+1000
> From: Hugh Leslie <hugh\.leslie@oceaninformatics\.com>
> Subject: Re: Redux: Circular Imports
> To: Peter Gummer <peter\.gummer@oceaninformatics\.com>, For openEHR
> technical discussions <openehr\-technical@openehr\.org>
> Message\-ID: <486D6C68\.6000801@oceaninformatics\.com>
> Content\-Type: text/plain; charset="us\-ascii"
>
> An HTML attachment was...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Redux: Circular Imports](https://discourse.openehr.org/t/redux-circular-imports/14786)
> Hi All,
This is different than the issues brought up by Rong in the Java
implementation\.
I brought this up before when reading the specs\. But now as my code has
matured my fears are confirmed\.
Using Python:
In an interface I define attributes of a class\. In addition to some
meta\-data I define the 'type' of that attribute\.
Code is here;
http://www.openehr.org/wsvn/ref_impl_python/TRUNK/oship/src/oship/openehr/am/archetype/?rev=0&sc=0
For example in IArchetype \(the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [How to start an application with openEHR](https://discourse.openehr.org/t/how-to-start-an-application-with-openehr/14784)
> Hi,
i'm Juan from Colombia and i want to start to develop a web application
using openEHR in the core arch of the app\.
i'm new on openEHR and i've downloaded the java implementation of the model
, but i've not founded an example or a kind of a tutorial to learn how to
start my app\.
The goal of my app is insert, search and retrieve medical data\.
Regards,
Juan
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Implementation fine details - case sensitivity and date time formats](https://discourse.openehr.org/t/implementation-fine-details-case-sensitivity-and-date-time-formats/14782)
> Hi implementers,
We have come across a few issues recently which will affect interoperability between openEHR implementations if we don’t have some tighter guidelines for implementation. I will start with a couple that relate to case sensitivity of code strings and identifier values. I am interested in people’s views about handling case sensitivity in the following cases.
The first is with regard to territory and encoding code phrase strings. Rong recently found when using the Ocean EhrBank...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Cardinality for a SECTION.](https://discourse.openehr.org/t/cardinality-for-a-section/16678)
> What does the cardinality \(the defenition tab\) in a SECTION stand for?
Is is how many times the SECTION can occur in one COMPOSITION?
In the tree\-structure each subsection or slot is constrained with occurences\. But is there an overall cardinality for the whole SECTION?
Richard Andersson
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Creating Archetypes based on questionaire](https://discourse.openehr.org/t/creating-archetypes-based-on-questionaire/14791)
> Hi there,
In our project, clinicians-who work in the area of oral medicine- use an online form editor that help them create forms based on their experiences any time needed.
It means that each clinician can create his/her own questionnaires. (experiences in this project showed that they are eager to have their own protocol including questionnaires and data they may access )there are some forms, or templates that are more general including questions like this one named GENERAL MEDICAL...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Slot constraints.](https://discourse.openehr.org/t/slot-constraints/14771)
> What does it mean when a slot is constrained via the Include/Exclude?
E\.g\. if I make an observation with a cluster\-slot, add a cluster to the Include and do nothing in the Exclude\. Is it constrained that only the cluster added to Include is possible to use in the slot?
I am convinced that I have read this once, but I can´t find it right now\.
Regards
Richard Andersson
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [* (en) problem of archetype editor](https://discourse.openehr.org/t/en-problem-of-archetype-editor/12846)
> Hi all.
Actually it may not be proper for this mailing list but [http://dev.oceanehr.com/mantis/main_page.php](http://dev.oceanehr.com/mantis/main_page.php) is not work now.
So I am posting this mailing list.
Problem is....
After I "Add Language" in "Language" Menu (korean in my case) in Archetype Editor, all sentences in "test & description in term_definitions" and "keywords in Header" are expressed as "* any english (en)".
For example,
at0000 *Apgar score(en) *Clinical score derived...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[413] Correcting a minor bug while parsing ISO 8601 DURATION values](https://discourse.openehr.org/t/413-correcting-a-minor-bug-while-parsing-iso-8601-duration-values/12831)
> Revision: 413
Author: humberto\.naves
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers unsubscribe notification](https://discourse.openehr.org/t/openehr-implementers-unsubscribe-notification/12661)
> viguera79@hotmail\.com has been removed from openEHR\-implementers\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Associated symptoms...](https://discourse.openehr.org/t/associated-symptoms/14778)
> Hi all,
In the archetype openEHR\-EHR\-CLUSTER\.symptom\.v3\.adl there is a CLUSTER archetype node with id at0020 with label "Associated symptoms and events"\.
Can a symptom A have an associated symptom B with onset date before the onset date of the symptom A or with a duration exceeding the duration of symptom A?
Example:
A patient was diagnosed influenza and suffers from time point 1 to time point 3 from chills, from time point 2 to time point 5 from fever and from time point 4...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Thoughts about Observation](https://discourse.openehr.org/t/thoughts-about-observation/12822)
> Via the enxt url you can down load a series of thoughts on two presentations about:
Observations, Qualitative, semi quantitative and quantitative measurements.
[http://tinyurl.com/5gczoh](http://tinyurl.com/5gczoh)
Comments are welcome.
Gerard
-- --
Gerard Freriks, MD
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands
T: +31 252544896
M: +31 620347088
E: [gfrer@luna.nl](mailto:gfrer@luna.nl)
Those who would give up essential Liberty, to purchase a little temporary
Safety,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Person State with History.](https://discourse.openehr.org/t/person-state-with-history/14769)
> Dear Richard,
For the best answers concerning the Clinical Modeling I refer you to the openEHR list for clinical discussions.
Most persons actively involved in clinical modeling can be found here.
[http://www.openehr.org/community/mailinglists.html](http://www.openehr.org/community/mailinglists.html)
Gerard Freriks
> Dear Gerard,
>
> Do you know of any existing OBSERVATION that uses the Person State with History?
>
> I haven´t found any, and I try to understand the difference between...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [release tag for 1.0.1](https://discourse.openehr.org/t/release-tag-for-1-0-1/12810)
> Dear all,
I intend to create a release tag for release-1.0.1, which is really a read-only copy of the current Trunk. Compared with the Branch release-1.0.1-RC (release candidate), the current Trunk has been improved considerably. I think the time is right to declare Release-1.0.1 and move on to other tasks, e.g. this would allow us to start to implement the CRs aimed for Release-1.0.2 on the Trunk.
Any reaction to this?
Cheers,
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 23, Issue 52](https://discourse.openehr.org/t/openehr-technical-digest-vol-23-issue-52/12805)
> GUI means implementation\. Software is written for different OS, programming
languages, etc\. Do you expect the specification to go as far as those
implementation issues?
Ogi Pishev
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [RESOURCE_DESCRIPTION_ITEM](https://discourse.openehr.org/t/resource-description-item/16675)
> Shouldn't:RESOURCE\_DESCRIPTION\_ITEM
original\_resource\_uri:
Hash<String, String>
really be:RESOURCE\_DESCRIPTION\_ITEM
original\_resource\_uri:
Hash<String, DV\_URI>
????
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GUI-hints in openEHR templates?](https://discourse.openehr.org/t/gui-hints-in-openehr-templates/16677)
> Similar to others we customize the GUI in the form builder tool where
complex logic \(hiding controls, looking up values, validation,
business logic etc\) can be added\. It would be a large \(but noble\)
effort to implement that in templates or even separate presentation
templates \(my preference\) for automation\.
However my question is if we want true interoperability are we
expecting a completed form created in PatientOS to be edited in an
external openEHR system?
If we are, I can see...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [[Archway Network Upgrade - Wednesday 2nd July]](https://discourse.openehr.org/t/archway-network-upgrade-wednesday-2nd-july/13408)
> Hi,
The site which hosts the openEHR web server is undergoing a network
upgrade on Wednesday 2nd July 2008\. There will be a definite outage
between 08:00 and 09:00 BST, and the network will be 'at risk' for the
rest of the day\.
This will affect the openEHR web server, wiki, issues syste, svn, etc\.
We apologise for any inconvenience this may cause\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Thoughts about Observations-severity-part 1](https://discourse.openehr.org/t/thoughts-about-observations-severity-part-1/13394)
> Dear all,
I'm sharing some thoughts for discussion.
[http://tinyurl.com/6xb8u5](http://tinyurl.com/6xb8u5)
Gerard Freriks
-- --
Gerard Freriks, MD
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands
T: +31 252544896
M: +31 620347088
E: [gfrer@luna.nl](mailto:gfrer@luna.nl)
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))](https://discourse.openehr.org/t/gui-hints-in-openehr-templates-was-patientos-archetype-to-form-demo-of-sorts/14776)
> Hi\!
> Thanks to the java reference implementation I have a demo of importing
> archetypes to auto generate forms which have the references to the
> archetype\.
Nice\. Keep up the good work\.
> One thing I noticed in the conversion that I don't have any way of
> distinguishing between a line of text and multiline text in the
> archetype \(I would generate an appropriate pane in the latter case\)\.
> Perhaps not a big deal\.
This might be a useful requirement for the current...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [PatientOS archetype to form demo (of sorts)](https://discourse.openehr.org/t/patientos-archetype-to-form-demo-of-sorts/14770)
> Thanks to the java reference implementation I have a demo of importing
archetypes to auto generate forms which have the references to the
archetype\. Here is the video example of doing blood pressure:
http://www.patientos.org/software/video_files/openehr/patientos_openehr.htm
If you are curious as to how the other forms came out you can view the
demo \(one at a time\) here:
http://www.patientos.org/demo.htm
username/password demo/demo \- double click a patient, forms tab and
press new...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Bloodpressure Cuff size](https://discourse.openehr.org/t/bloodpressure-cuff-size/14775)
> Dear all,
Something to think about.
At least Josina made me.
Cuff sizes.
Do we really need a list with codes stating small, normal and large?
When we know that small for children is different from small for adults, etc, etc.
Isn't it tru that we only need to record whether we measured the blood pressure with the appropriate or non-appropriate cuffsize.
In other words is it in many occasions not enough to have one flag: 'trust this' or 'do not trust this'?
Gerard
-- --
Gerard...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [openEHR Extract](https://discourse.openehr.org/t/openehr-extract/14774)
> Hello,
I was wondering if there is support within the java implementation for
the openEHR exract? I haven't found that spec yet but I was hoping
that I could take an Archetype and \(populate?\) it and then leverage it
to convert it to an extract \(despite one being a reference based and
the other being patient data based\)\.
I see a class org\.openehr\.rm\.ehrextract\.EHRExtract but I am concerned
whether the entire system needs to be \(directly\) EHR compliant \-
versus being able to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Step by step Achetype editing](https://discourse.openehr.org/t/step-by-step-achetype-editing/14779)
> Hi all,
I've just started browsing and investigating two existing archetype
editors,
hardly could I find a step by step tutorial for creating Archetypes
\(and then Templates\)
Is there any recommended resource?
Regards
paria
PhD Student
IDC | Interaction Design Collegium
Department of Computing Science and Engineering
Chalmers University of Technology
Email: hajar\.kashfi@chalmers\.se
Office:\+46 \(0\)31 7725407
Mobile Phone: \+46 \(0\)707222815
Postal adress:
IT University of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question on the role of EHR reference models for achieving functional interoperability](https://discourse.openehr.org/t/question-on-the-role-of-ehr-reference-models-for-achieving-functional-interoperability/14773)
> Dear all,
I would like to ask you for your opinion on a statement in ISO/DTR 20514 (Definition, scope and context of the EHR), which says that "[...] a standardised EHR reference model is required for achieving functional interoperability [...]" (page 7 of ISO 20514).
Functional interoperability is defined as "the ability of two or more systems to exchange information (so that it is human readable by the receiver)".
I am now wondering why an EHR reference model is seen to be REQUIRED for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Not entirely related to this mail list...](https://discourse.openehr.org/t/not-entirely-related-to-this-mail-list/14777)
> Apologies for taking the liberty of sharing this with you, but IMHO it is worth seeing. Tim Benson has noticed it first.
[http://ca.youtube.com/watch?v=IfprGOiQklU&feature=related](http://ca.youtube.com/watch?v=IfprGOiQklU&feature=related)
Regards
Seref
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Possible error in UML: ITEM does not inherit from LOCATABLE...](https://discourse.openehr.org/t/possible-error-in-uml-item-does-not-inherit-from-locatable/12691)
> Hi,
In the actual UML diagram the ITEM class does not inherit from the LOCATABLE class, whereas in the document 'Data Structures Information Model' on p23 it does\.
Is there any reason for that or is it an error?
Cheers
Bruno
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Toughts about archetypes and patient system](https://discourse.openehr.org/t/toughts-about-archetypes-and-patient-system/14772)
> Dear all,
A few thoughts I wrote down last days but now they are translated into a pictures.
It helps me understand when to use what Archetype.
The ZIP-file with PDF's can be downloaded via: [http://tinyurl.com/63dfg7](http://tinyurl.com/63dfg7)
1- EHR's are about the Patient system and document the medical treatment process from the healthcare providers perspective.
2- The Patient System consists of:
a- Inner system (chemistry, physiology, genomics, etc)
b- Patient as a body
c- Direct...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [684] The Eiffel builder now uses environment variables similarly to EiffelStudio itself.](https://discourse.openehr.org/t/ref-impl-eiffel-684-the-eiffel-builder-now-uses-environment-variables-similarly-to-eiffelstudio-itself/16021)
> Revision: 684
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The archetypical (ideal) health business process model and documentation patterns](https://discourse.openehr.org/t/the-archetypical-ideal-health-business-process-model-and-documentation-patterns/13265)
> Dear all,
Below the shortest way I can think of, to make clear when to use what Type of Archetype, also called by me a Documenting Pattern.
**The archetypical (ideal) health business process model and documentation patterns**
**Based on observations leading to evaluations the healthcare provider tries to improve the state in the patient system via assumptions (personal opinions) about processes in the patient system.**
He operationalizes this via **Instructions** that are intended to lead...
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [Stories From the Trenches](https://discourse.openehr.org/t/stories-from-the-trenches/12676)
> Hi All,
Well, after our great discussion on decision support and a call for a
mailinglist and 40\+ subscribers\. We stopped talking\. :\-\)
So, never letting a list be quiet for too long, I thought I'd propose
this restart\.
Does anyone have success or failure stories that we can all learn from
they would like to share concerning decision support in healthcare IT
apps?
What technologies/approaches were used?
Embedded reminders
Standalone response systems
???
If/then...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [DV_INTERVAL Docs](https://discourse.openehr.org/t/dv-interval-docs/14758)
> In the Data Types Information Model Quantity Package Rev 2\.1\.0
there are no attributes in the DV\_INTERVAL class
Don't we need at least an upper, lower ?
Also there is no discussion on normalization\. maybe because there are no
attributes\. :\-\) But how are others implementing this? Is it valid to
normalize say \(5,2\) to \(2,5\); or do you just throw an exception?
Thanks,
Tim
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Thread on the clinical list](https://discourse.openehr.org/t/thread-on-the-clinical-list/13218)
> I know we all only have so much time to read emails especially as busy
as this community is getting lately\. But \.\.\.
I'm not sure what the membership crossover is between lists but
Implementers that may not be on the openehr\-clinical list
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
are likely interested in a thread with the subject line "use cases" and
especially the wiki page Tom has started...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [683] Fix the handling of nested clusters in the SCons Eiffel builder.](https://discourse.openehr.org/t/ref-impl-eiffel-683-fix-the-handling-of-nested-clusters-in-the-scons-eiffel-builder/13193)
> Revision: 683
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [use cases](https://discourse.openehr.org/t/use-cases/14761)
> Dear all,
Could you help me with some clinical use cases to demonstrate the
differences between an 'EHR' based on standardized messages and an
EHR based on a standardized information architecture/ reference model\.
As you might be aware here in the Netherlands our government has
chosen, for now, to use standardized messages in combination with a
central 'switch point'\. Basically this provides a communication
infrastructure which deals with identification and authorization...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Patient reported history](https://discourse.openehr.org/t/patient-reported-history/14764)
> Dear Everyone,
I have a question regarding patient reported history and how the time\(s\)
of that would be represented in the reference model\.
1971\-1992 patient married to X
2008\-06\-17 patient asked about social history, reports that he/she was
married to X 1971\-1992\.
What would be the HISTORY\.origin and EVENT\.time \(or
INTERVAL\_EVENT\.width?\) of this? Or would the timings of this be
archetyped? Is this an observation of the patients memory taking place
now or an observation of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [682] Fix a minor error in the SCons Eiffel builder.](https://discourse.openehr.org/t/ref-impl-eiffel-682-fix-a-minor-error-in-the-scons-eiffel-builder/13138)
> Revision: 682
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Handling Archetype Versions](https://discourse.openehr.org/t/handling-archetype-versions/14760)
> Hi All,
I do not recall who said it or even which openEHR mailing list it
appeared on but I would like to get feedback from implementers\.
I recently read a comment that seemed to me to be counter to a core
philosophy of openEHR\. The comment was regarding how to handle
different versions of an archetype and it basically posited that there
should be some automated intervention that would migrate data from one
archetype version to another\.
In my mind, this is a TOTALLY wrong approach\. ...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Request: openEHR temporal data instance needed ...](https://discourse.openehr.org/t/request-openehr-temporal-data-instance-needed/14766)
> hi list,
for my research on temporal data management of hierarchical medical data i am looking for a openEHR data instance that can be used as running example to work with\.
the data instance should have following properties:
\* contain time intervals, e\.g\. a history of patient's symptoms, history of medications etc\.
\* the time intervals should possibly overlap\.
\* aggregates like count, min, max, avg over the data \(e\.g\. number of medications taken, avg of a observed value,...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [adl to java object](https://discourse.openehr.org/t/adl-to-java-object/12627)
> Hi dev guys,
I just hope this is the right place to ask this\.
Today, I just successfully got the java openehr jars\.\.\.
I am now looking looking forward to being able to parse adl into a java object\.
Please I need some documentation or sense of direction in trying to do this cos I need to work with the object\.
Pls help
Thanks a lot
ime
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [A question and problem a report](https://discourse.openehr.org/t/a-question-and-problem-a-report/11997)
> Dear list members,
I followed the process described in Quickstart ([http://www.openehr.org/wiki/display/projects/Quick+start+guide+for+the+openEHR+Java+project](http://www.openehr.org/wiki/display/projects/Quick+start+guide+for+the+openEHR+Java+project) )
and run into some trouble. The ADL-Parser would not compile when running the 'mvn clean install'. Maven reported that...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [681] The CruiseControl server is still complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)".](https://discourse.openehr.org/t/ref-impl-eiffel-681-the-cruisecontrol-server-is-still-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128/12614)
> Revision: 681
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [680] Last revision's reversion somehow fixed the build on the CruiseControl server.](https://discourse.openehr.org/t/ref-impl-eiffel-680-last-revisions-reversion-somehow-fixed-the-build-on-the-cruisecontrol-server/13070)
> Revision: 680
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [679] The CruiseControl server is still complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)", so I'm reverting the change where it started failing.](https://discourse.openehr.org/t/ref-impl-eiffel-679-the-cruisecontrol-server-is-still-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128-so-im-reverting-the-change-where-it-started-failing/12585)
> Revision: 679
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [678] Still trying to fix the build on the CruiseControl server.](https://discourse.openehr.org/t/ref-impl-eiffel-678-still-trying-to-fix-the-build-on-the-cruisecontrol-server/12584)
> Revision: 678
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [677] The CruiseControl server is still complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)", and last revision's print statements show it's happening at the point where it should be building the](https://discourse.openehr.org/t/ref-impl-eiffel-677-the-cruisecontrol-server-is-still-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128-and-last-revisions-print-statements-show-its-happening-at-the-point-where-it-should-be-building-the/15973)
> Revision: 677
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [676] The CruiseControl server is still complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)", and last revision's print statements show it's happening after compiling adl_workbench, so I'm trying](https://discourse.openehr.org/t/ref-impl-eiffel-676-the-cruisecontrol-server-is-still-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128-and-last-revisions-print-statements-show-its-happening-after-compiling-adl-workbench-so-im-trying/12581)
> Revision: 676
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [675] The CruiseControl server is still complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)", so I'm reverting last revision's use of the Python unicode() function.](https://discourse.openehr.org/t/ref-impl-eiffel-675-the-cruisecontrol-server-is-still-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128-so-im-reverting-last-revisions-use-of-the-python-unicode-function/12580)
> Revision: 675
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [674] The CruiseControl server is now complaining, "'ascii' codec can't decode byte 0x92 in position 139: ordinal not in range(128)".](https://discourse.openehr.org/t/ref-impl-eiffel-674-the-cruisecontrol-server-is-now-complaining-ascii-codec-cant-decode-byte-0x92-in-position-139-ordinal-not-in-range-128/12577)
> Revision: 674
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [673] I've learned how to view the CruiseControl server's error messages, and it turns out that the version of SCons installed there doesn't support Variables(), so I'll revert it again.](https://discourse.openehr.org/t/ref-impl-eiffel-673-ive-learned-how-to-view-the-cruisecontrol-servers-error-messages-and-it-turns-out-that-the-version-of-scons-installed-there-doesnt-support-variables-so-ill-revert-it-again/13042)
> Revision: 673
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes - regex question](https://discourse.openehr.org/t/archetypes-regex-question/14763)
> Dear All,
Could you explain a little piece of expected beahviour to me wrt
including/allowing one archetype to include others
A\) If the include is a list of regex's matching archetype names etc e\.g\.
/checklist\_item\-general\-cvs1\\\.v1|checklist\_item\-general\-cvs2\\\.v1|checklist\_
item\-general\-cvs3\\\.v2|checklist\_item\-general\-cvs4\\\.v2draft|checklist\_item\-ge
neral\\\.v1|checklist\_item\-general\\\.v2|checklist\_item\-general\\\.v3/
& the exclude...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [672] Revert the last revision, because it didn't fix the build on the CruiseControl server.](https://discourse.openehr.org/t/ref-impl-eiffel-672-revert-the-last-revision-because-it-didnt-fix-the-build-on-the-cruisecontrol-server/12983)
> Revision: 672
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [671] The last revision broke the build on the CruiseControl server.](https://discourse.openehr.org/t/ref-impl-eiffel-671-the-last-revision-broke-the-build-on-the-cruisecontrol-server/12952)
> Revision: 671
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [670] The target passed to the SCons Eiffel builder used to be the base name of the main executable or .dll that was to be built, but this "target" was confusingly different from the ECF project "target".](https://discourse.openehr.org/t/ref-impl-eiffel-670-the-target-passed-to-the-scons-eiffel-builder-used-to-be-the-base-name-of-the-main-executable-or-dll-that-was-to-be-built-but-this-target-was-confusingly-different-from-the-ecf-project-target/12480)
> Revision: 670
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [669] AWB-128: Copy changes from EiffelStudio 6.2's GTK implementation of EV_TREE_IMP to our override of it.](https://discourse.openehr.org/t/ref-impl-eiffel-669-awb-128-copy-changes-from-eiffelstudio-6-2s-gtk-implementation-of-ev-tree-imp-to-our-override-of-it/12896)
> Revision: 669
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [668] EDT-291: Fix a precondition violation in C_CODE_PHRASE.make_from_pattern, caused by revision 659.](https://discourse.openehr.org/t/ref-impl-eiffel-668-edt-291-fix-a-precondition-violation-in-c-code-phrase-make-from-pattern-caused-by-revision-659/12884)
> Revision: 668
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [667] Merged fixes from the TRUNK into TAGS/Aug2007 in order to do a release of the ADL Parser for Archetype Editor:](https://discourse.openehr.org/t/ref-impl-eiffel-667-merged-fixes-from-the-trunk-into-tags-aug2007-in-order-to-do-a-release-of-the-adl-parser-for-archetype-editor/12424)
> Revision: 667
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [666] EDT-284: Fix exceptions in ARCHETYPE_ONTOLOGY that occurred while testing the parser with Archetype Editor and when opening adl-test-ENTRY.ontology_term_binding_empty.v1.adl in ADL Workbench.](https://discourse.openehr.org/t/ref-impl-eiffel-666-edt-284-fix-exceptions-in-archetype-ontology-that-occurred-while-testing-the-parser-with-archetype-editor-and-when-opening-adl-test-entry-ontology-term-binding-empty-v1-adl-in-adl-workbench/12847)
> Revision: 666
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parsing archetype xml with JAXB](https://discourse.openehr.org/t/parsing-archetype-xml-with-jaxb/14762)
> Hi,
I used JAXB to generate java files from the XSD files but I am not
getting very far with the unmarshalling, currently I get:
javax\.xml\.bind\.UnmarshalException: Unable to create an instance of
test123\.COBJECT: Unable to create an instance of test123\.COBJECT
when executing the following code:
JAXBContext jc = JAXBContext\.newInstance\(ARCHETYPE\.class\);
Unmarshaller unmarshaller = jc\.createUnmarshaller\(\);
JAXBElement<ARCHETYPE> root =...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [665] AWB-128: In TAGS/Aug2007 (from which the publicly released builds of the ADL Parser are currently being made), copy changes from EiffelStudio 6.2's .NET implementation of INTERNAL to our override of it.](https://discourse.openehr.org/t/ref-impl-eiffel-665-awb-128-in-tags-aug2007-from-which-the-publicly-released-builds-of-the-adl-parser-are-currently-being-made-copy-changes-from-eiffelstudio-6-2s-net-implementation-of-internal-to-our-override-of-it/12356)
> Revision: 665
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [664] The TRUNK EiffelBuild project file was pointing to BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-664-the-trunk-eiffelbuild-project-file-was-pointing-to-branches-specialisation/15938)
> Revision: 664
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [663] Catch-up - merge revisions 643-662 from TRUNK into specialisation branch.](https://discourse.openehr.org/t/ref-impl-eiffel-663-catch-up-merge-revisions-643-662-from-trunk-into-specialisation-branch/12330)
> Revision: 663
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR templates specification draft proposals available](https://discourse.openehr.org/t/openehr-templates-specification-draft-proposals-available/15936)
> An important part of the specfications work this year is the upgraded
archetype specification and the new template specification\. These
specifications define specialised archeytpes and also openEHR templates\.
The latter will now have the equivalent of the Archetype Definition
Language \(ADL\) and the Archetype Object Model \(AOM\) \- known as the
Template Definition Language \(TDL\) and the Template Object Model \(TOM\)\.
There will also be an Operational Template Model \(OTM\)\. The...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Terminology releases](https://discourse.openehr.org/t/terminology-releases/16712)
> Dear All
The Terminology ID in openEHR has a name = SNOMED-CT, ICD-10AM, LOINC2.5 etc
and a version_id (actually a release) = 2008.3, 1.2, 2007
The NHS want to be able to store the release - something that could be difficult as there will be different releases locally, nationally and internationally of SNOMED. Which release do we mean and how is it identified?
I think we need to use the international release in archetypes.
Why store the release?
Well it is more useful than the time to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype official versions](https://discourse.openehr.org/t/archetype-official-versions/12312)
> In subversion there are a number of versions of archetypes - are any officially released or are all considered under development?
dev\adl\openehr\ehr\entry\observation\openEHR-EHR-OBSERVATION.blood_pressure.v1.adl
dev-uk-nhs\adl\openehr\ehr\entry\observation\openEHR-EHR-OBSERVATION.blood_pressure.v3.adl
dev-uk-nhs\adl\openehr\ehr\entry\observation\openEHR-EHR-OBSERVATION.blood_pressure.v2.adl
dev-uk-nhs\adl\openehr\ehr\entry\observation\openEHR-EHR-OBSERVATION.blood_pressure.v1.adl
The NHS...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[Dcm] terminfo meeting room requirements/Planning for Phoenix](https://discourse.openehr.org/t/dcm-terminfo-meeting-room-requirements-planning-for-phoenix/14983)
> Dear all,
The way I see it DCM could be very useful is when it truly separates clinical domain knowledge from technical issues such as the modelling to a certain reference model and/or standard. Which doesn’t mean that these technical aspects shouldn’t be addressed as well. Only it should be a separate discussion.
From the health care professional (HCP) perspective it’s important to have an, as broad as possible (and independent of technique), agreement on:
- what is the relevant...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [662] Fix a bug in ARCHETYPE_ONTOLOGY where the addition of a term binding caused it to be put under a group whose identifier included the terminology version rather than just using the terminology name.](https://discourse.openehr.org/t/ref-impl-eiffel-662-fix-a-bug-in-archetype-ontology-where-the-addition-of-a-term-binding-caused-it-to-be-put-under-a-group-whose-identifier-included-the-terminology-version-rather-than-just-using-the-terminology-name/12292)
> Revision: 662
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Mutable openEHR Java (Was: Java XML-Archetype Parser?)](https://discourse.openehr.org/t/mutable-openehr-java-was-java-xml-archetype-parser/12281)
> Hi\!
Any status updates on the open source ADL/XML reader/writer \(Tom\) and
the mutable Java\-based AM/RM \(Humberto\)?
Best regards,
Erik Sundvall
erisu@imt\.liu\.se http://www.imt.liu.se/~erisu/ Tel: \+46\-13\-227579
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [2 Ref_impl_eiffel moderator request(s) waiting](https://discourse.openehr.org/t/2-ref-impl-eiffel-moderator-request-s-waiting/12647)
> The Ref\_impl\_eiffel@openehr\.org mailing list has 2 request\(s\) waiting
for your consideration at:
http://lists.chime.ucl.ac.uk/mailman/admindb/ref_impl_eiffel
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending subscriptions:
skoba@moss\.gr\.jp \(Shinji KOBAYASHI\) Tue Jun 3 12:42:38 2008
erisu@imt\.liu\.se \(Erik Sundvall\) Tue Jun 3...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Querying specifications](https://discourse.openehr.org/t/openehr-querying-specifications/14765)
> As part of the ongoing specification work this year, we have started to
build some resource pages for the various specifications\. One of them
concerns a querying solution for openEHR \- see the wiki page at:
http://www.openehr.org/wiki/display/spec/openEHR+Query+Specifications
I have uploaded the Ocean Informatics developed 'Archetype Query
Language' \(AQL\) as a candidate solution for querying archetype\-based
data\. As explained in the query specification home page, AQL can...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Python project and mailing list](https://discourse.openehr.org/t/python-project-and-mailing-list/15917)
> Dear all,
there now a mailing list for the new openEHR Python project, led by Tim
Cook\. See http://www.openehr.org/community/mailinglists.html for links\.
\- thomas beale
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [test message](https://discourse.openehr.org/t/test-message/12622)
> test
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [new openEHR Decision support list](https://discourse.openehr.org/t/new-openehr-decision-support-list/12611)
> A new openEHR decision support list has been created for discussions
about decision support in openEHR environments, support in the openEHR
EHR for decision support and so on\. Please see
http://www.openehr.org/community/mailinglists.html for links to
subscribe to and access this list\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[412] removed wrong comments at current date(time) constructor](https://discourse.openehr.org/t/412-removed-wrong-comments-at-current-date-time-constructor/12596)
> Revision: 412
Author: bert\.verhees
Log Message:
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [Welcome to the "openEHR-decisionsupport" mailing list](https://discourse.openehr.org/t/welcome-to-the-openehr-decisionsupport-mailing-list/12571)
> Welcome to the openEHR\-decisionsupport@openehr\.org mailing list\!
To post to this list, send your email to:
openehr\-decisionsupport@openehr\.org
General information about the mailing list is at:
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-decisionsupport
If you ever want to unsubscribe or change your options \(eg, switch to
or from digest mode, change your password, etc\.\), visit your
subscription page...
**[Decision Support (archive)](https://discourse.openehr.org/c/decision-support-archive/159)** - [confirm 6c4a566b0e9e662da3fe18c18cec750954f835ee](https://discourse.openehr.org/t/confirm-6c4a566b0e9e662da3fe18c18cec750954f835ee/12540)
> Mailing list subscription confirmation notice for mailing list
openEHR\-decisionsupport
We have received a request from
62\-31\-246\-89\.cable\.ubr07\.dals\.blueyonder\.co\.uk for subscription of
your email address, "thomas\.beale@oceaninformatics\.com", to the
openehr\-decisionsupport@openehr\.org mailing list\. To confirm that you
want to be added to this mailing list, simply reply to this message,
keeping the Subject: header intact\. Or visit this web...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Crystal Ball Gazing at its best!](https://discourse.openehr.org/t/crystal-ball-gazing-at-its-best/12513)
> Okay, thinking into the future\.\.\.\.far into the future\.
We know that the openEHR RM is good\.\.\.it is very good\. But we also know
that it will need changes\.
This thought I have has nothing to do with the quality of the model
\(hence this is here and not on the technical list\) but on the perception
of the model\.
More and more we are seeing definitions for acronyms like PHR, EMR and
EHR from organizations, NGOs and government health agencies\. It is the
kinds of things that they...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [661] The SCons Eiffel builder's scanner was not detecting .e files in clusters that were specified via an environment variable.](https://discourse.openehr.org/t/ref-impl-eiffel-661-the-scons-eiffel-builders-scanner-was-not-detecting-e-files-in-clusters-that-were-specified-via-an-environment-variable/12161)
> Revision: 661
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANN:openEHR Python Implementation](https://discourse.openehr.org/t/ann-openehr-python-implementation/14759)
> Congratulations Tim - you are really getting your hands dirty now! Welcome to level 3 (or is it 4?)
Sam
Tim Cook wrote:
[details="(attachments)"]
[/details]
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR solution for DSS in epidemiology](https://discourse.openehr.org/t/openehr-solution-for-dss-in-epidemiology/14756)
> Dear members of openEHR Clinical List,
I am much honored in joining this mailing list.
My name is Luciana Tricai Cavalini, and at this moment I occupying the position as the Director of the of at in .
My research field is social epidemiology, that is located on a triple boundary among health sciences, social sciences and biostatistics, and the critical concept for this knowledge area is *information*.
Thus, our research group has been developing some critical approach abour how...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [660] EDT-291: The parser now detects if an ordinal duplicates the same code term.](https://discourse.openehr.org/t/ref-impl-eiffel-660-edt-291-the-parser-now-detects-if-an-ordinal-duplicates-the-same-code-term/12157)
> Revision: 660
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [659] Add validation for C_CODE_PHRASE and C_DV_ORDINAL.](https://discourse.openehr.org/t/ref-impl-eiffel-659-add-validation-for-c-code-phrase-and-c-dv-ordinal/15878)
> Revision: 659
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[410] fixed attribute value (for TerminologyService) to terminologyService in constructor (thought, this was save to do)](https://discourse.openehr.org/t/410-fixed-attribute-value-for-terminologyservice-to-terminologyservice-in-constructor-thought-this-was-save-to-do/12156)
> Revision: 410
Author: bert\.verhees
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [658] The SCons Eiffel builder now has a construction variable EC, which defaults to 'ec' but can be set to use, say, the 'ecb' Eiffel compiler which is new to EiffelStudio 6.2.](https://discourse.openehr.org/t/ref-impl-eiffel-658-the-scons-eiffel-builder-now-has-a-construction-variable-ec-which-defaults-to-ec-but-can-be-set-to-use-say-the-ecb-eiffel-compiler-which-is-new-to-eiffelstudio-6-2/15877)
> Revision: 658
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [657] The SCons Eiffel builder now uses the Eiffel compiler's -clean flag, rather than removing the EIFGENs project tree itself.](https://discourse.openehr.org/t/ref-impl-eiffel-657-the-scons-eiffel-builder-now-uses-the-eiffel-compilers-clean-flag-rather-than-removing-the-eifgens-project-tree-itself/15876)
> Revision: 657
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [maintaining openEHR's online UML diagrams](https://discourse.openehr.org/t/maintaining-openehrs-online-uml-diagrams/14757)
> Dear all,
most of you would be familiar with the online UML diagrams of the
reference model \- at
http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/architecture/computable/UML/uml_start_view.html
David Lloyd started building these some 2 years or more ago using the
MagicDraw tool, which appeared to be one of the better tools on the
market\. The current version of the model is in MagicDraw 9\.5 and can be
found...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [656] The NSI installer script was trying to get adl_workbench.exe from the wrong place if the Eiffel compiler's -project_path flag was set.](https://discourse.openehr.org/t/ref-impl-eiffel-656-the-nsi-installer-script-was-trying-to-get-adl-workbench-exe-from-the-wrong-place-if-the-eiffel-compilers-project-path-flag-was-set/15875)
> Revision: 656
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[409] Updated constructor of all Locatable subclasses](https://discourse.openehr.org/t/409-updated-constructor-of-all-locatable-subclasses/12154)
> Revision: 409
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[408] updated the type of constructor parameter parent of all Locatable subclasses according to the specs](https://discourse.openehr.org/t/408-updated-the-type-of-constructor-parameter-parent-of-all-locatable-subclasses-according-to-the-specs/12152)
> Revision: 408
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [PHICON National Personal Health Record Program](https://discourse.openehr.org/t/phicon-national-personal-health-record-program/14755)
> PHICON is in the process of the development and implementation of a state of the art Portable Personal Health Record () System. The PHICON- will form the bases of the **PHICON National Personal Health Record Program** for all Americans.
With a shift in the healthcare sector towards an automated and paperless environment, it has become increasingly necessary for everyone to develop and maintain an electronic version of their medical records.
Disasters such as Hurricane Katrina showed that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MIE-2008](https://discourse.openehr.org/t/mie-2008/15583)
> This may/may not be the correct place to discuss this but in case you
haven't noticed\. There were eight tutorials scheduled at MIE last
Sunday\. Six of those tutorials were cancelled\. The only two remaining
were the two openEHR related tutorials\.
http://www.sfmi.org/home/page.asp?sid=63&mid=2&PageId=1834
Thanks for doing a great job openEHR advocates\!
Tom, Rong and Sebastian were scheduled for a workshop on
interoperability sing archetypes\. How did that go?
I'm also...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [655] The last revision to the SCons Eiffel builder did not set the Eiffel compiler's -target flag by default to the target executable's base name.](https://discourse.openehr.org/t/ref-impl-eiffel-655-the-last-revision-to-the-scons-eiffel-builder-did-not-set-the-eiffel-compilers-target-flag-by-default-to-the-target-executables-base-name/12427)
> Revision: 655
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [654] The SCons Eiffel builder is now able to recognise the Eiffel compiler's -project_path flag, allowing projects to be built in other than the .ecf file's location.](https://discourse.openehr.org/t/ref-impl-eiffel-654-the-scons-eiffel-builder-is-now-able-to-recognise-the-eiffel-compilers-project-path-flag-allowing-projects-to-be-built-in-other-than-the-ecf-files-location/12390)
> Revision: 654
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Dates and times in an Observation...](https://discourse.openehr.org/t/dates-and-times-in-an-observation/14750)
> Hi all,
I have a question regarding dates and times in openehr\.
I read the section "Time in the EHR" on page 29 of the document "The openEHR Reference Model \- EHR Information Model"\.
As far as I understood it, OBSERVATION\.data\.origin and OBSERVATION\.data\.event\[x\]\.time must not necessarily be within the interval COMPOSITION\.context\.start\_time and COMPOSITION\.context\.end\_time or after COMPOSITION\.context\.start\_time\.
Is this right?
An example:
A...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [DV_ENCAPSULATED.charset attribute - rename to 'encoding'?](https://discourse.openehr.org/t/dv-encapsulated-charset-attribute-rename-to-encoding/12072)
> All implementers need to carefully consider a change proposal like this\.
Theoretically the attribute should have been renamed in some previous
release, but was missed\. Today, the current name is in software, XML
schemas, and in any data instances of DV\_ENCAPSULATED\. The compatibility
costs of changing this may therefore be too high\.
If this group reaches a consensus to go ahead, a CR can be raised\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data arrangement, storage and relationship based on other packages](https://discourse.openehr.org/t/data-arrangement-storage-and-relationship-based-on-other-packages/12298)
> Hi
The published archetypes and difinition of table arrangement in the form
of EAV model \(like quary map and archetype profile\) were so helpful among
openEHR documents\.As a result we have no problem in understanding clinical
data storage and quarying in a dual model\. However, it is difficult to
interprete the other packages\. So, I have some questions about these
packages:
1\- Are there any archetypes based on other packages, \(not only EHR package,
eg\. demographic and common...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [653] AWB-87: In the Options dialog, allow more than one external editor command.](https://discourse.openehr.org/t/ref-impl-eiffel-653-awb-87-in-the-options-dialog-allow-more-than-one-external-editor-command/12251)
> Revision: 653
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [652] AWB-139: Allow the user to choose whether to edit the .adl or .adls file.](https://discourse.openehr.org/t/ref-impl-eiffel-652-awb-139-allow-the-user-to-choose-whether-to-edit-the-adl-or-adls-file/15815)
> Revision: 652
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [651] AWB-136: Instead of generating an HTML file from the repository report, place a processing instruction at the top of the XML file for the browser to use the XSLT for rendering.](https://discourse.openehr.org/t/ref-impl-eiffel-651-awb-136-instead-of-generating-an-html-file-from-the-repository-report-place-a-processing-instruction-at-the-top-of-the-xml-file-for-the-browser-to-use-the-xslt-for-rendering/12186)
> Revision: 651
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [parent-property](https://discourse.openehr.org/t/parent-property/12008)
> Hi Rong, I think the parent\-rpoerty which appears in every constructor
in Locatable\-classes should be of Pathable\-type\. But mostly it is
Locatable\-type\.
Or am I wrong?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [650] AWB-117: The decision whether to recompile an archetype no longer takes into account whether it has already been validly built, to ensure that changes to an archetype always get recompiled.](https://discourse.openehr.org/t/ref-impl-eiffel-650-awb-117-the-decision-whether-to-recompile-an-archetype-no-longer-takes-into-account-whether-it-has-already-been-validly-built-to-ensure-that-changes-to-an-archetype-always-get-recompiled/12004)
> Revision: 650
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [changes on health computing platform page](https://discourse.openehr.org/t/changes-on-health-computing-platform-page/12017)
> Dear all,
I have made some improvements to the page [http://www.openehr.org/201-OE.html](http://www.openehr.org/201-OE.html) - improved text and re-arranged the diagrams. Feedback welcome.
- thomas
[details="(attachments)"]
[/details]
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[407] updated FullConstructor of some ID classes](https://discourse.openehr.org/t/407-updated-fullconstructor-of-some-id-classes/13024)
> Revision: 407
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[406] updated due to changes in the rm-core](https://discourse.openehr.org/t/406-updated-due-to-changes-in-the-rm-core/13023)
> Revision: 406
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[405] updated list of the skipped rm class for finding rm class using value map](https://discourse.openehr.org/t/405-updated-list-of-the-skipped-rm-class-for-finding-rm-class-using-value-map/13022)
> Revision: 405
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[404] fixed the issue with binding array values](https://discourse.openehr.org/t/404-fixed-the-issue-with-binding-array-values/13021)
> Revision: 404
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[403] initial import of xml-binding component to SANDBOX area](https://discourse.openehr.org/t/403-initial-import-of-xml-binding-component-to-sandbox-area/13020)
> Revision: 403
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[402] domain classes updated due to change of ObjectRef](https://discourse.openehr.org/t/402-domain-classes-updated-due-to-change-of-objectref/13019)
> Revision: 402
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[401] replaced enum type of ObjectRef namespace and type with normal string](https://discourse.openehr.org/t/401-replaced-enum-type-of-objectref-namespace-and-type-with-normal-string/13018)
> Revision: 401
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[400] fixed failed testcase of building composition](https://discourse.openehr.org/t/400-fixed-failed-testcase-of-building-composition/13017)
> Revision: 400
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[399] fixed missing annotations in Participation and AuditDetails; removed the dependency to mini-term to avoid cyclic reference](https://discourse.openehr.org/t/399-fixed-missing-annotations-in-participation-and-auditdetails-removed-the-dependency-to-mini-term-to-avoid-cyclic-reference/13016)
> Revision: 399
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[398] added rm data binding between generated xml objects](https://discourse.openehr.org/t/398-added-rm-data-binding-between-generated-xml-objects/13012)
> Revision: 398
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[397] adjusted constructor annotations](https://discourse.openehr.org/t/397-adjusted-constructor-annotations/13011)
> Revision: 397
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[396] added full constructor annotations to some common and support classes](https://discourse.openehr.org/t/396-added-full-constructor-annotations-to-some-common-and-support-classes/13010)
> Revision: 396
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[395] added rm data binding using reflection](https://discourse.openehr.org/t/395-added-rm-data-binding-using-reflection/16065)
> Revision: 395
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[394] fixed a bug in DvText constructor triggered by null value of either language or encoding](https://discourse.openehr.org/t/394-fixed-a-bug-in-dvtext-constructor-triggered-by-null-value-of-either-language-or-encoding/13695)
> Revision: 394
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ehr.entry.activity](https://discourse.openehr.org/t/ehr-entry-activity/16674)
> Comments on ehr\.activity\.entry\.activity\.action\_archetype\_id being a Perl
compliant string instead of an ArchetypeId class instance\. ???
I probably won't be engaging too much in these discussions the next few
days\. I'm just making comments on things I am encountering at a lower
level than I have before\. Hopefully this will all improve my
understanding of openEHR\.
Seems the more I learn the less I know\. :\-\)
Cheers,
Tim
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[393] added a script to retrieve composition from ehr-bank inside cosmic](https://discourse.openehr.org/t/393-added-a-script-to-retrieve-composition-from-ehr-bank-inside-cosmic/16064)
> Revision: 393
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[392] adjusted the interface of this component](https://discourse.openehr.org/t/392-adjusted-the-interface-of-this-component/13007)
> Revision: 392
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [649] Merge revisions 641 to 648 from the TRUNK into BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-649-merge-revisions-641-to-648-from-the-trunk-into-branches-specialisation/13006)
> Revision: 649
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[391] dependencies completely managed by maven now; removed mock terminology service and jars in the lib](https://discourse.openehr.org/t/391-dependencies-completely-managed-by-maven-now-removed-mock-terminology-service-and-jars-in-the-lib/13005)
> Revision: 391
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[390] added a testcase for creating AuditDetails with openehr code](https://discourse.openehr.org/t/390-added-a-testcase-for-creating-auditdetails-with-openehr-code/13004)
> Revision: 390
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[389] added pom.xml to manage the dependencies](https://discourse.openehr.org/t/389-added-pom-xml-to-manage-the-dependencies/13003)
> Revision: 389
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[388] updated and confirmed still working](https://discourse.openehr.org/t/388-updated-and-confirmed-still-working/13002)
> Revision: 388
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[387] added convenient constructors to CDateTime, CDate and CTime](https://discourse.openehr.org/t/387-added-convenient-constructors-to-cdatetime-cdate-and-ctime/13001)
> Revision: 387
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [648] AWB-117: Because of revision 619, which made sure that an invalid .adl file was re-parsed after it had changed, archetypes that had already been successfully compiled were recompiled whenever the user selected them in the repositor](https://discourse.openehr.org/t/ref-impl-eiffel-648-awb-117-because-of-revision-619-which-made-sure-that-an-invalid-adl-file-was-re-parsed-after-it-had-changed-archetypes-that-had-already-been-successfully-compiled-were-recompiled-whenever-the-user-selected-them-in-the-repositor/12999)
> Revision: 648
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[386] fixed a bug in serializing CAttribute with empty children list](https://discourse.openehr.org/t/386-fixed-a-bug-in-serializing-cattribute-with-empty-children-list/12997)
> Revision: 386
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[385] changed to suppress adl-output on default occurrences](https://discourse.openehr.org/t/385-changed-to-suppress-adl-output-on-default-occurrences/13684)
> Revision: 385
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[384] fixed missing adl_version in adl-serializer and added a nearly complete round-trip test](https://discourse.openehr.org/t/384-fixed-missing-adl-version-in-adl-serializer-and-added-a-nearly-complete-round-trip-test/13683)
> Revision: 384
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[383] added value equality check in ArchetypeTerm](https://discourse.openehr.org/t/383-added-value-equality-check-in-archetypeterm/12996)
> Revision: 383
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [647] AWB-136: The HTML repository report could not be displayed if its path contained spaces.](https://discourse.openehr.org/t/ref-impl-eiffel-647-awb-136-the-html-repository-report-could-not-be-displayed-if-its-path-contained-spaces/12995)
> Revision: 647
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[382] added skeleton code for validationTestCase and archetype loading in the base class](https://discourse.openehr.org/t/382-added-skeleton-code-for-validationtestcase-and-archetype-loading-in-the-base-class/12994)
> Revision: 382
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [646] AWB-136: Add a simple CSS to make the HTML repository report look legible.](https://discourse.openehr.org/t/ref-impl-eiffel-646-awb-136-add-a-simple-css-to-make-the-html-repository-report-look-legible/12993)
> Revision: 646
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [645] AWB-136: Add the XSLT script to the installers.](https://discourse.openehr.org/t/ref-impl-eiffel-645-awb-136-add-the-xslt-script-to-the-installers/16063)
> Revision: 645
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [644] AWB-136: Add a simple XSLT script to generate HTML from the XML repository report.](https://discourse.openehr.org/t/ref-impl-eiffel-644-awb-136-add-a-simple-xslt-script-to-generate-html-from-the-xml-repository-report/12992)
> Revision: 644
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[381] added integration.GenericEntry to the rm-domain component](https://discourse.openehr.org/t/381-added-integration-genericentry-to-the-rm-domain-component/12991)
> Revision: 381
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[380] method renamed in archetype-testing classes](https://discourse.openehr.org/t/380-method-renamed-in-archetype-testing-classes/12990)
> Revision: 380
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [643] AWB-136: Move menu option Tools | Export Error Report...](https://discourse.openehr.org/t/ref-impl-eiffel-643-awb-136-move-menu-option-tools-export-error-report/12989)
> Revision: 643
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[379] added one more testcase to dadl-binding](https://discourse.openehr.org/t/379-added-one-more-testcase-to-dadl-binding/12988)
> Revision: 379
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[378] minor doc update](https://discourse.openehr.org/t/378-minor-doc-update/12987)
> Revision: 378
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [642] Bring specialisation branch up to current TRUNK (revision 641) for use with further specialisation and templates work.](https://discourse.openehr.org/t/ref-impl-eiffel-642-bring-specialisation-branch-up-to-current-trunk-revision-641-for-use-with-further-specialisation-and-templates-work/12986)
> Revision: 642
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[377] import of archetype-testing prototype to sandbox area](https://discourse.openehr.org/t/377-import-of-archetype-testing-prototype-to-sandbox-area/13670)
> Revision: 377
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [641] AWB-136: Add menu option Tools | Export Error Report..., which generates an XML file of what is in the Errors grid.](https://discourse.openehr.org/t/ref-impl-eiffel-641-awb-136-add-menu-option-tools-export-error-report-which-generates-an-xml-file-of-what-is-in-the-errors-grid/12985)
> Revision: 641
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [640] Renaming in ARCHETYPE_FLATTENER of output to output_archetype;](https://discourse.openehr.org/t/ref-impl-eiffel-640-renaming-in-archetype-flattener-of-output-to-output-archetype/12980)
> Revision: 640
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[376] improved path processing now supports non-locatable rmClass](https://discourse.openehr.org/t/376-improved-path-processing-now-supports-non-locatable-rmclass/12979)
> Revision: 376
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[375] added support for partial dates in adl-parser](https://discourse.openehr.org/t/375-added-support-for-partial-dates-in-adl-parser/12978)
> Revision: 375
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[374] updated rm-builder due to changes in the data structures and included rm-builder to the root pom](https://discourse.openehr.org/t/374-updated-rm-builder-due-to-changes-in-the-data-structures-and-included-rm-builder-to-the-root-pom/12974)
> Revision: 374
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[373] updated domain classes due to new implementation of Locatable.itemAtPath()](https://discourse.openehr.org/t/373-updated-domain-classes-due-to-new-implementation-of-locatable-itematpath/12977)
> Revision: 373
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[372] rewrite of itemAtPath() in Loctable and updated the several data structure classes according to the specs](https://discourse.openehr.org/t/372-rewrite-of-itematpath-in-loctable-and-updated-the-several-data-structure-classes-according-to-the-specs/12976)
> Revision: 372
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [question about assumed_types test archetype](https://discourse.openehr.org/t/question-about-assumed-types-test-archetype/16672)
> On following URL
[http://www.openehr.org/wsvn/knowledge/archetypes/dev/adl/test/basics/adl-test-entry.assumed_types.v1.adl?op=file&rev=0&sc=0](http://www.openehr.org/wsvn/knowledge/archetypes/dev/adl/test/basics/adl-test-entry.assumed_types.v1.adl?op=file&rev=0&sc=0)
we find an archetype called:
**adl-test-entry.assumed_types.v1.adl**
In there is:
```
date_attr1 matches {yyyy-mm-dd; 1995-03-17}
date_attr2 matches {yyyy-??-??; 1995-03-17}
date_attr3 matches...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Architectural Review Board (ARB) & governance](https://discourse.openehr.org/t/openehr-architectural-review-board-arb-governance/12005)
> Dear all,
on behalf of Prof David Ingram (UCL; chairman of the openEHR Foundation), I would like to announce the reconstituted Architectural Review Board (ARB) of openEHR - [http://www.openehr.org/about/arb.html](http://www.openehr.org/about/arb.html)
We would like to welcome the following new members:
- John Arnett, UK NHS. In his current role of Interoperability Architect, John is responsible for developing architectural frameworks and design methodologies for optimising the development,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [639] AWB-117: Fix problems in the Errors grid when re-parsing an archetype successfully that previously had errors or warnings:](https://discourse.openehr.org/t/ref-impl-eiffel-639-awb-117-fix-problems-in-the-errors-grid-when-re-parsing-an-archetype-successfully-that-previously-had-errors-or-warnings/12975)
> Revision: 639
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [638] AWB-133: Let the dADL parser support type identifiers surrounded by parentheses, as described in adl.pdf section 4.4.5.](https://discourse.openehr.org/t/ref-impl-eiffel-638-awb-133-let-the-dadl-parser-support-type-identifiers-surrounded-by-parentheses-as-described-in-adl-pdf-section-4-4-5/12973)
> Revision: 638
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [missing rmclasses in rmbuilder](https://discourse.openehr.org/t/missing-rmclasses-in-rmbuilder/16671)
> Hi Rong, can you please tell me what criteria are used for having a
class in the rm\-builder\.
At this moment I am missing some\.
The EHR class, but I can imagine that, it s the top class of an EHR, and
maybe noone ever wants to build that in the rm\-builder\.
But I am also missing ReferenceRange, ISMtransition, and some more\.
Thanks for any pointer to information
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [637] AWB-132: Fix a Void target call that showed up with some of the test archetypes, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-637-awb-132-fix-a-void-target-call-that-showed-up-with-some-of-the-test-archetypes-e-g/13656)
> Revision: 637
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[371] updated pom.xml and changed some attributes in the dadl files to underscore separated style](https://discourse.openehr.org/t/371-updated-pom-xml-and-changed-some-attributes-in-the-dadl-files-to-underscore-separated-style/13655)
> Revision: 371
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[370] improved RM class loading and a few testcases in the rm-builder](https://discourse.openehr.org/t/370-improved-rm-class-loading-and-a-few-testcases-in-the-rm-builder/12972)
> Revision: 370
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[369] fixed the missing s in the FullConstructor annotations in several Entry subclasses](https://discourse.openehr.org/t/369-fixed-the-missing-s-in-the-fullconstructor-annotations-in-several-entry-subclasses/12971)
> Revision: 369
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[368] added FullConstructor annotations to several classes from common and support package](https://discourse.openehr.org/t/368-added-fullconstructor-annotations-to-several-classes-from-common-and-support-package/12970)
> Revision: 368
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[367] initial import of dadl-binding component to SANDBOX](https://discourse.openehr.org/t/367-initial-import-of-dadl-binding-component-to-sandbox/12969)
> Revision: 367
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[366] added parentheses around type identifier and support for empty attr list in object block](https://discourse.openehr.org/t/366-added-parentheses-around-type-identifier-and-support-for-empty-attr-list-in-object-block/12968)
> Revision: 366
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [two issues in dADL grammar](https://discourse.openehr.org/t/two-issues-in-dadl-grammar/12967)
> Hi all,
There are two issues in dADL grammer (as part of the ADL 1.4 specs) I discovered recently when I work on the Java DADL parser. [http://www.openehr.org/svn/ref_impl_java/SANDBOX/dadl-parser/](http://www.openehr.org/svn/ref_impl_java/SANDBOX/dadl-parser/)
1) the parentheses around the optional type identifier is missing in the grammar
The example on type information ( from the ADL document) looks like this:
destinations = <
["seville"] = (TOURIST_DESTINATION) <
....
>
Note that the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [representation in Item_structure](https://discourse.openehr.org/t/representation-in-item-structure/16670)
> Hi Rong, I see that you have removed the null test on representation in
Item\_structure\.
When I look in the specs,
http://www.openehr.org/releases/1.0.1/architecture/rm/data_structures_im.pdf
I see there is no representation attribute in item\_structure\. Same for
the from ItemStructure derived classes
Can you please explain how I have to understand this?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [636] AWB-131: Fix a Void target call that occurred when populating the Node Map if QUANTITY.units was Void.](https://discourse.openehr.org/t/ref-impl-eiffel-636-awb-131-fix-a-void-target-call-that-occurred-when-populating-the-node-map-if-quantity-units-was-void/12966)
> Revision: 636
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [635] AWB-130: Commit some clean-ups that were done while attempting to fix this issue (mainly avoiding explicit mentions of the QUANTITY class).](https://discourse.openehr.org/t/ref-impl-eiffel-635-awb-130-commit-some-clean-ups-that-were-done-while-attempting-to-fix-this-issue-mainly-avoiding-explicit-mentions-of-the-quantity-class/12965)
> Revision: 635
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [634] Fix some obsolete "creation" keywords.](https://discourse.openehr.org/t/ref-impl-eiffel-634-fix-some-obsolete-creation-keywords/16062)
> Revision: 634
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [633] AWB-130: DV_QUANTITY did not compile if the references in C_DV_QUANTITY to QUANTITY were change to DV_QUANTITY.](https://discourse.openehr.org/t/ref-impl-eiffel-633-awb-130-dv-quantity-did-not-compile-if-the-references-in-c-dv-quantity-to-quantity-were-change-to-dv-quantity/16061)
> Revision: 633
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[365] added a convenient constructor to ItemList; updated the commons-lang dependency with a later version](https://discourse.openehr.org/t/365-added-a-convenient-constructor-to-itemlist-updated-the-commons-lang-dependency-with-a-later-version/12964)
> Revision: 365
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[364] added support to underscore separated attriubte names in finding matching rm classes](https://discourse.openehr.org/t/364-added-support-to-underscore-separated-attriubte-names-in-finding-matching-rm-classes/12963)
> Revision: 364
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[363] adjusted the constructor of ItemList according to the specs](https://discourse.openehr.org/t/363-adjusted-the-constructor-of-itemlist-according-to-the-specs/12962)
> Revision: 363
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[362] added findMatchingRMClass by valueMap to rm-builder](https://discourse.openehr.org/t/362-added-findmatchingrmclass-by-valuemap-to-rm-builder/12961)
> Revision: 362
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[361] added FullConstructor annotation to CodePhrase](https://discourse.openehr.org/t/361-added-fullconstructor-annotation-to-codephrase/12960)
> Revision: 361
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[360] updated the FullConstructor annotation of Activity](https://discourse.openehr.org/t/360-updated-the-fullconstructor-annotation-of-activity/12959)
> Revision: 360
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[359] updated FullConstructor annotation for DvProportion](https://discourse.openehr.org/t/359-updated-fullconstructor-annotation-for-dvproportion/12958)
> Revision: 359
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[358] fixed a bug in the parser related to parsing typed object block](https://discourse.openehr.org/t/358-fixed-a-bug-in-the-parser-related-to-parsing-typed-object-block/12957)
> Revision: 358
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Ref_impl_java mailing list submissions](https://discourse.openehr.org/t/ref-impl-java-mailing-list-submissions/12956)
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [This topic needs a title](https://discourse.openehr.org/t/this-topic-needs-a-title/14751)
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[357] move sandbox projects to the new SANDBOX top directory](https://discourse.openehr.org/t/357-move-sandbox-projects-to-the-new-sandbox-top-directory/12955)
> Revision: 357
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[356] move sandbox projects to the new SANDBOX top directory](https://discourse.openehr.org/t/356-move-sandbox-projects-to-the-new-sandbox-top-directory/12953)
> Revision: 356
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[355] move sandbox projects to the new SANDBOX top directory](https://discourse.openehr.org/t/355-move-sandbox-projects-to-the-new-sandbox-top-directory/12950)
> Revision: 355
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [632] EDT-272: Fix a bug introduced by revision 132.](https://discourse.openehr.org/t/ref-impl-eiffel-632-edt-272-fix-a-bug-introduced-by-revision-132/12949)
> Revision: 632
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[354] fixed minor typo in DvText](https://discourse.openehr.org/t/354-fixed-minor-typo-in-dvtext/12948)
> Revision: 354
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[353] updated pom of rm-builder to exclude unnecessary dependencies](https://discourse.openehr.org/t/353-updated-pom-of-rm-builder-to-exclude-unnecessary-dependencies/16060)
> Revision: 353
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[352] rm-builder updated to latest rm-core and rm-domain, all tests passed](https://discourse.openehr.org/t/352-rm-builder-updated-to-latest-rm-core-and-rm-domain-all-tests-passed/12947)
> Revision: 352
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[351] fixed a code phrase validation bug in the constructor of Composition](https://discourse.openehr.org/t/351-fixed-a-code-phrase-validation-bug-in-the-constructor-of-composition/12946)
> Revision: 351
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[350] completed country codeset in the mini-termserv component](https://discourse.openehr.org/t/350-completed-country-codeset-in-the-mini-termserv-component/12944)
> Revision: 350
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[349] fixed some typos in DvCount](https://discourse.openehr.org/t/349-fixed-some-typos-in-dvcount/12943)
> Revision: 349
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[348] fixed a bug in the constructor of ISMTransition](https://discourse.openehr.org/t/348-fixed-a-bug-in-the-constructor-of-ismtransition/12942)
> Revision: 348
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[347] fixed two minor inconsistences in the full constructor annotations](https://discourse.openehr.org/t/347-fixed-two-minor-inconsistences-in-the-full-constructor-annotations/12941)
> Revision: 347
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [charset attribute in ENCAPSULATED](https://discourse.openehr.org/t/charset-attribute-in-encapsulated/12951)
> Hi all,
The attribute "charset" in ENCAPSULATED should probably be renamed to "encoding" to be consistent with similar attributes in DV_TEXT etc. Both "charset" and "encoding" are using the same code set "character sets" from openEHR terminology.
Cheers,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[346] added a testcase to DvCount](https://discourse.openehr.org/t/346-added-a-testcase-to-dvcount/16058)
> Revision: 346
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [PARTICIPATION needs to be a LOCATABLE](https://discourse.openehr.org/t/participation-needs-to-be-a-locatable/14749)
> Dear all,
the group at Ocean have found that the PARTICIPATION class probably
should be LOCATABLE, or act like it is LOCATABLE, because a\) it needs to
be archetyped and b\) it occurs as children of 2 container attributes,
namely ENTRY\.other\_particpants and EVENT\_CONTEXT\.participations\. The
latter fact means that PARTICIPATION objects in archetypes need
archetype\_node\_ids to be distinguishable from siblings in these attributes\.
Currently, PARTICIPATION is not LOCATABLE or even...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [termCodes/constraintCodes](https://discourse.openehr.org/t/termcodes-constraintcodes/12001)
> Hi All,
considering translations of term and constraint codes in the archetype
ontology:
Can the archetype editor developers or users tell me if the editors do
any validation to insure that there the same codes and same number of
codes in a translation as there is in the original language?
Thanks,
Tim
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ADL Files Missing Required Section](https://discourse.openehr.org/t/adl-files-missing-required-section/16059)
> Hi All,
The following ADL files are missing the required 'language' section\. It
would be very helpful to we consumers of ADL if you could repair/remove
the ones that you have custodial obligations for\. ...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [broken link](https://discourse.openehr.org/t/broken-link/16057)
> Hi Tom,
There is a broken link on "what is an archetype" page ([http://www.openehr.org/116-OE.html?branch=1&language=1](http://www.openehr.org/116-OE.html?branch=1&language=1)), which links to the archetype paper hosted on [http://www.deepthought.com.au/](http://www.deepthought.com.au/). But the site seems to be down at the moment.
Maybe we could host the paper on the openEHR site instead.
Cheers,
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ARCHETYPE_ONTOLOGY](https://discourse.openehr.org/t/archetype-ontology/14748)
> While implementing ARCHETYPE objects I ran into an odd thing\. Maybe I
am missing something or there is a mistake in the documentation?
The ontology attribute of ARCHETYPE is of the type ARCHETYPE\_ONTOLOGY\.
The AOM then says that the attribute ARCHETYPE\_ONTOLOGY\.parent\_archetype
is of type ARCHETYPE and it is described as the; "Archetype which owns
this ontology\."
Is that REALLY what it should be or should
ARCHETYPE\_ONTOLOGY\.parent\_archetype be an...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[345] initial import of dadl-parser to sandbox area](https://discourse.openehr.org/t/345-initial-import-of-dadl-parser-to-sandbox-area/16056)
> Revision: 345
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[344] create sandbox top directory](https://discourse.openehr.org/t/344-create-sandbox-top-directory/13612)
> Revision: 344
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Datatype questions](https://discourse.openehr.org/t/datatype-questions/14747)
> Dear All,
I am still mulling over how to validate openEhr messages \(wrt testing\) &
how to create Xforms etc\.
3 separate questions\.\.\.\.
A\) I noticed this:
http://www.openehr.org/wiki/display/dev/Data+type+widgets
Has any progress been made?
B\) Is there a datatype for rich text \(e\.g\. XHTML \(possibly CData'ed\)\)?
C\) Assuming a starting point of XML\.\.\.\.what are the current ideas wrt
representing datatypes etc in a form which can be useful in a XForms
environment...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parsing ADL 1.4 w/Python](https://discourse.openehr.org/t/parsing-adl-1-4-w-python/14744)
> Hi All,
Today was "Stress Test Day" for my Python ADL 1\.4\. parser\. The goal was
to see how well I could parse ADL 1\.4 in order to create a data
structure that can be used for building in memory Python archetype
objects from the reference model so they can be persisted in an
archetype repository for local use\.
I used almost all of the archetypes in SVN control on openEHR\.org\. The
exceptions were the test ones involving automotive information and the
duplicates between...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [631] AWB-127: Fix a catcall that occurred when building an archetype lineage.](https://discourse.openehr.org/t/ref-impl-eiffel-631-awb-127-fix-a-catcall-that-occurred-when-building-an-archetype-lineage/16055)
> Revision: 631
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[343] renamed otherReferenceRanges parameter in the constructors of DvOrdered subclasses according to the specs](https://discourse.openehr.org/t/343-renamed-otherreferenceranges-parameter-in-the-constructors-of-dvordered-subclasses-according-to-the-specs/13611)
> Revision: 343
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[342] added the missing FullConstructor annotation in the constructor of DvProportion](https://discourse.openehr.org/t/342-added-the-missing-fullconstructor-annotation-in-the-constructor-of-dvproportion/16053)
> Revision: 342
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Ruby implementation project release 0.0.1 package](https://discourse.openehr.org/t/ruby-implementation-project-release-0-0-1-package/16052)
> Dear all,
We announce that we released Ruby implementation version 0\.0\.1 package
on May 5, 2008\. This is a memorable firlst release for us\. The package
is available on the URL shown bellow:
http://openehr.jp/svn/ruby/tags/release-0.0.1/adl_parser/pkg/adl_parser-0.0.1.gem
The release notes are also shown bellow:
= Synopsis
Ruby openEHR implementation project
= Version
Release\-0\.0\.1
= Requirements
\* Ruby 1\.8\.6 or higher
\* Yaparc Library 0\.2\.0 or higer
\* Tested with Ruby...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Constant Values and "sub" Elements](https://discourse.openehr.org/t/constant-values-and-sub-elements/16711)
> Hello\!
Within the context of my bachelor thesis, i am trying to transform a domain
model into an archetype, but now i am having some problems and i hope maybe
some of you here can help me\.
My first question is, is it possible to define constant or "hard coded"
values ie\. constant text which contains a description?
So far I am trying to add a CODED\_TEXT that matches a defined constraint
ac0001, but i am not sure if this is a valid solution\.
ITEM\_TREE\[at0003\]...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [630] In the ADL Workbench help, fix a couple of typos, a misnamed file and an accidentally-committed copy of a file.](https://discourse.openehr.org/t/ref-impl-eiffel-630-in-the-adl-workbench-help-fix-a-couple-of-typos-a-misnamed-file-and-an-accidentally-committed-copy-of-a-file/12939)
> Revision: 630
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New directions for openEHR 2008](https://discourse.openehr.org/t/new-directions-for-openehr-2008/16664)
> Dear all,
we have created some new pages describing at a strategic level what the openEHR Foundation and community might try to do in the current and next year (20088/9).
- openEHR Vision - [http://www.openehr.org/about/vision.html](http://www.openehr.org/234-OE.html)
- openEHR Specifications - Strategic directions - [http://www.openehr.org/specifications/spec_strategy.html](http://www.openehr.org/230-OE.html)
- openEHR Specification Roadmap 2008 -...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Rahils thesis -> the openEHR web.](https://discourse.openehr.org/t/rahils-thesis-the-openehr-web/14753)
> Hi openEHR\-web\-people\!
Would somebody with write\-access to the openEHR site like to help us
get Rahils PhD thesis pubished there? I have put a temporary copy of
it for download at:
http://www.imt.liu.se/~erisu/2008/temp/FinalThesis-Mar2008-RQamar.pdf
It should probably be placed in the directory\.\.\.
http://www.openehr.org/publications/archetypes/
\.\.\.and linked to from\.\.\.
http://www.openehr.org/shared-resources/publications/archetypes.html
Best regards,
Erik...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [@FullConstructor in DvProportion is forgotten](https://discourse.openehr.org/t/fullconstructor-in-dvproportion-is-forgotten/16054)
> @FullConstructor in DvProportion is forgotten
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [referenceranges in Quantity package](https://discourse.openehr.org/t/referenceranges-in-quantity-package/12940)
> Excuse me when I am wrong, I checked it in the specs\.
In DvOrdered, there is a attribute otherReferenceRanges, this is
inherited by about all the other classes in the Quantity\-package, but
there the name changed to referenceRanges\. I believe this is not
according the specs\. I think it should be otherReferenceRanges in all
subclasses involved
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [629] EiffelStudio 6.1 made a change to the .NET version of INTERNAL.](https://discourse.openehr.org/t/ref-impl-eiffel-629-eiffelstudio-6-1-made-a-change-to-the-net-version-of-internal/16051)
> Revision: 629
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [typo in Action.java](https://discourse.openehr.org/t/typo-in-action-java/16050)
> I think the constructor\-parameter otherparticipation should be called
otherParticipations \(with "s"\), because, for consistency, it is also
called that way in its parents CareEntry and Entry\.
Still have no access to SVN, always think that it is only incidental
that I need it\.
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [628] AWB-122: Fix an off-by-one error in the last commit of the SConstruct.](https://discourse.openehr.org/t/ref-impl-eiffel-628-awb-122-fix-an-off-by-one-error-in-the-last-commit-of-the-sconstruct/16049)
> Revision: 628
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [627] AWB-122: In the SCons Eiffel builder, do not call finish_freezing, because it slows down building a release and is pointless because developers can easily freeze manually if they need to.](https://discourse.openehr.org/t/ref-impl-eiffel-627-awb-122-in-the-scons-eiffel-builder-do-not-call-finish-freezing-because-it-slows-down-building-a-release-and-is-pointless-because-developers-can-easily-freeze-manually-if-they-need-to/16048)
> Revision: 627
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [TDS, public development on openEHR wiki instead? (Was: Data-entry for OpenEhr)](https://discourse.openehr.org/t/tds-public-development-on-openehr-wiki-instead-was-data-entry-for-openehr/11992)
> Hi\!
I believe TDS is a very nice approach for som especific integration
purposes\. Simple and wonderful invention \(the best ones are often
simple\.\.\.\) For those new to TDS there was a thread regarding this
earlier: http://www.openehr.org/mailarchives/openehr-technical/msg03116.html
Are there any specific reasons for keeping the development internal to
Ocean Informatics? As I understand it you sometimes internally use a
wiki for these kinds of developments, I would suggest that you...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Icons for openEHR](https://discourse.openehr.org/t/icons-for-openehr/12938)
> Dear all
We are interested in a set of icons for the openEHR tools and display that are better than the ones that have come together many years ago. I guess they have some familiarity but they are dependent on language (Q and T) and would benefit from an overhaul.
Ian McNicoll has suggested one site that is leading the way in this area ;-)
[http://www.reason.com/blog/show/126187.html](http://www.reason.com/blog/show/126187.html)
I have written to a number of icon developer sites to ask...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Example messages](https://discourse.openehr.org/t/example-messages/14752)
> Dear All,
Is there an easy way to create or does anyone have any messages in XML?
i\.e\. if one has a template or archetype is there any way to create an
example of the message which would be sent using that archetype/template?
Our message checking s/w in our Integration Center uses XPath, XSLT etc
to run rules against incoming HL7 messages & I'd like to get an initial
feeling wrt how/if this system could be used wrt OpenEHR messages\.
Forget about any external layers of the onion...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data-entry for OpenEhr](https://discourse.openehr.org/t/data-entry-for-openehr/14746)
> Hi all,
I am building an application on base of an OpenEhr kernel\.
I would be very happy if people can give some ideas about one question I
have\.
I don't need complete technical worked out docuemnts \(although I don't
mind to recieve them\)
But just some hints make me happy\.
My problem is, I am looking for a good way to enter data into an OpenEhr
system\.
I did some experiments with XML, which is good but I ran against
limitations \(specially in cardinality\), which may be...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] problem compiling adl_workbench](https://discourse.openehr.org/t/ref-impl-eiffel-problem-compiling-adl-workbench/14743)
> Hi, Peter,
I have some problems compiling the ADL workbench\. I tried two versions\.
One from BRANCHES/specialisation, I get 4 compiler\-errors\. Do you want
to know them\.
\(maybe it is a code\-tree for developing purposem, not for public\)
The TRUNK version does not open the ECF\. It gives an error while
opening the project:
TRUNK/apps/adl?workbench?ecf: 1:2 parse error
I am using EiffelStudio 6 \(6\.1\.7\.1223 GPL Edition \- linux\-x86\)
What can I do? is the compiled version on the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML Schema for the openEHR Demographics package?](https://discourse.openehr.org/t/xml-schema-for-the-openehr-demographics-package/13800)
> Hi\!
When browsing through the xsd files for the openEHR RM at
http://www.openehr.org/releases/1.0.1/its/XML-schema/index.html I did
not find the classes from the demographics package in the schema\. Am I
partially blind or have they not been published as XML Schemas along
with the rest of the model? Is there anybody out there who have
created an XML\-schema for the openEHR demographics package?
Best regards,
Erik Sundvall
erisu@imt\.liu\.se http://www.imt.liu.se/~erisu/ Tel:...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [626] EDT-192: In TAGS/Aug2007, set the ADL Parser DLL's version to 1.4.0, to be consistent with the ADL Workbench version number upon which the code is most closely based.](https://discourse.openehr.org/t/ref-impl-eiffel-626-edt-192-in-tags-aug2007-set-the-adl-parser-dlls-version-to-1-4-0-to-be-consistent-with-the-adl-workbench-version-number-upon-which-the-code-is-most-closely-based/12934)
> Revision: 626
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [new pages](https://discourse.openehr.org/t/new-pages/14745)
> Dear all,
I would like to get some feedback on the following new pages:
- openEHR Vision 2008 - [http://www.openehr.org/234-OE.html](http://www.openehr.org/234-OE.html)
- openEHR Specifications - Strategic directions 2008 - [http://www.openehr.org/230-OE.html](http://www.openehr.org/230-OE.html)
- openEHR Specification Roadmap 2008 - [http://www.openehr.org/233-OE.html](http://www.openehr.org/233-OE.html)
- openEHR Clinical Strategic Directions 2008 -...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AOM MOF mapping](https://discourse.openehr.org/t/aom-mof-mapping/14742)
> In a reply wrt "On Information and Interoperability" I have noted that
there is a move underway to try & produce an HL7 model \(via EMF/MOF\) for
use in our /OHT eclipse tooling\.
Has anyone looked at an AOM/MOF mapping?
If so any thoughts?
E\.g\. were one to want to sit down & do some Eclipse OpenEHR tooling then
an obvious contender would be the Eclipse EMF/GMF & that would require a
AOM<>EMF mapping & given EMF is a subset of MOF then \.\.\.\.etc\.
Adam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [On Information and Interoperability](https://discourse.openehr.org/t/on-information-and-interoperability/14732)
> \[extracted from the thread "Archetype documentation using XML \+ XSLT"\]
> Tim Cook wrote:
>
> >>
> >
> > ADL does semantically describe the AOM\.
> >
>
> No reason why XML could not\.
>
> It can suffice for anything from a webform \(e\.g\. XForms\) to a vector
> graphic \(e\.g\. SVG\) to an object model to formatted text \(e\.g\. XHTML\)
> to
> an office file \(e\.g\. ODF or OOXML\) to a process such as XSLT\.
>
Hi Adam,
Please let me start by saying that I would...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Smiljana Slavec - sprememba/change](https://discourse.openehr.org/t/smiljana-slavec-sprememba-change/12933)
> Perhaps the starting date is significant?
Thilo Schuler wrote:
[details="(attachments)"]
[/details]
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [625] EDT-192: In DATE_TIME_ROUTINES, valid_time_constraint_patterns and valid_date_time_constraint_patterns were inconsistent.](https://discourse.openehr.org/t/ref-impl-eiffel-625-edt-192-in-date-time-routines-valid-time-constraint-patterns-and-valid-date-time-constraint-patterns-were-inconsistent/12932)
> Revision: 625
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [624] AWB-103 and AWB-117: Update news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-624-awb-103-and-awb-117-update-news-txt/12931)
> Revision: 624
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [procedure or finding?](https://discourse.openehr.org/t/procedure-or-finding/14739)
> I am making some Snomed bindings for some sample
archetypes but am having some meta\-level problems\.
An example will probably help \-
Say I want to snomed code the urinalysis archetype\. It
lists a large set of potential measurements from a
urine dipstick test \- blood, glucose, ketones etc\.
Snomed has comprehensive coverage of all of these
categories as 'procedures'
252384001 Urine dipstick for bilirubin \(procedure\)
270894005 Urine dipstick for blood \(procedure\)
269879003...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype documentation using XML + XSLT](https://discourse.openehr.org/t/archetype-documentation-using-xml-xslt/14741)
> Dear All
After discussions with users and in consideration of the range of platforms now being implemented, it would seem appropriate to move to a multiplatform documentation process for openEHR artefacts. The important specific documentation to consider are for archetypes and templates. It seems prudent to start with the former. An outline is on the wiki below:
[http://www.openehr.org/wiki/display/dev/Archetype+to+HTML](http://www.openehr.org/wiki/display/dev/Archetype+to+HTML)
What we...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [623] AWB-103: Remove an empty routine and call that appear to have bee committed by accident in revision 622.](https://discourse.openehr.org/t/ref-impl-eiffel-623-awb-103-remove-an-empty-routine-and-call-that-appear-to-have-bee-committed-by-accident-in-revision-622/16047)
> Revision: 623
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [622] Corrected the logic in ARCHETYPE_FLATTENER.node_graft, and also added attributes paths back into OG_OBJECT_NODE.generate_all_paths, because otherwise ARCHETYPE.has_path was incorrectly responding negative to attribute paths, and ob](https://discourse.openehr.org/t/ref-impl-eiffel-622-corrected-the-logic-in-archetype-flattener-node-graft-and-also-added-attributes-paths-back-into-og-object-node-generate-all-paths-because-otherwise-archetype-has-path-was-incorrectly-responding-negative-to-attribute-paths-and-ob/16046)
> Revision: 622
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [621] AWB-117: Complete the work begun in revision 619 to make sure that an invalid .adl file is re-parsed after it has changed.](https://discourse.openehr.org/t/ref-impl-eiffel-621-awb-117-complete-the-work-begun-in-revision-619-to-make-sure-that-an-invalid-adl-file-is-re-parsed-after-it-has-changed/16045)
> Revision: 621
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [question abouit minitermserv](https://discourse.openehr.org/t/question-abouit-minitermserv/16665)
> Hi,
I wonder if I misunderstand something
In the file: mini-termserv/src/main/resources/openehr_terminology_en.xml
we find for example, this line:
In the file XMLTerminologySource.java, this line is interpreted as
`private CodeSet loadCodeSet(Element element) {`
`CodeSet codeset = new CodeSet();`
`codeset.openehrId = element.getAttributeValue("openehr_id");`
`codeset.issuer =...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR vs MDA/MDD & DSLs](https://discourse.openehr.org/t/openehr-vs-mda-mdd-dsls/16668)
> Hi all, just wanna share this:
For many of you this might not be something new, but today I
consciously noticed to many analogies between the Model Driven
Architecture \(MDA\) or Model Driven Development \(MDD\) including the
trendy Domain Specific Languages \(DSL\) with openEHR's two model
approach \(see attached png from
http://www.omg.org/cgi-bin/apps/doc?omg/03-06-01.pdf \) Obviously the
reasons are partly different \(plattform independant code vs semantic
interoperability \-...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [619] AWB-117: Make sure that an invalid .adl file is re-parsed after it has changed.](https://discourse.openehr.org/t/ref-impl-eiffel-619-awb-117-make-sure-that-an-invalid-adl-file-is-re-parsed-after-it-has-changed/12929)
> Revision: 619
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Smiljana Slavec - sprememba/change](https://discourse.openehr.org/t/smiljana-slavec-sprememba-change/12928)
> I will be out of the office starting 01\.04\.2008 and will not return until
31\.12\.2020\.
Spoštovani,
moj stari elektronski naslov se ukinja, zato prosim, da mi
uradno pošto v bodoče pošiljate na:
smiljana\.voncina\-slavec@gov\.si,
privatno pa na
smiljana\.v\.slavec@gmail\.com
Dear all,
my old e\-mail adress is closing\. I ask you to use my new adress:
smiljana\.voncina\-slavec@gov\.si
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [617] AWB-84 and AWB-115: Update news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-617-awb-84-and-awb-115-update-news-txt/12927)
> Revision: 617
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [616] AWB-115: On the Statistics tab, the Archetypes Containing Slots" and "Archetypes Used in Slots" fields were only updated after a full build.](https://discourse.openehr.org/t/ref-impl-eiffel-616-awb-115-on-the-statistics-tab-the-archetypes-containing-slots-and-archetypes-used-in-slots-fields-were-only-updated-after-a-full-build/12926)
> Revision: 616
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [615] AWB-84: Remove the left arrow indicating that an archetype is used by other archetypes, since it doesn't work properly and and it's probably not very useful.](https://discourse.openehr.org/t/ref-impl-eiffel-615-awb-84-remove-the-left-arrow-indicating-that-an-archetype-is-used-by-other-archetypes-since-it-doesnt-work-properly-and-and-its-probably-not-very-useful/12922)
> Revision: 615
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [614] AWB-107: Revision 604's override of EV_TREE_IMP was working on Mac but not on Linux, because the latter was built with the precompiled Vision2 library.](https://discourse.openehr.org/t/ref-impl-eiffel-614-awb-107-revision-604s-override-of-ev-tree-imp-was-working-on-mac-but-not-on-linux-because-the-latter-was-built-with-the-precompiled-vision2-library/12921)
> Revision: 614
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [613] AWB-84: Use different arrow characters to indicate if there are slots, or if the archetype is used by other archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-613-awb-84-use-different-arrow-characters-to-indicate-if-there-are-slots-or-if-the-archetype-is-used-by-other-archetypes/12920)
> Revision: 613
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [612] AWB-84: Update news.txt to mention the user interface improvements, and to remove changes from the previous release.](https://discourse.openehr.org/t/ref-impl-eiffel-612-awb-84-update-news-txt-to-mention-the-user-interface-improvements-and-to-remove-changes-from-the-previous-release/12919)
> Revision: 612
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [611] AWB-84: In the repository explorer, append some characters after each archetype's name indicating if there are slots, or if the archetype is used by other archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-611-awb-84-in-the-repository-explorer-append-some-characters-after-each-archetypes-name-indicating-if-there-are-slots-or-if-the-archetype-is-used-by-other-archetypes/16044)
> Revision: 611
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [610] Work around an apparent compiler bug in EiffelStudio 6.1.7.1477.](https://discourse.openehr.org/t/ref-impl-eiffel-610-work-around-an-apparent-compiler-bug-in-eiffelstudio-6-1-7-1477/12918)
> Revision: 610
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [609] AWB-84: On the Slots tab, indicate the number of slots in the current archetype and the number of other archetypes that use the current archetype, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-609-awb-84-on-the-slots-tab-indicate-the-number-of-slots-in-the-current-archetype-and-the-number-of-other-archetypes-that-use-the-current-archetype-e-g/13554)
> Revision: 609
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [608] AWB-111: In the developer page, describe how to install NSIS.](https://discourse.openehr.org/t/ref-impl-eiffel-608-awb-111-in-the-developer-page-describe-how-to-install-nsis/12916)
> Revision: 608
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [inheritance of cdomaintype](https://discourse.openehr.org/t/inheritance-of-cdomaintype/16667)
> Hi,
I found out that in the java\-kernel CDomainType inherits from CObject\.
In the website of openehr, I found in the documentation that it should
inherit from CDefinedObject\.
\(http://www.openehr.org/uml/release-1.0.1/Browsable/S.040.1433.36.172Report.html)
hope this link works
Is there a special reason why this is different in the reference code?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [607] AWB-84: On the Errors tab, indicate the number of parse errors, validity errors and warnings, e.g.](https://discourse.openehr.org/t/ref-impl-eiffel-607-awb-84-on-the-errors-tab-indicate-the-number-of-parse-errors-validity-errors-and-warnings-e-g/12914)
> Revision: 607
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [606] AWB-86: Update the link in the documentation to the Mac OS X Tiger installer, which has just been uploaded.](https://discourse.openehr.org/t/ref-impl-eiffel-606-awb-86-update-the-link-in-the-documentation-to-the-mac-os-x-tiger-installer-which-has-just-been-uploaded/12913)
> Revision: 606
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [605] AWB-74: Increment the version number in OPENEHR_VERSION.](https://discourse.openehr.org/t/ref-impl-eiffel-605-awb-74-increment-the-version-number-in-openehr-version/12912)
> Revision: 605
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [604] AWB-107: Override the GTK implementation of EV_TREE_IMP.ensure_item-visible, because EiffelVision's version of it does not expand the given node's parent nodes.](https://discourse.openehr.org/t/ref-impl-eiffel-604-awb-107-override-the-gtk-implementation-of-ev-tree-imp-ensure-item-visible-because-eiffelvisions-version-of-it-does-not-expand-the-given-nodes-parent-nodes/12911)
> Revision: 604
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [603] AWB-74: Add the word "Preview" to the version string in OPENEHR_VERSION, now that we are beginning work on the next release.](https://discourse.openehr.org/t/ref-impl-eiffel-603-awb-74-add-the-word-preview-to-the-version-string-in-openehr-version-now-that-we-are-beginning-work-on-the-next-release/12910)
> Revision: 603
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Archetype Workbench - Release 1.4.1 available](https://discourse.openehr.org/t/archetype-workbench-release-1-4-1-available/12898)
> Release 1.4.1 of the Archetype Workbench is now available - see the help page at [http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm](http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm). This release includes some major new features:
- specialisation semantics are now 90% implemented.
- a new file extension is now in use - .adls, for 'ADL source' files, allowing specialised archetypes to be represented 'differentially' (like...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [602] Rempove old project page (contents now in Daisy)](https://discourse.openehr.org/t/ref-impl-eiffel-602-rempove-old-project-page-contents-now-in-daisy/12906)
> Revision: 602
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [601] AWB-74: Increment the version number to 1.4.2 in adl_workbench.rc, ADLWorkbenchInstall.nsi and both Info.plist files, in readiness for the next release.](https://discourse.openehr.org/t/ref-impl-eiffel-601-awb-74-increment-the-version-number-to-1-4-2-in-adl-workbench-rc-adlworkbenchinstall-nsi-and-both-info-plist-files-in-readiness-for-the-next-release/12905)
> Revision: 601
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [600] Update project page](https://discourse.openehr.org/t/ref-impl-eiffel-600-update-project-page/12904)
> Revision: 600
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [599] Tag of Sabicas specialisation release of Archetype Workbench version 1.4.1](https://discourse.openehr.org/t/ref-impl-eiffel-599-tag-of-sabicas-specialisation-release-of-archetype-workbench-version-1-4-1/12903)
> Revision: 599
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [598] Final adjustments to release naming.](https://discourse.openehr.org/t/ref-impl-eiffel-598-final-adjustments-to-release-naming/12902)
> Revision: 598
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [597] Add a link to Ocean wiki to provide better download instructions](https://discourse.openehr.org/t/ref-impl-eiffel-597-add-a-link-to-ocean-wiki-to-provide-better-download-instructions/12901)
> Revision: 597
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [596] Add some simple navigation aids to AWB help pages](https://discourse.openehr.org/t/ref-impl-eiffel-596-add-some-simple-navigation-aids-to-awb-help-pages/12900)
> Revision: 596
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [595] AWB-86: A few last-minute fixes to the documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-595-awb-86-a-few-last-minute-fixes-to-the-documentation/12899)
> Revision: 595
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [594] AWB-86: Merge BRANCHES/specialisation revisions 586-593 (updated help page) into the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-594-awb-86-merge-branches-specialisation-revisions-586-593-updated-help-page-into-the-trunk/12895)
> Revision: 594
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [593] Adjustments to documentation.](https://discourse.openehr.org/t/ref-impl-eiffel-593-adjustments-to-documentation/12894)
> Revision: 593
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [592] AWB-109: On Mac OS X, the Path Analysis sub-tab always showed the AOM Type column, even when the AOM Type check box was off.](https://discourse.openehr.org/t/ref-impl-eiffel-592-awb-109-on-mac-os-x-the-path-analysis-sub-tab-always-showed-the-aom-type-column-even-when-the-aom-type-check-box-was-off/12893)
> Revision: 592
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [591] AWB-108: The Accreditation field was an expandable EV_TEXT_FIELD, and on Windows it expanded but on Mac OS X it did not.](https://discourse.openehr.org/t/ref-impl-eiffel-591-awb-108-the-accreditation-field-was-an-expandable-ev-text-field-and-on-windows-it-expanded-but-on-mac-os-x-it-did-not/12892)
> Revision: 591
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [590] AWB-74: Merge TRUNK revisions 576-588 back into BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-590-awb-74-merge-trunk-revisions-576-588-back-into-branches-specialisation/12891)
> Revision: 590
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [589] AWB-86: Fix some typos in the documentation, and complete a few ommissions in the Downloads section and the description of the Repository menu.](https://discourse.openehr.org/t/ref-impl-eiffel-589-awb-86-fix-some-typos-in-the-documentation-and-complete-a-few-ommissions-in-the-downloads-section-and-the-description-of-the-repository-menu/12889)
> Revision: 589
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [588] AWB-74: Update the developer page for EiffelStudio 6.1 and SCons 0.98.](https://discourse.openehr.org/t/ref-impl-eiffel-588-awb-74-update-the-developer-page-for-eiffelstudio-6-1-and-scons-0-98/16043)
> Revision: 588
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [587] FIrst draft of reworked help pages and images for April 2008 release of AWB](https://discourse.openehr.org/t/ref-impl-eiffel-587-first-draft-of-reworked-help-pages-and-images-for-april-2008-release-of-awb/12888)
> Revision: 587
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR site outage - Wed 2nd April 19:00 - Thu 3rd April 08:00 BST](https://discourse.openehr.org/t/openehr-site-outage-wed-2nd-april-19-00-thu-3rd-april-08-00-bst/12887)
> Please note the following warning of network outage\.
The external connection used by the openEHR servers will be affected
from Wed 2nd April 19:00BST \- Thu 3rd April 08:00BST\.
The connection might not be out for the entire time, but should be
considered "at risk" for that period\.
This will affect the openEHR web site, wiki, issues server, email lists,
etc\.
I apologise for the short notice\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [586] AWB-74: Update the project page for the 1.4.1.585 release.](https://discourse.openehr.org/t/ref-impl-eiffel-586-awb-74-update-the-project-page-for-the-1-4-1-585-release/12886)
> Revision: 586
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [585] AWB-74: Remove the words "Release Candidate" from the version string in OPENEHR_VERSION and commit it so that the last_changed attribute will be updated by Subversion.](https://discourse.openehr.org/t/ref-impl-eiffel-585-awb-74-remove-the-words-release-candidate-from-the-version-string-in-openehr-version-and-commit-it-so-that-the-last-changed-attribute-will-be-updated-by-subversion/12883)
> Revision: 585
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[341] minor updates in the openehr tutorial files](https://discourse.openehr.org/t/341-minor-updates-in-the-openehr-tutorial-files/12882)
> Revision: 341
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[340] updated ehr-bank demo classes](https://discourse.openehr.org/t/340-updated-ehr-bank-demo-classes/12881)
> Revision: 340
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [584] AWB-104: Fix a bug in the Differential View tab.](https://discourse.openehr.org/t/ref-impl-eiffel-584-awb-104-fix-a-bug-in-the-differential-view-tab/12880)
> Revision: 584
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[339] minor change in top pom.xml](https://discourse.openehr.org/t/339-minor-change-in-top-pom-xml/13514)
> Revision: 339
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [583] AWB-59: Enable more Eiffel compiler warnings and fix all of the remaining uses of the obsolete "creation" keyword.](https://discourse.openehr.org/t/ref-impl-eiffel-583-awb-59-enable-more-eiffel-compiler-warnings-and-fix-all-of-the-remaining-uses-of-the-obsolete-creation-keyword/12879)
> Revision: 583
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [582] AWB-100: On opening a specialised archetype ad-hoc, set its specialisation parent if it exists in the repository.](https://discourse.openehr.org/t/ref-impl-eiffel-582-awb-100-on-opening-a-specialised-archetype-ad-hoc-set-its-specialisation-parent-if-it-exists-in-the-repository/12878)
> Revision: 582
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [581] AWB-102: Don't set the position of a splitter if it is outside the allowed bounds.](https://discourse.openehr.org/t/ref-impl-eiffel-581-awb-102-dont-set-the-position-of-a-splitter-if-it-is-outside-the-allowed-bounds/12877)
> Revision: 581
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [580] AWB-99: Fix a violation of the language_valid precondition in ARCETYPE_ONTOLOGY.term_definition.](https://discourse.openehr.org/t/ref-impl-eiffel-580-awb-99-fix-a-violation-of-the-language-valid-precondition-in-arcetype-ontology-term-definition/13513)
> Revision: 580
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Can you open a template (.oet) from an Href?](https://discourse.openehr.org/t/can-you-open-a-template-oet-from-an-href/14738)
> Dear All,
I have build a complete publishing system for OpenEHR\.
It ends up in part with a bunch of href's in an HTML page e\.g\. if it
finds errors then it creates a link to the file in the relevant working
copy\.
2 points:
A\) Wrt \.adl I can set the filetype etc in windows & when I clik on a
link to an adl, the archetype editor opens with that file\.
Hurray\.
However\.\.\.\.\.\.If I click on a \.oet even if I set the template designer to
be the default file handler I just...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [579] AWB-74: Add three icon files that I missed when merging revisions 351-575 from BRANCHES/specialisation into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-579-awb-74-add-three-icon-files-that-i-missed-when-merging-revisions-351-575-from-branches-specialisation-into-trunk/12876)
> Revision: 579
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [578] AWB-13: Fix a bug introduced by revision 276: the current directory was not being set whenever the user chooses a file in the Open dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-578-awb-13-fix-a-bug-introduced-by-revision-276-the-current-directory-was-not-being-set-whenever-the-user-chooses-a-file-in-the-open-dialog/12875)
> Revision: 578
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [577] AWB-82: Add a tooltip to each node in the Tests tree showing the item's full path.](https://discourse.openehr.org/t/ref-impl-eiffel-577-awb-82-add-a-tooltip-to-each-node-in-the-tests-tree-showing-the-items-full-path/12874)
> Revision: 577
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Security & Privacy with openEHR](https://discourse.openehr.org/t/security-privacy-with-openehr/14737)
> Hi All,
I'm just beginning a research project on
security/privacy/confidentiality in EHRs\. I will greatly appreciate any
pointers to any material on this topic, especially with respect to
openEHR\.
I've just noted that in the US, HIPAA is driving
security/privacy/confidentiality implementations in existing EHR systems
and it seems its is turning out to be a policy/framework\-level security
standard for EHRs in the US that does not prescribe implementation
issues\. I am not sure...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[338] minor doc changes in ehr-bank](https://discourse.openehr.org/t/338-minor-doc-changes-in-ehr-bank/12873)
> Revision: 338
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[337] Added missing properties to openehr_terminology_en.xml and also fixed a few minor spelling mistakes or cut-off properties](https://discourse.openehr.org/t/337-added-missing-properties-to-openehr-terminology-en-xml-and-also-fixed-a-few-minor-spelling-mistakes-or-cut-off-properties/12871)
> Revision: 337
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[336] improved checking of language and encoding in the constructor of Entry, tested with mini-termserv now included in test scope of rm-domain](https://discourse.openehr.org/t/336-improved-checking-of-language-and-encoding-in-the-constructor-of-entry-tested-with-mini-termserv-now-included-in-test-scope-of-rm-domain/12870)
> Revision: 336
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[335] added a few common character-sets to mini-termserv](https://discourse.openehr.org/t/335-added-a-few-common-character-sets-to-mini-termserv/12869)
> Revision: 335
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[334] fixed a bug in the logic for loading terminology xml in class XMLTerminologySource](https://discourse.openehr.org/t/334-fixed-a-bug-in-the-logic-for-loading-terminology-xml-in-class-xmlterminologysource/12868)
> Revision: 334
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[333] improved the javadoc of the constructor of EventContext and added a convenient constructor](https://discourse.openehr.org/t/333-improved-the-javadoc-of-the-constructor-of-eventcontext-and-added-a-convenient-constructor/12867)
> Revision: 333
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[332] fixed the javadoc for PartySelf constructor and added a default constructor](https://discourse.openehr.org/t/332-fixed-the-javadoc-for-partyself-constructor-and-added-a-default-constructor/12866)
> Revision: 332
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[331] Ordinal now implements Comparable, so that ordinals can be retrieved easily in their intended order, e.g.](https://discourse.openehr.org/t/331-ordinal-now-implements-comparable-so-that-ordinals-can-be-retrieved-easily-in-their-intended-order-e-g/12865)
> Revision: 331
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[330] added a convenient constructor to History](https://discourse.openehr.org/t/330-added-a-convenient-constructor-to-history/16042)
> Revision: 330
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [576] AWB-74: Merge revisions 351-575 from BRANCHES/specialisation into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-576-awb-74-merge-revisions-351-575-from-branches-specialisation-into-trunk/12864)
> Revision: 576
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[329] added a convenient constructor to PointEvent](https://discourse.openehr.org/t/329-added-a-convenient-constructor-to-pointevent/16041)
> Revision: 329
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [575] AWB-59: Fix all compiler warnings (mainly misnamed class files), with the exception of a couple of unused local variable warnings in DT_TYPES that have to remain for now in order to ensure that other types are compiled in.](https://discourse.openehr.org/t/ref-impl-eiffel-575-awb-59-fix-all-compiler-warnings-mainly-misnamed-class-files-with-the-exception-of-a-couple-of-unused-local-variable-warnings-in-dt-types-that-have-to-remain-for-now-in-order-to-ensure-that-other-types-are-compiled-in/16040)
> Revision: 575
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Google summer of code deadline tomorrow!](https://discourse.openehr.org/t/google-summer-of-code-deadline-tomorrow/16669)
> Hi\!
We have nearly missed the chance to apply for mentoring Google Summer
of code \(GSoC\) projects\.\.\.
> We'll begin accepting applications from open source mentoring organizations on Monday,
> March 3, 2008; we'll stop accepting organization applications on Wednesday, March 12th
That is tomorrow at 19\.00 UTC
GSoC main page: http://code.google.com/soc/2008/
Mentor hints including advice for ideas list:
http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors
An...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [574] Apply an optimisation to the last change in the SCons Eiffel builder, suggested by one of the SCons gurus.](https://discourse.openehr.org/t/ref-impl-eiffel-574-apply-an-optimisation-to-the-last-change-in-the-scons-eiffel-builder-suggested-by-one-of-the-scons-gurus/12863)
> Revision: 574
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [573] Update slots and used-by counts in statistics when Test page tests are run.](https://discourse.openehr.org/t/ref-impl-eiffel-573-update-slots-and-used-by-counts-in-statistics-when-test-page-tests-are-run/12862)
> Revision: 573
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [572] Add check to ensure archetype id in filename and at top of file match, including in case, since case-sensitive archetype ids are being used in the indexes in ARCH_DIRECTORY.](https://discourse.openehr.org/t/ref-impl-eiffel-572-add-check-to-ensure-archetype-id-in-filename-and-at-top-of-file-match-including-in-case-since-case-sensitive-archetype-ids-are-being-used-in-the-indexes-in-arch-directory/12861)
> Revision: 572
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [571] Fix a crash when scanning non-recursive clusters in the SCons Eiffel builder.](https://discourse.openehr.org/t/ref-impl-eiffel-571-fix-a-crash-when-scanning-non-recursive-clusters-in-the-scons-eiffel-builder/13489)
> Revision: 571
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [570] AWB-71: Colourise the HTML we can show what is inherited and redefined, using the ARCHETYPE_CONSTRAINT.specialisation_status.](https://discourse.openehr.org/t/ref-impl-eiffel-570-awb-71-colourise-the-html-we-can-show-what-is-inherited-and-redefined-using-the-archetype-constraint-specialisation-status/13488)
> Revision: 570
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [569] Fix a typo in a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-569-fix-a-typo-in-a-comment/12860)
> Revision: 569
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [568] Fix a typo in a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-568-fix-a-typo-in-a-comment/12859)
> Revision: 568
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [567] AWB-71: Fix saving as HTML, which was always saving with a .adl or .adls extension instead of .html, due to change in revision 539 to ARCH_REP_ARCHETYPE.](https://discourse.openehr.org/t/ref-impl-eiffel-567-awb-71-fix-saving-as-html-which-was-always-saving-with-a-adl-or-adls-extension-instead-of-html-due-to-change-in-revision-539-to-arch-rep-archetype/12858)
> Revision: 567
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [566] AWB-14 - Change the test view to properly accommodate differential form archetypes and to ignore flat form archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-566-awb-14-change-the-test-view-to-properly-accommodate-differential-form-archetypes-and-to-ignore-flat-form-archetypes/12857)
> Revision: 566
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [565] Correct missing call to update_specialised_codes from constraint code part of ARCHETYPE_ONTOLOGY.synchronise_from_tree](https://discourse.openehr.org/t/ref-impl-eiffel-565-correct-missing-call-to-update-specialised-codes-from-constraint-code-part-of-archetype-ontology-synchronise-from-tree/12856)
> Revision: 565
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [564] Correct problem where duplicate child nodes in dADL were not detected.](https://discourse.openehr.org/t/ref-impl-eiffel-564-correct-problem-where-duplicate-child-nodes-in-dadl-were-not-detected/12855)
> Revision: 564
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [563] AWB-55: The test archetypes added by revision 2988 of the knowledge repository revealed a few more bugs in the validation of languages.](https://discourse.openehr.org/t/ref-impl-eiffel-563-awb-55-the-test-archetypes-added-by-revision-2988-of-the-knowledge-repository-revealed-a-few-more-bugs-in-the-validation-of-languages/12854)
> Revision: 563
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [562] AWB-15: Fix a bug in ARCHETYPE_ONTOLOGY.update_highest_constraint_code_index, which was comparing with highest_term_code_index instead of highest_constraint_code_index.](https://discourse.openehr.org/t/ref-impl-eiffel-562-awb-15-fix-a-bug-in-archetype-ontology-update-highest-constraint-code-index-which-was-comparing-with-highest-term-code-index-instead-of-highest-constraint-code-index/12853)
> Revision: 562
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [561] AWB-55: Fix a typo in a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-561-awb-55-fix-a-typo-in-a-comment/13477)
> Revision: 561
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [560] AWB-55 Exception in archetype with missing terms.](https://discourse.openehr.org/t/ref-impl-eiffel-560-awb-55-exception-in-archetype-with-missing-terms/13476)
> Revision: 560
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [559] AWB-93: Prevent automatic switching between the Term Definitions and Constraint Definitions tabs.](https://discourse.openehr.org/t/ref-impl-eiffel-559-awb-93-prevent-automatic-switching-between-the-term-definitions-and-constraint-definitions-tabs/12852)
> Revision: 559
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Use of Accuracy in mathematical operations on DV_AMOUNT and DV_ABSOLUTE_QUANTITY](https://discourse.openehr.org/t/use-of-accuracy-in-mathematical-operations-on-dv-amount-and-dv-absolute-quantity/14736)
> Gerke Geurts wrote:
> Hello all,
>
> The DV\_AMOUNT and DV\_ABSOLUTE\_QUANTITY classes contain \(optional\)
> accuracy attributes\. However the specifications for the outcome of
> mathematical operations \(especially the add/subtract operators\) seem
> to be silent on the accuracy of the results of these operations\. Is
> this intentional or an omission in the specs?
>
that is indeed an omission\. I think that both addition and subtraction
of two quantities with accuracies of \+/\- x and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [558] AWB-95: Fix the width and alignment of the labels on the Statistics tab.](https://discourse.openehr.org/t/ref-impl-eiffel-558-awb-95-fix-the-width-and-alignment-of-the-labels-on-the-statistics-tab/12851)
> Revision: 558
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [557] Minor simplification and optimisation.](https://discourse.openehr.org/t/ref-impl-eiffel-557-minor-simplification-and-optimisation/12850)
> Revision: 557
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [556] Set the Subversion eol style to native for the SConstruct and Eiffel.py.](https://discourse.openehr.org/t/ref-impl-eiffel-556-set-the-subversion-eol-style-to-native-for-the-sconstruct-and-eiffel-py/12849)
> Revision: 556
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [555] AWB-15: Fix a Void target call in ARCHETYPE_VALIDATOR.build_slot_id_index, due to an attempt to access the slot_id_index before it has been instantiated.](https://discourse.openehr.org/t/ref-impl-eiffel-555-awb-15-fix-a-void-target-call-in-archetype-validator-build-slot-id-index-due-to-an-attempt-to-access-the-slot-id-index-before-it-has-been-instantiated/12848)
> Revision: 555
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[328] added three new methods to Cardinality class](https://discourse.openehr.org/t/328-added-three-new-methods-to-cardinality-class/12845)
> Revision: 328
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[327] fixed the bugs that generate invalid ISO date string value in three DvDate integer constructors](https://discourse.openehr.org/t/327-fixed-the-bugs-that-generate-invalid-iso-date-string-value-in-three-dvdate-integer-constructors/12844)
> Revision: 327
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [554] AWB-25: Add a Ctrl+S shortcut for File | Save As...](https://discourse.openehr.org/t/ref-impl-eiffel-554-awb-25-add-a-ctrl-s-shortcut-for-file-save-as/12843)
> Revision: 554
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [553] AWB-15: Remove a FIXME comment added by revision 533 to C_ATTRIBUTE.is_valid.](https://discourse.openehr.org/t/ref-impl-eiffel-553-awb-15-remove-a-fixme-comment-added-by-revision-533-to-c-attribute-is-valid/12842)
> Revision: 553
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [552] AWB-74: Add the words "Release Candidate" to the version string.](https://discourse.openehr.org/t/ref-impl-eiffel-552-awb-74-add-the-words-release-candidate-to-the-version-string/13463)
> Revision: 552
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [551] AWB-91: Ensure that the columns in the Path Analysis list do not shrink to a ridiculously small width when the list is empty.](https://discourse.openehr.org/t/ref-impl-eiffel-551-awb-91-ensure-that-the-columns-in-the-path-analysis-list-do-not-shrink-to-a-ridiculously-small-width-when-the-list-is-empty/13462)
> Revision: 551
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [550] AWB-59: Change a few cases of the obsolete "creation" keyword to "create".](https://discourse.openehr.org/t/ref-impl-eiffel-550-awb-59-change-a-few-cases-of-the-obsolete-creation-keyword-to-create/12841)
> Revision: 550
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [549] AWB-15: Add FIXME comments to some checks that I believe should be deleted from C_ATTRIBUTE.is_valid.](https://discourse.openehr.org/t/ref-impl-eiffel-549-awb-15-add-fixme-comments-to-some-checks-that-i-believe-should-be-deleted-from-c-attribute-is-valid/12840)
> Revision: 549
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [548] AWB-74: Update news.txt to describe recent changes.](https://discourse.openehr.org/t/ref-impl-eiffel-548-awb-74-update-news-txt-to-describe-recent-changes/12839)
> Revision: 548
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [547] AWB-15: Fix a void target call when running the Diff on the Tests page.](https://discourse.openehr.org/t/ref-impl-eiffel-547-awb-15-fix-a-void-target-call-when-running-the-diff-on-the-tests-page/12837)
> Revision: 547
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [546] Replace www.OceanInformatics.biz with www.OceanInformatics.com.](https://discourse.openehr.org/t/ref-impl-eiffel-546-replace-www-oceaninformatics-biz-with-www-oceaninformatics-com/12836)
> Revision: 546
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [545] Fix a typo in a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-545-fix-a-typo-in-a-comment/13450)
> Revision: 545
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [543] AWB-63: After the user switches line numbers on or off in the Options dialog, if the Source was currently visible then the effect was not immediate: the user had to do something to cause repopulation of the rich text box to see the](https://discourse.openehr.org/t/ref-impl-eiffel-543-awb-63-after-the-user-switches-line-numbers-on-or-off-in-the-options-dialog-if-the-source-was-currently-visible-then-the-effect-was-not-immediate-the-user-had-to-do-something-to-cause-repopulation-of-the-rich-text-box-to-see-the/12833)
> Revision: 543
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [542] AWB-14: When the user clicks on an archetype in the repository explorer tree that has previously been parsed but has an error, then a rebuild is automatically triggered; this in turn causes the Errors grid to jump to it.](https://discourse.openehr.org/t/ref-impl-eiffel-542-awb-14-when-the-user-clicks-on-an-archetype-in-the-repository-explorer-tree-that-has-previously-been-parsed-but-has-an-error-then-a-rebuild-is-automatically-triggered-this-in-turn-causes-the-errors-grid-to-jump-to-it/12832)
> Revision: 542
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [540] AWB-14: Revision 524 made the Errors grid visible automatically but, as Thomas noted in an email to me, the user can't really read anything (it's too fast) and also can't see when it's finished, since it says that on the Status tab](https://discourse.openehr.org/t/ref-impl-eiffel-540-awb-14-revision-524-made-the-errors-grid-visible-automatically-but-as-thomas-noted-in-an-email-to-me-the-user-cant-really-read-anything-its-too-fast-and-also-cant-see-when-its-finished-since-it-says-that-on-the-status-tab/12830)
> Revision: 540
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [539] AWB-14: Previously, the user could open only .adl files ad-hoc.](https://discourse.openehr.org/t/ref-impl-eiffel-539-awb-14-previously-the-user-could-open-only-adl-files-ad-hoc/12829)
> Revision: 539
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [538] AWB-14: Fix a bug in the Errors grid, introduced by revision 524.](https://discourse.openehr.org/t/ref-impl-eiffel-538-awb-14-fix-a-bug-in-the-errors-grid-introduced-by-revision-524/12828)
> Revision: 538
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [537] AWB-14: Replace the "Inheritance" and "Flat View" radio buttons with two tab pages, "Differential View" and "Flat View", each containing similar widgets: the Node Map, the Path Analysis and the Source.](https://discourse.openehr.org/t/ref-impl-eiffel-537-awb-14-replace-the-inheritance-and-flat-view-radio-buttons-with-two-tab-pages-differential-view-and-flat-view-each-containing-similar-widgets-the-node-map-the-path-analysis-and-the-source/12827)
> Revision: 537
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [536] AWB-15: Fix a bug introduced by revision 527, where a specialised archetype's parent id was set to its own id.](https://discourse.openehr.org/t/ref-impl-eiffel-536-awb-15-fix-a-bug-introduced-by-revision-527-where-a-specialised-archetypes-parent-id-was-set-to-its-own-id/12825)
> Revision: 536
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [535] AWB-14: After compiling, don't redisplay the source of the currently selected archetype unless it happens to be the one that was just compiled.](https://discourse.openehr.org/t/ref-impl-eiffel-535-awb-14-after-compiling-dont-redisplay-the-source-of-the-currently-selected-archetype-unless-it-happens-to-be-the-one-that-was-just-compiled/12824)
> Revision: 535
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [534] AWB-14: Add a new tab page for viewing the archetype's flat text: so the "Source" tab now has a "Flat Text" tab to its right.](https://discourse.openehr.org/t/ref-impl-eiffel-534-awb-14-add-a-new-tab-page-for-viewing-the-archetypes-flat-text-so-the-source-tab-now-has-a-flat-text-tab-to-its-right/12821)
> Revision: 534
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [533] AWB-15: Make explicit the implicit assumption that ARCHETYPE_CONSTRAINT.representation is attached.](https://discourse.openehr.org/t/ref-impl-eiffel-533-awb-15-make-explicit-the-implicit-assumption-that-archetype-constraint-representation-is-attached/12818)
> Revision: 533
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [532] AWB-15: Fix a bug that prevented the archetype from being displayed when the project is frozen in EiffelStudio 6.1.](https://discourse.openehr.org/t/ref-impl-eiffel-532-awb-15-fix-a-bug-that-prevented-the-archetype-from-being-displayed-when-the-project-is-frozen-in-eiffelstudio-6-1/12817)
> Revision: 532
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[326] fixed typo in the constructor of Instruction class](https://discourse.openehr.org/t/326-fixed-typo-in-the-constructor-of-instruction-class/12816)
> Revision: 326
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [typo in Instruction](https://discourse.openehr.org/t/typo-in-instruction/13421)
> @Attribute\(name = "wfDefinition"\) DvParsable wfDeinition,
This is a tricky one\!
I am working on the files, that is why I find them
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [531] AWB-15: Similar to revisions 525 and 527, ARCHETYPE.invariants could never be empty if attached, so there was no point in ARCHETYPE_VALIDATOR.validate_basics checking this.](https://discourse.openehr.org/t/ref-impl-eiffel-531-awb-15-similar-to-revisions-525-and-527-archetype-invariants-could-never-be-empty-if-attached-so-there-was-no-point-in-archetype-validator-validate-basics-checking-this/12815)
> Revision: 531
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[325] Fixed typo in Pathable.java (getParnent -> getParent)](https://discourse.openehr.org/t/325-fixed-typo-in-pathable-java-getparnent-getparent/12809)
> Revision: 325
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [typo in Pathable](https://discourse.openehr.org/t/typo-in-pathable/12808)
> public Pathable getParnent\(\) \{
return this\.parent;
\}
I would repair it myself, just like the errors from yesterday, but I
guess I have no access, to the code, which I don't need also \(this is
not a hidden request for code\-change\-access\)
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Understanding XML archetypes..](https://discourse.openehr.org/t/understanding-xml-archetypes/14733)
> I have been looking at the OpenEHR Information Model ( ehr_im.pdf ) to get a better understanding of the underlying classes used within the OpenEHR.
Whilst I am beginning to understand the main classes used within the archetypes, I am still confused as how they make it to the XML version of the archetypes.
For example if you consider the "Composition" class, it has a number of attributes 'language', 'territory' and 'category' all of which are looking to be mandatory.
Now if I look at one...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [530] AWB-15: When double-clicking the Errors grid, expand the error message.](https://discourse.openehr.org/t/ref-impl-eiffel-530-awb-15-when-double-clicking-the-errors-grid-expand-the-error-message/12807)
> Revision: 530
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [529] AWB-83: Revision 528 failed to disable the Back and Forward buttons and menu options when populating the repository tree.](https://discourse.openehr.org/t/ref-impl-eiffel-529-awb-83-revision-528-failed-to-disable-the-back-and-forward-buttons-and-menu-options-when-populating-the-repository-tree/12806)
> Revision: 529
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [528] AWB-83: Fix a void target call in MAIN_WINDOW.populate_archetype_id.](https://discourse.openehr.org/t/ref-impl-eiffel-528-awb-83-fix-a-void-target-call-in-main-window-populate-archetype-id/16039)
> Revision: 528
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [527] AWB-15: In ARCHETYPE, similar to revision 525's change for ontology, archetype_id and defintion could never be Void, so there was no point in ARCHETYPE_VALIDATOR.validate_basics checking whether they were Void.](https://discourse.openehr.org/t/ref-impl-eiffel-527-awb-15-in-archetype-similar-to-revision-525s-change-for-ontology-archetype-id-and-defintion-could-never-be-void-so-there-was-no-point-in-archetype-validator-validate-basics-checking-whether-they-were-void/12804)
> Revision: 527
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [526] AWB-15: Fix precondition failures in DADL_ENGINE.set_source and CADL_ENGINE.set_source when the archetype definition or ontology sections are completely empty.](https://discourse.openehr.org/t/ref-impl-eiffel-526-awb-15-fix-precondition-failures-in-dadl-engine-set-source-and-cadl-engine-set-source-when-the-archetype-definition-or-ontology-sections-are-completely-empty/12803)
> Revision: 526
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Possible bug in DvDate?](https://discourse.openehr.org/t/possible-bug-in-dvdate/16666)
> Hi, Maybe it is a bug, maybe it is my misunderstanding, please help me out\.
Thanks in advance
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [525] AWB-15: Fix ARCHETYPE_VALIDATOR.validate_found_codes, which was not checking that at-codes were at the correct specialisation level.](https://discourse.openehr.org/t/ref-impl-eiffel-525-awb-15-fix-archetype-validator-validate-found-codes-which-was-not-checking-that-at-codes-were-at-the-correct-specialisation-level/12802)
> Revision: 525
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [524] AWB-14: When adding a message to the Errors grid:](https://discourse.openehr.org/t/ref-impl-eiffel-524-awb-14-when-adding-a-message-to-the-errors-grid/12801)
> Revision: 524
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [523] Reverting the temporary hack committed a few minutes ago to try to fix CruiseControl, which has now hopefully removed the conflicted files so that we should now get a successful build with this commit.](https://discourse.openehr.org/t/ref-impl-eiffel-523-reverting-the-temporary-hack-committed-a-few-minutes-ago-to-try-to-fix-cruisecontrol-which-has-now-hopefully-removed-the-conflicted-files-so-that-we-should-now-get-a-successful-build-with-this-commit/12800)
> Revision: 523
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [522] AWB-15: There is a precondition failure in ARCHETYPE_TERM_CODE_TOOLS.specialisation_depth_from_code if the code is invalid.](https://discourse.openehr.org/t/ref-impl-eiffel-522-awb-15-there-is-a-precondition-failure-in-archetype-term-code-tools-specialisation-depth-from-code-if-the-code-is-invalid/12799)
> Revision: 522
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [521] Temporary hack to try to fix CruiseControl, which should be overwriting local changes but instead is getting conflicts.](https://discourse.openehr.org/t/ref-impl-eiffel-521-temporary-hack-to-try-to-fix-cruisecontrol-which-should-be-overwriting-local-changes-but-instead-is-getting-conflicts/12798)
> Revision: 521
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [520] AWB-37: Fix the Left arrow key in the Errors grid, which failed to close the node in the second column.](https://discourse.openehr.org/t/ref-impl-eiffel-520-awb-37-fix-the-left-arrow-key-in-the-errors-grid-which-failed-to-close-the-node-in-the-second-column/12797)
> Revision: 520
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [519] AWB-37: Fix various exceptions that occurred on the Errors grid when it was empty, when scrolling the mouse wheel or using various keys to navigate.](https://discourse.openehr.org/t/ref-impl-eiffel-519-awb-37-fix-various-exceptions-that-occurred-on-the-errors-grid-when-it-was-empty-when-scrolling-the-mouse-wheel-or-using-various-keys-to-navigate/16038)
> Revision: 519
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [518] AWB-14: Fix a precondition failure in ARCHETYPE_ID.make_from_string, caused by ADL_ENGINE passing through an invalid concept code.](https://discourse.openehr.org/t/ref-impl-eiffel-518-awb-14-fix-a-precondition-failure-in-archetype-id-make-from-string-caused-by-adl-engine-passing-through-an-invalid-concept-code/13409)
> Revision: 518
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [517] AWB-15: Fix a void target call when validating a specialised archetype that is structurally sound, but whose parent is missing.](https://discourse.openehr.org/t/ref-impl-eiffel-517-awb-15-fix-a-void-target-call-when-validating-a-specialised-archetype-that-is-structurally-sound-but-whose-parent-is-missing/12796)
> Revision: 517
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [516] AWB-14: When we tightened up ARCHETYPE_ID.valid_id in revision 428, we forgot to apply the same changes to the lexer.](https://discourse.openehr.org/t/ref-impl-eiffel-516-awb-14-when-we-tightened-up-archetype-id-valid-id-in-revision-428-we-forgot-to-apply-the-same-changes-to-the-lexer/12795)
> Revision: 516
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [515] AWB-15: At Thomas's request, all .adls files in the repository are now deleted automatically on start-up for the first time, to ensure the effects of previous bugs are erased.](https://discourse.openehr.org/t/ref-impl-eiffel-515-awb-15-at-thomass-request-all-adls-files-in-the-repository-are-now-deleted-automatically-on-start-up-for-the-first-time-to-ensure-the-effects-of-previous-bugs-are-erased/12794)
> Revision: 515
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [514] AWB-85: Put the reference repository path in the main window's title bar, followed by a dash, followed by the old title.](https://discourse.openehr.org/t/ref-impl-eiffel-514-awb-85-put-the-reference-repository-path-in-the-main-windows-title-bar-followed-by-a-dash-followed-by-the-old-title/12793)
> Revision: 514
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [513] AWB-83: Update news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-513-awb-83-update-news-txt/12792)
> Revision: 513
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [512] AWB-83: Add a History menu, containing Back and Forward options for getting back to the previous archetype the user was on.](https://discourse.openehr.org/t/ref-impl-eiffel-512-awb-83-add-a-history-menu-containing-back-and-forward-options-for-getting-back-to-the-previous-archetype-the-user-was-on/12791)
> Revision: 512
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [511] Fix ARCH_REP_ITEM.relative_path: if the full path was, say, "C:\openEHR-EHR-EVALUATION.xx.v1.adl", it was chopping off the first character of the base name, resulting in "penEHR-EHR-EVALUATION.xx.v1.adl".](https://discourse.openehr.org/t/ref-impl-eiffel-511-fix-arch-rep-item-relative-path-if-the-full-path-was-say-c-openehr-ehr-evaluation-xx-v1-adl-it-was-chopping-off-the-first-character-of-the-base-name-resulting-in-penehr-ehr-evaluation-xx-v1-adl/12790)
> Revision: 511
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [510] AWB-82: Add a tooltip to each node in the repository tree showing the item's full path.](https://discourse.openehr.org/t/ref-impl-eiffel-510-awb-82-add-a-tooltip-to-each-node-in-the-repository-tree-showing-the-items-full-path/12788)
> Revision: 510
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [509] Revert an accidental commit.](https://discourse.openehr.org/t/ref-impl-eiffel-509-revert-an-accidental-commit/16037)
> Revision: 509
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [508] AWB-46: After displaying two archetypes, successively, in a non-English language, the language combo box showed "en" despite the fact that the archetype was being shown the other language.](https://discourse.openehr.org/t/ref-impl-eiffel-508-awb-46-after-displaying-two-archetypes-successively-in-a-non-english-language-the-language-combo-box-showed-en-despite-the-fact-that-the-archetype-was-being-shown-the-other-language/16036)
> Revision: 508
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [507] AWB-72: Fix a few problems with the Mac OS X installer.](https://discourse.openehr.org/t/ref-impl-eiffel-507-awb-72-fix-a-few-problems-with-the-mac-os-x-installer/12787)
> Revision: 507
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [506] Correct flat->differential conversion that was missing translations.](https://discourse.openehr.org/t/ref-impl-eiffel-506-correct-flat-differential-conversion-that-was-missing-translations/12786)
> Revision: 506
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [504] AWB-38: If the user tried to open a file that does not exist, then a node was added to the repository tree, with a parse error due to the file contents being empty.](https://discourse.openehr.org/t/ref-impl-eiffel-504-awb-38-if-the-user-tried-to-open-a-file-that-does-not-exist-then-a-node-was-added-to-the-repository-tree-with-a-parse-error-due-to-the-file-contents-being-empty/12784)
> Revision: 504
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [503] AWB-33: On the Statistics tab, the text was not being selected on setting focus to three of the fields.](https://discourse.openehr.org/t/ref-impl-eiffel-503-awb-33-on-the-statistics-tab-the-text-was-not-being-selected-on-setting-focus-to-three-of-the-fields/12783)
> Revision: 503
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [502] AWB-14: Fix a couple of problems with the File | Save As menu:](https://discourse.openehr.org/t/ref-impl-eiffel-502-awb-14-fix-a-couple-of-problems-with-the-file-save-as-menu/12782)
> Revision: 502
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [501] AWB-14: Fix a precondition violation in the Node Map, when the user selects an external term code.](https://discourse.openehr.org/t/ref-impl-eiffel-501-awb-14-fix-a-precondition-violation-in-the-node-map-when-the-user-selects-an-external-term-code/12781)
> Revision: 501
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [499] AWB-14: Revert the experimental changes from the last revision (498), since it doesn't make sense to have the errors and status in the same tab block that is otherwise concerned with archetype analysis.](https://discourse.openehr.org/t/ref-impl-eiffel-499-awb-14-revert-the-experimental-changes-from-the-last-revision-498-since-it-doesnt-make-sense-to-have-the-errors-and-status-in-the-same-tab-block-that-is-otherwise-concerned-with-archetype-analysis/12779)
> Revision: 499
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Formal methods for Evaluation ofInteroperability &Maintainability?](https://discourse.openehr.org/t/formal-methods-for-evaluation-ofinteroperability-maintainability/14731)
> Tom
Many thanks for this \-\- are there examples of TDS schemas or instances available?
Also are there any example document instances available \-\- particularly for the draft Extract schema, but any instances or instance fragments would be useful\.
All the best
Charlie
Charlie McCay, charlie@RamseySystems\.co\.uk
Ramsey Systems Ltd, 23D Dogpole, Shrewsbury, Shropshire SY1 1ES
tel \+44 1743 232278 / \+44 7808 570172 skype: charliemccay linkedin:charliemccay
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [should this simplification be allowed?](https://discourse.openehr.org/t/should-this-simplification-be-allowed/14735)
> Hi,
I'm testing my implementation about the openEHR specification, with
some archetypes examples, and I'm finding things like this:
CLUSTER\[at0018\] occurrences matches \{0 \.\.\*\} matches \{ name matches \{
CODED\_TEXT matches \{
code matches \{\[ac0002\]\} \}
\}
I'd like to follow the specification as much as possible, and I think
that the correct way of expressing it, should have...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [498] AWB-14: Experimental cosmetic change: move the Status box and the Errors grid to a new main tab page, called "Status".](https://discourse.openehr.org/t/ref-impl-eiffel-498-awb-14-experimental-cosmetic-change-move-the-status-box-and-the-errors-grid-to-a-new-main-tab-page-called-status/12776)
> Revision: 498
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [497] * When the user sets a different repository, clear the Errors grid, the Slot Map and the Used By tree.](https://discourse.openehr.org/t/ref-impl-eiffel-497-when-the-user-sets-a-different-repository-clear-the-errors-grid-the-slot-map-and-the-used-by-tree/16035)
> Revision: 497
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Formal methods for Evaluation of Interoperability &Maintainability?](https://discourse.openehr.org/t/formal-methods-for-evaluation-of-interoperability-maintainability/12767)
> All
I do not recognize this description of RMIMs as modifications to the HL7 RIM. RMIMs express constraints on the HL7 RIM – the RMIM is a static model that is defined as a constraint on the RIM, with all the semantics defined in the RIM and associated vocabularies. There is NO additional semantics introduced in the refinement process, just a restriction on the set of conforming structures.
It is true that the HL7 XML ITS uses the association names from the RMIM for the XML element names,...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [496] Fix a precondition failure the first time ADL Workbench is run, caused by setting the splitter above the status notebook to an out-of-range position.](https://discourse.openehr.org/t/ref-impl-eiffel-496-fix-a-precondition-failure-the-first-time-adl-workbench-is-run-caused-by-setting-the-splitter-above-the-status-notebook-to-an-out-of-range-position/12775)
> Revision: 496
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [495] AWB-13: Fix grafting an ad hoc archetype into the repository tree, where (a) either the archetype's file name indicated that it was not specialised, or else the specialisation parent was not present in the repository; and (b) the l](https://discourse.openehr.org/t/ref-impl-eiffel-495-awb-13-fix-grafting-an-ad-hoc-archetype-into-the-repository-tree-where-a-either-the-archetypes-file-name-indicated-that-it-was-not-specialised-or-else-the-specialisation-parent-was-not-present-in-the-repository-and-b-the-l/12774)
> Revision: 495
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Formal methods for Evaluation of Interoperability & Maintainability?](https://discourse.openehr.org/t/formal-methods-for-evaluation-of-interoperability-maintainability/14740)
> Hi,
I want to learn how we can formally/objectively prove that Archetype
based dual level development formalism alleviates problems of
interoperability and maintainability\. I was wondering if someone did or
know of any such study which applies formal validation methods?
Best regards,
Koray Atalag, MD, Ph\.D\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [494] AWB-14: Flattening a specialised differential archetype did not set the parent archetype id.](https://discourse.openehr.org/t/ref-impl-eiffel-494-awb-14-flattening-a-specialised-differential-archetype-did-not-set-the-parent-archetype-id/12773)
> Revision: 494
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [493] AWB-14: Fix the contents of the .adls or .html file created by File | Save As.](https://discourse.openehr.org/t/ref-impl-eiffel-493-awb-14-fix-the-contents-of-the-adls-or-html-file-created-by-file-save-as/12772)
> Revision: 493
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [492] AWB-71: Move the Export HTML option to the Repository menu, which makes more sense now that it acts upon the whole repository and is so tightly integrated with the Build options.](https://discourse.openehr.org/t/ref-impl-eiffel-492-awb-71-move-the-export-html-option-to-the-repository-menu-which-makes-more-sense-now-that-it-acts-upon-the-whole-repository-and-is-so-tightly-integrated-with-the-build-options/13369)
> Revision: 492
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [491] AWB-14: Fix the file extension when the user selects File | Save As.](https://discourse.openehr.org/t/ref-impl-eiffel-491-awb-14-fix-the-file-extension-when-the-user-selects-file-save-as/12771)
> Revision: 491
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [490] Minor change that should allow ARCH_DIRECTORY to compile under the EiffelStudio 6.1.7.1223 beta release.](https://discourse.openehr.org/t/ref-impl-eiffel-490-minor-change-that-should-allow-arch-directory-to-compile-under-the-eiffelstudio-6-1-7-1223-beta-release/16034)
> Revision: 490
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [489] AWB-71: Under the Tools menu, the Export HTML and Clean Generated Files options now ignore the node selected in the repository explorer.](https://discourse.openehr.org/t/ref-impl-eiffel-489-awb-71-under-the-tools-menu-the-export-html-and-clean-generated-files-options-now-ignore-the-node-selected-in-the-repository-explorer/12770)
> Revision: 489
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [488] AWB-14: Fix several Void target calls introduced by revision 380, caused by testing whether the selected archetype is valid when there is no selected archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-488-awb-14-fix-several-void-target-calls-introduced-by-revision-380-caused-by-testing-whether-the-selected-archetype-is-valid-when-there-is-no-selected-archetype/12769)
> Revision: 488
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [487] AWB-71: HTML is generated for all archetypes under the currently selected node in the repository explorer.](https://discourse.openehr.org/t/ref-impl-eiffel-487-awb-71-html-is-generated-for-all-archetypes-under-the-currently-selected-node-in-the-repository-explorer/16033)
> Revision: 487
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [486] AWB-13: Fix an infinite loop, caused by revision 394.](https://discourse.openehr.org/t/ref-impl-eiffel-486-awb-13-fix-an-infinite-loop-caused-by-revision-394/12765)
> Revision: 486
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [485] AWB-74: Update news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-485-awb-74-update-news-txt/12764)
> Revision: 485
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [484] Put some basic repository-wide statistics in place, mainly to help NHS users.](https://discourse.openehr.org/t/ref-impl-eiffel-484-put-some-basic-repository-wide-statistics-in-place-mainly-to-help-nhs-users/12763)
> Revision: 484
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [483] Correct a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-483-correct-a-comment/16032)
> Revision: 483
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [482] AWB-74: Update news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-482-awb-74-update-news-txt/13358)
> Revision: 482
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [481] AWB-15: Under the Tools menu, add an option Clean Generated Files.](https://discourse.openehr.org/t/ref-impl-eiffel-481-awb-15-under-the-tools-menu-add-an-option-clean-generated-files/13355)
> Revision: 481
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [possible error in: ref_impl_java/TRUNK/openehr-rm-core/src/main/java/org/openehr/rm/support/identification/HierObjectID.java](https://discourse.openehr.org/t/possible-error-in-ref-impl-java-trunk-openehr-rm-core-src-main-java-org-openehr-rm-support-identification-hierobjectid-java/16662)
> Please correct me if I am wrong:
It says in method:
private void loadValue\(String value\) \{
int doubleColons = value\.indexOf\("::"\);
// Check for root segment
if \(doubleColons == 0\) \{
throw new IllegalArgumentException\("bad format, missing...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Bounce action notification](https://discourse.openehr.org/t/bounce-action-notification/16030)
> This is a Mailman mailing list bounce action notice:
List: openEHR\-implementers
Member: brian\.hill@health\.gov\.au
Action: Subscription disabled\.
Reason: Excessive or fatal bounces\.
The triggering bounce notice is attached below\.
Questions? Contact the Mailman site administrator at
mailman@openehr\.org\.
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [480] Correct case-changing error introduced with slot table building.](https://discourse.openehr.org/t/ref-impl-eiffel-480-correct-case-changing-error-introduced-with-slot-table-building/12762)
> Revision: 480
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [479] Correct some anomalies in displaying Archetype id for archetypes that did not compile.](https://discourse.openehr.org/t/ref-impl-eiffel-479-correct-some-anomalies-in-displaying-archetype-id-for-archetypes-that-did-not-compile/14734)
> Revision: 479
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [How to express a LINK?](https://discourse.openehr.org/t/how-to-express-a-link/14730)
> Hi everybody,
I'm trying to model the class LINK in Openehr and I'm doubting about
how to do it\.
According to its syntax in ADL, a LINK could be expressed as the
following \(use\_node\.\.\.\), isn't it?
ELEMENT\[at0008\] occurrences matches \{0 \.\.1\} matches \{
value matches \{
DV\_CODED\_TEXT matches \{
defining\_code matches...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [478] Correct logic of building archetype directory tree to exclude specialisation orphans and output an error instead.](https://discourse.openehr.org/t/ref-impl-eiffel-478-correct-logic-of-building-archetype-directory-tree-to-exclude-specialisation-orphans-and-output-an-error-instead/12761)
> Revision: 478
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [477] AWB-76: Allow the Column View widget on the Path Analysis sub-tab to expand.](https://discourse.openehr.org/t/ref-impl-eiffel-477-awb-76-allow-the-column-view-widget-on-the-path-analysis-sub-tab-to-expand/12760)
> Revision: 477
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [476] AWB-81: Don't change the main window's title when minimising the window.](https://discourse.openehr.org/t/ref-impl-eiffel-476-awb-81-dont-change-the-main-windows-title-when-minimising-the-window/12759)
> Revision: 476
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [475] Correct error where specialised archetype whose definition is a copy of that of the parent was causing an exception during DIFFERENTIAL_ARCHETYPE.make_from_flat](https://discourse.openehr.org/t/ref-impl-eiffel-475-correct-error-where-specialised-archetype-whose-definition-is-a-copy-of-that-of-the-parent-was-causing-an-exception-during-differential-archetype-make-from-flat/12758)
> Revision: 475
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [474] AWB-74: Update news.txt for changes that are in BRANCHES/specialisation but not yet in the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-474-awb-74-update-news-txt-for-changes-that-are-in-branches-specialisation-but-not-yet-in-the-trunk/12757)
> Revision: 474
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [473] AWB-71: HTML for a specialised archetype goes into the same directory as the specialisation parent's HTML.](https://discourse.openehr.org/t/ref-impl-eiffel-473-awb-71-html-for-a-specialised-archetype-goes-into-the-same-directory-as-the-specialisation-parents-html/16031)
> Revision: 473
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [472] Add double-click redirection functionality to slot map and used-by map.](https://discourse.openehr.org/t/ref-impl-eiffel-472-add-double-click-redirection-functionality-to-slot-map-and-used-by-map/13344)
> Revision: 472
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [471] Correct bug in slot computation](https://discourse.openehr.org/t/ref-impl-eiffel-471-correct-bug-in-slot-computation/13342)
> Revision: 471
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [469] AWB-71: Remove the HTML column from the Test page.](https://discourse.openehr.org/t/ref-impl-eiffel-469-awb-71-remove-the-html-column-from-the-test-page/12755)
> Revision: 469
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [468] AWB-7: Until we get around to implementing it, hide the Statistics tab.](https://discourse.openehr.org/t/ref-impl-eiffel-468-awb-7-until-we-get-around-to-implementing-it-hide-the-statistics-tab/12753)
> Revision: 468
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [467] Small modifications to add icons to slot map.](https://discourse.openehr.org/t/ref-impl-eiffel-467-small-modifications-to-add-icons-to-slot-map/12752)
> Revision: 467
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [466] AWB-71: Correct the height of the Options dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-466-awb-71-correct-the-height-of-the-options-dialog/12751)
> Revision: 466
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [465] AWB-71: Fix a non-portable path in the last commit.](https://discourse.openehr.org/t/ref-impl-eiffel-465-awb-71-fix-a-non-portable-path-in-the-last-commit/12750)
> Revision: 465
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [464] AWB-71: Add a new option "Export HTML" to the Tools menu.](https://discourse.openehr.org/t/ref-impl-eiffel-464-awb-71-add-a-new-option-export-html-to-the-tools-menu/12749)
> Revision: 464
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [463] Remove an unused copy of a routine that I left in by accident in revision 404.](https://discourse.openehr.org/t/ref-impl-eiffel-463-remove-an-unused-copy-of-a-routine-that-i-left-in-by-accident-in-revision-404/12748)
> Revision: 463
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [462] Initial working (apparently) version of slot display.](https://discourse.openehr.org/t/ref-impl-eiffel-462-initial-working-apparently-version-of-slot-display/12747)
> Revision: 462
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [461] AWB-74: Fix an error in news.txt.](https://discourse.openehr.org/t/ref-impl-eiffel-461-awb-74-fix-an-error-in-news-txt/16029)
> Revision: 461
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [460] AWB-74: Update news.txt with changes since the April 2007 release.](https://discourse.openehr.org/t/ref-impl-eiffel-460-awb-74-update-news-txt-with-changes-since-the-april-2007-release/12746)
> Revision: 460
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [value of DV_COUNT::magnitude as Integer or C_INTEGER?](https://discourse.openehr.org/t/value-of-dv-count-magnitude-as-integer-or-c-integer/16661)
> Hello again\!
Now, I have a new doubt, if for example I have the following
openehr\_ELEMENT which value is a DV\_COUNT datatype\.\.\.
ELEMENT\[at0025\] occurrences matches \{0\.\.1\} matches \{ \-\- Rating
value matches \{
DV\_COUNT matches \{
magnitude matches...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [459] AWB-80: Remove the "Specializes" box in the tool bar.](https://discourse.openehr.org/t/ref-impl-eiffel-459-awb-80-remove-the-specializes-box-in-the-tool-bar/12745)
> Revision: 459
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [458] AWB-75: Fix the painting of the splash screen on Linux and Mac OS X.](https://discourse.openehr.org/t/ref-impl-eiffel-458-awb-75-fix-the-painting-of-the-splash-screen-on-linux-and-mac-os-x/12744)
> Revision: 458
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[324] added equals() and relevant testcases to CDvQuantity and CDvOrdinal](https://discourse.openehr.org/t/324-added-equals-and-relevant-testcases-to-cdvquantity-and-cdvordinal/12743)
> Revision: 324
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[323] Generate shell scripts for testing](https://discourse.openehr.org/t/323-generate-shell-scripts-for-testing/12742)
> Revision: 323
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[322] Abandoned branch, not used any more](https://discourse.openehr.org/t/322-abandoned-branch-not-used-any-more/12739)
> Revision: 322
Author: humberto\.naves
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Iconography & Screen shots.](https://discourse.openehr.org/t/iconography-screen-shots/14726)
> Are there are screen shots available for the template editor available from Ocean. I can see the contents of the *.oet files and can make a guess at how these would be derived, but seeing something would be nice.
Also, are there standard icons for use within tools used within the OpenEHR world. If so where would I get hold of them.
Thanks again
Joe
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [value as a C_ORDINAL?](https://discourse.openehr.org/t/value-as-a-c-ordinal/14718)
> Hi everybody,
I'm working with OpenEHR archetypes from this site
"http://www.openehr.org/svn/knowledge/archetypes/dev/html/index_en.html",
and I can't interpret the following section:
ELEMENT\[at0\.17\] occurrences matches \{0\.\.1\} matches \{ \-\- Volume
value matches \{
0|\[local::at0\.18\], \-\- Not heard
1|\[local::at0\.19\], \-\- Variable
2|\[local::at0\.20\], \-\-...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [457] Added classes and routines to properly iterate through Assertion expression trees, with or without a visitor.](https://discourse.openehr.org/t/ref-impl-eiffel-457-added-classes-and-routines-to-properly-iterate-through-assertion-expression-trees-with-or-without-a-visitor/12738)
> Revision: 457
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[321] added equals() and hashcode() to CCodePhrase](https://discourse.openehr.org/t/321-added-equals-and-hashcode-to-ccodephrase/13318)
> Revision: 321
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [456] AWB-76: Widen the buttons, labels and combo box on the tool bar to ensure that the text is not truncated.](https://discourse.openehr.org/t/ref-impl-eiffel-456-awb-76-widen-the-buttons-labels-and-combo-box-on-the-tool-bar-to-ensure-that-the-text-is-not-truncated/12737)
> Revision: 456
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [455] AWB-78 and AWB-79: On Mac OS X, the default editor is TextEdit and the default browser is Safari.](https://discourse.openehr.org/t/ref-impl-eiffel-455-awb-78-and-awb-79-on-mac-os-x-the-default-editor-is-textedit-and-the-default-browser-is-safari/12736)
> Revision: 455
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [454] AWB-77: Editing an archetype failed if the path to the archetype had spaces in it.](https://discourse.openehr.org/t/ref-impl-eiffel-454-awb-77-editing-an-archetype-failed-if-the-path-to-the-archetype-had-spaces-in-it/12735)
> Revision: 454
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [453] Fix some small bugs to do with specialisation:](https://discourse.openehr.org/t/ref-impl-eiffel-453-fix-some-small-bugs-to-do-with-specialisation/12734)
> Revision: 453
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[320] Added a getAttribute method for CComplexObject to retrieve an attribute by its name.](https://discourse.openehr.org/t/320-added-a-getattribute-method-for-ccomplexobject-to-retrieve-an-attribute-by-its-name/12733)
> Revision: 320
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EqualsBuilder problem](https://discourse.openehr.org/t/equalsbuilder-problem/16660)
> Dear Rong et al\.,
I am trying to remove a CComplexObjects from a list of CComplexObjects
by using remove\(myCComplexObject\)\.
This call always removes the first element of the list, not the
appropriate one \(where defining\_code etc\. is the same\)\.
In my case, I have all the ISM\_TRANSITIONs of
openEHR\-EHR\-ACTION\.follow\_up\.v1draft\.adl in this list\.
I believe this has something to do with the EqualsBuilder used in
CComplexObject and related Classes\.
For example:
In...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [452] AWB-73: The SConstruct can now create an installer for Linux, in the form of a bzipped tar file.](https://discourse.openehr.org/t/ref-impl-eiffel-452-awb-73-the-sconstruct-can-now-create-an-installer-for-linux-in-the-form-of-a-bzipped-tar-file/13317)
> Revision: 452
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Template Files](https://discourse.openehr.org/t/template-files/13316)
> Hello
I have been lurking on the lists for a while, specifically looking at mails relating to the templates being constructed. I see that the UK NHS is creating templates ( that is *.oet ) files, which are published on their SVN site.
A few questions :
- What tools are used to create these files, are the tools open source?
- Is the *.oet file format an OpenEHR standard file format? - I can not find any reference to it on the OpenEHR site.
- Are there any other organisations creating...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [451] AWB-72: Enable building of installers for Tiger and Leopard, PowerPC and Intel.](https://discourse.openehr.org/t/ref-impl-eiffel-451-awb-72-enable-building-of-installers-for-tiger-and-leopard-powerpc-and-intel/12732)
> Revision: 451
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [450] Correct OPENEHR_VERSION.revision, which I somehow committed with a non-zero value in revision 424.](https://discourse.openehr.org/t/ref-impl-eiffel-450-correct-openehr-version-revision-which-i-somehow-committed-with-a-non-zero-value-in-revision-424/12731)
> Revision: 450
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [{Disarmed} Comparison of EHR models](https://discourse.openehr.org/t/disarmed-comparison-of-ehr-models/14724)
> # Dear all,Recently an article by Bernd Blobel was published in the Dutch HL7 magazine (Dec 07 issue) in which he compares the different EHR models: openEHR, HL7v3, EN/ISO 13606 and CCR. Robert Stegwee, the chair of HL7.nl, kindly translates this article in Dutch, which unfortunately makes it unsuitable for distribution outside the Netherlands
I’ve tried to ask Bernd Blobel to share the original text of this article (which is hopefully in English), so that the openEHR community also can take...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [449] Correct some basic errors that stopped the test page from working.](https://discourse.openehr.org/t/ref-impl-eiffel-449-correct-some-basic-errors-that-stopped-the-test-page-from-working/16027)
> Revision: 449
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [448] Refactored version of specialisation logic, now with ARCHETYPE specialised into FLAT_ARCHETYPE and DIFFERENTIAL_ARCHETYPE, and ARCHETYPE_ONTOLOGY similarly specialised into two new classes.](https://discourse.openehr.org/t/ref-impl-eiffel-448-refactored-version-of-specialisation-logic-now-with-archetype-specialised-into-flat-archetype-and-differential-archetype-and-archetype-ontology-similarly-specialised-into-two-new-classes/16026)
> Revision: 448
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [447] Revision 439 fixed the packagemaker path in the SConstruct for Mac OS X Leopard, but unfortunately this link did not exist in Tiger.](https://discourse.openehr.org/t/ref-impl-eiffel-447-revision-439-fixed-the-packagemaker-path-in-the-sconstruct-for-mac-os-x-leopard-but-unfortunately-this-link-did-not-exist-in-tiger/12729)
> Revision: 447
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [446] Current set of changes appear to be pretty good for specialisation semantics and checking.](https://discourse.openehr.org/t/ref-impl-eiffel-446-current-set-of-changes-appear-to-be-pretty-good-for-specialisation-semantics-and-checking/12728)
> Revision: 446
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Developing with Archetypes](https://discourse.openehr.org/t/developing-with-archetypes/14725)
> Hello everyone
I am attempting to build some tools to help in the development/publication of archetypes, as such I have a couple of questions :
- Is it possible to get an up to date copy of the schemas for archetypes, I see the versions on SVN but they seem to be a little out of date ( certainly the type "C_CODE_PHRASE" seems to be missing )
-Secondly I also see that Ocean have release a DLL for parsing ADL files. Has anyone managed to build a .NET project that can take an ADL file and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [445] Commit change to allow Eiffel 6.0 build to proceed normally.](https://discourse.openehr.org/t/ref-impl-eiffel-445-commit-change-to-allow-eiffel-6-0-build-to-proceed-normally/12727)
> Revision: 445
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [444] Reverting the attempted fix in revision 443 because it didn't fix the build in EiffelStudio 6.0, and 6.0 doesn't seem to mind the change in ECF version anyway.](https://discourse.openehr.org/t/ref-impl-eiffel-444-reverting-the-attempted-fix-in-revision-443-because-it-didnt-fix-the-build-in-eiffelstudio-6-0-and-6-0-doesnt-seem-to-mind-the-change-in-ecf-version-anyway/12724)
> Revision: 444
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [443] Revision 442 broke the build on CruiseControl.](https://discourse.openehr.org/t/ref-impl-eiffel-443-revision-442-broke-the-build-on-cruisecontrol/12723)
> Revision: 443
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [442] Initial working cut of flattening functionality:](https://discourse.openehr.org/t/ref-impl-eiffel-442-initial-working-cut-of-flattening-functionality/13305)
> Revision: 442
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [support in building templates](https://discourse.openehr.org/t/support-in-building-templates/12721)
> Dear all,
thank you for your support :)
I'm going deeper into specifications and taking care of your suggestions!
In these days I'm going to develop my first aggregation of archetypes for building a specific health record.. I will let yo know the results :)
Greetings
Nicola
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [441] Fix a typo in the last revision that caused the TRUNK build to fail on Windows.](https://discourse.openehr.org/t/ref-impl-eiffel-441-fix-a-typo-in-the-last-revision-that-caused-the-trunk-build-to-fail-on-windows/16025)
> Revision: 441
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [440] The last revision missed a case where the SConstruct referred to adl_parser on non-Windows platforms, causing the build to fail.](https://discourse.openehr.org/t/ref-impl-eiffel-440-the-last-revision-missed-a-case-where-the-sconstruct-referred-to-adl-parser-on-non-windows-platforms-causing-the-build-to-fail/12720)
> Revision: 440
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [439] Fix two problems with the SConstruct:](https://discourse.openehr.org/t/ref-impl-eiffel-439-fix-two-problems-with-the-sconstruct/16024)
> Revision: 439
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Java XML-Archetype Parser?](https://discourse.openehr.org/t/java-xml-archetype-parser/12730)
> Dear all,
Does anybody know of any current initiative and/or interest to develop a
Java\-based XML\-Archetype Parser?
Cheers
Sebastian
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [help in building templates](https://discourse.openehr.org/t/help-in-building-templates/14727)
> Hi,
My name is Nicola Onano.
I work for CRS4, a not-for-profit research center in Cagliari (Italy).
My group is interested in the openEHR project. Our aim is to build EHRs in collaboration with "Ospedale G. Brotzu" (a public hospital, here in Italy).
I studied the openEHR project, I found it very interesting and I appreciated the ease of use of the archetype editor developed by Ocean Informatics.
On the other hand, I can't understand how to create a template from single archetypes, how to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Help in building templates](https://discourse.openehr.org/t/help-in-building-templates/16023)
> Hi,
My name is Nicola Onano.
I work for CRS4, a not-for-profit research center in Cagliari (Italy).
My group is interested in the openEHR project. Our aim is to build EHRs in collaboration with "Ospedale G. Brotzu" (a public hospital, here in Italy).
I studied the openEHR project, I found it very interesting and I appreciated the ease of use of the archetype editor developed by Ocean Informatics.
On the other hand, I can't understand how to create a template from single archetypes, how to...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CCR/ASTM](https://discourse.openehr.org/t/ccr-astm/12722)
> Dear all,
Through a Health 2.0 blog ([http://www.health2blog.com/2007/11/health-20-compu.html](http://www.health2blog.com/2007/11/health-20-compu.html)), I've came into contact with David Kibbe, who's secretary (and possibly the new chairman) of the ASTM E31 technical committee, which is responsible for continuity of care (CCR) standard.
His reaction when I suggested to look into the openEHR work was: "I think we're very much on the same page about separating technology from knowledge, and...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [preventing spam on openEHR wiki](https://discourse.openehr.org/t/preventing-spam-on-openehr-wiki/12717)
> Dear all,
we have enabled the 'captcha' mechanism on the openEHR wiki, due to
spamming in the form of comments on some pages\. This will mean that to
create comments you now either need to be logged in or else you are
going to be challenged with a dialogue designed to determine if you are
a human rather than a spambot of some kind\. Sadly nothing appears to be
safe from the mentally bereft\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[319] Added missing ISO_639-1 Languages to openehr_terminology_en.xml (otherwise parser won't parse archetypes with languages other than those specified)](https://discourse.openehr.org/t/319-added-missing-iso-639-1-languages-to-openehr-terminology-en-xml-otherwise-parser-wont-parse-archetypes-with-languages-other-than-those-specified/12719)
> Revision: 319
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [438] AWB-14: Remove a "not" in ARCHETYPE.physical_paths that was accidentally left in a few revisions ago.](https://discourse.openehr.org/t/ref-impl-eiffel-438-awb-14-remove-a-not-in-archetype-physical-paths-that-was-accidentally-left-in-a-few-revisions-ago/12718)
> Revision: 438
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [437] AWB-14: If the user collapses a top-level row in GUI_COMPILER_ERROR_CONTROL, one of whose whose sub-rows is selected, the top-level row becomes selected instead.](https://discourse.openehr.org/t/ref-impl-eiffel-437-awb-14-if-the-user-collapses-a-top-level-row-in-gui-compiler-error-control-one-of-whose-whose-sub-rows-is-selected-the-top-level-row-becomes-selected-instead/12716)
> Revision: 437
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [436] Specialisation changes:](https://discourse.openehr.org/t/ref-impl-eiffel-436-specialisation-changes/12711)
> Revision: 436
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [435] Minor fix to source code formatting.](https://discourse.openehr.org/t/ref-impl-eiffel-435-minor-fix-to-source-code-formatting/12710)
> Revision: 435
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [434] AWB-14: Pull the keyboard and mouse wheel handling routines up from GUI_TEST_ARCHETYPE_TREE_CONTROL to a new class called GUI_GRID_CONTROLLER.](https://discourse.openehr.org/t/ref-impl-eiffel-434-awb-14-pull-the-keyboard-and-mouse-wheel-handling-routines-up-from-gui-test-archetype-tree-control-to-a-new-class-called-gui-grid-controller/12709)
> Revision: 434
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [433] Various small specialisation-related changes:](https://discourse.openehr.org/t/ref-impl-eiffel-433-various-small-specialisation-related-changes/12708)
> Revision: 433
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [432] This is a checkpoint of changes to the validation code and some slight GUI improvement.](https://discourse.openehr.org/t/ref-impl-eiffel-432-this-is-a-checkpoint-of-changes-to-the-validation-code-and-some-slight-gui-improvement/12707)
> Revision: 432
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [431] AWB-14: Fix a precondition violation in set_focus when called from MAIN_WINDOW.suppress_tab_key_insertion.](https://discourse.openehr.org/t/ref-impl-eiffel-431-awb-14-fix-a-precondition-violation-in-set-focus-when-called-from-main-window-suppress-tab-key-insertion/12706)
> Revision: 431
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [persistence](https://discourse.openehr.org/t/persistence/16710)
> HAPPY NEW YEAR!!!
My question is on persistence layer for openehr java.
I was wondering if any body could give me a link to such.
Also, is it possibe to generate a hibernate mapping for the openehr java classes for use for a db schema. In other words, does the openehr classes include a data model layer.
(Apologies if its a stupid question but please someone kindly elucidate)
Cheers,
Ime
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [430] AWB-14: Fix a bug that opening a flat .adl file in the external editor only worked if the user dismissed the information dialog by clicking the OK button with the mouse.](https://discourse.openehr.org/t/ref-impl-eiffel-430-awb-14-fix-a-bug-that-opening-a-flat-adl-file-in-the-external-editor-only-worked-if-the-user-dismissed-the-information-dialog-by-clicking-the-ok-button-with-the-mouse/16022)
> Revision: 430
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [429] AWB-65: Minor cosmetic change to the indenting of the splash text.](https://discourse.openehr.org/t/ref-impl-eiffel-429-awb-65-minor-cosmetic-change-to-the-indenting-of-the-splash-text/12705)
> Revision: 429
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Party ref in EHR status.](https://discourse.openehr.org/t/party-ref-in-ehr-status/12713)
> I willb e grateful if you correct me if I am wrong\.
I wonder how the subject connection should look like\.
The available archetype\-editors do not offer demographic\-archetypes, and
in the collection of available archetypes, there are also no
demographic\-based archetypes \.
One could think that demographic archetypes are a kind of legacy\.
Does that mean that the demographic classes in the Reference Model will
go the same way?
I mean, In the EHR\-class, there is EHR\-Status, which...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [428] Correct errors / omissions in ARCHETYPE_ID regex, according to Peter Gummer's analysis.](https://discourse.openehr.org/t/ref-impl-eiffel-428-correct-errors-omissions-in-archetype-id-regex-according-to-peter-gummers-analysis/12704)
> Revision: 428
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [427] Add support for detecting if OG_* objects and C_* objects are leaves or not; this allows a proper leaf path list to be constructed, which is the basis of path comparisons for specialised archetypes with respect to parents.](https://discourse.openehr.org/t/ref-impl-eiffel-427-add-support-for-detecting-if-og-objects-and-c-objects-are-leaves-or-not-this-allows-a-proper-leaf-path-list-to-be-constructed-which-is-the-basis-of-path-comparisons-for-specialised-archetypes-with-respect-to-parents/13279)
> Revision: 427
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [426] Further small changes for compiling:](https://discourse.openehr.org/t/ref-impl-eiffel-426-further-small-changes-for-compiling/12701)
> Revision: 426
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [425] AWB-65: Revision 424 broke the build in the TRUNK on CruiseControl, although it works fine on my computer.](https://discourse.openehr.org/t/ref-impl-eiffel-425-awb-65-revision-424-broke-the-build-in-the-trunk-on-cruisecontrol-although-it-works-fine-on-my-computer/12700)
> Revision: 425
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [424] AWB-65: In both the TRUNK and BRANCHES/specialisation, set version number 1.4.1.0.](https://discourse.openehr.org/t/ref-impl-eiffel-424-awb-65-in-both-the-trunk-and-branches-specialisation-set-version-number-1-4-1-0/12695)
> Revision: 424
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [423] Improvements to compiler error output:](https://discourse.openehr.org/t/ref-impl-eiffel-423-improvements-to-compiler-error-output/12694)
> Revision: 423
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[318] Bug corrected at ArchetypeSlot serialization](https://discourse.openehr.org/t/318-bug-corrected-at-archetypeslot-serialization/12693)
> Revision: 318
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[317] Bug corrected at ExpressionLeaf serialization](https://discourse.openehr.org/t/317-bug-corrected-at-expressionleaf-serialization/12692)
> Revision: 317
Author: humberto\.naves
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [422] Add the beginnings of a compiler error GRID control, like the EiffelStudio one.](https://discourse.openehr.org/t/ref-impl-eiffel-422-add-the-beginnings-of-a-compiler-error-grid-control-like-the-eiffelstudio-one/12690)
> Revision: 422
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [421] Correct a comment.](https://discourse.openehr.org/t/ref-impl-eiffel-421-correct-a-comment/12689)
> Revision: 421
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [420] AWB-67: Merge revisions 413, 417 and 418 from BRANCHES/specialisation into the TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-420-awb-67-merge-revisions-413-417-and-418-from-branches-specialisation-into-the-trunk/12688)
> Revision: 420
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [419] Fix a minor typo on the project page.](https://discourse.openehr.org/t/ref-impl-eiffel-419-fix-a-minor-typo-on-the-project-page/12687)
> Revision: 419
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [418] AWB-67: On Mac OS X, replace the application icon with an openEHR logo; and add openEHR at the top of the GIF that appears in the installer.](https://discourse.openehr.org/t/ref-impl-eiffel-418-awb-67-on-mac-os-x-replace-the-application-icon-with-an-openehr-logo-and-add-openehr-at-the-top-of-the-gif-that-appears-in-the-installer/12686)
> Revision: 418
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [417] AWB-67: Change the icons directory constant to be under the application start-up directory, rather than just "icons".](https://discourse.openehr.org/t/ref-impl-eiffel-417-awb-67-change-the-icons-directory-constant-to-be-under-the-application-start-up-directory-rather-than-just-icons/12684)
> Revision: 417
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [416] AWB-14: In OPTION_DIALOG, initialise the status reporting level combo box to the current value; and set the standard border width and padding around the combo box and its label.](https://discourse.openehr.org/t/ref-impl-eiffel-416-awb-14-in-option-dialog-initialise-the-status-reporting-level-combo-box-to-the-current-value-and-set-the-standard-border-width-and-padding-around-the-combo-box-and-its-label/12683)
> Revision: 416
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [415] AWB-14: Fix the adl_parser project, which no longer compiled because revision 414 created a dependency on the adl_workbench app cluster: MESSAGE_BILLBOARD inherited from SHARED_UI_RESOURCES because it needed to access the new statu](https://discourse.openehr.org/t/ref-impl-eiffel-415-awb-14-fix-the-adl-parser-project-which-no-longer-compiled-because-revision-414-created-a-dependency-on-the-adl-workbench-app-cluster-message-billboard-inherited-from-shared-ui-resources-because-it-needed-to-access-the-new-statu/12682)
> Revision: 415
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [414] Small set of changes to make error reporting level configurable.](https://discourse.openehr.org/t/ref-impl-eiffel-414-small-set-of-changes-to-make-error-reporting-level-configurable/12681)
> Revision: 414
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [413] AWB-67: Replace the Ocean logo in the splash screen and the About box with an image that combines the openEHR and Ocean logos.](https://discourse.openehr.org/t/ref-impl-eiffel-413-awb-67-replace-the-ocean-logo-in-the-splash-screen-and-the-about-box-with-an-image-that-combines-the-openehr-and-ocean-logos/12680)
> Revision: 413
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [412] AWB-14 - Further specialisation development.](https://discourse.openehr.org/t/ref-impl-eiffel-412-awb-14-further-specialisation-development/12679)
> Revision: 412
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [411] Correct error where non-local codes were being searched for in ARCHTEYPE_ONTOLOGY](https://discourse.openehr.org/t/ref-impl-eiffel-411-correct-error-where-non-local-codes-were-being-searched-for-in-archteype-ontology/12678)
> Revision: 411
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[316] Now the XML serializer uses the JDOM library](https://discourse.openehr.org/t/316-now-the-xml-serializer-uses-the-jdom-library/16663)
> Revision: 316
Author: humberto\.naves
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [410] Correct preconditions on has_xxx_code routines so as to check that codes are at least ac- and at- style codes.](https://discourse.openehr.org/t/ref-impl-eiffel-410-correct-preconditions-on-has-xxx-code-routines-so-as-to-check-that-codes-are-at-least-ac-and-at-style-codes/16020)
> Revision: 410
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The ontology of checklists?](https://discourse.openehr.org/t/the-ontology-of-checklists/16019)
> Quite a number of the documents being worked on as part of the NHS modelling work present themselves as checklists e.g Pre-op systems checks or Risk Assessment questionnaire. To date these have mostly been modelled as simple boolean or short termlist laden archetypes but it is my impression that there are a variety of styles of checklists some of which may merit different degrees of expansion below the top-level simple boolean and may have wholly different functions within clinical recording....
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [protocol definition (was maximum heart rate)](https://discourse.openehr.org/t/protocol-definition-was-maximum-heart-rate/14722)
> Is a protocol a cluster archetype or a component of an observation?
[http://www.openehr.org/137-OE.html](http://www.openehr.org/137-OE.html) defines the term 'protocol' as an attribute of CARE_ENTRY.
A clinical trial protocol document may define a collection of trial specific observations (as used in the openEHR protocol sense), for example a trial specific definition (e.g. of an MI) or reference ranges of blood chemistry that differ for males and females and by country of birth, or a new...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[315] Refactoring to use terminology.xml file](https://discourse.openehr.org/t/315-refactoring-to-use-terminology-xml-file/13242)
> Revision: 315
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [(Im)mutable java RM? (Was: Re: Improving the minimal terminology service)](https://discourse.openehr.org/t/im-mutable-java-rm-was-re-improving-the-minimal-terminology-service/12673)
> Hi Humberto and others\!
There is a zip at
http://www.imt.liu.se/~erisu/2007/mutable_immutable.zip with a small
test \(including java\-code and comments\) of an approach that possibly
would let us have a choice of both mutable and immutable classes and a
conversion mechanism between the two\. Please have a look and comment\.
There was a lot of mail discussion before this regarding arguments for
and against \(im\)mutability, some excerpts to start searching the mail
archives from are listed...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Antw: Re: Antw: Author Information Mandate (Re: Archetype production: Types o...](https://discourse.openehr.org/t/antw-re-antw-author-information-mandate-re-archetype-production-types-o/12672)
> In een bericht met de datum 15-12-2007 23:30:20 West-Europa (standaardtijd), schrijft jpfreriks@gmail.com:
> William and Stef, thank you for your clarifying inputs.
>
> I'm not a clinician and as I said - the cancer situation isn't a good, ethical or even legal example, as you've (rightfully) pointed out.
>
> But in general: are there situations thinkable where a health professional doesn't want to disclose her/his comments to the patient? Because if there are, it will be neccessary to put...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Antw: Author Information Mandate (Re: Archetype production: Types of Archetyp...](https://discourse.openehr.org/t/antw-author-information-mandate-re-archetype-production-types-of-archetyp/15540)
> In een bericht met de datum 14-12-2007 21:13:21 West-Europa (standaardtijd), schrijft jpfreriks@gmail.com:
Dear Josina,
This question should perhaps be in the openEHR legal list serve :-)
From the clinical point of view I understand your question. However, the two use cases differ 180 degrees.
The cancer use case is according to Dutch law at the edge of illegality. A Doctor is not allowed to not enter objective patient data in the record. He is allowed to keep personal notes on the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [409] AWB-13: Fix ARCHETYPE_TERM_CODE_TOOLS.is_valid_code, which was clearly wrong, because although it correctly checked whether the given code stated with "ac" or "at", it then ignored the result and returned True solely on the basis o](https://discourse.openehr.org/t/ref-impl-eiffel-409-awb-13-fix-archetype-term-code-tools-is-valid-code-which-was-clearly-wrong-because-although-it-correctly-checked-whether-the-given-code-stated-with-ac-or-at-it-then-ignored-the-result-and-returned-true-solely-on-the-basis-o/16018)
> Revision: 409
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Portuguese translation task-force](https://discourse.openehr.org/t/portuguese-translation-task-force/12677)
> Hi,
Let's try to assemble a team that will translate all archetypes of openEHR repositories to Brazillian Portuguese?
Humberto
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [New page about the team](https://discourse.openehr.org/t/new-page-about-the-team/16017)
> Hi all,
I would like to put up a page about the current development team and contributors to the Java project similar to the one for the specification project, [http://www.openehr.org/200-OE.html](http://www.openehr.org/200-OE.html)
So if you are currently listed as member of the development team or contributors, could you please send me your mini-CV and photos please? I know some people are probably not on the list, I will try to write to them individually.
Cheers,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Documentation moved to Wiki](https://discourse.openehr.org/t/documentation-moved-to-wiki/16016)
> Dear all,
I managed to move most of the existing documentation about the Java project into the Wiki and linked it to the project page. I hope this movement will make it easier for the Java community to join in the effort to improve the documentation. Please note that you don't need to be a svn repository committer to be able to contribute to the documentation now.
Also we can use the built-in commenting support to discuss possible design improvements and questions raised from...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype production: Types of Archetypes](https://discourse.openehr.org/t/archetype-production-types-of-archetypes/14728)
> A few thoughts about Types of Archetypes
Archetypes are constraints on an UML model.
Archetypes define what can be documented about a topic.
Templates are Archetypes.
Archetypes are not Templates
because Templates are the aggregated archetypes, collected and further constrained to suit a specific business context.
In order to reduce possibilities for confusion we need to become more clear what we mean.
Semantic interoperability and confusing meanings of things do not go well...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Improving the minimal terminology service](https://discourse.openehr.org/t/improving-the-minimal-terminology-service/13240)
> Hi Rong,
I want to improve the terminology service (I think we should use the terminology.xml file at "specification/TRUNK/publishing/architecture/computable/terminology.xml" as our source of data), and so I will make a branch in the current minimal term server. Also, may I make a "mutable experiment" (a new branch) of the RM and AM? (This will turn my life much better...)
Regards,
Humberto Naves
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[314] test to commit to new url of the respository](https://discourse.openehr.org/t/314-test-to-commit-to-new-url-of-the-respository/16015)
> Revision: 314
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with the new repositories](https://discourse.openehr.org/t/problem-with-the-new-repositories/14723)
> Hi,
Is the new repository "[http://www.openehr.org/svn/ref_impl_java](http://www.openehr.org/svn/ref_impl_java)" a "proxy" to the old one? Because when I tried to commit, I got "MKCOL.... Error 404"... Then I changed to the old one, and the commit worked!!!
[http://svn.haxx.se/dev/archive-2007-06/0491.shtml](http://svn.haxx.se/dev/archive-2007-06/0491.shtml)
Humberto
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[313] Minimal tool to convert ADL to XML](https://discourse.openehr.org/t/313-minimal-tool-to-convert-adl-to-xml/12671)
> Revision: 313
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[312] New version of the XML serializer, compatible with xsd schema version 1.0.1](https://discourse.openehr.org/t/312-new-version-of-the-xml-serializer-compatible-with-xsd-schema-version-1-0-1/12669)
> Revision: 312
Author: humberto\.naves
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Struggling to get started with the Java ref implementation](https://discourse.openehr.org/t/struggling-to-get-started-with-the-java-ref-implementation/16659)
> Hi all,
Am new to this list and recently our team of developers got introduced to openEHR and the design principles behind it. Everyone in the team got totally sold on it. However, despite reading the various docs on the site (overview pdf-very helpful), we are still struggling on how to just get started with the java implementation code. We just can't get our heard round it.
We are trying to build an application based on openEHR to manage records of HIV/AIDs patients for about five rural...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [A new committer to the ref_impl_java project](https://discourse.openehr.org/t/a-new-committer-to-the-ref-impl-java-project/12670)
> Dear all,
I am glad to announce that the Java project just got a new committer, Humberto Naves from Zilics, Brazil. He is working closely with Beatriz de Faria Leão and Lincoln A Moura Jr in a team prototyping archetype based system. Over the past months, Humberto has demonstrated that he is both a competent Java developer and engaged in the Java implementation of openEHR.
Welcome, Humberto!
Cheers,
Rong
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [maximum heart rate](https://discourse.openehr.org/t/maximum-heart-rate/14971)
> I suggest that the maximum rate is not an item that you would store per
se, but rather the result of a query on observations stored with an
\(exercise\) procedure\.
The table of recommended maximum heart rates during exercise according
to age would be in an instruction\.
Colin
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [heart rates](https://discourse.openehr.org/t/heart-rates/12668)
> This is both an archetyping question and a physiology question
I want to record various heart rates in archetyped data\.
One concept that seems important in athletics is a maximum heart
rate \- now this concept seems to have clear semantics in
exercise circles, but I'm not sure whether a person actually really
has a 'maximum' heart rate\. It's more the heart rate plateau that you will
get to if you are exercising at 'maximum' intensity\. The maximum
heart rate is...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem with javacc version 2.2](https://discourse.openehr.org/t/problem-with-javacc-version-2-2/12667)
> Hi,
When building the "adl-parser", i noticed that the javacc plugin did not work ... And so when I added the following lines...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Possible improvement of the Archetype Editor](https://discourse.openehr.org/t/possible-improvement-of-the-archetype-editor/14721)
> Hi,
I was using the Archetype Editor for a new COMPOSITION archetype, but the tool does not allow to put SECTION (or ENTRYies) on the content tab, only SLOT's (to SECTION or ENTRYies), and so, I checked at the specification, and I found out that this limitation is caused by the tool... So, my question is: why is not possible to define the SECTION's of a composition inside the archetype (the only possible way is through SLOT's, and so, I have to use a template to fill that slot)?
Many...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Report From the WHO Standards Workshop](https://discourse.openehr.org/t/report-from-the-who-standards-workshop/14720)
> Hi All,
Several people had asked me to let them know how this meeting in Nairobi
went, so here goes\! Of course these are my personal opinions and
impressions\. :\-\)
My already too short 15 minute presentation on comparing OpenMRS
concepts and Archetypes plus Vocabulary management in Archetypes was
scrunched to 5 minutes\. Needless to say I was not pleased and was very
concerned \(and nervous\) about trying to convey anything meaningful in
five minutes\. I believe that I got across the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [408] Next instalment of specialisation related changes:](https://discourse.openehr.org/t/ref-impl-eiffel-408-next-instalment-of-specialisation-related-changes/12666)
> Revision: 408
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [407] AWB-66: Change links on the project page and Subversion externals to use http://www.openehr.org/svn instead of http://svn.openehr.org.](https://discourse.openehr.org/t/ref-impl-eiffel-407-awb-66-change-links-on-the-project-page-and-subversion-externals-to-use-http-www-openehr-org-svn-instead-of-http-svn-openehr-org/12665)
> Revision: 407
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [path of ArchetypeInternalRef](https://discourse.openehr.org/t/path-of-archetypeinternalref/14712)
> How is the path to an ArchetypeInternalRef constructed so that it is
pssible that it points to some ohter point in an archetype, and at the
same time is identifiable as being an unique point in the archetype\.
For example:
I have contacts in an archetype, and these have addresses, for
efficiency\-reasons the addresses are defined only once in the archetype,
like this:
addresses cardinality matches \{0\.\.\*; ordered\} matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Transforms](https://discourse.openehr.org/t/transforms/14716)
> Dear All,
I am wondering about transforms as I move along to a complete
build/release system for a repository of archetypes\.
A\) Is there an XML \-> ADL transform?
B\) Are the HTML docs presently transformed from the ADL or XSLT'ed from
the XML?
C\) Same as \(B\) but for the CSV files\.
What I would prefer would be:
1\) Only XML Archetypes & Templates\.
2\) At the end of the processing \(e\.g\. changing \.vNdraft to \.vN inc all
references in other files\) run a generate...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] question about PartyIdentity in ref_eiffel_impl](https://discourse.openehr.org/t/ref-impl-eiffel-question-about-partyidentity-in-ref-eiffel-impl/16012)
> Hi all,
I found in party\_identity\.e the attribute "details"\. which is of type:
ITEM\_STRUCTURE
Reading the documentation, it should be of type List, which is not a
special RM\-type\.
What it is, I could not find, but I guess it is a List like the generic
container in msot programming languages is\.
Is there any reason why this is an ITEM\_STRUCTURE in the Eiffel\-code?
thanks
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [PartyIdentity -> Purpose](https://discourse.openehr.org/t/partyidentity-purpose/16013)
> Maybe Rong, has some time to answer this, but I am very glad with
anyone's answer\.
I have a question about the ref\_java\_impl\. I checked the latest TRUNK
version, there is something that is not clear to me\.
I looked in the document: Demographic Information Model, version
Revision: 2\.0\.1, which is, I believe, the latest published version\.
I look at PartyIdentity and see the required attribute "purpose"\.
But it is not in the rm\-domain\-object PartyIdentity in the...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Notice of relocation of all openEHR Subversion URLs](https://discourse.openehr.org/t/notice-of-relocation-of-all-openehr-subversion-urls/16014)
> All openEHR Subversion repositories have been relocated in a new
structure, with a new URL pattern\.
The old URL for the repositories was of the form:
http://svn.openehr.org/repo_name
The new URL form is http://www.openehr.org/svn/repo_name
Everyone using a Subversion repository in openEHR should change the
location of the repository to the new location\. In TortoiseSVN, this can
be done easily be using the 'Relocate' command at the top level of the
checked out repository\. This...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR and CEN models](https://discourse.openehr.org/t/openehr-and-cen-models/14708)
> Hi
I hope its all right to ask a few standards related question on this forum\.
I wanted to know how different the openEHR and CEN Ref Models and
Archetypes are from each other at a logical level\. Is it necessary to
understand the CEN stds if working with openEHR stds? In particular, is
it important to know the CEN13606 archetypes if working with openEHR
archetypes\. At a logical level what are the differences between the two?
Another topic area that alludes my understanding is a...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [feedback - openEHR website + wiki](https://discourse.openehr.org/t/feedback-openehr-website-wiki/12663)
> Dear all,
Some very useful feedback on the website and wiki from Josina Freriks (Gerard's daughter). I improved 2 things she mentions, which I hope are uncontroversial - the mailing list page (under 'community') and I added a small description to the specificatoin project main page. But she has many other useful comments, mainly about content, rather than formatting. Reactions?
- thomas
|
Subject:
|
openEHR website
|
|
Date:
|
Wed, 05 Dec...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [new component mini-termserv](https://discourse.openehr.org/t/new-component-mini-termserv/16011)
> Dear all,
I just uploaded a new component, mini-termserv, which stands for "Minimum terminology service". It is a simple in-memory implementation of TERMINOLOGY_SERVICE and provides required minimum terminology service for the kernel to work properly. Basically it provides access to all the concept groups from the openEHR terminology and several code sets used by the reference model. It is now used by the parser for some basic validation.
The terminology content is loaded from a XML file,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GUIs for openEHR data](https://discourse.openehr.org/t/guis-for-openehr-data/14710)
> Hi
As I assume not everybody interested in openEHR GUIs has set watches
for the relevant pages in the openEHR wiki, I would like to point to a
rather lengthly comment of mine:
http://www.openehr.org/wiki/display/dev/User+Interface+and+openEHR+data?focusedCommentId=1540136#comment-1540136
For further remarks etc please use the wiki\.
\- Thilo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] possible problem in ADL_Workbench?](https://discourse.openehr.org/t/ref-impl-eiffel-possible-problem-in-adl-workbench/14709)
> When a string contains multiple lines, the workbench gives an error\-message:
ERROR \- line 92: duplicate attribute string\_attr21 \[last cADL token =
SYM\_MATCHES\]
\(Parse failed\) \(ARCHETYPE\_COMPILER\.parse\_archetype\)
The offending ADL\-line is:
string\_attr21 matches \{"this is what it is used for, this...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Intravenous Therapy Template](https://discourse.openehr.org/t/intravenous-therapy-template/14911)
> Dear all,
I am not a clinician and I am trying to develop a template for the intravenous
therapy. I found the archetype:
openEHR-EHR-ACTION.intravenous_fluid_administration.v1draft
Where I put this
openEHR-EHR-ITEM_TREE.intravenous_fluids.v1draft
archetype into the slot.
But unfortunately it does not cover all of the data items I need.
'Additives including Dose' is not covered and I couldn't find it in
any other archetype.
Do I have to specialise the archetype or is there any other...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CVS ROOT](https://discourse.openehr.org/t/cvs-root/14713)
> Hi all,
I've got a practical question: how can I download archetypes from a
repository into the archetype editor?
I've installed TortoiseCVS and created a local file\. What CVS ROOT do I
need to specify in the Checkout dialog? \(and am I right that this is all
I need to fill in in the dialog box?\)
Couldn't find any info about downloading from a repository or CVS roots
on the website, except a link to a tgz file which is/should be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specialisation](https://discourse.openehr.org/t/specialisation/14711)
> Dear Everyone,
Background:
We are in Sweden starting a number of clinical archetype\-construction
projects and we are hoping to re\-use as much as possible from the
openEHR repository by specialisation\.
So to my problem:
Looking at the openEHR\-EHR\-OBSERVATION\.body\_weight\.v1 archetype
\(hereafter named BW\) and the
openEHR\-EHR\-OBSERVATION\.body\_weight\-birth\.v1 archetype \(BWB\), BWB does
not seem to be a specialisation of BW\. BWB specifies the event to be
birth and clothing state...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New Standard Proposal](https://discourse.openehr.org/t/new-standard-proposal/14715)
> <sarcasm>Now here is a proposal we should all get behind\!</sarcasm>
http://empowerhealthcare.blogspot.com/
PDF Healthcare
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[311] added support for parsing datetime without specified minutes or seconds; separated datetime parsing test from basic types paring test](https://discourse.openehr.org/t/311-added-support-for-parsing-datetime-without-specified-minutes-or-seconds-separated-datetime-parsing-test-from-basic-types-paring-test/13219)
> Revision: 311
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Looking for the LiU Archetype Editor authors](https://discourse.openehr.org/t/looking-for-the-liu-archetype-editor-authors/16007)
> Dear all,
Has anyone got the email addresses etc of the authors of the LiU
Archetype Editor?
I would like to get in touch with them as I may be able to help with the
code\.
Adam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Suggestion wrt XML Archetypes & Templates](https://discourse.openehr.org/t/suggestion-wrt-xml-archetypes-templates/14714)
> Dear All,
1\) Problem statement
2\) Solution
3\) Points to Note
4\) XSLT Sheet
5\) Summary
1\) Problem statement
I have been writing an OpenEHR publishing & QA routine which is basically Ant, which includes running XSLT tasks for the NHS\.
There is a problem with the current structure of the XML archetypes & templates which is that the values are contained as a text\(\) child of an element & sometimes as the text\(\) child of a value child of the element\.
This is dangerous...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[310] adjusted a few testcases due to changed TerminologyServiceAccess interface](https://discourse.openehr.org/t/310-adjusted-a-few-testcases-due-to-changed-terminologyserviceaccess-interface/12664)
> Revision: 310
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[309] adjusted adl-paser to include newly added mini-termserv component](https://discourse.openehr.org/t/309-adjusted-adl-paser-to-include-newly-added-mini-termserv-component/12662)
> Revision: 309
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[308] adjusted testcases due to changes in TerminologyAccess interface](https://discourse.openehr.org/t/308-adjusted-testcases-due-to-changes-in-terminologyaccess-interface/12657)
> Revision: 308
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[307] fixed issues in DvOrdered and openehr codes related validation in several classes](https://discourse.openehr.org/t/307-fixed-issues-in-dvordered-and-openehr-codes-related-validation-in-several-classes/16010)
> Revision: 307
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[306] initial import of minimum terminology service component](https://discourse.openehr.org/t/306-initial-import-of-minimum-terminology-service-component/16009)
> Revision: 306
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Null Flavours, boolean values in openEHR](https://discourse.openehr.org/t/null-flavours-boolean-values-in-openehr/14702)
> As a result of a conversation with John Arnett at NHS CfH and others on the
soomewhat controversial topic of Null flavours, I have started a short wiki
page on the topic at
http://www.openehr.org/wiki/display/spec/Null+Flavours+and+Boolean+data+in+openEHR
Feel free to comment\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [PACS reporting system](https://discourse.openehr.org/t/pacs-reporting-system/16006)
> Hi, I'm working en develop a reporting software for a PACS system\.
My questios is, exist archetypes for a reporting of RX, RMI ?
Thank you
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [some possible problems with ADL-parser](https://discourse.openehr.org/t/some-possible-problems-with-adl-parser/16658)
> Below are some strings which return an exception in the parser, I would
appreciate if someone shortly comments on that\.
\(for readability I parted the email in "case 1" etc\.\)
Thanks
Bert Verhees
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [components in action and services](https://discourse.openehr.org/t/components-in-action-and-services/16008)
> Hello to all.
I dont know if all of you are subscribers of the tech list. So Ill present myself again:
Im a psychologist from Brazil and Im ahead of the GestorPsi Project ([www.gestorpsi.com.br](http://www.gestorpsi.com.br))
We will develop a management system for psychology services.
The system will be opensource
After knowing openEHR the only thing I want is to develop GestorPsi as an openEHR system.
The problem is that we have a close dead line (for the admin part of the system) and...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Pulmonary function Tests](https://discourse.openehr.org/t/pulmonary-function-tests/14901)
> Hi\!
I am an intern in respiratory medicine in Athens\-Greece\. I've seen the list of archetypes and i did not see one about pulmonary function tests \(spirometry\)\. Is an archetype about it going on? If not how can i help?
thanks\!
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [406] AWB-63: In the Options dialog, provide an option to display the ADL source without line numbers.](https://discourse.openehr.org/t/ref-impl-eiffel-406-awb-63-in-the-options-dialog-provide-an-option-to-display-the-adl-source-without-line-numbers/16005)
> Revision: 406
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ref_impl_ruby](https://discourse.openehr.org/t/ref-impl-ruby/14699)
> Dear all
We launched ref\_impl\_ruby project in August 2007 in Japan\. Now, we
succeeded in implementation of ADL parser\. The bellow URL shows detail
of the project\.
http://www.openehr.jp/wiki/Ruby%20reference%20implementation
Ruby is a smart and powerful object oriented script language, which
takes less effort to programming\. I believe that Ruby implementation
will enhance the availability of openEHR well\.
We have many module to implement to openEHR environment, but members are
not...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[305] changed the separator separator to comma in datetime value parsing](https://discourse.openehr.org/t/305-changed-the-separator-separator-to-comma-in-datetime-value-parsing/16657)
> Revision: 305
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[304] allow one or two digits for fractional seconds](https://discourse.openehr.org/t/304-allow-one-or-two-digits-for-fractional-seconds/12656)
> Revision: 304
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Compact XML format...?](https://discourse.openehr.org/t/compact-xml-format/14705)
> Hi\!
During Medinfo2007 I believe Ocean Informatics presented a compact XML
format for interchange of predefined information snippets that was
used for integration purposes\. I do not believe it was based on the
official RM\-schemas that cover everything but instead a compact form
for a specific purpose \(e\.g\. using a specific template or set of
archetypes\)\. Does anybody understand what I am referring to or was I
just dreaming?
Could somebody please send a snippet with an example of...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [se.acode.openehr.parser.ParseException: Encountered "precision" at line 92, column 25](https://discourse.openehr.org/t/se-acode-openehr-parser-parseexception-encountered-precision-at-line-92-column-25/16000)
> Should I report more errors?
All these errors do not occur in the adl\_workbench
regards
Bert
archetype:
archetypes/dev/adl/test/clinical\_types/adl\-test\-entry\.c\_dv\_quantity\.draft\.adl
se\.acode\.openehr\.parser\.ParseException: Encountered "precision" at line
92, column 25\.
Was expecting one of:
"units" \.\.\.
"units"...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [One more](https://discourse.openehr.org/t/one-more/13195)
> I saved a few, sorry to have send the previous errors in separate
messages before, it was not my purpose to make a lot of noise\.
same archetype, lines containing :
time\_attr6 matches \{|00:00:59,0|\}
date\_time\_attr2 matches \{yyyy\-mm\-ddThh:mm:??; 1995\-03\-17T12:01\}
date\_time\_attr3 matches \{yyyy\-mm\-ddThh:mm:XX; 1995\-03\-17T12:01\}
date\_time\_attr4 matches \{yyyy\-mm\-ddThh:??:XX; 1995\-03\-17T12:01\}
date\_time\_attr5 matches \{yyyy\-??\-??T??:??:??;...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [another possible error in ADL-parser?](https://discourse.openehr.org/t/another-possible-error-in-adl-parser/12654)
> It is the same archetype, as previous mail, but the line\-number below is
not correct,
this is the line: time\_attr5 matches \{|22:00:05,0|\}
regards
Bert Verhees
se\.acode\.openehr\.parser\.ParseException: Encountered "| 22:00:05 ," at
line 412, column 69\.
Was expecting one of:
"use\_node" \.\.\.
<SYM\_ALLOW\_ARCHETYPE> \.\.\.
"c\_dv\_quantity"...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Possible error in ADL-parser](https://discourse.openehr.org/t/possible-error-in-adl-parser/12655)
> This is the archetype in which the error occurs
archetypes/dev/adl/test/basics/adl\-test\-entry\.assumed\_types\.draft\.adl
regards
Bert Verhees
se\.acode\.openehr\.parser\.ParseException: Encountered "1995" at line 51,
column 49\.
Was expecting:
<V\_DATE>...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [405] AWB-62: Fix a void reference exception in SPLASH_WINDOW, caused by revision 404.](https://discourse.openehr.org/t/ref-impl-eiffel-405-awb-62-fix-a-void-reference-exception-in-splash-window-caused-by-revision-404/16002)
> Revision: 405
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [editorial workflow](https://discourse.openehr.org/t/editorial-workflow/12650)
> Dear Helma
have been talking with Sergio Carmona about the update process of the website. Currently, update is completely live, which is convenient, but could also be dangerous, for obvious reasons.
It would be desirable to allow multiple people to work on the site, particularly for translation purposes and to have something like the following controls, to prevent us from publishing dumb mistakes - they do happen!
- define groups of users, e.g. openehr.cl group, openehr.jp group
- each...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR wiki rich text editor working now](https://discourse.openehr.org/t/openehr-wiki-rich-text-editor-working-now/16001)
> There was a problem preventing the rich text editor plug\-in on the
openEHR wiki \(http://www.openehr.org/wiki) from working\. This has now
been fixed by resident wizard Anthony Peacock at UCL, and all the
plug\-ins now work on the wiki\.
\- thomas bele
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetype](https://discourse.openehr.org/t/archetype/15745)
> Is there somewhere an archetype available for testing purposes, which
has all/many possible item\-kinds in it?
If there is not, I shall make one, does someone want to have it?
Bert
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Setting up openehr.cl dns](https://discourse.openehr.org/t/setting-up-openehr-cl-dns/14701)
> Hi George,
That is what I thought\.
In which case, www\.openehr\.org will be synonomous with www\.openehr\.cl\. And can be ignored in the discussions about URLs for Daisy\.
The way Daisy works is that each 'site' has a top level directory, which is used in the URL\. Only one of those directories can be rewritten by the Apache front end to remove the directory\.
So, /openehr/ is rewritten so that all public URLs appear as /\.
However, any other sites in Daisy will require their...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] adl_workbench for Linux](https://discourse.openehr.org/t/ref-impl-eiffel-adl-workbench-for-linux/14700)
> The code written bij Ocean, compiled for Linux, can be downloaded here
http://www.rosa.nl/_downloads/adl_workbench.gz
Take care, many browsers try to open a \*\.gz, you should download it, not
open it in a browser\.
Just put it somewhere on your computer, decompress it with gunzip, do
chmod 755 to make it executable, and ready you are\.
Please report back if it works for you, I tested it on a KDE desktop\.
kind regards
Bert Verhees
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [On translating openEHR.org to openEHR.cl](https://discourse.openehr.org/t/on-translating-openehr-org-to-openehr-cl/16650)
> Hi all, some of you may already know I'm translating, with the help of a few fellow chileans, openEHR.org to spanish as well as writing some information pages for the chilean/latin american community.
So far, so good. It's been a bit tricky using the Daisy interface, but I've found a few bugs or glitches in this process, while I'm reading a page and I try to go to the variants tab and go to my new translated version I get the following error (it's long, sorry about that)
# ErrorPath not...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [404] AWB-13: Many improvements to the handling of repository path names:](https://discourse.openehr.org/t/ref-impl-eiffel-404-awb-13-many-improvements-to-the-handling-of-repository-path-names/13192)
> Revision: 404
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Question about site](https://discourse.openehr.org/t/question-about-site/14697)
> Helma,
would there be a way to create a query that would show the latest
changed / added pages to the website \- in a form that would look ok on
the home page\.\.\.\.\.maybe it can't be automated, since we wouldn't want to
list pages with just a typo fixed\.\.\.\.any ideas? Otherwise we have no
easy way of showing on teh website what has been added\.\.\.or
substantially changed\.\.\.
anyone else have thoughts on this?
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [BRIDG](https://discourse.openehr.org/t/bridg/14704)
> Is this to be taken any notice of:
http://www.bridgmodel.org/
?
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [invariants of datatypes.quantity.DvOrdered](https://discourse.openehr.org/t/invariants-of-datatypes-quantity-dvordered/15999)
> Hi Sergio,
Thanks for the report, please find my comments below.
> Hi,
>
> I have the following observations regarding class DvOrdered:
>
> 1) Method isNormal() checks only if normalRange contains current DvOrdered, but omits the situation where normalStatus is present.
>
> One possibility is to change the method implementation to:
>
> public boolean isNormal() {
>
> return ((normalRange == null) ? false : getNormalRange().has(this)) ||
>
> ((normalStatus == null) ? false :...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New paper on archetypes](https://discourse.openehr.org/t/new-paper-on-archetypes/16003)
> The following paper on archetypes and clinical data sets was recently published.
- __Expressing Clinical Data Sets with *open*EHR Archetypes: A Solid Basis for Ubiquitous Computing.__ ([IJMI Link](http://www.ijmijournal.com/article/PIIS1386505607000457/abstract))
- Garde S, Hovenga E, Buck J, Knaup P
- _*International Journal of Medical Informatics.*_ 76 (S3): _*S334-S341.*_
- *Abstract*:
*Purpose:* The purpose of this paper is to analyse the feasibility and usefulness of expressing...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [where to start?](https://discourse.openehr.org/t/where-to-start/14696)
> Hello\!
Im a psychologist from Brazil and ahead of a project to develop a
management system for psychology services\. www\.gestorpsi\.com\.br
The project is being sponsored by FAPESP, a public research agency in
São Paulo, Brazil
The system will manage the administrative tasks as well as the clinical
and research tasks involving psychology services\.
The system will be free software and it will be possible to incorporate
other clinical practices on it
We are about to begin the construction...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [possible HL7 / openEHR FAQ for the website](https://discourse.openehr.org/t/possible-hl7-openehr-faq-for-the-website/12658)
> I get asked the question that prompted this post I made some time ago. Should it become an FAQ and/or be added to the pages about standards (that are very out of date)?
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [403] EDT-145: Update a link on the project page, broken by the previous revision.](https://discourse.openehr.org/t/ref-impl-eiffel-403-edt-145-update-a-link-on-the-project-page-broken-by-the-previous-revision/12653)
> Revision: 403
Author: peter\.gummer
Log Message:
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [My persistence 'FAQ'](https://discourse.openehr.org/t/my-persistence-faq/14698)
> Dear all,
enough people seem to want to read my persistence page that was under
the FAQ section of the old site\. It is not really an FAQ\. It is really
material for a paper and proper research, but I decided to pubish it
anyway on teh web\. Question is: if I move it to the new web, where does
it go?
Resources > \.\.\.\.?
Tutorial? Not really\. Do we need a new group for material that is just
'published' on the web?
\- thomas
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [402] EDT-145: Rename adl_dotnet_lib.dll to OceanInformatics.AdlParser.dll, to conform to .NET naming conventions.](https://discourse.openehr.org/t/ref-impl-eiffel-402-edt-145-rename-adl-dotnet-lib-dll-to-oceaninformatics-adlparser-dll-to-conform-to-net-naming-conventions/12652)
> Revision: 402
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [401] made a copy](https://discourse.openehr.org/t/ref-impl-eiffel-401-made-a-copy/13180)
> Revision: 401
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Persistence in openEHR](https://discourse.openehr.org/t/persistence-in-openehr/16004)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Discussion on persistence](https://discourse.openehr.org/t/discussion-on-persistence/14692)
> The interesting discussion about database persistence layers for EHRs minds me to point the group to my PhD student Tony Austin's research, which underpinned the current CHIME clinical cardiology record and decision support system demonstrators, based on our precursor work to openEHR, in the EU GEHR and Synapses projects.
The thesis can be accessed...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openehr system validation](https://discourse.openehr.org/t/openehr-system-validation/14684)
> So regardless of data persistence \(which is an implementation detail
and a software engineering choice independent of OpenEhr\) how can we
test the compliance of an OpenEHR system?
CCHIT developed inter\-operability tests \(I believe\)\.
Can we do the same? Can we have say a template that reflects the
context of data and have OpenEHR systems demonstrate their display or
data entry?
Or perhaps a set of data and a set of AQL queries that should all
return the same results?
Some kind of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Antw: Re: {Disarmed} Antw: Call For Participation in HIT Definitions Work Gro...](https://discourse.openehr.org/t/antw-re-disarmed-antw-call-for-participation-in-hit-definitions-work-gro/13178)
> In een bericht met de datum 7-11-2007 20:25:21 West-Europa (standaardtijd), schrijft hammo001@mc.duke.edu:
One of Ed's famous quotes is: "standards, there are so many to choose from"
We could add: "EMR defenitions, there are too many to choose from"
I usually say we have about 6 billion definitions of EMR / EHR / PHR. Each person living on this planet defines his own record :-)
> I agree with that concern. I will be even more concerned if the
> definitions are different - particularly the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [{Disarmed} Antw: Call For Participation in HIT Definitions Work Groups](https://discourse.openehr.org/t/disarmed-antw-call-for-participation-in-hit-definitions-work-groups/14682)
> In een bericht met de datum 7-11-2007 18:41:26 West-Europa (standaardtijd), schrijft ed.dodds@gmail.com:
Can anyone explain me why this is NOT a duplication of efforts with ongoing ISO - CEN - OpenEHR - HL7 - IHE work?
> [Call For Participation in HIT Definitions Work Groups](http://edodds.blogs.com/conmergence/2007/11/call-for-partic.html)
>
> Under the direction of management and technology consulting firm BearingPoint, Inc. (NYSE: BE), The National Alliance for Health Information...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Call For Participation in HIT Definitions Work Groups](https://discourse.openehr.org/t/call-for-participation-in-hit-definitions-work-groups/12651)
> ### [Call For Participation in HIT Definitions Work Groups](http://edodds.blogs.com/conmergence/2007/11/call-for-partic.html)
Under the direction of management and technology consulting firm BearingPoint, Inc. (NYSE: BE), The National Alliance for Health Information Technology (Alliance) is working with the Office of the National Coordinator for Health Information Technology (ONC) to engage health care stakeholders in a participatory process to define key health IT terms.
The first step is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Exchanging codified content via HL7](https://discourse.openehr.org/t/exchanging-codified-content-via-hl7/12649)
> So I have completed a first pass at parsing the OpenEHR content,
extracting some initial information I would import into to my
application\. More work to be done but if you look at this text file
as a preliminary output from the process:
http://www.patientos.org/forum_temp/openehr.txt
My question is if I send the information out via HL7 in say OBX
segments, what 'code' would I assign to the data elements\.
For example if my message is sending the 'Anaesthetic evaluation...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - ['width' in Interval_Event](https://discourse.openehr.org/t/width-in-interval-event/14685)
> All,
I originally posted this on the Implementers list but did not receive a
response so I will post it here as well and see if anyone/everyone
thinks as I do that this should be considered a typo and not a change in
the model\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML versions of the ADL](https://discourse.openehr.org/t/xml-versions-of-the-adl/14688)
> In writing some code to parse the XML to populate my database I notice
there is not always a matching XML on subversion for a given ADL\.
For example there is
http://svn.openehr.org/knowledge/archetypes/dev/adl/openehr/ehr/entry/observation/openEHR-EHR-OBSERVATION.blood_pressure.v1.adl
http://svn.openehr.org/knowledge/archetypes/dev/xml/openehr/ehr/entry/observation/openEHR-EHR-OBSERVATION.blood_pressure.v1.xml
but not an XML...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [BP cuff sizes](https://discourse.openehr.org/t/bp-cuff-sizes/14687)
> Hi all,
Advice from clever clinicians please:
In OBSERVATION.blood_pressure.v1 BP cuff sizes are currently:
· Neonatal
· Paediatric
· Adult
· Wide adult
· Thigh
I’m wondering if they should be slightly different ie:
· neonatal,
· infant,
· child and/or paediatric,
· small adult,
· adult, and
· large adult (or thigh) cuff
Can anyone clarify for me?
Thanks
Heather
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Pls add me also in the list](https://discourse.openehr.org/t/pls-add-me-also-in-the-list/12644)
> Sir,
I am a java professional working on healthcare Domain .
Please include me also in above group.
Thanks
Husain Abdul Hameed .
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[303] added Sebastian as author; some minor cosmetic changes on the code](https://discourse.openehr.org/t/303-added-sebastian-as-author-some-minor-cosmetic-changes-on-the-code/15998)
> Revision: 303
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[302] added support and testcases for serializing empty CDvQuantity and CCodePhrase](https://discourse.openehr.org/t/302-added-support-and-testcases-for-serializing-empty-cdvquantity-and-ccodephrase/15997)
> Revision: 302
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[301] fixed broken test classes due to changed TerminologyAccess interface](https://discourse.openehr.org/t/301-fixed-broken-test-classes-due-to-changed-terminologyaccess-interface/15996)
> Revision: 301
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[300] fixed borken TestTerminologyAccess due to changed interface](https://discourse.openehr.org/t/300-fixed-borken-testterminologyaccess-due-to-changed-interface/15995)
> Revision: 300
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[299] minor change for code clarity and updated testcase for empty CDvOrdinal](https://discourse.openehr.org/t/299-minor-change-for-code-clarity-and-updated-testcase-for-empty-cdvordinal/15994)
> Revision: 299
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR queries](https://discourse.openehr.org/t/openehr-queries/14680)
> Hi,
Somewhere I recall reading that there was an OpenEHR query that
theoretically an OpenEHR compliant system could execute a return
results for\.
Is there a spec somewhere, preferably with a simple example\.
So if someone knew my patient and queried for all instances of
Respiratory Rate greater than n?
openEHR\-EHR\-OBSERVATION\.respiration\.v1\.adl
Rate at0004 > n
Units /min \(is that a default or are the units passed in the query\)
Or is this future...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[298] Added serialisation support for empty CDvOrdinal](https://discourse.openehr.org/t/298-added-serialisation-support-for-empty-cdvordinal/13164)
> Revision: 298
Author: sebastian\.garde
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR website and wiki are now live](https://discourse.openehr.org/t/new-openehr-website-and-wiki-are-now-live/12636)
> Dear all,
NEW TODAY\.\.\.
we have launched the new openEHR website, at http://www.openEHR.org \. We
hope this new site provides an improved experience for the community
over the old one\. It will allow us to more efficiently respond to your
needs, in terms of new and better information\.
You will notice a link on the website pointing to the new Wiki, which is
at http://www.openehr.org/wiki \. This will provide a place to have
discussions, and particularly to record the outcome of some of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Congraturation to our new Web site](https://discourse.openehr.org/t/congraturation-to-our-new-web-site/14683)
> Now, we can access our new web site\. It is very smart and cool\.
Though, it seems to me that took some difficulty and troubles, the web
team has successfully finished to establish this site\.
I praise and appliciate this great work on web team\. Thank you\!
And please take care of yourself\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [demographic archetypes](https://discourse.openehr.org/t/demographic-archetypes/14690)
> Hi all,
Which archetypes are best to use for demographic\-purposes\. I found the
ones in knowledge/archetypes/dev/adl/openehr/demographic but they seem
uncomplete to me\. I found an archetypeslot to
openehr\-list\_s\.person\_name\.\*, but then I cannot find that archetype\. SO
what can I do best, to build demographic datacollection?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [398] Correct an incorrect regular expression that had been replicated across all of the .ecf files.](https://discourse.openehr.org/t/ref-impl-eiffel-398-correct-an-incorrect-regular-expression-that-had-been-replicated-across-all-of-the-ecf-files/12641)
> Revision: 398
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [397] Fix incorrect export statuses that were preventing a couple of classes from compiling.](https://discourse.openehr.org/t/ref-impl-eiffel-397-fix-incorrect-export-statuses-that-were-preventing-a-couple-of-classes-from-compiling/12640)
> Revision: 397
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] ADLworkbench in Linux](https://discourse.openehr.org/t/ref-impl-eiffel-adlworkbench-in-linux/14681)
> I have it running, the Eiffel Studio 6\.0 for Linux, the workbench
compiles and opens single archetypes
Everything looks good and the application is stable\. It is a wonder how
code can run multi\-platform\. Bravo\!
So this is all fine\. There is only some small problems\.
1\) I am not able to set the reference\-repository\. I try to set it to
/home/verhees/OpenEhr/knowledge/archetypes/
That is where my SVN\-archetypes directory is\.
2\) There is a mousepointer missing in the compiled...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [395] There were two ARCHETYPE_COMPARATOR classes, neither of which is used yet.](https://discourse.openehr.org/t/ref-impl-eiffel-395-there-were-two-archetype-comparator-classes-neither-of-which-is-used-yet/15993)
> Revision: 395
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[297] fixed a bug in a error message generating method in IntervalTest; added a missing method to TerminologyAccess](https://discourse.openehr.org/t/297-fixed-a-bug-in-a-error-message-generating-method-in-intervaltest-added-a-missing-method-to-terminologyaccess/13154)
> Revision: 297
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[ADL-Serialiser] C_DV_ORDINAL](https://discourse.openehr.org/t/adl-serialiser-c-dv-ordinal/14686)
> Hi
in
http://svn.openehr.org/knowledge/archetypes/dev/adl/openehr/ehr/entry/ob
servation/openEHR\-EHR\-OBSERVATION\.pre\_operative\.v1draft\.adl
The
C\_DV\_ORDINAL <
>
in Element\[at0005\]
is that legal ADL?
If yes \- the ADL\-Serialiser needs to be updated as it causes a null
pointer exception \(I could probably do this\)
if not \- could or should that archetype be fixed?
Cheers
Sebastian
Dr Sebastian Garde
Dr\. sc\. hum\., Dipl\.\-Inform\. Med, FACHI
Faculty of Business and...
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [openEHR web (last?) URI makeover...](https://discourse.openehr.org/t/openehr-web-last-uri-makeover/13152)
> Time to start using this list\.\.\.\.
Erik Sundvall wrote:
> Hi\!
>
> I have made some comments regarding URI structure with the intention
> to get some debate going, and some discussions have taken place\.
>
> This is a last\(?\) attempt at being of help for a somewhat futureproof
> and good\-looking URI space for openEHR\. The intention is not to be
> mean to anybody\.\.\. Seems like people are pressed by a deadline and
> concrete suggestions might then be better than trying to speak in
>...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Comments about the rm implementation](https://discourse.openehr.org/t/comments-about-the-rm-implementation/12635)
> Hello everybody,
I am new to this list.
I have been studying openEhr specifications and the corresponding java implementation and have some comments about the reference model implementation
I exchanged e-mails with Rong Chen who asked me to post them to the list so that everyone could see and comment on them.
I think that it will be more effective to post some at a time.
I will start with the support package.
**support.basic.IntervalTest**
private String testString(int[] row) {
return...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Evaluation Archetypes and assessment protocol](https://discourse.openehr.org/t/evaluation-archetypes-and-assessment-protocol/14689)
> Dear all,
From the lengthy and educative discussions on this mail list, the last couple of weeks, the following occurred to me:
- observations are to do with gathering evidence
- an evaluation is an activity of comparing data to a knowledge base (and draw a conclusion based on that comparison (SV))
(Both excellent definitions provided by Thomas Beale)
The other thing that occurred to me is that the ‘assessment’ of data quality is an evaluation too, based on a knowledge base, which...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [394] AWB-14: Implement the Build Subtree and Rebuild Subtree options under the Repository menu.](https://discourse.openehr.org/t/ref-impl-eiffel-394-awb-14-implement-the-build-subtree-and-rebuild-subtree-options-under-the-repository-menu/15992)
> Revision: 394
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[296] added a testcase for two new functions in ArchetypeTerm](https://discourse.openehr.org/t/296-added-a-testcase-for-two-new-functions-in-archetypeterm/15990)
> Revision: 296
Author: rong\.chen
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [new openEHR website - changeover period](https://discourse.openehr.org/t/new-openehr-website-changeover-period/15991)
> Dear all,
we are in the process of switching the existing openEHR\.org website to a
new one\. We expect the change to be completed in the next 24h or so\.
During that time, due to necessary re\-arrangements of some file
resources, some links on the existing website may not work during this
period\. Please bear with us, everything should be available from the new
website when it is up\.
Thanks for your patience,
\- thomas beale
**[openEHR.org Website (archive)](https://discourse.openehr.org/c/openehr-org-website-archive/160)** - [Welcome to the "Openehr-web" mailing list](https://discourse.openehr.org/t/welcome-to-the-openehr-web-mailing-list/12638)
> Welcome to the Openehr\-web@openehr\.org mailing list\!
To post to this list, send your email to:
openehr\-web@openehr\.org
General information about the mailing list is at:
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-web
If you ever want to unsubscribe or change your options \(eg, switch to
or from digest mode, change your password, etc\.\), visit your
subscription page...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [possible getParent-error in parser?](https://discourse.openehr.org/t/possible-getparent-error-in-parser/15987)
> PERSON: /
0 identities: /identities \-> CMultipleAttribute
1 \*PARTY\_IDENTITY\*: /identities\[at1\] \-> CComplexObject \->
parent: null
2 name: /identities\[at1\]/name \-> CSingleAttribute
I query the objects/attributes of an archetype and print the result\.
I get for the object\-class PARTY\_IDENTITY that it has no parent\.
Shouldn't the parent be "identities"
Or do I misunderstand something?
I used the latest source\-version of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [393] AWB-14: Implement the Build | Interrupt menu option.](https://discourse.openehr.org/t/ref-impl-eiffel-393-awb-14-implement-the-build-interrupt-menu-option/12637)
> Revision: 393
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[295] 1.](https://discourse.openehr.org/t/295-1/12634)
> Revision: 295
Author: sebastian\.garde
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[294] minor project page change](https://discourse.openehr.org/t/294-minor-project-page-change/15988)
> Revision: 294
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [392] AWB-15.](https://discourse.openehr.org/t/ref-impl-eiffel-392-awb-15/13139)
> Revision: 392
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [getting the concept name](https://discourse.openehr.org/t/getting-the-concept-name/14691)
> Hi,
I am trying to get the \(full\!\) concept name for a parsed archetype\.
The best I can come up with is:
String conceptName="";
List<ArchetypeTerm> terms =
myArchetype\.getOntology\(\)\.getTermDefinitionsList\(\)\.get\(0\)\.getDefinitions
\(\);
for \(int i=0; i< terms\.size\(\); i\+\+\) \{
if \(terms\.get\(i\)\.getCode\(\)\.equals\(myArchetype\.getConcept\(\)\)\) \{
conceptName=...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [identifying and organizing of archetypes](https://discourse.openehr.org/t/identifying-and-organizing-of-archetypes/16649)
> What is the unique identifier for each archetype?
I assume it is the id
e\.g\. openEHR\-EHR\-OBSERVATION\.blood\_pressure\.v1
but is there no URI that I could always resolve to get the definition\.
For instance the NHS templates refer to an the ID but how do I know
where to go to get that?
The organization of the archectypes is currently by action,
evaluation, instruction, observation etc\. \- is that the only defined
organization \(versus breaking it out by domain e\.g\. vital...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [391] EDT-30: In Archetype Editor, deleting the references from the Description tab did not work because RESOURCE_DESCRIPTION.add_other_detail requires that the value be non-empty, but RESOURCE_DESCRIPTION provides no procedure for remov](https://discourse.openehr.org/t/ref-impl-eiffel-391-edt-30-in-archetype-editor-deleting-the-references-from-the-description-tab-did-not-work-because-resource-description-add-other-detail-requires-that-the-value-be-non-empty-but-resource-description-provides-no-procedure-for-remov/12633)
> Revision: 391
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[293] - Modified adl.jj to ignore a UTF-8 BOM (Byte Order Mark) as created by some Windows Editors for UTF-8 encoded files and not correctly handled by Java.](https://discourse.openehr.org/t/293-modified-adl-jj-to-ignore-a-utf-8-bom-byte-order-mark-as-created-by-some-windows-editors-for-utf-8-encoded-files-and-not-correctly-handled-by-java/15985)
> Revision: 293
Author: sebastian\.garde
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [parsing templates](https://discourse.openehr.org/t/parsing-templates/14673)
> Hi,
More basic questions\.\.\.
The Archetype\-Editor is great for defining archetypes for technical
users\. I am looking to leverage templates and archetype content but
provide a simple to use front end\.
The user would go through iterations of searching and selecting
content, adding it to what would be their own template \- or at least
something I can persist without losing the archetype hierarchy\.
Looking at the oet template files...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Interfaces and Templates](https://discourse.openehr.org/t/interfaces-and-templates/14674)
> Sorry, I meant to start a new thread, not hijack\. Let me do it now\.
A couple more questions \(by the way Leslies description was awesome
and makes total sense\)\.
Interfaces
a\) When creating a generic outbound or inbound interface with an
extrernal system \- do you build based upon the archetypes only \- i\.e\.
provide as many values possible? or your specializations? or is this
all mute and we stick with HL7?
Templates, as a collection for a use case\. I looked out in...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Welcome 4 new committers to the Java project](https://discourse.openehr.org/t/welcome-4-new-committers-to-the-java-project/12632)
> Dear all,
I am delighted to announce that we will have 4 new committers to the Java project and please join me in welcoming Thilo Schuler, Helma van der Linden, Sebastian Garde and Lisa Thurston!
All of them have been openEHR implementer for quite long time and in different ways helping out the Java project. So their names won't be unfamiliar to you if you have been on this list for a while. As a delayed update on the openEHR implementation tutorial/workshop at Medinfo, the Java project...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [2 Ref_impl_java moderator request(s) waiting](https://discourse.openehr.org/t/2-ref-impl-java-moderator-request-s-waiting/16656)
> The Ref\_impl\_java@openehr\.org mailing list has 2 request\(s\) waiting
for your consideration at:
http://lists.chime.ucl.ac.uk/mailman/admindb/ref_impl_java
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending subscriptions:
edgars\.roze@gmail\.com Tue Oct 16 11:44:47 2007
caultonpos@gmail\.com \(Greg Caulton\) Thu Oct 18 17:01:50 2007
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Parsing of UTF-8 archetypes](https://discourse.openehr.org/t/parsing-of-utf-8-archetypes/14671)
> Dear all,
Ever tried to parse a UTF\-8\-encoded archetype with the Java ADL Parser?
If it worked you were probably lucky to have the 'right' UTF\-8, i\.e\. one
that does not contain the optional \(i\.e\. legal, yet totally superfluous\)
initial Byte Order Mark \(see
http://en.wikipedia.org/wiki/Byte_Order_Mark \)\.\.\. \(Most Windows tools
like Notepad, Notepad\+\+, Babelpad add this BOM\.\.\.\)
I just learned the hard way that Java InputStreams/Readers insist on
interpreting this...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [dependent evaluations](https://discourse.openehr.org/t/dependent-evaluations/14670)
> Good to see the lists hotting up with some questions\.\.
here is one I have had to ponder recently\.
I have an evaluation being made directly from an observation\.
Specifically \- I have a particular type of athletic session
from which an 'maximum power' number is being derived\.
Whilst the calculation is automatic, the coach is
'evaluating' the automatically generated score before it is
put into the system \(to make sure that the number is
sensible given what he knows of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [software development & starting out](https://discourse.openehr.org/t/software-development-starting-out/14677)
> Hi,
As someone who is an OpenEHR novice can you give me any tips \- there
is so much information on the website it is difficult to know where to
start\.
While I have yet to understand the full potential of the framework, I
would like to start with something simple\.
Suppose a surgeon signs onto my system and wishes to create a new
progress note\. On paper he may have written \(swapping out the <>\)
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MIE2008 openEHR workshops?](https://discourse.openehr.org/t/mie2008-openehr-workshops/15989)
> Hi\!
Is anybody else planning to do openEHR related workshops at MIE2008 in
in Göteborg \(Gothenburg\), Sweden May 25\-28, 2008?
http://www.mie2008.org/
We \(our MI group at Linköping University\) are planning to coordinate a
general openEHR overview workshop targeted towards people unfamiliar
with openEHR\. The MIE workshop will of course be in English, but we
also want to run the same workshop in Swedish since a major Swedish
health IT event "Vitalis" is collocated with...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [1 Ref_impl_java moderator request(s) waiting](https://discourse.openehr.org/t/1-ref-impl-java-moderator-request-s-waiting/15986)
> The Ref\_impl\_java@openehr\.org mailing list has 1 request\(s\) waiting
for your consideration at:
http://lists.chime.ucl.ac.uk/mailman/admindb/ref_impl_java
Please attend to this at your earliest convenience\. This notice of
pending requests, if any, will be sent out daily\.
Pending subscriptions:
edgars\.roze@gmail\.com Tue Oct 16 11:44:47 2007
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [390] AWB-14: Adjust the archetype icons to indicate three possible states (not parsed, parsed but invalid, or compiled) to make them easier to distinguish.](https://discourse.openehr.org/t/ref-impl-eiffel-390-awb-14-adjust-the-archetype-icons-to-indicate-three-possible-states-not-parsed-parsed-but-invalid-or-compiled-to-make-them-easier-to-distinguish/13130)
> Revision: 390
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [389] AWB-14: Delete icon files that I'm about to commit changes to.](https://discourse.openehr.org/t/ref-impl-eiffel-389-awb-14-delete-icon-files-that-im-about-to-commit-changes-to/13128)
> Revision: 389
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Questions on EHR implementation](https://discourse.openehr.org/t/questions-on-ehr-implementation/14668)
> GlobalHealthUSA would like to design and implement an EHR system for their disease management system platform. We would like to use OpenEHR but have the following questions:
1. Can OpenEHR be implemented in a windows(MS) .NET environment?
1. Can OpenEHR be used to develop an ISP version so several doctors can use it?
1. Has any one done such an implementation before, if so is there any web documentation?
1. Can we use our existing SQL 2005(MS) database?
1. Is there an existing client used to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Multiple parents and max number of nested specialized archetypes?](https://discourse.openehr.org/t/multiple-parents-and-max-number-of-nested-specialized-archetypes/14678)
> Hi,
I have a question about the referencing of archetypes in specialization\. And also want to know if there is a limit on the number of specializations of archetypes\.
For example:
A is top level archetype
B is specialization of A
C has to further specialize B
and there is possibility that D also has to further specialize C and so on\.
So in theory all childs have to conform to A\. But the question is in C which archetype will be written in 'specialize' section? A or A & B ?...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [388] AWB-14: Complete the work started in revisions 383 and 384 of adjusting the archetype icons to indicate not parsed, parsed but invalid, or compiled.](https://discourse.openehr.org/t/ref-impl-eiffel-388-awb-14-complete-the-work-started-in-revisions-383-and-384-of-adjusting-the-archetype-icons-to-indicate-not-parsed-parsed-but-invalid-or-compiled/12631)
> Revision: 388
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [387] AWB-13: When the user set the reference repository path to a directory containing some archetypes but no subdirectories, then the repository tree did not show the archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-387-awb-13-when-the-user-set-the-reference-repository-path-to-a-directory-containing-some-archetypes-but-no-subdirectories-then-the-repository-tree-did-not-show-the-archetypes/12630)
> Revision: 387
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [386] When building the repository tree.](https://discourse.openehr.org/t/ref-impl-eiffel-386-when-building-the-repository-tree/12629)
> Revision: 386
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [385] Simplify the main window's handling of keyboard constants.](https://discourse.openehr.org/t/ref-impl-eiffel-385-simplify-the-main-windows-handling-of-keyboard-constants/15984)
> Revision: 385
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [384] AWB-14: Give some graphical feedback while doing this system and lineage-level compiles.](https://discourse.openehr.org/t/ref-impl-eiffel-384-awb-14-give-some-graphical-feedback-while-doing-this-system-and-lineage-level-compiles/15983)
> Revision: 384
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [383] Delete three icon files that I'm about to commit changes to.](https://discourse.openehr.org/t/ref-impl-eiffel-383-delete-three-icon-files-that-im-about-to-commit-changes-to/15982)
> Revision: 383
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [382] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-382-1/15981)
> Revision: 382
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Cervicovaginal smears and Bethesda System 2001](https://discourse.openehr.org/t/cervicovaginal-smears-and-bethesda-system-2001/15572)
> Dear all,
I was wondering if anyone is interested/involved with reporting of cervicovaginal smears. A quite mature and stable micro terminology exists that is aimed to provide effective communication between gynecologist and cyto-pathologists and for reporting of cases: Bethesda System 2001. It had been discussed in 2001 at NCI and published at: [http://bethesda2001.cancer.gov/terminology.html](http://bethesda2001.cancer.gov/terminology.html)
I had modeled it with classical relational...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [381] Fix an obvious programming error, where a BOOLEAN was being compared to Void.](https://discourse.openehr.org/t/ref-impl-eiffel-381-fix-an-obvious-programming-error-where-a-boolean-was-being-compared-to-void/13117)
> Revision: 381
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [380] AWB-14 - Further changes toward differential form of archetypes, and compilation structured tool.](https://discourse.openehr.org/t/ref-impl-eiffel-380-awb-14-further-changes-toward-differential-form-of-archetypes-and-compilation-structured-tool/13115)
> Revision: 380
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [379] Further changes on the way to managing the repository with an ARCHEYTPE_COMPILER, ARCHETYPE_PARSER (this class used to be called ARCHETYPE_COMPILER) and various compilation state objects.](https://discourse.openehr.org/t/ref-impl-eiffel-379-further-changes-on-the-way-to-managing-the-repository-with-an-archeytpe-compiler-archetype-parser-this-class-used-to-be-called-archetype-compiler-and-various-compilation-state-objects/15980)
> Revision: 379
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [378] Add the NSIS script to BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-378-add-the-nsis-script-to-branches-specialisation/12628)
> Revision: 378
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [terminolgoy.xml](https://discourse.openehr.org/t/terminolgoy-xml/16646)
> IMHO following line should contain "Incomplete" with uppercase first
character, for consistency
<Concept Language="en" ConceptID="553" Rubric="incomplete" />
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ObjectReference](https://discourse.openehr.org/t/objectreference/14669)
> Hi,
It is a bit of theoretical question
*(I haven't looked at the Eiffel-code, because Eiffel does not install and run on any of my Linux-machines, and I hate to change the OS because of the Eiffel-IDE. )*
I have some problem with the reference-objects
So in the Java-code there is not any check at creation of a reference model if the object referring to really exists, also there is no check if the type from the (if existing) object is conform the type of the reffering...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [377] In the SConstruct:](https://discourse.openehr.org/t/ref-impl-eiffel-377-in-the-sconstruct/12626)
> Revision: 377
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [376] Revision 372 broke the fix made in revision 367; i.e., opening an ad-hoc archetype at the root of the file system (e.g., C:\x.adl) violated a precondition checking that the archetype's directory was a valid path, because the traili](https://discourse.openehr.org/t/ref-impl-eiffel-376-revision-372-broke-the-fix-made-in-revision-367-i-e-opening-an-ad-hoc-archetype-at-the-root-of-the-file-system-e-g-c-x-adl-violated-a-precondition-checking-that-the-archetypes-directory-was-a-valid-path-because-the-traili/12625)
> Revision: 376
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [375] Fix the build of adl_dotnet_lib, broken by revision 374.](https://discourse.openehr.org/t/ref-impl-eiffel-375-fix-the-build-of-adl-dotnet-lib-broken-by-revision-374/12623)
> Revision: 375
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [374] Rename ARCHETYPE_COMPILER as ARCHETYPE_PARSER, since it deals with only one archetype at a time, whereas a 'compiler' is normally understood to compile a system of artefacts.](https://discourse.openehr.org/t/ref-impl-eiffel-374-rename-archetype-compiler-as-archetype-parser-since-it-deals-with-only-one-archetype-at-a-time-whereas-a-compiler-is-normally-understood-to-compile-a-system-of-artefacts/12621)
> Revision: 374
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [373] Correct a few comments in accord with changes made in revision 372.](https://discourse.openehr.org/t/ref-impl-eiffel-373-correct-a-few-comments-in-accord-with-changes-made-in-revision-372/13108)
> Revision: 373
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [372] Various changes to make ADL workbench treat .adl files as 'flat' files and create .adls files to contain differential form source.](https://discourse.openehr.org/t/ref-impl-eiffel-372-various-changes-to-make-adl-workbench-treat-adl-files-as-flat-files-and-create-adls-files-to-contain-differential-form-source/13107)
> Revision: 372
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EHR-class](https://discourse.openehr.org/t/ehr-class/16645)
> Hi Rong,
I wonder, how can we create an EHR\-object?
We need the ehrAccess which is required, and the EhrAccess needs
AccessControlSettings \(also required\), which is nowhere defined in the
specs \(I think yet to come\)
\(required means, throws an Exception if not there\)
What do you advise for the meantime?
Thanks very much,
kind regards
Bert Verhees
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [371] The SConstruct now generates the units and dadl scanners and parsers.](https://discourse.openehr.org/t/ref-impl-eiffel-371-the-sconstruct-now-generates-the-units-and-dadl-scanners-and-parsers/12620)
> Revision: 371
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [370] Update the Project Page to describe the previous release.](https://discourse.openehr.org/t/ref-impl-eiffel-370-update-the-project-page-to-describe-the-previous-release/12619)
> Revision: 370
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [369] Update the ADL Workbench Help Page to reflect changes that have occurred since the last release.](https://discourse.openehr.org/t/ref-impl-eiffel-369-update-the-adl-workbench-help-page-to-reflect-changes-that-have-occurred-since-the-last-release/12618)
> Revision: 369
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [368] Fix a precondition failure when the user sets the Reference Repository Path to an empty string.](https://discourse.openehr.org/t/ref-impl-eiffel-368-fix-a-precondition-failure-when-the-user-sets-the-reference-repository-path-to-an-empty-string/12617)
> Revision: 368
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] eiffel binaries for linux](https://discourse.openehr.org/t/ref-impl-eiffel-eiffel-binaries-for-linux/14667)
> Thomas,
Is it possible to publish the Linux\-binary for adl\_workshop somewhere?
I tried to install Eiffel56, 57 en 60, on two different computers with
Suse 10\.2\.
It does not compile EiffelVision2, searching the Internet did not help\.
I also tried the Windows\-binary on wine \(Linux\-windows\-emulator\), latest
version, it is fully functional except for one thing, the both list
views do not clean up and are also transparent, so, also not useable\.
The only solution I can think of is...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [367] Opening an ad-hoc archetype at the root of the file system (e.g., C:\x.adl) violated a precondition checking that the archetype's directory was a valid path, because the trailing directory separator was wrongly stripped in order to](https://discourse.openehr.org/t/ref-impl-eiffel-367-opening-an-ad-hoc-archetype-at-the-root-of-the-file-system-e-g-c-x-adl-violated-a-precondition-checking-that-the-archetypes-directory-was-a-valid-path-because-the-trailing-directory-separator-was-wrongly-stripped-in-order-to/15979)
> Revision: 367
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [366] In the SConstruct, instead of executing Visual Studio to build the installer, use an NSIS script.](https://discourse.openehr.org/t/ref-impl-eiffel-366-in-the-sconstruct-instead-of-executing-visual-studio-to-build-the-installer-use-an-nsis-script/12616)
> Revision: 366
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [365] In the SConstruct, allow the command line to specify specific targets within the oe_distrib directory.](https://discourse.openehr.org/t/ref-impl-eiffel-365-in-the-sconstruct-allow-the-command-line-to-specify-specific-targets-within-the-oe-distrib-directory/12615)
> Revision: 365
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [compiling the LiU archtetype editor](https://discourse.openehr.org/t/compiling-the-liu-archtetype-editor/14676)
> I runagianst some errors, I mention them in List, so they can be repaired:
It has to do with external dependencies, which cannot be resolved in the
repositories that are available in the pom\.xml's
I downlaoded the trunk\-version and try to do a: /mvn install/ from the
root of the trunk dir\.
Maybe some errors I should repair at my site\.
Thankyou for any advice
Kind regards
Bert Verhees
now the list of Missing:
Missing:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Sample Code](https://discourse.openehr.org/t/sample-code/13095)
> Hi everyone,
Trying to prove that I am worthy of being a contributor, I am sending a sample code (a simple implementation of the still in development TOM - Template Object Model), to be audited by you.
See ya,
Humberto
[details="(attachments)"]
[openehr-tom.zip|attachment](upload://7poUJXtroBHNFqX2NftHEjych0k.zip) (27.7 KB)
[/details]
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[292] fixed a bug in DvDateTimeParser.parseTime(), the bug occurs when the default timezone is GMT minus; patch contributed by Humberto Naves](https://discourse.openehr.org/t/292-fixed-a-bug-in-dvdatetimeparser-parsetime-the-bug-occurs-when-the-default-timezone-is-gmt-minus-patch-contributed-by-humberto-naves/13094)
> Revision: 292
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in openEHR RM Core](https://discourse.openehr.org/t/bug-in-openehr-rm-core/12613)
> Hi,
I found a bug at org.openehr.rm.datatypes.quantity.datetime.DvDateTimeParser.convertTimeZone(int tzMillis, boolean isExtended), when you invoke with tzMillis = -10800000 (GMT-0300). The correct answer should be "-0300", not "--0300".
Here is the suggested correction (patch)
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[291] updated rm-domain for newly added openehr codeset and terminology group identifiers](https://discourse.openehr.org/t/291-updated-rm-domain-for-newly-added-openehr-codeset-and-terminology-group-identifiers/12612)
> Revision: 291
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[290] added OpenEHRCodeSetIdentifiers and OpenEHRTerminologyGroupIdentifiers](https://discourse.openehr.org/t/290-added-openehrcodesetidentifiers-and-openehrterminologygroupidentifiers/15978)
> Revision: 290
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [I want to contribute](https://discourse.openehr.org/t/i-want-to-contribute/16709)
> Hi Everybody,
I really want to contribute with openEHR Java RI project, and how do
I become a developer?
Thanks,
Humberto
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [363] Corrected two bugs:](https://discourse.openehr.org/t/ref-impl-eiffel-363-corrected-two-bugs/15977)
> Revision: 363
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [362] Fix some weak conditions in archetype validity checking.](https://discourse.openehr.org/t/ref-impl-eiffel-362-fix-some-weak-conditions-in-archetype-validity-checking/13083)
> Revision: 362
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[archetypes.com.au] Functionality to compare two archetypes](https://discourse.openehr.org/t/archetypes-com-au-functionality-to-compare-two-archetypes/14672)
> Dear all,
We have added prototype functionality to the Archetypefinder to compare
two versions/revisions of an archetype at
http://www.archetypes.com.au/archetypefinder/compare.html. This
functionality will later be integrated into the appropriate tools, but
can be useful on its own too\.
You can upload two archetypes and then see what changes have been made
between the two versions of an archetype\. Also, the type of the changes
with regard to compatibility of the two archetypes \(e\.g\....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [361] In the Eiffel builder, use xml.dom rather than a regular expression to scan for clusters in the ECF file.](https://discourse.openehr.org/t/ref-impl-eiffel-361-in-the-eiffel-builder-use-xml-dom-rather-than-a-regular-expression-to-scan-for-clusters-in-the-ecf-file/15976)
> Revision: 361
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [360] AWB-14: Fix a precondition violation in STRING.to_integer, called from ARCHETYPE_ONTOLOGY.update_highest_non_specialised_term_code_index.](https://discourse.openehr.org/t/ref-impl-eiffel-360-awb-14-fix-a-precondition-violation-in-string-to-integer-called-from-archetype-ontology-update-highest-non-specialised-term-code-index/15975)
> Revision: 360
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [359] AWB-14: Fix void target references in ARCHETYPE.remove_inherited_subtrees.](https://discourse.openehr.org/t/ref-impl-eiffel-359-awb-14-fix-void-target-references-in-archetype-remove-inherited-subtrees/12606)
> Revision: 359
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [358] Differential definition section and path map now appears to be correct.](https://discourse.openehr.org/t/ref-impl-eiffel-358-differential-definition-section-and-path-map-now-appears-to-be-correct/12605)
> Revision: 358
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [357] Removal of inherited subtrees now works.](https://discourse.openehr.org/t/ref-impl-eiffel-357-removal-of-inherited-subtrees-now-works/12604)
> Revision: 357
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [356] Added some new archetype comparator and related classes;](https://discourse.openehr.org/t/ref-impl-eiffel-356-added-some-new-archetype-comparator-and-related-classes/12603)
> Revision: 356
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[289] updated adl-serializer due to changes in CObject](https://discourse.openehr.org/t/289-updated-adl-serializer-due-to-changes-in-cobject/12602)
> Revision: 289
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[288] updated adl-parser due to changes in CObject](https://discourse.openehr.org/t/288-updated-adl-parser-due-to-changes-in-cobject/12601)
> Revision: 288
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[287] fixed broken testcases due to changes in CObject](https://discourse.openehr.org/t/287-fixed-broken-testcases-due-to-changes-in-cobject/12600)
> Revision: 287
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[286] made occurrences mandatory in CObject](https://discourse.openehr.org/t/286-made-occurrences-mandatory-in-cobject/13071)
> Revision: 286
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [mandatory occurrences in ADL Parser](https://discourse.openehr.org/t/mandatory-occurrences-in-adl-parser/12609)
> Hi,
In using the ADL Parser, I just want to be sure I got this right:
CComplexObject myNode = <get a node within a parsed archetype from somewhere>;
Interval<Integer> myOccurrences = myNode\.getOccurrences\(\);
Now, if the occurrence is mandatory \(1\.\.1\), myOccurrences will be null as mandatory is the default\. For easier handling I therefore want to set the following in my code before proceeding:
if \(myOccurrence == null\) myOccurrence = new...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Vaccinations](https://discourse.openehr.org/t/vaccinations/12599)
> Dear All
I would like to start a discussion about what we need to record in the EHR about vaccinations in the context of my thoughts about medication instructions. People may have some good references on this matter. It may be appropriate to start a wiki page on this - and medications in general - for the openEHR community?
First, on medications in general. I believe we should have a new activity in the medication order which is review - this can have its own timing and be carried out as...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Implementers' list archives are now visible](https://discourse.openehr.org/t/implementers-list-archives-are-now-visible/12597)
> Dear all,
the page http://www.openehr.org/advice/t_contents.html now provides
access to the 3 implementers' mailing lists \- implementers \(a general
list\), ref\_impl\_eiffel and ref\_impl\_java \- and their archives, which
were previously not visible on the website\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Do we need a new list for commits on the Java project?](https://discourse.openehr.org/t/do-we-need-a-new-list-for-commits-on-the-java-project/11999)
> Dear all,
Recently we have discussed the need for a new dedicated email list for receiving SVN commits on the Java development project. Right now, we only have one common list for both discussions and details of all SVN commits on the java project. It seems to be difficult to follow and find discussions which are mixed with large amount of commits. On the other hand, Thomas suggested one could configure email clients to sort out commits using filters. It is of course some extra work to...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Notice of openEHR.org server downtime](https://discourse.openehr.org/t/notice-of-openehr-org-server-downtime/12598)
> \*\*\*\*\* Notice of openEHR server downtime \*\*\*\*\*
Wed 12th September 2007, 08:00 \- 10:00\.
The openEHR server will be unavailable between 08:00 and 09:00 \(London,
GMT\+1\) on Wednesday 12th Septemebr 2007 for an important hardware
upgrade\. Services should be considered "at risk" until 10:00\.
This will affect the openEHR web site and Subversion services\.
Thanks for your understanding\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Embedded archetypes - should there be any tooling constraints?](https://discourse.openehr.org/t/embedded-archetypes-should-there-be-any-tooling-constraints/14675)
> Dear All
A design issue has arisen from the NHS team as there is a bug in the archetype editor when you try and embed an archetype in the data page. You do this by clicking the embed archetype check box before you choose the structure type (list, tree, table...).
This has traditionally been used to utilise the same structure for ordering as for recording the action as in medication or procedure. It is possible that archetypes could share the same state information (e.g. pulse and blood...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [355] AWB-13: Revision 287 added the class WINDOWS_SHORT_PATH, to ensure that SHARED_RESOURCES.system_temp_file_directory always returned a long path name, rather than an old DOS-style 8.3 tilde-mangled short path name.](https://discourse.openehr.org/t/ref-impl-eiffel-355-awb-13-revision-287-added-the-class-windows-short-path-to-ensure-that-shared-resources-system-temp-file-directory-always-returned-a-long-path-name-rather-than-an-old-dos-style-8-3-tilde-mangled-short-path-name/12594)
> Revision: 355
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [354] AWB-13: Revision 347 installed the new icons into the Application folder rather than the icons folder on Windows.](https://discourse.openehr.org/t/ref-impl-eiffel-354-awb-13-revision-347-installed-the-new-icons-into-the-application-folder-rather-than-the-icons-folder-on-windows/15974)
> Revision: 354
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Device information in the EHR](https://discourse.openehr.org/t/device-information-in-the-ehr/14664)
> Hi Everyone
I have just returned home after many weeks of meetings which have been an extraordinary experience - but one involved a session at the ISO meeting in Brisbane with the devices group and Melvin Reynolds. He is interested in standardising the information we keep about the device as part of the observation protocol.
We have agreed to try and get a standard model (a cluster in openEHR) that we use to record information about the device used to make the observation. It was raised at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MedInfo papers and other new papers](https://discourse.openehr.org/t/medinfo-papers-and-other-new-papers/12595)
> Dear all,
MedInfo 2007 was a great event and full of interesting presentations,
including many openEHR\- and archetype\-related works\.
I have posted MedInfo 2007 paper PDFs and other presentations from
MedIinfo 2007 that I have received at
http://www.openehr.org/publications/conferences/MedInfo2007/t_medinfo_2007.htm
Others are welcome to send their presentations and pre\-publication paper
PDFs \(apparently we can't post the IOS final papers as found in the CD\)
and I will post them...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [353] Fix a precondition violation in SPLASH_WINDOW if the icons directory is missing.](https://discourse.openehr.org/t/ref-impl-eiffel-353-fix-a-precondition-violation-in-splash-window-if-the-icons-directory-is-missing/12593)
> Revision: 353
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[285] added two new abstract subclasses of CObject according to the lastest AOM specs; committed from brisbane medinfo ; )](https://discourse.openehr.org/t/285-added-two-new-abstract-subclasses-of-cobject-according-to-the-lastest-aom-specs-committed-from-brisbane-medinfo/12592)
> Revision: 285
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MedInfo 2007 - presenters can host material on openEHR.org](https://discourse.openehr.org/t/medinfo-2007-presenters-can-host-material-on-openehr-org/12588)
> To all those presenting in MedInfo \(I hope all are now listed at
http://www.openehr.org/t_medinfo_2007.htm) we propose to host
presentations and papers on the openEHR website, if you would find this
useful\. This should be a useful resource for the community and will save
you time having to make multiple personal copies on USB keys, in the
usual way\!
Please forward any material you would like hosted on the site including
the session identifier \(e\.g\. S093\) to me at...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [352] Merge revisions 340-351 from BRANCHES/specialisation into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-352-merge-revisions-340-351-from-branches-specialisation-into-trunk/12591)
> Revision: 352
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [351] Fix a few void reference calls.](https://discourse.openehr.org/t/ref-impl-eiffel-351-fix-a-few-void-reference-calls/12590)
> Revision: 351
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [350] Fix a few void reference calls.](https://discourse.openehr.org/t/ref-impl-eiffel-350-fix-a-few-void-reference-calls/12589)
> Revision: 350
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [MedInfo 2007 - 2 further sessions relating to openEHR & archetypes](https://discourse.openehr.org/t/medinfo-2007-2-further-sessions-relating-to-openehr-archetypes/11996)
> The following two sessions were missed from the previous announcement:
- Wed 22 Aug - *11am* - session S104 - Semantic Issues in Healthdata Classification Chair: Joanne Callen - Room M4
Semantic Issues in Integrating Data from Different Models to Achieve Data Interoperability
Rahil Qamar, Alan Rector
- Thu 23 Aug - 2-3:30pm - Poster P354
Representing clinical knowledge as Archetypes
Knut Bernstein, Mette R Darmer
Please see...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[283] re-arranged test composition generation logic and added two relevant adl files](https://discourse.openehr.org/t/283-re-arranged-test-composition-generation-logic-and-added-two-relevant-adl-files/12587)
> Revision: 283
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[282] init import of openehr-tutorial coding exercise from Singapore =)](https://discourse.openehr.org/t/282-init-import-of-openehr-tutorial-coding-exercise-from-singapore/12586)
> Revision: 282
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [349] Fix some void reference calls.](https://discourse.openehr.org/t/ref-impl-eiffel-349-fix-some-void-reference-calls/12578)
> Revision: 349
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [348] Rename a cluster, consistent with other projects.](https://discourse.openehr.org/t/ref-impl-eiffel-348-rename-a-cluster-consistent-with-other-projects/12576)
> Revision: 348
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Constraints on Participation](https://discourse.openehr.org/t/constraints-on-participation/14659)
> Dear All
We are adding constraints on participation to the Archetype Editor. Participations can be recorded at two levels, the Composition and at the level of the Entry. Remember that the reference model knows who was the author of the composition - which is mandatory. There is a special participation on each entry called provider which is just the identification of the source of the information.
If we see archetypes as the shared maximal data set we never want to constrain something in a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[281] added some more links for required software](https://discourse.openehr.org/t/281-added-some-more-links-for-required-software/12574)
> Revision: 281
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[280] added download links to some pages](https://discourse.openehr.org/t/280-added-download-links-to-some-pages/12573)
> Revision: 280
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[279] another update on the docs](https://discourse.openehr.org/t/279-another-update-on-the-docs/12568)
> Revision: 279
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[278] inserted a project page link to all the documents](https://discourse.openehr.org/t/278-inserted-a-project-page-link-to-all-the-documents/12567)
> Revision: 278
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[277] download page updated with links to latest builds](https://discourse.openehr.org/t/277-download-page-updated-with-links-to-latest-builds/12566)
> Revision: 277
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[276] completed initial integration with EhrService and data can be viewed by EhrViewer, also included jar files and more sample xmls](https://discourse.openehr.org/t/276-completed-initial-integration-with-ehrservice-and-data-can-be-viewed-by-ehrviewer-also-included-jar-files-and-more-sample-xmls/15972)
> Revision: 276
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Java coding exercise on the openEHR Implementation Tutorial and Software Workshop](https://discourse.openehr.org/t/java-coding-exercise-on-the-openehr-implementation-tutorial-and-software-workshop/12565)
> Dear all,
There will be a coding exercise session on The openEHR implementation tutorial and software workshop. It will be about 45 minutes and right after the introduction of the Java Reference Implementation Project. The goal of this coding exercise is to get you familiarized with the core openEHR components and their APIs using the existing open source Java implementation. We will cover the Reference Model, Archetype Model (with the ADL parser) and finally integration using XML and Web...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR at MedInfo 2007 page](https://discourse.openehr.org/t/openehr-at-medinfo-2007-page/12569)
> Further on MedInfo 2007
\* see the home page for the quick summary \- http://www.openehr.org/
\* follow the top link to this page for the details \-
http://www.openehr.org/t_medinfo_2007.htm
This page will be updated during the conference\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[275] fixed a bug in UUID related validation](https://discourse.openehr.org/t/275-fixed-a-bug-in-uuid-related-validation/12564)
> Revision: 275
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[274] added getValue() to TerminologyGroupIdentifier](https://discourse.openehr.org/t/274-added-getvalue-to-terminologygroupidentifier/12563)
> Revision: 274
Author: rong\.chen
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR at MedInfo 2007, Brisbane, Australia](https://discourse.openehr.org/t/openehr-at-medinfo-2007-brisbane-australia/12000)
> For those going to, already at, or interested in the proceedings of MedInfo 2007, there are quite a number of presentations, papers and workshops, as listed below.
The MedInfo website is at [http://www.medinfo2007.org/](http://www.medinfo2007.org/)
**Sun 19** **Aug**
9-1pm - tutorial S001 - Room Great Hall 1
**Electronic health record and telemedicine: Latino American approach (Part A)** [IN SPANISH]
Carola...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[273] added generated src from wsdl since some binding classes required manual adjustment](https://discourse.openehr.org/t/273-added-generated-src-from-wsdl-since-some-binding-classes-required-manual-adjustment/12562)
> Revision: 273
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [347] AWB-13: Fix the icons in the Windows installer project.](https://discourse.openehr.org/t/ref-impl-eiffel-347-awb-13-fix-the-icons-in-the-windows-installer-project/12561)
> Revision: 347
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [346] Fix the SCons Eiffel scanner to work on Unix with .ecf files that, because they were ported from Windows, contain backslashes rather than slashes.](https://discourse.openehr.org/t/ref-impl-eiffel-346-fix-the-scons-eiffel-scanner-to-work-on-unix-with-ecf-files-that-because-they-were-ported-from-windows-contain-backslashes-rather-than-slashes/12560)
> Revision: 346
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [345] Fix the SConstruct to recognise the 'oe_distrib' directory as a command-line target, even if specified with a trailing slash (or, on Windows, backslash).](https://discourse.openehr.org/t/ref-impl-eiffel-345-fix-the-sconstruct-to-recognise-the-oe-distrib-directory-as-a-command-line-target-even-if-specified-with-a-trailing-slash-or-on-windows-backslash/15971)
> Revision: 345
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [344] Correct a couple of comments.](https://discourse.openehr.org/t/ref-impl-eiffel-344-correct-a-couple-of-comments/15970)
> Revision: 344
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[272] updated java project roadmap document](https://discourse.openehr.org/t/272-updated-java-project-roadmap-document/15969)
> Revision: 272
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[271] added medinfo openEHR workshop instructions link to the project page](https://discourse.openehr.org/t/271-added-medinfo-openehr-workshop-instructions-link-to-the-project-page/12559)
> Revision: 271
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[270] updated svn:mime-type of medinfo-workshop page](https://discourse.openehr.org/t/270-updated-svn-mime-type-of-medinfo-workshop-page/12558)
> Revision: 270
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[269] updated svn:mime-type of newly added docs](https://discourse.openehr.org/t/269-updated-svn-mime-type-of-newly-added-docs/12557)
> Revision: 269
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[268] updated project_page](https://discourse.openehr.org/t/268-updated-project-page/12556)
> Revision: 268
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[267] added some new docs to the java project](https://discourse.openehr.org/t/267-added-some-new-docs-to-the-java-project/12555)
> Revision: 267
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [343] Fix a void reference exception, triggered by an empty term_definitions list like this:](https://discourse.openehr.org/t/ref-impl-eiffel-343-fix-a-void-reference-exception-triggered-by-an-empty-term-definitions-list-like-this/12553)
> Revision: 343
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[266] updated xml-serializer due to changes in other components](https://discourse.openehr.org/t/266-updated-xml-serializer-due-to-changes-in-other-components/12552)
> Revision: 266
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[265] fixed a broken testcase in DvTimeTest](https://discourse.openehr.org/t/265-fixed-a-broken-testcase-in-dvtimetest/12551)
> Revision: 265
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[264] minor update to ehr-bank docs](https://discourse.openehr.org/t/264-minor-update-to-ehr-bank-docs/13015)
> Revision: 264
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[263] init import of ehr-bank integration demo project to sandbox branch](https://discourse.openehr.org/t/263-init-import-of-ehr-bank-integration-demo-project-to-sandbox-branch/13014)
> Revision: 263
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[262] create sandbox branch for experimental stuff](https://discourse.openehr.org/t/262-create-sandbox-branch-for-experimental-stuff/13013)
> Revision: 262
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[261] fixed return type of getItems in ItemTable](https://discourse.openehr.org/t/261-fixed-return-type-of-getitems-in-itemtable/12550)
> Revision: 261
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[260] added fromValue() and getValue() to ProportionKind](https://discourse.openehr.org/t/260-added-fromvalue-and-getvalue-to-proportionkind/12549)
> Revision: 260
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[259] corrected accuracy type in DvTemopral and related changes in the subclasses](https://discourse.openehr.org/t/259-corrected-accuracy-type-in-dvtemopral-and-related-changes-in-the-subclasses/12548)
> Revision: 259
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[258] adjusted domain classes due to tppe change of attribute uid in Locatable](https://discourse.openehr.org/t/258-adjusted-domain-classes-due-to-tppe-change-of-attribute-uid-in-locatable/12547)
> Revision: 258
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[257] changes du to type change of attribute uid in Locatable](https://discourse.openehr.org/t/257-changes-du-to-type-change-of-attribute-uid-in-locatable/12546)
> Revision: 257
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[256] updated due to newly added Pathable in rm-core](https://discourse.openehr.org/t/256-updated-due-to-newly-added-pathable-in-rm-core/12545)
> Revision: 256
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[255] added Pathable and adjusted all its subclass in core component](https://discourse.openehr.org/t/255-added-pathable-and-adjusted-all-its-subclass-in-core-component/12544)
> Revision: 255
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [342] These additions now compute the 'inherited subtree list' of an archetype (see routine of that name in ARCHETYPE), which](https://discourse.openehr.org/t/ref-impl-eiffel-342-these-additions-now-compute-the-inherited-subtree-list-of-an-archetype-see-routine-of-that-name-in-archetype-which/12543)
> Revision: 342
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[254] updated due to changes in other modules](https://discourse.openehr.org/t/254-updated-due-to-changes-in-other-modules/12542)
> Revision: 254
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[253] parser updated due to changes in other modules](https://discourse.openehr.org/t/253-parser-updated-due-to-changes-in-other-modules/12541)
> Revision: 253
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[252] updated due to changes in other modules](https://discourse.openehr.org/t/252-updated-due-to-changes-in-other-modules/12538)
> Revision: 252
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[251] renamed some attributes according to the specs](https://discourse.openehr.org/t/251-renamed-some-attributes-according-to-the-specs/12537)
> Revision: 251
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[250] renamed some attributes according to the specs](https://discourse.openehr.org/t/250-renamed-some-attributes-according-to-the-specs/12998)
> Revision: 250
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [341] Merge revisions 273-340 from BRANCHES/specialisation into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-341-merge-revisions-273-340-from-branches-specialisation-into-trunk/12536)
> Revision: 341
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[249] added DvTemporal and adjusted inheritance in datetime package](https://discourse.openehr.org/t/249-added-dvtemporal-and-adjusted-inheritance-in-datetime-package/12535)
> Revision: 249
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [340] AWB-13: Fix a void target reference, caused by a creation routine not satisfying an invariant.](https://discourse.openehr.org/t/ref-impl-eiffel-340-awb-13-fix-a-void-target-reference-caused-by-a-creation-routine-not-satisfying-an-invariant/12534)
> Revision: 340
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [339] AWB-13: Fix void target references when an archetype fails to parse.](https://discourse.openehr.org/t/ref-impl-eiffel-339-awb-13-fix-void-target-references-when-an-archetype-fails-to-parse/12533)
> Revision: 339
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [338] Rework specialisation code in ARCHETYPE_ONTOLOGY, ARCHETYPE, ARCHETYPE_COMPILER, archetype_term_code_tools.](https://discourse.openehr.org/t/ref-impl-eiffel-338-rework-specialisation-code-in-archetype-ontology-archetype-archetype-compiler-archetype-term-code-tools/12532)
> Revision: 338
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[248] adjusted references to renamed identity class](https://discourse.openehr.org/t/248-adjusted-references-to-renamed-identity-class/12531)
> Revision: 248
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[247] added GenericID and UIDBasedID; renamed HierarchicalObjectID to HierObjectID and updated inheritance of HierObjectID and ObjectVersionID](https://discourse.openehr.org/t/247-added-genericid-and-uidbasedid-renamed-hierarchicalobjectid-to-hierobjectid-and-updated-inheritance-of-hierobjectid-and-objectversionid/12530)
> Revision: 247
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[246] added class TemplateID](https://discourse.openehr.org/t/246-added-class-templateid/15968)
> Revision: 246
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[245] added class AccessGroupRef](https://discourse.openehr.org/t/245-added-class-accessgroupref/12984)
> Revision: 245
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[244] updated references to renamed object reference classes](https://discourse.openehr.org/t/244-updated-references-to-renamed-object-reference-classes/12529)
> Revision: 244
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[243] renamed LocatableReference to LocatableRef according to the specs](https://discourse.openehr.org/t/243-renamed-locatablereference-to-locatableref-according-to-the-specs/12528)
> Revision: 243
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[242] renamed PartyReference to PartyRef according to the specs](https://discourse.openehr.org/t/242-renamed-partyreference-to-partyref-according-to-the-specs/12527)
> Revision: 242
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[241] renamed ObjectReference to ObjectRef according to the specs](https://discourse.openehr.org/t/241-renamed-objectreference-to-objectref-according-to-the-specs/12526)
> Revision: 241
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[240] adjusted a domain testcase due to changes in core rm.quantity](https://discourse.openehr.org/t/240-adjusted-a-domain-testcase-due-to-changes-in-core-rm-quantity/15967)
> Revision: 240
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[239] updated rm.quantity package - adjusted inheritance tree; added DvProportion, DvAmount and DvAbsoluteQuantity; removed DvMeasurable, DvQuantityRatio and DvCustomaryQuantity](https://discourse.openehr.org/t/239-updated-rm-quantity-package-adjusted-inheritance-tree-added-dvproportion-dvamount-and-dvabsolutequantity-removed-dvmeasurable-dvquantityratio-and-dvcustomaryquantity/12523)
> Revision: 239
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [337] AWB-13: When opening an ad hoc archetype, do not add it again if it is already in the reference, work or ad hoc repositories.](https://discourse.openehr.org/t/ref-impl-eiffel-337-awb-13-when-opening-an-ad-hoc-archetype-do-not-add-it-again-if-it-is-already-in-the-reference-work-or-ad-hoc-repositories/12522)
> Revision: 337
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [336] AWB-13: Fix the icons legend shown under the Help | Icons menu.](https://discourse.openehr.org/t/ref-impl-eiffel-336-awb-13-fix-the-icons-legend-shown-under-the-help-icons-menu/12521)
> Revision: 336
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [335] Update the copyright date and the domain name.](https://discourse.openehr.org/t/ref-impl-eiffel-335-update-the-copyright-date-and-the-domain-name/12520)
> Revision: 335
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [334] AWB-13: Remove nested setting of the wait cursor when parsing an archetype.](https://discourse.openehr.org/t/ref-impl-eiffel-334-awb-13-remove-nested-setting-of-the-wait-cursor-when-parsing-an-archetype/12519)
> Revision: 334
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [333] Remove unneeded code from C_PRIMITIVE_OBJECT.](https://discourse.openehr.org/t/ref-impl-eiffel-333-remove-unneeded-code-from-c-primitive-object/12518)
> Revision: 333
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [332] Re-engineer rolled-up specialisation status;](https://discourse.openehr.org/t/ref-impl-eiffel-332-re-engineer-rolled-up-specialisation-status/12517)
> Revision: 332
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [The Build Server for the Java project](https://discourse.openehr.org/t/the-build-server-for-the-java-project/15966)
> Dear all,
The build server, kindly donated by Cambio Healthcare Systems, has been set up to facilitate the Java development.
A Continuous Integration Server, known as "Continuum" from Apache has been installed and configured to monitor all the core Java components in the Subversion repository. At the moment, only the components on the trunk are monitored since that's where the main development activities are taking place. The CI server can be reached at...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [331] AWB-13: Fix precondition violation "has_language" in ARCHETYPE.logical_paths.](https://discourse.openehr.org/t/ref-impl-eiffel-331-awb-13-fix-precondition-violation-has-language-in-archetype-logical-paths/12516)
> Revision: 331
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[Archetypefinder] Archetypes as mindmaps, German archetypes](https://discourse.openehr.org/t/archetypefinder-archetypes-as-mindmaps-german-archetypes/14663)
> Dear all,
There is a new version of the Archetypefinder available at [http://www.archetypes.com.au](http://www.archetypes.com.au) where you can easily find the latest openEHR archetypes.
Most noticable changes:
- we have included a browsable mindmap for each of the archetypes now (see e.g....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [330] AWB-13: When running the scenario test case:](https://discourse.openehr.org/t/ref-impl-eiffel-330-awb-13-when-running-the-scenario-test-case/12514)
> Revision: 330
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [329] AWB-50: Fix precondition violations when the reference or working repository does not exist.](https://discourse.openehr.org/t/ref-impl-eiffel-329-awb-50-fix-precondition-violations-when-the-reference-or-working-repository-does-not-exist/12510)
> Revision: 329
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Link on openher website dus not work](https://discourse.openehr.org/t/link-on-openher-website-dus-not-work/16640)
> Maybe it is already being repaired, just for sure
http://www.openehr.org/uml/release-1.0.1/Printable/Printable.html
does not work
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [328] The adl_parser_test project was broken by revisions 319 and 287, as well as the refactoring from ADL_INTERFACE to ARCHETYPE_COMPILER that occurred a couple of months ago.](https://discourse.openehr.org/t/ref-impl-eiffel-328-the-adl-parser-test-project-was-broken-by-revisions-319-and-287-as-well-as-the-refactoring-from-adl-interface-to-archetype-compiler-that-occurred-a-couple-of-months-ago/12509)
> Revision: 328
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [327] Missed error in ASSERTION_SERIALISER finalise, which is no longer needed.](https://discourse.openehr.org/t/ref-impl-eiffel-327-missed-error-in-assertion-serialiser-finalise-which-is-no-longer-needed/12508)
> Revision: 327
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [326] Make some further adjustments:](https://discourse.openehr.org/t/ref-impl-eiffel-326-make-some-further-adjustments/12507)
> Revision: 326
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [325] Cleaner version of work done in previous commit.](https://discourse.openehr.org/t/ref-impl-eiffel-325-cleaner-version-of-work-done-in-previous-commit/12506)
> Revision: 325
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [324] Revision 287 broke the build for the common_libs_test and openehr_test projects.](https://discourse.openehr.org/t/ref-impl-eiffel-324-revision-287-broke-the-build-for-the-common-libs-test-and-openehr-test-projects/12505)
> Revision: 324
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [323] Merge revisions 243 from TRUNK into BRANCHES/gui and BRANCHES/specialisation (renaming C_STRING from the base library to BASE_C_STRING, etc.).](https://discourse.openehr.org/t/ref-impl-eiffel-323-merge-revisions-243-from-trunk-into-branches-gui-and-branches-specialisation-renaming-c-string-from-the-base-library-to-base-c-string-etc/12504)
> Revision: 323
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [322] AWB-48: Revision 309 broke the build for the adl_parser_test project.](https://discourse.openehr.org/t/ref-impl-eiffel-322-awb-48-revision-309-broke-the-build-for-the-adl-parser-test-project/12503)
> Revision: 322
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [321] Merge revisions 320 from TRUNK into BRANCHES/gui and BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-321-merge-revisions-320-from-trunk-into-branches-gui-and-branches-specialisation/12502)
> Revision: 321
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [320] In the Eiffel SCons builder:](https://discourse.openehr.org/t/ref-impl-eiffel-320-in-the-eiffel-scons-builder/12496)
> Revision: 320
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [319] Validation of ARCHETYPE is now done by ARCHETYPE_VALIDATOR, which in turn uses various visitor objects to do its work](https://discourse.openehr.org/t/ref-impl-eiffel-319-validation-of-archetype-is-now-done-by-archetype-validator-which-in-turn-uses-various-visitor-objects-to-do-its-work/12495)
> Revision: 319
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-technical Digest, Vol 12, Issue 14](https://discourse.openehr.org/t/openehr-technical-digest-vol-12-issue-14/12494)
> ask everyone to subscribe to the announce list - automatic subscribe those not currently subscribed.
MC
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [318] Extensive refactoring, renaming etc.](https://discourse.openehr.org/t/ref-impl-eiffel-318-extensive-refactoring-renaming-etc/12493)
> Revision: 318
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New website coming soon + wiki + issue tracking](https://discourse.openehr.org/t/new-website-coming-soon-wiki-issue-tracking/12497)
> Some exciting changes are in the pipeline for the openEHR online community\.
1\. New website\. The existing website, as many of you would know is not
terribly flexible, consistent or visually appealing\. The new website is
being built with Daisy, which is a layer on top of Cocoon, a content
management system that sits on top of Apache\. The new website will look
better, and allow far easier updating, searching and other facilities\.
The aim is to get this online in the next month or so, not...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [317] Various refactoring, including class rename of ARCHETYPE_REPOSITORY_XX classes to ARCH_REP_XX.](https://discourse.openehr.org/t/ref-impl-eiffel-317-various-refactoring-including-class-rename-of-archetype-repository-xx-classes-to-arch-rep-xx/12492)
> Revision: 317
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [316] Remove the unused, empty "distrib" directory.](https://discourse.openehr.org/t/ref-impl-eiffel-316-remove-the-unused-empty-distrib-directory/12491)
> Revision: 316
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [315] Refactoring changes (incomplete) to separate functionality among ARCHETYPE_DIRECTORY, ARCHETYPE_COMPILER, ARCH_REP_ARCHETYPE.](https://discourse.openehr.org/t/ref-impl-eiffel-315-refactoring-changes-incomplete-to-separate-functionality-among-archetype-directory-archetype-compiler-arch-rep-archetype/12490)
> Revision: 315
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [314] Merge revisions 312 and 313 from BRANCHES/gui into TRUNK and BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-314-merge-revisions-312-and-313-from-branches-gui-into-trunk-and-branches-specialisation/12489)
> Revision: 314
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [[ref_impl_eiffel] [313] AWB 42: Ensure that the splash screen appears at the earliest opportunity, and ensure that it closes.](https://discourse.openehr.org/t/ref-impl-eiffel-313-awb-42-ensure-that-the-splash-screen-appears-at-the-earliest-opportunity-and-ensure-that-it-closes/12488)
> Revision: 313
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[238] add scm to rm-domain pom](https://discourse.openehr.org/t/238-add-scm-to-rm-domain-pom/12487)
> Revision: 238
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [312] Partially revert revision 296.](https://discourse.openehr.org/t/ref-impl-eiffel-312-partially-revert-revision-296/12486)
> Revision: 312
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Open Sorce Database](https://discourse.openehr.org/t/open-sorce-database/14666)
> Dear group
I’ve a question about ? what is the experience implementing openEHR in opensource database like mysql or progreSQL in a hospital of 500 beds?
Thank
Adrian Gomez
Hospital Italiano - ARGENTINA
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [311] Merge revisions 307-310 from TRUNK into BRANCHES/gui and BRANCHES/specialisation (AWB-48 and EDT-77).](https://discourse.openehr.org/t/ref-impl-eiffel-311-merge-revisions-307-310-from-trunk-into-branches-gui-and-branches-specialisation-awb-48-and-edt-77/12484)
> Revision: 311
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Pregnancy History](https://discourse.openehr.org/t/pregnancy-history/16630)
> The pregnancy_evaluation archetype provides ability to capture previous pregnancies information in a very limited way.
For each previous pregnancy, users need the ability to capture information such as date of pregnancy, gestational age, length of labor, baby’s birth weight, baby’s gender, type of delivery, place of delivery, if pregnancy resulted in preterm labor and any additional comments.
Can this be accomplished by adding to the pregnancy_evaluation archetype or is there a “history”...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[237] add scm to pom](https://discourse.openehr.org/t/237-add-scm-to-pom/12936)
> Revision: 237
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-clinical Digest, Vol 10, Issue 32](https://discourse.openehr.org/t/openehr-clinical-digest-vol-10-issue-32/12479)
> Hi,
Since you are cc-ing anyways, might as well have only one list.
To get subcribers attention to an announcement you might consider writing in the subject line with [ANNOUCEMENT] followed by the announcement title.
Simplicity rules.
Nizan MD
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question of net etiquette for this community](https://discourse.openehr.org/t/question-of-net-etiquette-for-this-community/14658)
> Dear all,
sometimes we make 'announcements' to the openehr\-announce list \-
messages globally applicable to all in the community, such as changes to
the website or licenses or whatever\. Currently we have to cc: these to
other lists, due to the fact that not everyone is on the announce list
\(about 135 out of many hundreds\)\. Making announcements \(which are very
few \- traffic averages I would say 1/month\) thus means that we have to
do this cc:ing, and it means some of you...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [308] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-308-1/15964)
> Revision: 308
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR.org server will be down 1-2 hours Thursday 2 August](https://discourse.openehr.org/t/openehr-org-server-will-be-down-1-2-hours-thursday-2-august/12485)
> Dear all,
the openEHR server \(including the Subversion server\), will be taken down
to be moved to a new UPS\-capable rack on Thursday 2 August 2007 between
08:00 and 09:00 \(London, currently on GMT\+1\), services should be
considered "At risk" until 10:00\.
thanks for your understanding\.
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [306] Merge revision 305 from BRANCHES/gui into TRUNK and BRANCHES/specialisation (AWB-24).](https://discourse.openehr.org/t/ref-impl-eiffel-306-merge-revision-305-from-branches-gui-into-trunk-and-branches-specialisation-awb-24/12478)
> Revision: 306
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [305] AWB-24: The previous fix (revision 251) was inconsistent with (and less friendly than) the "Save As" functionality in Archetype Editor.](https://discourse.openehr.org/t/ref-impl-eiffel-305-awb-24-the-previous-fix-revision-251-was-inconsistent-with-and-less-friendly-than-the-save-as-functionality-in-archetype-editor/12477)
> Revision: 305
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[236] fixed typo in ArchetypeID](https://discourse.openehr.org/t/236-fixed-typo-in-archetypeid/12472)
> Revision: 236
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [303] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-303-1/12471)
> Revision: 303
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[235] bug fix in ISMTransitionTest constructor](https://discourse.openehr.org/t/235-bug-fix-in-ismtransitiontest-constructor/12470)
> Revision: 235
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [302] Work around incorrect namespace generation in EiffelStudio 6.0.6.9021.](https://discourse.openehr.org/t/ref-impl-eiffel-302-work-around-incorrect-namespace-generation-in-eiffelstudio-6-0-6-9021/12469)
> Revision: 302
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Error in constructor ISMTransition](https://discourse.openehr.org/t/error-in-constructor-ismtransition/12468)
> Forgotten is to assign the constructor parameter to the local variables\.
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [an archetype for a home-based device composition](https://discourse.openehr.org/t/an-archetype-for-a-home-based-device-composition/14662)
> The openehr spec details how COMPOSITION's can occur
without any event\_context for the case of home
monitoring devices etc\. I am in a situation where I will be
constructing compositions along these lines, but now I
need an archetype that corresponds to such a
composition\.
Has any standard approach to this been considered in
the NHS work? It's essentially a pretty empty archetype
\- so I'm sure I could knock one up \- but would defer to
those with more experience in this area...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [301] AWB-36: Remove check box icons from the Windows installer project.](https://discourse.openehr.org/t/ref-impl-eiffel-301-awb-36-remove-check-box-icons-from-the-windows-installer-project/12923)
> Revision: 301
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR.jp launched](https://discourse.openehr.org/t/openehr-jp-launched/15960)
> Dear all,
We have been discussed on open source software on medicine for this
three years in Japan\. We have meetings as medical open source software
council twice a year from 2004\.
We are very interested in openEHR/CEN13606 standardization\. For our
repository of Japanese, we launched openEHR\.jp last night\. Please visit
our site\.
http://www.openehr.jp
We are going to translate the documants and specifications to Japanese
and try to implement openEHR by Ruby language\.
I found some typos...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new discussion page for ontologies and openEHR.](https://discourse.openehr.org/t/new-discussion-page-for-ontologies-and-openehr/14661)
> Dear all,
we have added a new page for the purpose of discussing ontologies and
openEHR, in particular aimed at improving openEHR in the future so that
it really does live up to the goal of creating truly computable
information \- information can safely be used in automatic processing,
inferencing and reasoning\. The page is here:
http://www.openehr.org/FAQs/t_ontology_FAQ.htm \. It is set up as a
starting point, not in any way finished \- just enough to get discussion
going\.
Discussion is...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [300] Allow adl_dotnet_lib to compile in the specialisation branch.](https://discourse.openehr.org/t/ref-impl-eiffel-300-allow-adl-dotnet-lib-to-compile-in-the-specialisation-branch/12467)
> Revision: 300
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [modeling non-medical data (from openEHR-technical Digest, Vol 12, Issue 1)](https://discourse.openehr.org/t/modeling-non-medical-data-from-openehr-technical-digest-vol-12-issue-1/15962)
> > All inputs are welcomed\. I will distributing the draft PARs to the PHD
> group today with the plan being to submit the PARs to the IEEE NESCOM
> for review and approval at their next meeting\. Also, all are encouraged
> to join Continua\. The membership structure is a relatively low barrier,
> with memberships starting as low as $5,000 per year and full voting
> memberships costing $35,000 per year\.
Eric, this all sounds like fantastic work \- I'm not sure how much
scope there...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Data quality questions/ proposal (from openEHR-clinical Digest, Vol 10, Issue 20)](https://discourse.openehr.org/t/data-quality-questions-proposal-from-openehr-clinical-digest-vol-10-issue-20/15961)
> A side\-note to this discussion:
The EN/ISO 11073 device comms standards provide for device\-originated
status flags of various sorts to be communicated\.
This does not of course get around the always\-erroneous first NIBP
reading, misplaced cuff \- or any manual readings\.
Nor, unless one resorts to further processing \(as Ed mentioned in an
earlier mail\) does it get around the correct reading and communication
of misleading data \(such as 'positional' or 'damped'...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [299] Merge revisions 273-296 from TRUNK into BRANCHES/specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-299-merge-revisions-273-296-from-trunk-into-branches-specialisation/12466)
> Revision: 299
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [hibernate](https://discourse.openehr.org/t/hibernate/12474)
> \(the previous message had accidently doubled the originally
sql\-statement and was therefor 80\.000 instead of 40\.000 characters, this
is a bit shortened to keep it under 40\.000, sorry moderator for the trouble\)
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Data quality 2](https://discourse.openehr.org/t/data-quality-2/14660)
> Thanks for all the responses. I’m glad I’m not the only one struggling with this.
If I try to summarize what I’ve learned form these responses is that there is ‘real’ data (although that also can be subjective scales f.i. for pain) and there is a ‘personal’ interpretation that can make the data ‘trustworthy and therefore re-useable by others.
As far as I’m concerned my questions aren’t about accuracy itself. That part will be taken care of by the certifying instance. A device can only be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New contribution to Dual Model EHR architectures and archetype development](https://discourse.openehr.org/t/new-contribution-to-dual-model-ehr-architectures-and-archetype-development/14656)
> Dear all,
Our Group of Biomedical Informatics (IBIME) at the Technical University of Valencia, Spain, has been working during the last years in the field of integration and standardization of clinical data for the construction of EHR systems. Our main project has been called LinkEHR, which is a prototype system for managing clinical data in the form of EHR Extracts, following a dual model approach.
This system is part of a coordinated project, together with the University of Murcia (Spain),...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Data quality questions/ proposal](https://discourse.openehr.org/t/data-quality-questions-proposal/14665)
> One of the major requirements we have is what I call a ‘data quality marker’. So the blood pressure recorded is 88/124 but what is the ‘value/ quality’ of this measurement.
IMHO any recorded value is useless unless the quality of this measurement can be established and taken into account when interpreting the data
In order to establish this data quality we need to add some attributes to the observation archetypes used to record such measurement.
So far as we can see now we think that these...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Microsoft/NHS common health interface and openEHR datatypes](https://discourse.openehr.org/t/microsoft-nhs-common-health-interface-and-openehr-datatypes/14653)
> Dear All
We are beginning to use the Microsoft Common Health Interface controls in our software. I think it would be good to keep this work open and shared so that we get them working with the openEHR datatypes (it is a very good fit at the moment). The first one off the rank will be the datetime control as this is the only one that looks finalised.
Should we keep the source on the openEHR site? I wonder if Tony Shannon or Mike Bainbridge could give us any direction on how to do this most...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [298] Merge revisions 273-296 from BRANCHES/gui into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-298-merge-revisions-273-296-from-branches-gui-into-trunk/15959)
> Revision: 298
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [297] Various structural modifications & simplifications on the way to a 'system of archetypes compiler' approach.](https://discourse.openehr.org/t/ref-impl-eiffel-297-various-structural-modifications-simplifications-on-the-way-to-a-system-of-archetypes-compiler-approach/12465)
> Revision: 297
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [296] Merge revision 295 from TRUNK into BRANCHES/gui.](https://discourse.openehr.org/t/ref-impl-eiffel-296-merge-revision-295-from-trunk-into-branches-gui/15958)
> Revision: 296
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [295] Merge revisions 243-294 from BRANCHES/eiffel6 into TRUNK.](https://discourse.openehr.org/t/ref-impl-eiffel-295-merge-revisions-243-294-from-branches-eiffel6-into-trunk/15957)
> Revision: 295
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [294] Upgrade to EiffelStudio 6.0.](https://discourse.openehr.org/t/ref-impl-eiffel-294-upgrade-to-eiffelstudio-6-0/15956)
> Revision: 294
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [scientifical significance of research proposal](https://discourse.openehr.org/t/scientifical-significance-of-research-proposal/14652)
> Dear All,
We plan to apply for a research proposal, which focuses on importing and exporting archetype compliant EN13606 ehr extracts, originating from medical data that has been stored previously in different proprietary format of the communicating HISs\. We plan to test our solution by developing an Archetype representation of a hospital discharge letter that should consider existing specifications for this document type and also integrate our corresponding national requirements for a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [modeling non-medical data](https://discourse.openehr.org/t/modeling-non-medical-data/14754)
> I have come across an interesting opportunity to do some openehr
modeling in a sports science context\. However, whilst half of
the data is medical \(heart rate etc\), the other half is
raw physical data \(GPS location, cadence etc\) related to in
this case a bike\.\.
So I would have one large history consisting of heart rate over
time which can be modeled with existing archetypes\. For the
other data \(the corresponding cadence over time\),
I will obviously need to construct my...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [293] Step two, to complete revision 292's change.](https://discourse.openehr.org/t/ref-impl-eiffel-293-step-two-to-complete-revision-292s-change/15955)
> Revision: 293
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [292] Revert the last revision's colour changes to archetype_3.ico, archetype_specialised_3.ico and file_folder_3.ico, because they were correct.](https://discourse.openehr.org/t/ref-impl-eiffel-292-revert-the-last-revisions-colour-changes-to-archetype-3-ico-archetype-specialised-3-ico-and-file-folder-3-ico-because-they-were-correct/15954)
> Revision: 292
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [291] Changed icon colours (just so we can see what is going on)](https://discourse.openehr.org/t/ref-impl-eiffel-291-changed-icon-colours-just-so-we-can-see-what-is-going-on/12464)
> Revision: 291
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [290] Fix a few bugs in GUI_VIEW_ARCHETYPE_TREE_CONTROL.repopulate.](https://discourse.openehr.org/t/ref-impl-eiffel-290-fix-a-few-bugs-in-gui-view-archetype-tree-control-repopulate/12463)
> Revision: 290
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [289] Grafting of ad hoc archetypes into the repository tree now works in a rudimentary fashion.](https://discourse.openehr.org/t/ref-impl-eiffel-289-grafting-of-ad-hoc-archetypes-into-the-repository-tree-now-works-in-a-rudimentary-fashion/12462)
> Revision: 289
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[234] fix the issue in parsing units with slash](https://discourse.openehr.org/t/234-fix-the-issue-in-parsing-units-with-slash/12460)
> Revision: 234
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Come join the openEHR social network](https://discourse.openehr.org/t/come-join-the-openehr-social-network/12897)
> Hi openEHR enthusiasts
This network was set up yesterday and I will be administering it\.
Should be informative and fun\. There is a special subgroup for people
who attend Medinfo\. Feel welcome to join\.
Here is the link: http://openehr.ning.com/
Which features \(forum, blog, rss, photos, videos, \.\.\.\) make sense will
be decided during the next couple of days\. It will be important to
avoid overlap with the lists\. Any comments welcome\.
\-Thilo
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [288] Implement group_id for ad hoc repositories consistently with indexed file repositories, i.e., ARCHETYPE_DIRECTORY assigns each repository's group id.](https://discourse.openehr.org/t/ref-impl-eiffel-288-implement-group-id-for-ad-hoc-repositories-consistently-with-indexed-file-repositories-i-e-archetype-directory-assigns-each-repositorys-group-id/12459)
> Revision: 288
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [287] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-287-1/12885)
> Revision: 287
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR-related papers available on the website](https://discourse.openehr.org/t/new-openehr-related-papers-available-on-the-website/12452)
> Three new openEHR\-related papers are available on the openEHR website,
at http://www.openehr.org/publications/health_IT/t_health_IT.htm
The new additions are:
\* Chen R, Enberg G, Klein GO\. Julius – a template based
supplementary electronic health record system\.
\* Chen R, Klein G\. The openEHR Java Reference Implementation Project\.
\* Beale T, Heard S\. An Ontology\-based Model of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [286] ARCHETYPE_ADHOC_FILE_REPOSITORY, now inherits from a new pure deferred class ARCHETYPE_REPOSITORY_I, so that it can create an ARCHETYPE_REPOSITORY_ARCHETYPE.](https://discourse.openehr.org/t/ref-impl-eiffel-286-archetype-adhoc-file-repository-now-inherits-from-a-new-pure-deferred-class-archetype-repository-i-so-that-it-can-create-an-archetype-repository-archetype/12458)
> Revision: 286
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [size in DvMultimedia](https://discourse.openehr.org/t/size-in-dvmultimedia/14646)
> Why is there a property size for data in DvMultimedia, and not for
integrity\_check?
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [285] SHARED_RESOURCES.system_temp_file_directory now has preconditions.](https://discourse.openehr.org/t/ref-impl-eiffel-285-shared-resources-system-temp-file-directory-now-has-preconditions/12457)
> Revision: 285
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [284] Correct ARCHETYPE_ADHOC_FILE_REPOSITORY.valid_path to handle a file, not a directory.](https://discourse.openehr.org/t/ref-impl-eiffel-284-correct-archetype-adhoc-file-repository-valid-path-to-handle-a-file-not-a-directory/12456)
> Revision: 284
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [283] AWB-44: Set the icon at the left of each dialog's title bar to be the same icon as the main window.](https://discourse.openehr.org/t/ref-impl-eiffel-283-awb-44-set-the-icon-at-the-left-of-each-dialogs-title-bar-to-be-the-same-icon-as-the-main-window/12455)
> Revision: 283
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [282] AWB-33: The whole of the text was not being selected on focussing the text boxes in the Repository Settings and Options dialogs.](https://discourse.openehr.org/t/ref-impl-eiffel-282-awb-33-the-whole-of-the-text-was-not-being-selected-on-focussing-the-text-boxes-in-the-repository-settings-and-options-dialogs/12454)
> Revision: 282
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [281] AWB-43: Ensure that, when a parent of the selected row collapses, that parent is selected.](https://discourse.openehr.org/t/ref-impl-eiffel-281-awb-43-ensure-that-when-a-parent-of-the-selected-row-collapses-that-parent-is-selected/12453)
> Revision: 281
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [280] Make SHARED_RESOURCES.system_temp_directory work properly;](https://discourse.openehr.org/t/ref-impl-eiffel-280-make-shared-resources-system-temp-directory-work-properly/15953)
> Revision: 280
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [279] Complete renaming of ADL_INTERFACE to ARCHETYPE_COMPILER](https://discourse.openehr.org/t/ref-impl-eiffel-279-complete-renaming-of-adl-interface-to-archetype-compiler/12449)
> Revision: 279
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [278] rename adl_interface to archetype_compiler](https://discourse.openehr.org/t/ref-impl-eiffel-278-rename-adl-interface-to-archetype-compiler/12448)
> Revision: 278
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [277] Correct valid_path() to handle file, directory or any kind of path.](https://discourse.openehr.org/t/ref-impl-eiffel-277-correct-valid-path-to-handle-file-directory-or-any-kind-of-path/12447)
> Revision: 277
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [276] Initial cut of structural changes for specialisation-based compiling of a 'system of archetypes'.](https://discourse.openehr.org/t/ref-impl-eiffel-276-initial-cut-of-structural-changes-for-specialisation-based-compiling-of-a-system-of-archetypes/12446)
> Revision: 276
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [275] AWB-38: In FILE_CONTEXT.file_changed, check that the file exists before trying to determine its date.](https://discourse.openehr.org/t/ref-impl-eiffel-275-awb-38-in-file-context-file-changed-check-that-the-file-exists-before-trying-to-determine-its-date/12445)
> Revision: 275
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [273] Merge revision 269-272 changes from BRANCHES/specialisation into TRUNK and BRANCHES/gui.](https://discourse.openehr.org/t/ref-impl-eiffel-273-merge-revision-269-272-changes-from-branches-specialisation-into-trunk-and-branches-gui/12443)
> Revision: 273
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [272] AWB-20: Allow keyboard navigation of the archetype tree by setting a timer to delay loading.](https://discourse.openehr.org/t/ref-impl-eiffel-272-awb-20-allow-keyboard-navigation-of-the-archetype-tree-by-setting-a-timer-to-delay-loading/12442)
> Revision: 272
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [271] AWB-41: Don't set repository tree width to zero on selecting an item.](https://discourse.openehr.org/t/ref-impl-eiffel-271-awb-41-dont-set-repository-tree-width-to-zero-on-selecting-an-item/12441)
> Revision: 271
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [270] Fix a bug in the last commit of ADL_INTERFACE.resync_file, demonstrated by this test:](https://discourse.openehr.org/t/ref-impl-eiffel-270-fix-a-bug-in-the-last-commit-of-adl-interface-resync-file-demonstrated-by-this-test/12440)
> Revision: 270
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [269] Initial steps in restructuring for specialisation](https://discourse.openehr.org/t/ref-impl-eiffel-269-initial-steps-in-restructuring-for-specialisation/12439)
> Revision: 269
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [268] Merge rev 243 - 267 of changes from BRANHCES/gui onto TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-268-merge-rev-243-267-of-changes-from-branhces-gui-onto-trunk/12436)
> Revision: 268
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [267] AWB-20: Allow keyboard navigation of the archetype tree, which was impractical because each archetype's details were loaded and displayed as it was selected in the tree, by setting a timer to delay loading.](https://discourse.openehr.org/t/ref-impl-eiffel-267-awb-20-allow-keyboard-navigation-of-the-archetype-tree-which-was-impractical-because-each-archetypes-details-were-loaded-and-displayed-as-it-was-selected-in-the-tree-by-setting-a-timer-to-delay-loading/12435)
> Revision: 267
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [266] AWB-1: The quantity unit constraint for degrees was displayed wrongly in the Node Map, because of an oversight when implementing Unicode in ADL Workbench that tree nodes were not being converted in several places.](https://discourse.openehr.org/t/ref-impl-eiffel-266-awb-1-the-quantity-unit-constraint-for-degrees-was-displayed-wrongly-in-the-node-map-because-of-an-oversight-when-implementing-unicode-in-adl-workbench-that-tree-nodes-were-not-being-converted-in-several-places/12872)
> Revision: 266
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [265] As an archetype was loaded, its file was pointlessly being read twice.](https://discourse.openehr.org/t/ref-impl-eiffel-265-as-an-archetype-was-loaded-its-file-was-pointlessly-being-read-twice/12434)
> Revision: 265
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [264] Simplify the loading of an archetype file by postponing the check for UTF-8 encoding until after the whole file has been read.](https://discourse.openehr.org/t/ref-impl-eiffel-264-simplify-the-loading-of-an-archetype-file-by-postponing-the-check-for-utf-8-encoding-until-after-the-whole-file-has-been-read/12433)
> Revision: 264
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [263] Prevent pointless reloading of the last selected archetype whenever a folder is selected.](https://discourse.openehr.org/t/ref-impl-eiffel-263-prevent-pointless-reloading-of-the-last-selected-archetype-whenever-a-folder-is-selected/12432)
> Revision: 263
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [261] AWB-37: Page Up and Page Down were working in the Test grid only if all rows were expanded.](https://discourse.openehr.org/t/ref-impl-eiffel-261-awb-37-page-up-and-page-down-were-working-in-the-test-grid-only-if-all-rows-were-expanded/12430)
> Revision: 261
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [260] AWB-16: Allow folder nodes to be checked in the Test view; checked_box.ico and unchecked_box.ico are no longer transparent inside the box, so that the state of the check box is visible when the cell is selected..](https://discourse.openehr.org/t/ref-impl-eiffel-260-awb-16-allow-folder-nodes-to-be-checked-in-the-test-view-checked-box-ico-and-unchecked-box-ico-are-no-longer-transparent-inside-the-box-so-that-the-state-of-the-check-box-is-visible-when-the-cell-is-selected/12429)
> Revision: 260
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR](https://discourse.openehr.org/t/openehr/14461)
> Hi Bernard
I have just made post the should cover part of your question\. As
mentioned in this post the kernel component is central to the
architecture of an openEHR system as it brings the two models
together\. For persistence many solutions would be possible\. Like XML
\(that what Ocean Informatics uses in their EhrBank product\) or an
object\-relational\-mapping solution\. But it should be noted that just
instances of the reference model need to be persisted including
references to the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Hidden reference model stuff in template](https://discourse.openehr.org/t/hidden-reference-model-stuff-in-template/14423)
> Maybe this question should be asked on the technical mailing list, since there's no reaction on the clinical list:-)
Cheers,
Stef
Begin doorgestuurd bericht:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [259] AWB-35: Prevent the user from editing in text and combo boxes.](https://discourse.openehr.org/t/ref-impl-eiffel-259-awb-35-prevent-the-user-from-editing-in-text-and-combo-boxes/12426)
> Revision: 259
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[233] fixed a path related issue in CAttribute](https://discourse.openehr.org/t/233-fixed-a-path-related-issue-in-cattribute/12425)
> Revision: 233
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [258] AWB-34: ARCHETYPE_ONTOLOGY.update_highest_constraint_code_index worked only if the archetype was at the top or the first level of specialisation.](https://discourse.openehr.org/t/ref-impl-eiffel-258-awb-34-archetype-ontology-update-highest-constraint-code-index-worked-only-if-the-archetype-was-at-the-top-or-the-first-level-of-specialisation/15952)
> Revision: 258
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [257] AWB-24: Remove the Save button from the toolbar.](https://discourse.openehr.org/t/ref-impl-eiffel-257-awb-24-remove-the-save-button-from-the-toolbar/15951)
> Revision: 257
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Runtime references to other archetypes?](https://discourse.openehr.org/t/runtime-references-to-other-archetypes/12414)
> Hi\!
Do I understand correctly that \(at least\) the following two archetypes
refer to specific parts \(selected by paths\) of other archetypes, and
that these references will be created/selected by clinicians at
runtime?
http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-INSTRUCTION.monitoring.v1draft.html
Concept: Archetype
Description: The id of the archetype\(s\) to be filled as part of this monitoring
Type:...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [256] The implementation of MAIN_WINDOW.focused_widget was Windows-specific and did not work on GTK.](https://discourse.openehr.org/t/ref-impl-eiffel-256-the-implementation-of-main-window-focused-widget-was-windows-specific-and-did-not-work-on-gtk/12423)
> Revision: 256
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [255] AWB-32: Simplify the implementation, and add a postcondition.](https://discourse.openehr.org/t/ref-impl-eiffel-255-awb-32-simplify-the-implementation-and-add-a-postcondition/12422)
> Revision: 255
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [254] Minor correction to the export status of some features.](https://discourse.openehr.org/t/ref-impl-eiffel-254-minor-correction-to-the-export-status-of-some-features/12421)
> Revision: 254
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [253] AWB-25: Provide accelerator keys and shortcuts for the menu bar.](https://discourse.openehr.org/t/ref-impl-eiffel-253-awb-25-provide-accelerator-keys-and-shortcuts-for-the-menu-bar/12420)
> Revision: 253
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [252] AWB-25: Provide accelerator keys and shortcuts for the menu bar.](https://discourse.openehr.org/t/ref-impl-eiffel-252-awb-25-provide-accelerator-keys-and-shortcuts-for-the-menu-bar/12419)
> Revision: 252
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Question about ItemTree](https://discourse.openehr.org/t/question-about-itemtree/12411)
> Hi Java Developers,
Allow me a small question
I have seen some example archetypes with an ITEM\_TREE in it, they all had the
attribute "items"
I wonder, is this correct?
Because, in the code, I look at the annotated constructor, I don't see a
attribute "items"
I see one that is called "representation", and it is required, but I cannot
find this attribute in the archetype\.
Maybe the code for ItemTree\.java is a bit outdated? It is from end 2005, also
the...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [251] AWB-24: Replace "Save as adl/html" on the toolbar with "Save as type" in the Save dialog.](https://discourse.openehr.org/t/ref-impl-eiffel-251-awb-24-replace-save-as-adl-html-on-the-toolbar-with-save-as-type-in-the-save-dialog/12412)
> Revision: 251
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Instruction & action archetypes?](https://discourse.openehr.org/t/instruction-action-archetypes/14648)
> Hi\!
Some \(possibly stupid\) questions:
\- Are there any examples of instruction archetypes with more than one
activity anywhere?
\- If different activities \(of the same instruction\) point to different
action archetypes how should then the resulting usage of the ISM be
interpreted? Can they be considered part of the same process with some
states in each action archetype?
A swift reply to one or more of the questions would be very welcome\.
Best regards,
Erik...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [possible error in ontology-parsing?](https://discourse.openehr.org/t/possible-error-in-ontology-parsing/15575)
> I have following ontology snippet:
ontology
primary\_language = <"en">
term\_definitions = <
\["en"\] = <
items =...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [250] Fix a crash caused by revision 244 in the GUI branch.](https://discourse.openehr.org/t/ref-impl-eiffel-250-fix-a-crash-caused-by-revision-244-in-the-gui-branch/12410)
> Revision: 250
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem with RM-builder/DV_CODED_TEXT](https://discourse.openehr.org/t/problem-with-rm-builder-dv-coded-text/13198)
> I have a problem, I have following ADL\-snippet
ELEMENT\[at1\.1\.1\.4\] matches \{ \-\- last name suffix
value matches \{
DV\_CODED\_TEXT matches \{
defining\_code matches...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [249] AWB-4: In the Node Map tree and the Test tree, display only the last specialisation segment of the domain concept.](https://discourse.openehr.org/t/ref-impl-eiffel-249-awb-4-in-the-node-map-tree-and-the-test-tree-display-only-the-last-specialisation-segment-of-the-domain-concept/12409)
> Revision: 249
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [248] Fix an error caused in revision 208, which changed the precompiled Vision2 target is selected, but failed to update ADL_Workbench.msi, causing it to be unable to find adl_workbench.exe.](https://discourse.openehr.org/t/ref-impl-eiffel-248-fix-an-error-caused-in-revision-208-which-changed-the-precompiled-vision2-target-is-selected-but-failed-to-update-adl-workbench-msi-causing-it-to-be-unable-to-find-adl-workbench-exe/12408)
> Revision: 248
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [247] Fix an error caused in revision 208, which changed the precompiled Vision2 target is selected, but failed to update ADL_Workbench.msi, causing it to be unable to find adl_workbench.exe.](https://discourse.openehr.org/t/ref-impl-eiffel-247-fix-an-error-caused-in-revision-208-which-changed-the-precompiled-vision2-target-is-selected-but-failed-to-update-adl-workbench-msi-causing-it-to-be-unable-to-find-adl-workbench-exe/12407)
> Revision: 247
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [246] Fix an error caused in revision 208, which changed the precompiled Vision2 target is selected, but failed to update ADL_Workbench.msi, causing it to be unable to find adl_workbench.exe.](https://discourse.openehr.org/t/ref-impl-eiffel-246-fix-an-error-caused-in-revision-208-which-changed-the-precompiled-vision2-target-is-selected-but-failed-to-update-adl-workbench-msi-causing-it-to-be-unable-to-find-adl-workbench-exe/12406)
> Revision: 246
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [245] Fix an error caused in revision 208, which changed the precompiled Vision2 target is selected, but failed to update ADL_Workbench.msi, causing it to be unable to find adl_workbench.exe.](https://discourse.openehr.org/t/ref-impl-eiffel-245-fix-an-error-caused-in-revision-208-which-changed-the-precompiled-vision2-target-is-selected-but-failed-to-update-adl-workbench-msi-causing-it-to-be-unable-to-find-adl-workbench-exe/12405)
> Revision: 245
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [244] AWB-28: Replace toggle buttons to the right of the Node Map with radio buttons:](https://discourse.openehr.org/t/ref-impl-eiffel-244-awb-28-replace-toggle-buttons-to-the-right-of-the-node-map-with-radio-buttons/12401)
> Revision: 244
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [243] Merge eiffel6 235-240 and performance 237 - 240 into TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-243-merge-eiffel6-235-240-and-performance-237-240-into-trunk/12400)
> Revision: 243
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Point in time 2](https://discourse.openehr.org/t/point-in-time-2/14642)
> Maybe I've been looking for something that isn't there, so for now
I've solved it to add a date and time of measurement field to the AT
data section\. That's the only place where I can add such a field by
using the OI archetype editor\. I started to look in the 'event'
section since this date/time filed option isn't available in the dev
AT's \(both the 'general' and the NHS\-UK ones\) and I couldn't imagine
that such a 'basic' parameter was...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [241] Branch for GUI fixes and enhancements](https://discourse.openehr.org/t/ref-impl-eiffel-241-branch-for-gui-fixes-and-enhancements/12834)
> Revision: 241
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [DV_TEXT, strange behaviour?](https://discourse.openehr.org/t/dv-text-strange-behaviour/12398)
> Hi,
I noticed some strange behaviour, which I cannot explain\.
I ask a question before in the same context, which Heath was so kind to
answer\.
But further investigating I found out, the question was not answered,
but the question also was wrong\.
So I try again
I have three ELEMENT\(s\) like this:
ELEMENT\[at1\.1\.2\.2\] matches \{ \-\- A
value matches \{
DV\_TEXT matches...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [cardinality](https://discourse.openehr.org/t/cardinality/14645)
> I had one more question, I said this morning:
What is the use of the numerical part of the Cardinality object, I wonder?
It can be calculated from the number and occurences of the items\. Or do
I misunderstand?
For example
events cardinality matches \{\*;ordered\} matches \{
EVENT\[at001\] occurences matches \{0\.\.1\} matches \{\*\}
EVENT\[at002\] occurences matches \{0\.\.1\} matches \{\*\}
EVENT\[at003\] occurences...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [[Another small question about archetypes]](https://discourse.openehr.org/t/another-small-question-about-archetypes/12396)
> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- Oorspronkelijk bericht \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [240] A new SCons "stable" release is available at last (0.97), so update the developer page accordingly.](https://discourse.openehr.org/t/ref-impl-eiffel-240-a-new-scons-stable-release-is-available-at-last-0-97-so-update-the-developer-page-accordingly/15949)
> Revision: 240
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Error in CAttribute.java?](https://discourse.openehr.org/t/error-in-cattribute-java/12397)
> Hi Rong, I believe there is an error in CAttribute\.java in the method
public String parentNodePath\(\) and also in the method which depends on
this: childNodePathBase\(\)
When I ask the parentNodePath of the value of an ELEMENT, I get this
\(missing bracket\)
parentNodePath:/data\[at0001\]/items\[at0005\]/items\[at0007
childNodePathBase:/data\[at0001\]/items\[at0005\]/items\[at0007/value
Can you please give a reply to this\.
Thanks
Kind Regards
Bert Verhees
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [239] Optimise our override of SYSTEM_STRING_FACTORY by using .NET Unicode encoding utilities, rather than creating temporary Gobo Unicode strings.](https://discourse.openehr.org/t/ref-impl-eiffel-239-optimise-our-override-of-system-string-factory-by-using-net-unicode-encoding-utilities-rather-than-creating-temporary-gobo-unicode-strings/15948)
> Revision: 239
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Another small question about archetypes](https://discourse.openehr.org/t/another-small-question-about-archetypes/14647)
> I keep it short to use as less of your time as possible
Two elements:
ELEMENT\[at1\.1\.1\.2\] matches \{ \-\- last name value
value matches \{
DV\_TEXT matches \{\*\}
\}
\}
path to value attribute of DV\_TEXT is
/data\[at0001\]/items\[at1\.1\.1\.2\]/value
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Point in time](https://discourse.openehr.org/t/point-in-time/16708)
> Hi all\.
I need some help in understanding the concept 'point in time'\. As far
as I understand it now the completion date/time of an event \(f\.i\. a
blood pressure measurement\) is registered as a point in time in the
event section of the archetype\.
Thing is that I expected to find an entry field where I can enter
that particular date and time\. In the EHR\_IM I found the Action
class \(p\.71\) which purpose seems to be to capture/record those points
in time, is I figured...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [question about archetype](https://discourse.openehr.org/t/question-about-archetype/12413)
> Please allow me a question, I don't know if an archetype on tne
openehrwebsite correct is and I would like to have a confirmation
I foudn structure below in the archetype: openEHR\-EHR\-EVALUATION\.goal\.v1
It has an ELEMENT, and an ELEMENT can only have one \(or none\) attribute:
value, accordig the lates version of document "Data structures"
The attribute "value" inside Element has to RM\-objects connected:
DV\_INTERVAL<COUNT> and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openehr website](https://discourse.openehr.org/t/openehr-website/13815)
> I don't know if it is a problem with a plugin form Firefox, never had
this problem before\.
But the menu\-structure of the openehrwebsite on the left is not visible
in my Firefox\.
It does work in the Internet Explorer\.
Am I the only one experiencing this?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [237] Update the developer help page to describe SCons and EiffelStudio 5.7.](https://discourse.openehr.org/t/ref-impl-eiffel-237-update-the-developer-help-page-to-describe-scons-and-eiffelstudio-5-7/12394)
> Revision: 237
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [236] Rename:](https://discourse.openehr.org/t/ref-impl-eiffel-236-rename/15947)
> Revision: 236
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [235] Create new branch for work on specialisation of archetypes, including diffing, flattening, etc](https://discourse.openehr.org/t/ref-impl-eiffel-235-create-new-branch-for-work-on-specialisation-of-archetypes-including-diffing-flattening-etc/12393)
> Revision: 235
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [234] Create performance enhancement branch](https://discourse.openehr.org/t/ref-impl-eiffel-234-create-performance-enhancement-branch/12392)
> Revision: 234
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [233] Merge changes from eiffel6 branch rev 230 - 231 into TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-233-merge-changes-from-eiffel6-branch-rev-230-231-into-trunk/12387)
> Revision: 233
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [232] Correct Expression tree keyword from 'feature' to 'attribute' in assertions.](https://discourse.openehr.org/t/ref-impl-eiffel-232-correct-expression-tree-keyword-from-feature-to-attribute-in-assertions/12386)
> Revision: 232
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ITEM_TREE spec confusing?](https://discourse.openehr.org/t/item-tree-spec-confusing/12389)
> Hi\!
The spec\.\.\.
http://svn.openehr.org/specification/TAGS/Release-1.0.1/publishing/architecture/rm/common_im.pdf
\.\.\.indicates that an ITEM\_TREE should contain it's items as an
attribute "items: LIST<ITEM> Physical representation of the tree\."
The function as\_hierarchy reads\.\.\.
"as\_hierarchy: CLUSTER Generate a CEN EN13606\-compatible hierarchy,
which is the same as the tree's physical representation\."
Then in another part of the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [download archetypes tar.gz archive](https://discourse.openehr.org/t/download-archetypes-tar-gz-archive/12388)
> Dear all,
The link for the archetype tar\.gz archive file is dead \(http://
my\.openehr\.org/wsvn/knowledge/archetypes/?op=dl&rev=0&isdir=1\)\. Who
is able to restore this link?
Cheers,
Stef Verlinden
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[232] Preformed a merge bringing immutable-experiment branch up to date with TRUNK (rev.231) before starting refactoring.](https://discourse.openehr.org/t/232-preformed-a-merge-bringing-immutable-experiment-branch-up-to-date-with-trunk-rev-231-before-starting-refactoring/12385)
> Revision: 232
Author: erik\.sundvall
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [231] Revert part of the last change to the SCons Eiffel Builder.](https://discourse.openehr.org/t/ref-impl-eiffel-231-revert-part-of-the-last-change-to-the-scons-eiffel-builder/12384)
> Revision: 231
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [230] Merge changes from rev 204 to rev 229 from eiffel6 branch into TRUNK](https://discourse.openehr.org/t/ref-impl-eiffel-230-merge-changes-from-rev-204-to-rev-229-from-eiffel6-branch-into-trunk/15946)
> Revision: 230
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [229] Remove the old makefiles and Ace files.](https://discourse.openehr.org/t/ref-impl-eiffel-229-remove-the-old-makefiles-and-ace-files/12814)
> Revision: 229
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [228] In common_libs_test, the external relied on the $OPENEHR environment variable.](https://discourse.openehr.org/t/ref-impl-eiffel-228-in-common-libs-test-the-external-relied-on-the-openehr-environment-variable/15945)
> Revision: 228
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [227] In the SConstruct, fix the Eiffel project aliases (broken by a revision committed a few hours ago).](https://discourse.openehr.org/t/ref-impl-eiffel-227-in-the-sconstruct-fix-the-eiffel-project-aliases-broken-by-a-revision-committed-a-few-hours-ago/12383)
> Revision: 227
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Demographic Archetypes](https://discourse.openehr.org/t/demographic-archetypes/14651)
> Hi, all\.
Please allow me to ask a question which may have been answered on this
list before\.
Just a hint to where I can find the information will do \(if possible\),
in that case, please also tell me the page/chapter, if possible, etc\.
Now my question,
As I am used from before, there should be demographic\-archetypes, which
have bindings to the RM\-objects which derive from Locatable\.
Such as Person, a\.o\. It is also still used as example in the ADL 1\.4
document, latest version...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [226] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-226-1/12813)
> Revision: 226
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [225] In the SCons Eiffel Builder, don't transform paths into absolute paths: this was necessary in old versions of Eiffel, but EiffelStudio 5.7 is smarter.](https://discourse.openehr.org/t/ref-impl-eiffel-225-in-the-scons-eiffel-builder-dont-transform-paths-into-absolute-paths-this-was-necessary-in-old-versions-of-eiffel-but-eiffelstudio-5-7-is-smarter/12382)
> Revision: 225
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [224] Fix adl_parser_test, which didn't compile due to renamed features in ASSERTION_FACTORY revision 213.](https://discourse.openehr.org/t/ref-impl-eiffel-224-fix-adl-parser-test-which-didnt-compile-due-to-renamed-features-in-assertion-factory-revision-213/12381)
> Revision: 224
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [223] In the SConstruct:](https://discourse.openehr.org/t/ref-impl-eiffel-223-in-the-sconstruct/12380)
> Revision: 223
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [222] Update the Macintosh installer's version from 1.4 to 1.4.2, consistent with the Windows installer.](https://discourse.openehr.org/t/ref-impl-eiffel-222-update-the-macintosh-installers-version-from-1-4-to-1-4-2-consistent-with-the-windows-installer/12379)
> Revision: 222
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [221] Add GTK-related files needed by the Macintosh version of ADL Workbench back into the Eiffel 5.7/Eiffel 6.0 test branch, but this time it comes from the 3rd-party repository as a Subversion external.](https://discourse.openehr.org/t/ref-impl-eiffel-221-add-gtk-related-files-needed-by-the-macintosh-version-of-adl-workbench-back-into-the-eiffel-5-7-eiffel-6-0-test-branch-but-this-time-it-comes-from-the-3rd-party-repository-as-a-subversion-external/12375)
> Revision: 221
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [220] Remove GTK-related files needed by the Macintosh version of ADL Workbench from the Eiffel 5.7/Eiffel 6.0 test branch, since these files are now kept in the 3rd-party repository.](https://discourse.openehr.org/t/ref-impl-eiffel-220-remove-gtk-related-files-needed-by-the-macintosh-version-of-adl-workbench-from-the-eiffel-5-7-eiffel-6-0-test-branch-since-these-files-are-now-kept-in-the-3rd-party-repository/12374)
> Revision: 220
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [219] Add GTK-related files needed by the Macintosh version of ADL Workbench to the 3rd-party repository.](https://discourse.openehr.org/t/ref-impl-eiffel-219-add-gtk-related-files-needed-by-the-macintosh-version-of-adl-workbench-to-the-3rd-party-repository/12373)
> Revision: 219
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [218] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-218-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12372)
> Revision: 218
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [217] Slight improvements in dADL parser error messages;](https://discourse.openehr.org/t/ref-impl-eiffel-217-slight-improvements-in-dadl-parser-error-messages/12371)
> Revision: 217
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [216] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-216-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12370)
> Revision: 216
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [215] Add missed TC_UML classes.](https://discourse.openehr.org/t/ref-impl-eiffel-215-add-missed-tc-uml-classes/12369)
> Revision: 215
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[231] updated parsing path-based term binding](https://discourse.openehr.org/t/231-updated-parsing-path-based-term-binding/12368)
> Revision: 231
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [214] Add C_DV_QUANTITY dADL text to dADL text classes](https://discourse.openehr.org/t/ref-impl-eiffel-214-add-c-dv-quantity-dadl-text-to-dadl-text-classes/12367)
> Revision: 214
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [213] Rename assertion API calls:](https://discourse.openehr.org/t/ref-impl-eiffel-213-rename-assertion-api-calls/12366)
> Revision: 213
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [new Archetypefinder version online](https://discourse.openehr.org/t/new-archetypefinder-version-online/12376)
> Dear all,
We uploaded a new version of the Archetypefinder. This new version at [http://www.archetypes.com.au](http://www.archetypes.com.au) allows you to search for all the latest archetypes (>200).
It also allows you to search for a certain term (e.g. blood) *within* the archetype - which is quite handy as we should avoid repetitive and overlapping archetypes (thanks to the work of Jana Graenz).
Apart from this comprehensive search, there are many other possibilities to search for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Understandability of archetypes when using openEHR Terminology](https://discourse.openehr.org/t/understandability-of-archetypes-when-using-openehr-terminology/14650)
> Dear all,
I am sorry if I this posting is a repetition because I was not able to
follow discussions properly nowadays\.
I find it very difficult and not user friendly at all \(of course during
manual writing of archetypes, not by using tools\) during both authoring
new archetypes or reading other archetypes when an openEHR Terminology
list is used\. For example take this one: property = <\[openehr::122\]>
which means "length"\.\.\.But I need to open Terminology file, find it...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[230] Updated XMLSerialiser to match changes in AOM (ArchetypeTerm).](https://discourse.openehr.org/t/230-updated-xmlserialiser-to-match-changes-in-aom-archetypeterm/12365)
> Revision: 230
Author: erik\.sundvall
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[229] Updated ADLSerialiser and some tests to match changes in AOM (ArchetypeTerm).](https://discourse.openehr.org/t/229-updated-adlserialiser-and-some-tests-to-match-changes-in-aom-archetypeterm/12364)
> Revision: 229
Author: erik\.sundvall
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[228] ArchetypeTerm has replaced the now deprecated DefinitionItem.](https://discourse.openehr.org/t/228-archetypeterm-has-replaced-the-now-deprecated-definitionitem/12360)
> Revision: 228
Author: erik\.sundvall
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [xml schemas finalised?](https://discourse.openehr.org/t/xml-schemas-finalised/13540)
> I have a project that needs some certainty with regards
the XML schema for 1\.0\.1\. Are they considered part of
the 1\.0\.1 release or are they on a different schedule?
I still have some blocking issues with the current versions in
subversion
Composition\.xsd \-> COMPOSITION no longer is an
extension of LOCATABLE\. I think this must be a typo?
Archetype\.xsd \-> ARCHETYPE\_ONTOLOGY is
inadequate to store the ontology data that can be
expressed in ADL\. Even if term\_codes is...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [212] Fix a precondition violation in revision 211, which did not check the number of components in the path before examining it.](https://discourse.openehr.org/t/ref-impl-eiffel-212-fix-a-precondition-violation-in-revision-211-which-did-not-check-the-number-of-components-in-the-path-before-examining-it/12359)
> Revision: 212
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [211] Fix SHARED_RESOURCES.application_startup_directory and SHARED_RESOURCES.application_full_path, which were returning the application's current working directory rather than the start-up directory.](https://discourse.openehr.org/t/ref-impl-eiffel-211-fix-shared-resources-application-startup-directory-and-shared-resources-application-full-path-which-were-returning-the-applications-current-working-directory-rather-than-the-start-up-directory/12358)
> Revision: 211
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [210] In ADL Workbench, MAIN_WINDOW.current_work_directory was not persisted to adl_workbench.cfg.](https://discourse.openehr.org/t/ref-impl-eiffel-210-in-adl-workbench-main-window-current-work-directory-was-not-persisted-to-adl-workbench-cfg/12357)
> Revision: 210
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [209] In the SConstruct, subdirectories of the "icons" directory were not listed as dependencies for ADL_Workbench, msi.](https://discourse.openehr.org/t/ref-impl-eiffel-209-in-the-sconstruct-subdirectories-of-the-icons-directory-were-not-listed-as-dependencies-for-adl-workbench-msi/12789)
> Revision: 209
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [208] Fix an error caused in trunk revision 202.](https://discourse.openehr.org/t/ref-impl-eiffel-208-fix-an-error-caused-in-trunk-revision-202/15943)
> Revision: 208
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [New FAQ on Observation and Evaluation Entry types in archetype development](https://discourse.openehr.org/t/new-faq-on-observation-and-evaluation-entry-types-in-archetype-development/12361)
> Some people building archetypes have had questions over the role of the
different openEHR Entry types, in particular Observation and Evaluation\.
A new FAQ page at http://www.openehr.org/FAQs/t_entry_types_FAQ.htm
discusses this issue\.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[227] added support for parsing empty C_DV_ORDINAL](https://discourse.openehr.org/t/227-added-support-for-parsing-empty-c-dv-ordinal/12355)
> Revision: 227
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[226] added support for comment in term and constraint definitions](https://discourse.openehr.org/t/226-added-support-for-comment-in-term-and-constraint-definitions/12354)
> Revision: 226
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[225] added ArchetypeTerm class and updated ArchetypeOntology methods](https://discourse.openehr.org/t/225-added-archetypeterm-class-and-updated-archetypeontology-methods/12353)
> Revision: 225
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[224] fixed parsing issue for ArchetypeID with multiple specialisation](https://discourse.openehr.org/t/224-fixed-parsing-issue-for-archetypeid-with-multiple-specialisation/12346)
> Revision: 224
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[223] updated EHR constructor and attribute](https://discourse.openehr.org/t/223-updated-ehr-constructor-and-attribute/12345)
> Revision: 223
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[222] minor code improvement](https://discourse.openehr.org/t/222-minor-code-improvement/12778)
> Revision: 222
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [CR: Allow empty lists in class EHR](https://discourse.openehr.org/t/cr-allow-empty-lists-in-class-ehr/12350)
> Hi\!
The current java code does not allow empty lists for contributions and
compositions when creating new EHR objects this is stricter than the
specification\. The spec only states that the target of the attributes
pointing to the lists must not be null\. My interpretation is that
empty lists should be allowed and that empty lists are useful when
creating a new blank EHR\.
The patch below describes my little change proposal\. Do you want me to
submit it to the TRUNK version in SVN?
Best...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [207] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-207-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12344)
> Revision: 207
Author: peter\.gummer
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR Release 1.0.1 published](https://discourse.openehr.org/t/openehr-release-1-0-1-published/12348)
> It has been a long wait, but we completed Release 1\.0\.1 of the openEHR
specifications over the weekend\. Quoting from the home page:
openEHR RELEASE 1\.0\.1
published 15 April 2007
The result of 14 months' review, implementation and testing, this
release is a major milestone, correcting and improving the openEHR
Release 1\.x platform\. We believe Release 1\.0\.1 to be a stable base for
ongoing implementation and forthcoming specifications, including the
Template Model, EHR Extract,...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [org.openehr.rm.ehr.EHR: getAllCompositions](https://discourse.openehr.org/t/org-openehr-rm-ehr-ehr-getallcompositions/12698)
> Hi\!
Is there any specific reason why the method to get compositions in the
class org\.openehr\.rm\.ehr\.EHR is called "getAllCompositions" instead of
"getCompositions"?
The same goes for "setAllCompositions"\.
Best regards,
Erik Sundvall
http://www.imt.liu.se/~erisu/
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [206] Make first language chosen the original_language of archetype (previously, was first language found in languages combo in GUI).](https://discourse.openehr.org/t/ref-impl-eiffel-206-make-first-language-chosen-the-original-language-of-archetype-previously-was-first-language-found-in-languages-combo-in-gui/12343)
> Revision: 206
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [assumed value in C_DURATION in xml schema](https://discourse.openehr.org/t/assumed-value-in-c-duration-in-xml-schema/12341)
> Is of type xs:duration, but must actually be
oe\_duration
in order to support the Openehr
extensions to the ISO duration format
\(the addition of the W week specifier\)\.
The other references to durations in the
schema are correct\.
Andrew
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [C_DEFINED_OBJECT](https://discourse.openehr.org/t/c-defined-object/14644)
> C\_DEFINED\_OBJECT in the current XML schema
is missing a
any\_allowed
boolean value\. Is this an oversight or is there some
other mechanism to express the wildcard
semantics?
Andrew
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [node_id is compulsory in all C_OBJECT subclasses](https://discourse.openehr.org/t/node-id-is-compulsory-in-all-c-object-subclasses/15942)
> Yet C\_PRIMITIVE\_OBJECT objects will not normally
have any node id \(i\.e\. at code\) set in the ADL? What
value should they use?
Andrew
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ARCHETYPE_TERM is not referenced in AOM (and XML schema)](https://discourse.openehr.org/t/archetype-term-is-not-referenced-in-aom-and-xml-schema/13216)
> term\_attribute\_names is listed in the AOM document
\(pg 51\) as type List<string> but surely this should be
of type List<ARCHETYPE\_TERM>?
The XML schema have used the same definition
so they need to be fixed as well\.
Andrew
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [205] The SConstruct now automates the build of a Mac OS X installer for ADL Workbench, by calling PackageMaker.](https://discourse.openehr.org/t/ref-impl-eiffel-205-the-sconstruct-now-automates-the-build-of-a-mac-os-x-installer-for-adl-workbench-by-calling-packagemaker/15941)
> Revision: 205
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Implementation Work](https://discourse.openehr.org/t/implementation-work/12340)
> All,
I am giving a short overview of openEHR at OSHCA2007 next month\.
I would like to show attendees that there is real implementation work in
progress\.
If you are working on an openEHR project or any archetype project then I
would appreciate an email with a short description of the work you are
doing\. Also if there is a public website where more information can be
found about your project then please supply that as well\.
Regards,
Tim
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Demographic archetype](https://discourse.openehr.org/t/demographic-archetype/12349)
> Dear all,
We're creating a Dutch demographic archetype PERSON\. My question is:
how can we create a demographic archetype using the OI or the LUI
Archetype editor \(latest release\)\.
By default \(so far I can see/understand\) the only reference models
these 2 editors support is the openEHR\-EHR and we need to use the
openEHR\-DEMOGRAPHIC reference model\.
Regards,
Stef Verlinden
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [204] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-204-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12339)
> Revision: 204
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [203] Update version file and correct version entry in help files.](https://discourse.openehr.org/t/ref-impl-eiffel-203-update-version-file-and-correct-version-entry-in-help-files/12338)
> Revision: 203
Author: thomas\.beale
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [unicode release of ADL workbench](https://discourse.openehr.org/t/unicode-release-of-adl-workbench/12347)
> Unicode support as well as some minor performance improvements have been
added to the ADL workbench\. See the ADL workbench help page \-
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm.
There is an english/farsi family history archetype in the test/unicode
directory of the Subversion knowledge repository to test it on\. I
believe that the Turkish translation of the Observation/mst\_colon
archetype also now displays correctly \- it requires unicode as well, due
to...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [202] Add unicode documentation](https://discourse.openehr.org/t/ref-impl-eiffel-202-add-unicode-documentation/12337)
> Revision: 202
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [201] Merge eiffel6 branch modifications in:](https://discourse.openehr.org/t/ref-impl-eiffel-201-merge-eiffel6-branch-modifications-in/12768)
> Revision: 201
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Help using ADL workbench.](https://discourse.openehr.org/t/help-using-adl-workbench/14643)
> I am lost in the adl\-workbench projects\. Maybe the simplest thing to do
is to provide a binary
I spent some time now in opening Eiffeprojects, Visual Studio projects,
etc, but have problems like, f\.e\. missing classes
Since it is not my primary task at this moment, and my primary task
takes huge lots of times, I would be delighted if I could just get a
running copyu of the most recent ADL\-workbench\.
I did not find a download link on the website, but maybe I overlooked\.
Thanks in...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [200] Fix two errors with ADL Workbench icons:](https://discourse.openehr.org/t/ref-impl-eiffel-200-fix-two-errors-with-adl-workbench-icons/12766)
> Revision: 200
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [199] Revision 195 sped up the loading of an archetype into ADL Workbench by checking whether the language combo box has focus, but this does not work correctly on Mac (and probably all GTK platforms), where EV_COMBO_BOX.has_focus is False](https://discourse.openehr.org/t/ref-impl-eiffel-199-revision-195-sped-up-the-loading-of-an-archetype-into-adl-workbench-by-checking-whether-the-language-combo-box-has-focus-but-this-does-not-work-correctly-on-mac-and-probably-all-gtk-platforms-where-ev-combo-box-has-focus-is-false/12334)
> Revision: 199
Author: peter\.gummer
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype Editors](https://discourse.openehr.org/t/archetype-editors/14649)
> I must say, good news, it is possible to work with the
Archetype\-editors, although there still are some quirks\.
I like the Swedisch ArcehtypeEditor because of the \(kind of\) debugging
facility
And I like the Workbench,b ecause it gives a lot of flexibility\.
It is too bad, that both do not seem to have \(completely\) the same
syntax\-ideas, although, they match for over 99%\.
I found some problems:
The Swedish editor does not want
language
original\_language =...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [198] Revert the last change to ADL Workbench's Test page, i.e, , remove the "UTF-8" test.](https://discourse.openehr.org/t/ref-impl-eiffel-198-revert-the-last-change-to-adl-workbenchs-test-page-i-e-remove-the-utf-8-test/12333)
> Revision: 198
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR-EHR-OBSERVATION.blood_pressure.v1 ISO TC215 WG7 and NHS comments.doc](https://discourse.openehr.org/t/openehr-ehr-observation-blood-pressure-v1-iso-tc215-wg7-and-nhs-comments-doc/14639)
> Thanks Melvin - you may want to pass this around...
Tom Seabury has raised comments that are very thoughtful - I have included some of his as well.
# Melvin's collation of commentsThe descriptionThe description at present reads:
"the measurement of systemic arterial blood pressure which is deemed to represent the actual systemic blood pressure"
The comment reads:
"Horribly inaccurate!
Maybe: "the non-invasive measurement of systemic arterial blood pressure which is deemed to represent...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [197] Revert the last change to STRING_UTILITIES.utf8, to avoid the performance hit.](https://discourse.openehr.org/t/ref-impl-eiffel-197-revert-the-last-change-to-string-utilities-utf8-to-avoid-the-performance-hit/12332)
> Revision: 197
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL / OpenEHR IM mismatch](https://discourse.openehr.org/t/adl-openehr-im-mismatch/15940)
> Hello everybody,
We are working on the Standard representation of Archetype Domain Types. When trying to convert a CDvQuantity object we found a possible mismatch between the ADL representation of a CDvQuantity and the EHR IM DvQuantity. According to the OpenEHR Archetype Profile document, an inline representation of the CDvQuantity is
age matches {
C_DV_QUANTITY <
property = <[openehr::128]> -- time
list = <
["1"] = <
units = <"yr">
magnitude = <|0.0..200.0|>
precision = <|2|>
>
>
}
and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [196] Fix a problem with Unicode support.](https://discourse.openehr.org/t/ref-impl-eiffel-196-fix-a-problem-with-unicode-support/15939)
> Revision: 196
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [195] Speed up the loading of an archetype into the ADL Workbench user interface.](https://discourse.openehr.org/t/ref-impl-eiffel-195-speed-up-the-loading-of-an-archetype-into-the-adl-workbench-user-interface/12331)
> Revision: 195
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [194] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-194-1/12329)
> Revision: 194
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [193] ADL Workbench was unable to display more than one language on Mac (and probably all GTK platforms) due to a bug in the event handler on the language selection combo box: instead of using the text of the selected combo box item, it wa](https://discourse.openehr.org/t/ref-impl-eiffel-193-adl-workbench-was-unable-to-display-more-than-one-language-on-mac-and-probably-all-gtk-platforms-due-to-a-bug-in-the-event-handler-on-the-language-selection-combo-box-instead-of-using-the-text-of-the-selected-combo-box-item-it-wa/12754)
> Revision: 193
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [192] 1.](https://discourse.openehr.org/t/ref-impl-eiffel-192-1/15937)
> Revision: 192
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [191] Correct bug in archetype_term_code_tools (how did the tool work before?)](https://discourse.openehr.org/t/ref-impl-eiffel-191-correct-bug-in-archetype-term-code-tools-how-did-the-tool-work-before/12327)
> Revision: 191
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [another NHS CFH archetypes review](https://discourse.openehr.org/t/another-nhs-cfh-archetypes-review/12326)
> All,
We are opening another archetypes review for detailed comments, this time
focusing feedback on 3 example archetypes \- blood pressure, adverse reaction
and substance use\. The review material may be found at
http://www.ehr.chime.ucl.ac.uk/display/nhsmodels/2007-04-02+Review.
We would welcome your comments by \*Monday, 2nd April\*\.
Please feel free to contact me, if you have any questions about this review
or about the overall project\.
Best regards,
Laura
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 status](https://discourse.openehr.org/t/release-1-0-1-status/12335)
> Dear friends,
All of the Release 1\.0\.1 specifications are now online, in their
expected final form
\(http://svn.openehr.org/specification/BRANCHES/Release-1.0.1-candidate/publishing/roadmap.html).
Some people are reporting minor typos which we are fixing as we go;
please keep them coming\.\.\.\.
As noted in another post, the Release 1\.0\.1 XML \-schemas are now online
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 candidate XML-schemas online](https://discourse.openehr.org/t/release-1-0-1-candidate-xml-schemas-online/14634)
> Dear all,
the latest drafts of the Release 1\.0\.1 XML schemas are now online \- see
http://svn.openehr.org/specification/BRANCHES/Release-1.0.1-candidate/publishing/its/XML-schema/index.html.
There are still some details to be fixed on this page, but we believe
the schemas are close to correct\. Feedback welcome\.
Thanks to Chunlan Ma and Heath Frankel for working on these, and to
Mattias Forss, Andrew Patterson and others here for their continued
feedback\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype slots](https://discourse.openehr.org/t/archetype-slots/14636)
> I am somewhat confused by the current implementation for archetype slots in the LiU and Ocean editors.
Whilst within SECTION archetypes, the full range of archetype slots can be embedded (OBSERVATION,EVALUATION.ACTION …), within, for example, an EVALUATION archetype the LiU editor supports only simple structural concepts such as list, tree and table whilst the Ocean editor supports only Element or Cluster style archetypes. Are these limitations of the editor implementations or are these...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Google comes with free EPD](https://discourse.openehr.org/t/google-comes-with-free-epd/12320)
> with advertising, datamining, etc\.
I found the information on a paid Dutch ICT news site http://www.qure.nl
http://www.practicefusion.com/
The site will be paid with AdSense, half of the Asense income will go
back to practicefusion\.
If it can be seen as a Google business or not, I cannot judge\.
More...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [190] ADL Workbench can now be built on Mac OS X PowerPC with EiffelStudio 5.7.64380, installed according to the instructions at http://eiffelsoftware.origo.ethz.ch/index.php/MacPorts_Gtk_Installation.](https://discourse.openehr.org/t/ref-impl-eiffel-190-adl-workbench-can-now-be-built-on-mac-os-x-powerpc-with-eiffelstudio-5-7-64380-installed-according-to-the-instructions-at-http-eiffelsoftware-origo-ethz-ch-index-php-macports-gtk-installation/12319)
> Revision: 190
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [189] Delete adl_cmd_line from the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-189-delete-adl-cmd-line-from-the-eiffel-5-7-eiffel-6-0-test-branch/12740)
> Revision: 189
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [A possible approach to model concepts with encapsulated data](https://discourse.openehr.org/t/a-possible-approach-to-model-concepts-with-encapsulated-data/15239)
> Dear all,
All that it takes is a "killer" function ;\)
The problem became obvious when discussing about ECG and Archetypes
recently\. When you want to assemble an archetype either for ECG or for a
composite concept with ECG data \(possibly not conforming to usual ECG
form\), electronic version of ECG contains both biosignal data and
annotations which contain valuable contextual data and clinical
information\. This also true for other modalities like EEG, EMG to name...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Representing binary data in XML schema](https://discourse.openehr.org/t/representing-binary-data-in-xml-schema/14635)
> Dear All,
I'm currently finalizing the release 1\.0\.1 RM XML schema\. I wonder if
anyone has any alternative suggestions on how to represent binary data
\(attributes "data" and "integrity\_check"\) in DV\_MULTIMEDIA? The current
schema uses type of "xs:base64Binary"\.
Thank you in advance\!
Best regards,
Chunlan
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[221] more explicit testcase for archetype slot parsing](https://discourse.openehr.org/t/221-more-explicit-testcase-for-archetype-slot-parsing/15935)
> Revision: 221
Author: rong\.chen
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Linköpings University Archetype Editor release](https://discourse.openehr.org/t/linkopings-university-archetype-editor-release/12322)
> Announcement:
The LiU Archetype Editor, version 0\.5\.2, by the Medical Informatics
group at the Department of Biomedical Engineering at Linköping
University in Sweden has now been released for public download\.
This release is historic in the sense that the ongoing harmonisation
among different openEHR specification and tool authors has reached a
point where the tools are compatible\. The official openEHR clinical
archetypes at http://svn.openehr.org/knowledge/archetypes/dev/index.html
are...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[cis-wg] Complexity, killer apps and other conundrums of health information was: cis-wg Digest, Vol 37, Issue 12 (Juliana Brixey)](https://discourse.openehr.org/t/cis-wg-complexity-killer-apps-and-other-conundrums-of-health-information-was-cis-wg-digest-vol-37-issue-12-juliana-brixey/14575)
> \[apologies for cross posting but I doubt it'll offend too many\]
Hi Tom \(and all\),
This is certainly true\.
The CDA and the more constrained CCD demonstrate very effectively the
difficulty in transferring health care information along with it's
semantic context\.
This is of course the reason for the development of two level modeling
and the maturation of over two decades work into the openEHR Reference
Model and Archetypes as data descriptors\. See: http://www.openehr.org
I...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [188] ADL Workbench can now display Unicode.](https://discourse.openehr.org/t/ref-impl-eiffel-188-adl-workbench-can-now-display-unicode/12318)
> Revision: 188
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Assertion objects in ADL parser](https://discourse.openehr.org/t/assertion-objects-in-adl-parser/12726)
> Hi all,
I have recently detected a small issue when serializing archetypes into ADL with the ADL serializer. The problem is that the serializer relies on that the string expression of Assertion objects (found in includes and excludes of ArchetypeSlot objects) is set, but the ADL parser always sets it to null.
I think it would be good from a maintenance point of view if the ADL serializer could output Assertion objects only by using the string expression, hence relieving it of the tedious...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [187] Remove ADL command line](https://discourse.openehr.org/t/ref-impl-eiffel-187-remove-adl-command-line/12317)
> Revision: 187
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [186] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-186-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12316)
> Revision: 186
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [185] remove old Ehr_extract directory](https://discourse.openehr.org/t/ref-impl-eiffel-185-remove-old-ehr-extract-directory/12315)
> Revision: 185
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [184] Merge Eiffel 5.7/6 changes from eiffel6 branch](https://discourse.openehr.org/t/ref-impl-eiffel-184-merge-eiffel-5-7-6-changes-from-eiffel6-branch/12314)
> Revision: 184
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [183] Final cut of software using Eiffel 5.6 tools](https://discourse.openehr.org/t/ref-impl-eiffel-183-final-cut-of-software-using-eiffel-5-6-tools/12313)
> Revision: 183
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[220] Made a small fix in the part of the ADL serializer that outputs Assertion objects.](https://discourse.openehr.org/t/220-made-a-small-fix-in-the-part-of-the-adl-serializer-that-outputs-assertion-objects/12311)
> Revision: 220
Author: mattias\.forss
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [181] The last bug fix in the SCons Eiffel Builder introduced a new bug: it didn't work if the given .ecf file was in the same directory as the SCons script.](https://discourse.openehr.org/t/ref-impl-eiffel-181-the-last-bug-fix-in-the-scons-eiffel-builder-introduced-a-new-bug-it-didnt-work-if-the-given-ecf-file-was-in-the-same-directory-as-the-scons-script/12307)
> Revision: 181
Author: peter\.gummer
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 candidate area SVN link](https://discourse.openehr.org/t/release-1-0-1-candidate-area-svn-link/12309)
> We have just changed \(apparently successfully\) the openEHR specification
subversion repository release 1\.0\.1 branch to its correct URL, which is
http://svn.openehr.org/specification/BRANCHES/Release-1.0.1-candidate
This will break a few URLs you may have stored, and probably has broken
more URLs on the site than we realise; for the latter please let us know\.
Thanks for your understanding\.
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [180] Add ECF files to upgrade to EiffelStudio 5.7, and update the SConstruct to build them.](https://discourse.openehr.org/t/ref-impl-eiffel-180-add-ecf-files-to-upgrade-to-eiffelstudio-5-7-and-update-the-sconstruct-to-build-them/12306)
> Revision: 180
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [179] Correct a bug in the SCons Eiffel Builder.](https://discourse.openehr.org/t/ref-impl-eiffel-179-correct-a-bug-in-the-scons-eiffel-builder/15934)
> Revision: 179
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [178] Merge changes from the trunk into the Eiffel 5.7/Eiffel 6.0 test branch.](https://discourse.openehr.org/t/ref-impl-eiffel-178-merge-changes-from-the-trunk-into-the-eiffel-5-7-eiffel-6-0-test-branch/12305)
> Revision: 178
Author: peter\.gummer
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[219] non-inclusive integer and real interval parsing](https://discourse.openehr.org/t/219-non-inclusive-integer-and-real-interval-parsing/12304)
> Revision: 219
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [177] Implement CR-000244: Separate LOCATABLE path functions into PATHABLE class](https://discourse.openehr.org/t/ref-impl-eiffel-177-implement-cr-000244-separate-locatable-path-functions-into-pathable-class/12303)
> Revision: 177
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[218] fixed missing upper bound in duration parsing](https://discourse.openehr.org/t/218-fixed-missing-upper-bound-in-duration-parsing/12715)
> Revision: 218
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Error in terminology.xml?](https://discourse.openehr.org/t/error-in-terminology-xml/14638)
> This line is in it:
<Concept Language="en" ConceptID="32" Rubric="Subject of data" />
when you go to grouper:
<Grouper id="1" ConceptID="32" />
and then to groupedconcept:
<GroupedConcept GrouperID="1" ChildID="0" />
<GroupedConcept GrouperID="1" ChildID="3" />
<GroupedConcept GrouperID="1" ChildID="6"...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EHR message example and schema](https://discourse.openehr.org/t/ehr-message-example-and-schema/12302)
> Hi,
I want to ask you if exists a schema for EHRcom message/extract and if the schema is avalaible for download. I'm creating an ontology of EHRcom extracts/message and if I can find some xml example (better a xsd schema) I think my work could be most complete. I've done this work on HL7 CDA schema and I'm trying to find a common metodology (If is possible) to do this task (create an OWL description of a message from a XSD schema) on a generic EHR message.
davide
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [A virtual bottle of champagne for...](https://discourse.openehr.org/t/a-virtual-bottle-of-champagne-for/12235)
> Dear all,
I would like to share a virtual bottle with champagne with you:
It looks like thanks to the hard work of Tom, Rong, Sam and many others we are very close to a subversion tag where 100% of the archetypes are being parsed by 100% of the existing ADL Parsers!
Cheers,
Sebastian
Dr Sebastian Garde
*Dr. sc....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [176] Update our override of SYsTEM_STRING_FACTORY to convert correctly back from a .NET Unicode string to a standard Eiffel STRING with UTF-8 encoding.](https://discourse.openehr.org/t/ref-impl-eiffel-176-update-our-override-of-system-string-factory-to-convert-correctly-back-from-a-net-unicode-string-to-a-standard-eiffel-string-with-utf-8-encoding/12300)
> Revision: 176
Author: peter\.gummer
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [wsvn interface - tarball option temporarily removed](https://discourse.openehr.org/t/wsvn-interface-tarball-option-temporarily-removed/12714)
> Dear all,
we have temporarily removed the websvn option to generate 'tarballs'
\(i\.e\. zipped & tarred archives\) from the openEHR Subversion repositories
because web robots \(google, msn etc\) cause an extremely heavy load by
hitting the tarball links for entire repositories\. We have to make a
change to the subversion configuration to prevent this happening
\(technically: to allow a robots\.txt file to be installed and read
properly\)\. However, as the openEHR Release 1\.0\.1...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[217] allow ordinal with negative value](https://discourse.openehr.org/t/217-allow-ordinal-with-negative-value/12296)
> Revision: 217
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CLUSTER archetypes](https://discourse.openehr.org/t/cluster-archetypes/14632)
> I have noticed a large number of CLUSTER archetypes
in the openehr archetype sample repository\. I was wondering
if anyone could explain the relationship between
the CLUSTER archetypes and the ENTRY\.OBSERVATION
archetypes \(there seems to be some overlap between them\)\.
I'm guessing this is a result of some work in Europe \(NHS?\) that
needs to be mapped onto CEN in a way that the
OBSERVATION/ENTRY system can't be\. Can anyone
give a non\-clinical explanation of the relative...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[216] Updated the ADLSerializer to conform with the changes to the language, description and ontology sections.](https://discourse.openehr.org/t/216-updated-the-adlserializer-to-conform-with-the-changes-to-the-language-description-and-ontology-sections/15932)
> Revision: 216
Author: mattias\.forss
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Release 1.0.1 UML online](https://discourse.openehr.org/t/openehr-release-1-0-1-uml-online/15933)
> The final Release 1\.0\.1 draft UML is now online at
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/computable/UML/uml_start_view.html
This has been made possible by another marathon effort by David Lloyd,
to whom we are all indebted for an invaluable online resource\.
Most of the PDFs are online in their final form as well, at
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.html
Any feedback on errors, typos...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New knowledge repository changes](https://discourse.openehr.org/t/new-knowledge-repository-changes/15574)
> Dear all,
the openEHR archetypes in the SVN knowledge repository have been
updated\. Only the archetypes under 'dev' are changed \- all other
archetypes are under management of other groups\. I believe this cut must
be ADL 1\.4 compliant, or very close to that\. Can those with archetype
tools run a check on this version; we are upgrading our checking tools
as well\.
I now have the go ahead to fix any final remaining errors as they are
identified\.
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Kitchen-sink standards & the Structure Document Complexity Metric](https://discourse.openehr.org/t/kitchen-sink-standards-the-structure-document-complexity-metric/12236)
> I like the notion of the Structure Document Complexity Metric
mentioned in this column:
http://www.oreillynet.com/xml/blog/2007/03/usage_schemas_to_tame_odf_and.html
http://www.oreillynet.com/xml/blog/2006/05/metrics_for_xml_projects_5_str_1.html
could it be relevant to patient record documents?
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [ECG archetypes](https://discourse.openehr.org/t/ecg-archetypes/14640)
> Greetings all;
We are two graduate students from Aalborg University, Denmark, taking our
master in Biomedical Engineering and Informatics\. In this semester our
finale, we are working with complex data interoperability to an Electronic
Health Record \(EHR\)\. We are following the openEHRs EHR architecture standard,
and therefore also working with archetypes\.
We have a few questions we would like you to help us deal with\.
\- What we are trying to investigate is how to represent a...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [175] Add the SCons Eiffel builder for EiffelStudio 5.7 and above.](https://discourse.openehr.org/t/ref-impl-eiffel-175-add-the-scons-eiffel-builder-for-eiffelstudio-5-7-and-above/15931)
> Revision: 175
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [174] Add EiffelStudio 5.7 config file for adl_dotnet_lib, plus some overrides for Unicode compatibility.](https://discourse.openehr.org/t/ref-impl-eiffel-174-add-eiffelstudio-5-7-config-file-for-adl-dotnet-lib-plus-some-overrides-for-unicode-compatibility/15930)
> Revision: 174
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [173] Add SCons build scripts for EiffelStudio 5.6.](https://discourse.openehr.org/t/ref-impl-eiffel-173-add-scons-build-scripts-for-eiffelstudio-5-6/12295)
> Revision: 173
Author: peter\.gummer
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [172] Add new .ecf file for ADL workbench, Eiffel 5.7 build](https://discourse.openehr.org/t/ref-impl-eiffel-172-add-new-ecf-file-for-adl-workbench-eiffel-5-7-build/12294)
> Revision: 172
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Antenatal Booking Assessment](https://discourse.openehr.org/t/antenatal-booking-assessment/12012)
> Greetings all;
I am working on an archetype for an antenatal booking assessment \(i\.e\.
the first antenatal appointment of a pregnancy\) and I am trying to find
some examples of the kinds of information that would be recorded by a
clinician \(OB or midwife\) at such an encounter\.
Does anyone on this list have access to such information and the
willingness to share it?
This archetype forms part of the NHS clinical record architecture pilot
project in the UK, which is being coordinated by...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [171] Branch for updating all builds to Eiffel 6, including unicode capability.](https://discourse.openehr.org/t/ref-impl-eiffel-171-branch-for-updating-all-builds-to-eiffel-6-including-unicode-capability/12699)
> Revision: 171
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [terminology](https://discourse.openehr.org/t/terminology/12297)
> Hi,
I hope this is a stupid question, and people can overload me with information.
I am trying to build a terminology-service, but because I want to conform as much as possible to the specs, I try to understand them.
I have a few questions:
we have the openehr-terminology, like this: (excuse me for using html-table)
|
Terminology: openehr
|
|
Group_name(“en”): “attestation...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CEN published En13606-1 EHRcom. Tutorial about Archetypes](https://discourse.openehr.org/t/cen-published-en13606-1-ehrcom-tutorial-about-archetypes/15756)
> Dear reader,
**Healthcare of the future needs ICT-systems of the future.**
Healthcare needs systems that are:
-patient safe,
-help respect privacy and
-make 'plug-and-play' exchange between systems possible,
CEN/tc251 has published part 1 of a new exciting European standard for the EHR.
It is CEN/tc251 EN13606 EHRcom.
Together with other CEN standards it will make possible 'plug-and-play' semantic interoperability between conforming EHR-systems.
1- ConSys: System of Concepts for Continuity...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [170] Update .msi build & help page for last fixes.](https://discourse.openehr.org/t/ref-impl-eiffel-170-update-msi-build-help-page-for-last-fixes/15929)
> Revision: 170
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [169] Fix bug where commas in comments in multi-line C_CODE_PHRASE were not scanned properly;](https://discourse.openehr.org/t/ref-impl-eiffel-169-fix-bug-where-commas-in-comments-in-multi-line-c-code-phrase-were-not-scanned-properly/15928)
> Revision: 169
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [TERMINOLOGY_ID](https://discourse.openehr.org/t/terminology-id/12163)
> I am trying to create a CODE\_PHRASE object for
a region such as 'australia'\. The code\_string is
"AU", but I can't work out if the terminology\_id
should be "countries" \(the openehr code set
id described in Terminology\.pdf\) or "ISO\_3166\-1"
\(the external identifier\)\.
If it is meant to be the external identifier ISO\_3166,
what is the openehr codeset id for?
Andrew
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[215] updated boolean expression parsing in the parser](https://discourse.openehr.org/t/215-updated-boolean-expression-parsing-in-the-parser/15927)
> Revision: 215
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [168] Implement CR-000242: Allow non-inclusive two-sided ranges in ADL.](https://discourse.openehr.org/t/ref-impl-eiffel-168-implement-cr-000242-allow-non-inclusive-two-sided-ranges-in-adl/15926)
> Revision: 168
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New CR to handle non-inclusive two-sided ranges](https://discourse.openehr.org/t/new-cr-to-handle-non-inclusive-two-sided-ranges/12696)
> In the NHS work, Sam has discovered the need to support non\-inclusive
two\-sided ranges in ADL, e\.g\. 0 > x <= 1000
This means some relatively easy additions to the dADL parse rules \(you
need to include the dADL primitive type patterns in the cADL production
rule set as well\)\.
I have created a CR for this \- see
http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/242.
I will put up the changed ADL document in a day or so, as well as a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Where to use "en" and [ISO_639-1::en]](https://discourse.openehr.org/t/where-to-use-en-and-iso-639-1-en/14633)
> Hi\!
The current java adl\-parser \(built from repository sources today\) does
not parse the current \(refreshed my copu today\) archetypes in the
openEHR knowledge repository without tweaking language coding format\.
Note the different formats after original\_language in the examples
below\. What is correct?
Also note the required ISO style language information in the java
adl\-parser version under the path description \-> details \-> \["en"\] \->
language\. What is...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [{Disarmed} Antw: SV: comments welcome on draft NHS models](https://discourse.openehr.org/t/disarmed-antw-sv-comments-welcome-on-draft-nhs-models/15925)
> In een bericht met de datum 28-2-2007 23:45:01 West-Europa (standaardtijd), schrijft kb@mediq.dk:
> Laura,
> A very interesting set of archetypes, which I will be happy to review.
> There is a substantial bulk of descriptions of clinical content from the
> Region of Copenhagen, which can be used as a reference. These are not in
> ADL, unfortunately, but the information is there.
>
> A zip file for download with all the AT would be useful...
>
> Kind regards
> Knut
>...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [167] Add UID_BASED_ID class](https://discourse.openehr.org/t/ref-impl-eiffel-167-add-uid-based-id-class/12291)
> Revision: 167
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [166] Fix bug in serialising C_DV_ORDINAL with no items.](https://discourse.openehr.org/t/ref-impl-eiffel-166-fix-bug-in-serialising-c-dv-ordinal-with-no-items/12290)
> Revision: 166
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest ADL workbench](https://discourse.openehr.org/t/latest-adl-workbench/12685)
> A new release of the ADL workbench is available\. See
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
Changes in this release:
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help_whats_new_20070302.htm
\- thomas beale\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problems saving adl with Ocean Archetype Editor RC1 1233](https://discourse.openehr.org/t/problems-saving-adl-with-ocean-archetype-editor-rc1-1233/16647)
> Hi,
I have been playing with the Ocean Archetype Editor RC version but am
getting an "erro saving: Object Reference not set\.\.\." error when trying to
save the archetype after even a minor change with both my own ADL \+ official
OpenEHR ADL downloaded today e\.g\. the barthel index archetype\. Rebooting did
not help\.
Regards,
Ian
Dr Ian McNicoll
MCMI
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [165] Correct serialisation bug in Slot expressions where {} were being left off.](https://discourse.openehr.org/t/ref-impl-eiffel-165-correct-serialisation-bug-in-slot-expressions-where-were-being-left-off/12289)
> Revision: 165
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [repository at medinfo 2007?](https://discourse.openehr.org/t/repository-at-medinfo-2007/12288)
> Dear Sebastian,
I guess you are going to attend Medinfo 07. Would you be willing and available to do a keynote / workshop style presentation /discussion on repositories of care information models (independent of formalism and technology, i mean yes refer to openEhr and UK etc, but summarize all ongoing work and repositories)?
Evelyn and Joan take care of logistics. It is eather on monday or saturday after I believe.
William
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openehr at medinfo 2007](https://discourse.openehr.org/t/openehr-at-medinfo-2007/15573)
> I presume many here will be presenting papers
at Medinfo \(or attending\)\. Are there any plans
for any openehr meetings, BOF sessions etc?
We should at least have an openehr\-list
drinks on one of the nights, as it would be
good to be able to put faces to some of the
names\.
Andrew
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [comments welcome on draft NHS models](https://discourse.openehr.org/t/comments-welcome-on-draft-nhs-models/12278)
> To the openEHR clinical list:
As some of you may know, the NHS Connecting for Health \(CFH\) in England is
piloting the use of archetypes as an approach for building a detailed
national clinical record architecture\.
As the project manager, I would like to invite you to review and provide
comments on the first set of draft models, via the project wiki at
http://www.ehr.chime.ucl.ac.uk/display/nhsmodels/Home. Ocean Informatics
have been assisting us in this effort, and you will notice that...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Friendly spam: Dutch OpenEHR Archetype Tutorial March 2007](https://discourse.openehr.org/t/friendly-spam-dutch-openehr-archetype-tutorial-march-2007/12287)
> Dear colleagues,
In collaboration with Ocean Informatics two small Dutch companies (**conexis** and Vivici) organise a two day tutorial.
The topic is Archetypes and OpenEHR.
Dates: 29-30 March
Venue: Leiden University Hospital Centre
Cost: 800 Euro
Language: English
Tutors: Sam Heard and Heather Lesly
More information: [http://web.mac.com/g.freriks/iWeb/conexis/Welcome.html](http://web.mac.com/g.freriks/iWeb/conexis/Welcome.html)
It is still possible to register participants.
(maximal...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [new committers to the ref_impl_java project](https://discourse.openehr.org/t/new-committers-to-the-ref-impl-java-project/12286)
> Dear all,
Please warmly welcome three new committers to the ref_impl_java project: Bert Verhees, Erik Sundvall and Mattias Forss. They all have been very much involved in the Java project and have contributed to the ref_impl_java project in many ways.
Bert will be working with the persistence layer based on OR mapping (Hibernate 3). Mattias will be responsible for the adl-serializer and xml-serializer components, which are used by the Archetype Editor. Erik will lead the experiment on the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[214] Testing SVN commit access for imutable-experiment branch.](https://discourse.openehr.org/t/214-testing-svn-commit-access-for-imutable-experiment-branch/12285)
> Revision: 214
Author: erik\.sundvall
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Latest documents online](https://discourse.openehr.org/t/latest-documents-online/14626)
> Nearly all openEHR specifications are online in their latest form at
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.html
Don't bother looking at the "in\-development" ones \- they have not gone
up yet; the XML\-schema, UML and terminology are being updated to conform\.
All feedback welcome; these are very close to the final versions for
openEHR Release 1\.0\.1
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFI](https://discourse.openehr.org/t/rfi/12280)
> Dear All,
I’ve been reviewing EHR architectures recently, and I’ve been quite
impressed with openEHR\. I am inclined to use openEHR for a “greenfield”
implementation, and I have some initial questions after reading the
architecture overview, ADL specification and various other documents\.
Our initial implementation is for a small clinic \(<500 patients\) that
offers health / wellness and anti\-aging therapies\. We have a near\-term
requirement to store LOINC encoded HL7 lab results and...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[213] improved special string parsing in adl-parser](https://discourse.openehr.org/t/213-improved-special-string-parsing-in-adl-parser/12279)
> Revision: 213
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [164] Fix missing items in feb/26 ADL workbench release](https://discourse.openehr.org/t/ref-impl-eiffel-164-fix-missing-items-in-feb-26-adl-workbench-release/15924)
> Revision: 164
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [163] Add documentation for 26/Feb/2007 release.](https://discourse.openehr.org/t/ref-impl-eiffel-163-add-documentation-for-26-feb-2007-release/15923)
> Revision: 163
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [162] Updates for](https://discourse.openehr.org/t/ref-impl-eiffel-162-updates-for/12675)
> Revision: 162
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[212] add missing parser testcase](https://discourse.openehr.org/t/212-add-missing-parser-testcase/15922)
> Revision: 212
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[211] src/test/resources/adl-test-entry.c_dv_quantity_empty.test.adl](https://discourse.openehr.org/t/211-src-test-resources-adl-test-entry-c-dv-quantity-empty-test-adl/15921)
> Revision: 211
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[210] added support for generics in type_identifier](https://discourse.openehr.org/t/210-added-support-for-generics-in-type-identifier/12277)
> Revision: 210
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[209] added support for CDvQuantity starts with assumed value](https://discourse.openehr.org/t/209-added-support-for-cdvquantity-starts-with-assumed-value/12276)
> Revision: 209
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[208] updated assumed value parsing for CDvQuantity](https://discourse.openehr.org/t/208-updated-assumed-value-parsing-for-cdvquantity/12275)
> Revision: 208
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[207] updated lower limit of precision attribute in DvQuantity](https://discourse.openehr.org/t/207-updated-lower-limit-of-precision-attribute-in-dvquantity/12274)
> Revision: 207
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 Final drafts coming online](https://discourse.openehr.org/t/release-1-0-1-final-drafts-coming-online/12282)
> See the Release 1\.0\.1 specification page, look for Status = FINAL DRAFT\.
The remainder of the specifications will be appearing in final draft
over the next few weeks before we announce the release\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CEN meeting and data types](https://discourse.openehr.org/t/cen-meeting-and-data-types/14629)
> Dear All
I have been at the CEN working group meetings representing Standards Australia. It is clear to me that CEN needs to take on the openEHR data types in order to progress quickly. The ISO data types are likely to be appropriate for the HL7 environment and will map to openEHR - but the openEHR data types are ready for archetypes and the cluster element (leaf node) architecture.
You can have a look at the ISO data type proposal likely to come through HL7 soon...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetype lists and possible archetypes](https://discourse.openehr.org/t/archetype-lists-and-possible-archetypes/14627)
> Dear All (apologies for cross posting)
I have been discussing the slot assertions off line and want to make sure the clinical requirements in this space are understood by the clinical guys. At the moment the Ocean tools work on the same basis as the Apache url include and exclude statements but I won't go into that.
My view on the slots is that they have to be open by default (ie let other archetypes in) as the archetype is an absolute rule which cannot be broken. If we close slots in the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[206] several parser improvements](https://discourse.openehr.org/t/206-several-parser-improvements/12272)
> Revision: 206
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [CCR and openehr](https://discourse.openehr.org/t/ccr-and-openehr/14625)
> Has anyone looked at making an openehr
composition archetype\(s\) corresponding to
the ASTM continuity of care record \(CCR\)?
I don't have access to the ASTM standard
but I was just looking at the HL7 document
describing how CCR maps into CDAr2 and
was thinking that it would be a good test of
the power/generality of the openehr RM
to see if similar could be done for it\.
\(I realise that CCR has its own specific
adhoc XML schema that are incompatible with
the openehr RM, but at some...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[205] updated code_phrase related parsing and made ontology primary language optional](https://discourse.openehr.org/t/205-updated-code-phrase-related-parsing-and-made-ontology-primary-language-optional/12271)
> Revision: 205
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[204] improved assertion and archetype_slot parsing](https://discourse.openehr.org/t/204-improved-assertion-and-archetype-slot-parsing/12270)
> Revision: 204
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[203] create immutable experiment branch](https://discourse.openehr.org/t/203-create-immutable-experiment-branch/12660)
> Revision: 203
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Chat regarding thoughts about the java-ref-impl future](https://discourse.openehr.org/t/chat-regarding-thoughts-about-the-java-ref-impl-future/14621)
> Hi\!
Rong initiated a chat as a followup to a live meeting we had here at
LiU last Friday\. It is attached below\. We are circulating it to you in
order to get some comments and more thoughts regarding this, so feel
free to reply\!
Summary: We'll start an experimental branch to test an approach with
mutable classes in addition to immutable ones\. We won't mess with the
TRUNK version until the experiment is finished and tested/commented\.
Pros/cons of hardwiring client components...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [CR to adjust identifier types in Support IM](https://discourse.openehr.org/t/cr-to-adjust-identifier-types-in-support-im/14623)
> There was a request from some time ago from Heath Frankel that I now
just dealing with, in the Identification package of the Support IM \- see
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/support_im.pdf
The request is to make OBJECT\_VERSION\_ID a subtype of HIER\_OBJECT\_ID\.
The latter type is the general type for Ids based on a UID of some kind,
possibly with an extension\. The former type is a specific type based on
a UID, whose extension...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[202] fixed parsing translations without accreditation](https://discourse.openehr.org/t/202-fixed-parsing-translations-without-accreditation/12269)
> Revision: 202
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[201] improved c_dv_quantity parsing](https://discourse.openehr.org/t/201-improved-c-dv-quantity-parsing/12268)
> Revision: 201
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[200] improved adl output for Interval, CDvQuantity and ConstraintRef](https://discourse.openehr.org/t/200-improved-adl-output-for-interval-cdvquantity-and-constraintref/12267)
> Revision: 200
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[199] fixed a few bugs in adl-serializer](https://discourse.openehr.org/t/199-fixed-a-few-bugs-in-adl-serializer/12266)
> Revision: 199
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [proposed quantity package changes](https://discourse.openehr.org/t/proposed-quantity-package-changes/16648)
> I have uploaded a set of changes to the Quantity package that simplify the existing classes while not changing any of their data; see - [http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/data_types_im.pdf](http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/data_types_im.pdf)
This is the kind of thing I have been contemplating for some time. It properly distinguishes between date/time/datetime and other...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[198] corrected parsing constraint_ref](https://discourse.openehr.org/t/198-corrected-parsing-constraint-ref/12265)
> Revision: 198
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[197] update the root pom file](https://discourse.openehr.org/t/197-update-the-root-pom-file/12264)
> Revision: 197
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[196] added support for assumed_value in c_dv_quantity](https://discourse.openehr.org/t/196-added-support-for-assumed-value-in-c-dv-quantity/12263)
> Revision: 196
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[195] initial import of measurement service implementation](https://discourse.openehr.org/t/195-initial-import-of-measurement-service-implementation/15920)
> Revision: 195
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[194] fixed a bug in the constructor of CDvQuantity](https://discourse.openehr.org/t/194-fixed-a-bug-in-the-constructor-of-cdvquantity/12262)
> Revision: 194
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[192] added parser support for single value interval for primitive types](https://discourse.openehr.org/t/192-added-parser-support-for-single-value-interval-for-primitive-types/12260)
> Revision: 192
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[191] updated C_DV_QUANTITY parsing](https://discourse.openehr.org/t/191-updated-c-dv-quantity-parsing/12259)
> Revision: 191
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[190] fixed parsing issue caused by the order of description attributes](https://discourse.openehr.org/t/190-fixed-parsing-issue-caused-by-the-order-of-description-attributes/12648)
> Revision: 190
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[189] testcase verifies node paths after parsing](https://discourse.openehr.org/t/189-testcase-verifies-node-paths-after-parsing/12646)
> Revision: 189
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[188] parser backwards compatibility for archetypes without language section](https://discourse.openehr.org/t/188-parser-backwards-compatibility-for-archetypes-without-language-section/12258)
> Revision: 188
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[187] added missing language attribute in translation details parsing](https://discourse.openehr.org/t/187-added-missing-language-attribute-in-translation-details-parsing/12257)
> Revision: 187
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[186] loosened checks in TranslationDetails](https://discourse.openehr.org/t/186-loosened-checks-in-translationdetails/12256)
> Revision: 186
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[185] added support for translations in language part](https://discourse.openehr.org/t/185-added-support-for-translations-in-language-part/12255)
> Revision: 185
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[184] added support for assumedValue in all CPrimitive and CDvOrdinal, and pattern in CDuration in adl-serializer](https://discourse.openehr.org/t/184-added-support-for-assumedvalue-in-all-cprimitive-and-cdvordinal-and-pattern-in-cduration-in-adl-serializer/12254)
> Revision: 184
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[183] added support for assumedValue parsing in CDvOrdinal](https://discourse.openehr.org/t/183-added-support-for-assumedvalue-parsing-in-cdvordinal/12250)
> Revision: 183
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[182] minor testcase change](https://discourse.openehr.org/t/182-minor-testcase-change/12249)
> Revision: 182
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[181] chages that facilitate CDvOrdinal parsing](https://discourse.openehr.org/t/181-chages-that-facilitate-cdvordinal-parsing/12248)
> Revision: 181
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[180] minor change in CDvOrdinal to facilitate parsing](https://discourse.openehr.org/t/180-minor-change-in-cdvordinal-to-facilitate-parsing/12247)
> Revision: 180
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[179] fixed a bug in parsing c_code_phrase with empty code list](https://discourse.openehr.org/t/179-fixed-a-bug-in-parsing-c-code-phrase-with-empty-code-list/12246)
> Revision: 179
Author: rong\.chen
Log Message:
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Recent thoughts from Prof David Ingram](https://discourse.openehr.org/t/recent-thoughts-from-prof-david-ingram/15919)
> Professor David Ingram, head of the CHIME department at UCL
\(http://www.chime.ucl.ac.uk\), and chair of the openEHR Foundation has
published some recent thoughts on the state of play in e\-health and
related endeavours\. Please see the top hot\-link at
http://www.openEHR.org or go directory to
http://www.openehr.org/about_openehr/t_01_feb_2007_DI_commentary.htm
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [161] Corrections to ADL language section conversion code for older archetypes.](https://discourse.openehr.org/t/ref-impl-eiffel-161-corrections-to-adl-language-section-conversion-code-for-older-archetypes/15918)
> Revision: 161
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [loss of type information in ID classes](https://discourse.openehr.org/t/loss-of-type-information-in-id-classes/14622)
> I am looking at a round trip of information
through an XML serialization\. Normally, type
information can be retained in an xml
serializer through the use of xsi:type
\(so where an attribute is defined as type
PARTY\_PROXY, we can assign an object
of type PARTY\_SELF to that attribute
and do a round trip serialization and it will
still be PARTY\_SELF\)\.
The OBJECT\_ID hierarchy defines an
abstract root class with a single attribute
called...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Mental health archetypes](https://discourse.openehr.org/t/mental-health-archetypes/14630)
> Dear all,
We have a psychiatrist from Chile here for the next month who will work with us on developing an initial set of **Mental Health archetypes**.
We would like to set up a little group to discuss these archetypes from a clinical point of view...so anybody with an interest in this area please drop me a quick email, we would very much love you to join us (most likely virtually...) and work together with us on these archetypes.
Kind regards
Sebastian
Dr Sebastian Garde
Faculty of...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [160] Upgrade ADL workbench to process ADL 1.4 languages section, including translations - and display on 'description' tab](https://discourse.openehr.org/t/ref-impl-eiffel-160-upgrade-adl-workbench-to-process-adl-1-4-languages-section-including-translations-and-display-on-description-tab/12245)
> Revision: 160
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Value or Null_Flavor in CLUSTERs?](https://discourse.openehr.org/t/value-or-null-flavor-in-clusters/14628)
> Hi,
I know that this is probably something very inappropriate but I happened
to need such a solution\. An example:
CLUSTER \[AAAA\]
CLUSTER \[BBBB\] Some type of finding \(a lesion: ulcers\)
ELEMENT \[CCCC\] A Feature of the finding \(i\.e\. bleeding\)
v: some...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Language and translations](https://discourse.openehr.org/t/language-and-translations/14624)
> Rong has alerted me to the fact that the example on page 91 of the ADL manual is incorrect - the following is how it would look. I should have this working in the ADL workbench and Ocean Archetype Editor over the weekend.
language
original_language = <“en”>
translations = <
[“de”] = <
language = <“de”>
author = <
[“name”] = <"Frederik Tyler">
[“email”] = <["freddy@something.somewhere.co.uk"](mailto:freddy@something.somewhere.co.uk)>
>
accreditation = <"British Medical Translator id...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [photos on project pages](https://discourse.openehr.org/t/photos-on-project-pages/14617)
> We all like those little photos used in skype and other similar places. It occurs to me that we could put the same kind of small images in the openEHR project pages, along with the names of the team members. If there was interest in this, I am happy to modify the project page of some or all projects to do this.
any interest?
- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [HL7 vs openEHR](https://discourse.openehr.org/t/hl7-vs-openehr/15914)
> When I first began browsing *open*EHR information a few weeks ago, I read something on the web that left me with the impression that at least some *open*EHR people are in strong disagreement with HL7 people and/or parts of the HL7 standard (version 3, I presume). Would anyone be willing to educate me about this? Exactly where is the thinking within *open*EHR incompatible with the current trends of HL7?
Best regards
Ole Jørgen Anfindsen
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [a question on ATTESTATION of ORIGINAL_VERSION](https://discourse.openehr.org/t/a-question-on-attestation-of-original-version/14616)
> In sec 6\.2\.3, in the section on attestations is
> Attestations can be
> added at any time after committal of the content being attested\.
I can't work out how a new version adding nothing but a
new attestation would be formed \- wouldn't it require the
submission of all the content
of the existing version \(existing list of any attestations plus
all actual composition content\) with a new attestation added?
Or is there a mechanism to add an attestation without
resubmitting the...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [CONTRIBUTION questions](https://discourse.openehr.org/t/contribution-questions/15916)
> Hello all ehrplementers,
I am looking at the semantics and mechanisms of
versioning\. Whilst I understand that the CONTRIBUTION
class is not fully specified \(because much of how it
works is dependant on the particular implementation\)
I was wondering if anyone had some clarifications for
the following:
a\) the AUDIT\_DETAILS of CONTRIBUTION has a
mandatory attribute 'change\_type'\. Would I be right
in thinking that for a CONTRIBUTION...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [occurrences in ARCHETYPE_INTERNAL_REF](https://discourse.openehr.org/t/occurrences-in-archetype-internal-ref/15913)
> Following Koray's finding of this problem, I have created the issue [http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/233](http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/233)
This problem is about handling occurrences on 'use_nodes' i.e. ARCHETYPE_INTERNAL_REF instances; see for example the use_node lines in the Apgar archetype -...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [159] Corrections to ADL and its sub-grammars - mainly cleanup of exprssions, better commenting,](https://discourse.openehr.org/t/ref-impl-eiffel-159-corrections-to-adl-and-its-sub-grammars-mainly-cleanup-of-exprssions-better-commenting/15912)
> Revision: 159
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Mutable/Immutable experiment.](https://discourse.openehr.org/t/mutable-immutable-experiment/15915)
> Hi\!
Attached you will find a zip with code for two simplified java
packages \(example\.immutable \+ example\) containing mutable and
immutable versions of some example objects\. Please read the comments
in the java\-files for more details\.
The intention of this experiment is to test and discuss some possible
solutions for a future version of the java\-ref\-impl\. The approach is
based om discussions between me, Mikael and Mattias but possible
implementation errors are probably my fault...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [updated versions of archetype specs](https://discourse.openehr.org/t/updated-versions-of-archetype-specs/14615)
> Dear all,
the ADL, ADL2, AOM and oAP specifications have all been updated with most, but not quite all changes on the todo list - many resulting from feedback on this list. You can find them in the usual place (the 1.0.1 branch - [http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.html](http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.html)).
Change log:
Major upgrade to ADL and oAP documents, including:
- split grammar...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Lists of dates, times etc in ADL](https://discourse.openehr.org/t/lists-of-dates-times-etc-in-adl/14614)
> Dear all,
the current ADL and AOM specifications do not include lists as a way to constrain dates, times, date/times or durations, although the ADL document implies that it is included without showing any examples. To my knowledge, this has never been required, and it does not seem terribly useful. It would not be that hard to add - it would require small changes to the ADL spec, the AOM spec, the parser grammars, and additions to the test archetypes....but I am inclined simply to correct...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Open Journals ( last time, really )](https://discourse.openehr.org/t/open-journals-last-time-really/14608)
> I wonder if the avaible technology says it is time to shift the paradigm and to post articles to wikis FOR PEER REVIEW... FWIW: Quasi-tangentially, I just saw a PR on the theme that OpenClinica is launching a wiki at [http://www.openclinica.org/dokuwiki/](http://www.openclinica.org/dokuwiki/)
Thanks for everyone's patience on this thread.
Ed
OJS is for example used by the open-access electronic Journal of Health Informatics (eJHI, [http://www.ejhi.net](http://www.ejhi.net/)) with...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Open Journals](https://discourse.openehr.org/t/open-journals/14613)
> FWIW: We just had a very similar thread over at the Ontolog Forum re: the state of paper journal | info dissemination mindset. I haven't used it but I saw: Open Journal Systems (OJS) is a journal management and publishing system that has been developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research. [http://pkp.sfu.ca/?q=ojs](http://pkp.sfu.ca/?q=ojs) in case open publishing is a real need.
Ed Dodds
Also discussion...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [aus health it](https://discourse.openehr.org/t/aus-health-it/14607)
> Does anyone want to respond to this?
http://aushealthit.blogspot.com/2007/01/archetypically-stupid.html
David More seems to be going on a bit of a crusade at the moment,
firing shots at all current work in Australian e\-health \(NEHTA etc\)\.
Some of it is deserved no doubt, but I think he is a bit confused
about exactly what the archetype approach is about\.
Andrew
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[177] added support for assumedValue in CCodePhrase](https://discourse.openehr.org/t/177-added-support-for-assumedvalue-in-ccodephrase/12244)
> Revision: 177
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[176] added support for assumedValue in CCodePhrase](https://discourse.openehr.org/t/176-added-support-for-assumedvalue-in-ccodephrase/12243)
> Revision: 176
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[175] updated constructors to allow defaultValue and assumedValue](https://discourse.openehr.org/t/175-updated-constructors-to-allow-defaultvalue-and-assumedvalue/12241)
> Revision: 175
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[174] updated CDomainType to add assumedValue](https://discourse.openehr.org/t/174-updated-cdomaintype-to-add-assumedvalue/12240)
> Revision: 174
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[173] minor code change](https://discourse.openehr.org/t/173-minor-code-change/12239)
> Revision: 173
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[172] added overwritting occurrences for ArchetypeInternalRef](https://discourse.openehr.org/t/172-added-overwritting-occurrences-for-archetypeinternalref/12238)
> Revision: 172
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[171] updated openehr-dao dependencies](https://discourse.openehr.org/t/171-updated-openehr-dao-dependencies/12237)
> Revision: 171
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[170] updated dependencies of xml-serializer](https://discourse.openehr.org/t/170-updated-dependencies-of-xml-serializer/12234)
> Revision: 170
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[169] bug fix in adl-serializer related to null includes or excludes in printArchetypeSlot](https://discourse.openehr.org/t/169-bug-fix-in-adl-serializer-related-to-null-includes-or-excludes-in-printarchetypeslot/12233)
> Revision: 169
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[178] minor code change](https://discourse.openehr.org/t/178-minor-code-change/15910)
> Revision: 178
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [update on RC2](https://discourse.openehr.org/t/update-on-rc2/15908)
> Hi All,
Some summary on the latest changes (last 48 hr) on the trunk.
1. Updated c_domain_type and its subclasses to add default value and assumed value; assumed value works for CCodePhrase in the parser and adl-serializer
2. Added support for overwritting occurrences of ArchetypeInternalRef in the parser
3. Bug fix of printArchetypeSlot, submitted by Mattias
Branch Release-1.0.1-RC2 will be created from the TRUNK within several days.
Regards,
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new ADL workbench release - repository merging and inheritance visualisation](https://discourse.openehr.org/t/new-adl-workbench-release-repository-merging-and-inheritance-visualisation/15909)
> There is a new ADL workbench available\. See
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
The new features are described here:
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help_whats_new_20070110.htm
\- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [LOCATABLE.item_at_path](https://discourse.openehr.org/t/locatable-item-at-path/14612)
> in class LOCATABLE there is the following function:
item_at_path (a_path: String): Any
require
path /=Void and then valid_path(a_path)
ensure
Result /= Void
There has been a request to add a function:
items_at_path (a_path: String): List
require
path /=Void and then valid_path(a_path)
ensure
Result /= Void
And to make the semantics as follows:
- item_at_path returns only one item; if the path target is a container, it returns the first item
- items_at_path - return the whole...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Bug in RM builder? (getParent) + Incomplete Common IM spec?](https://discourse.openehr.org/t/bug-in-rm-builder-getparent-incomplete-common-im-spec/14618)
> Hi Rong\! \(\+Tom\)
Mattias mentioned that the two of you \(MF\+RC\) had chatted about the
issue that the parent is set null instead of the real parent in the
AOM by the parser\. I now had a look at the RMObjectBuilder and found a
similar issue\. Is it not so that RM objects that inherit from
Locatable should know \(have a reference to or be able to look up\)
their parent if they have one \(i\.e all non root objects\)?
A question to Tom:
Why is parent optional \(0\.\.1\) in the spec, is it...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Revisiting RESOURCE_DESCRIPTION.details: Hash or List question](https://discourse.openehr.org/t/revisiting-resource-description-details-hash-or-list-question/14609)
> All,
I can't seem to find the original posts on this subject, but in any case, am processing it now. I have written a CR ([http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/231](http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/231)). I am in favour of changing the type of RESOURCE_DESCRIPTION.details from a List<> to a Hash<>. I seem also to remember that there were complaints about the language attribute in the class...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [158]](https://discourse.openehr.org/t/ref-impl-eiffel-158/12232)
> Revision: 158
Author:
Date:
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Discussion](https://discourse.openehr.org/t/discussion/15906)
> I am many time surprised by code\-changes\.
What can i do to avoid this
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel ACE-files](https://discourse.openehr.org/t/ref-impl-eiffel-ace-files/14611)
> Hi Thomas,
after some time, I thought it would be good to find an easy way to click
through the Eiffel files, but then I forgot how hard it was without any
ACE or projectfiles\.
Or isn't it?
Can you please give some hints how to do this easy
Thanks
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[168]](https://discourse.openehr.org/t/topic/12231)
> Revision: 168
Author:
Date:
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [java implementation part 3](https://discourse.openehr.org/t/java-implementation-part-3/12230)
> It is very good that we are changing plans\. There is one disadvantage\.
It messes up the SVN\-trees\. You can't tell which Java files are new, and
which are the same, because in SVN they are all new, because the tree
has got another name
For me this is very inconvenient, because, at this moment I cannot copy
the Java\-sources to my own work, because I am doing things
different\.than is done in the reference tree\.\\
So I have to open and compare them manually, and see if there are...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [java-implementation part2](https://discourse.openehr.org/t/java-implementation-part2/12229)
> Erik said that a POJO\-style base for Java\-reference\-implementation is a
good idea\.
Is anyone supporting this, are there any plans?
thanks for explanation
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [different java-implementations](https://discourse.openehr.org/t/different-java-implementations/15907)
> I see that there are different Java\-implementations, non\-splitted and
splitted\.
Will the non\-splitted be kept up to date, or do we have to focus on the
splitted implementation?
Thanks for explanation
Bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[167]](https://discourse.openehr.org/t/topic/12228)
> Revision: 167
Author:
Date:
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[166]](https://discourse.openehr.org/t/topic/12227)
> Revision: 166
Author:
Date:
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[165]](https://discourse.openehr.org/t/topic/12226)
> Revision: 165
Author:
Date:
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openehr website broken?](https://discourse.openehr.org/t/openehr-website-broken/14610)
> I hardly dare to say, because of false alarms in the past, but I cannot
download one document of the specification project
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/sm/ehr_sm.pdf
By the way, in which document is security described?
thanks
bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [157]](https://discourse.openehr.org/t/ref-impl-eiffel-157/12225)
> Revision: 157
Author:
Date:
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [156]](https://discourse.openehr.org/t/ref-impl-eiffel-156/12224)
> Revision: 156
Author:
Date:
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [proposed change to ADL 1.4 to handle langauges & translations better](https://discourse.openehr.org/t/proposed-change-to-adl-1-4-to-handle-langauges-translations-better/14576)
> Dear all,
I would like to propose to make a small change in the archetype structure of ADL 1.4. See the published structure below:
******* current published ADL 1.4 archetype structure *****
archetype
archetype_id
[specialize
parent_archetype_id]
concept
coded_concept_name
language
dADL language description section
description
dADL meta-data section
definition
cADL structural section
invariant
assertions
ontology
dADL definitions section
[revision_history
dADL section]
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[164]](https://discourse.openehr.org/t/topic/12223)
> Revision: 164
Author:
Date:
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Subversion 1.4 upgrade](https://discourse.openehr.org/t/subversion-1-4-upgrade/14599)
> Dear all,
we have just upgraded Subversion on the openEHR server to 1.4 from 1.2.1, a version that caused occasional repository corruption in the past. One small glitch occurred that lasted about 1 hour, but after that I believe you should not see anything different. If anyone experiences any problems, make a short post to this list, and we will address it as quickly as possible.
thanks,
- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Java v.s. Eiffel + What should the setters do as mandatory checks...](https://discourse.openehr.org/t/java-v-s-eiffel-what-should-the-setters-do-as-mandatory-checks/14604)
> Hi\!
> well whatever you do, don't try it \[Eiffel\] now, otherwise you will go mad when you go
> back to do something in Java ;\-\)
I agree that Java as in \_the Java language\_ is not always ideal and
not the most productive environment\. I'm not a seasoned expert but
some experience with e\.g\. Smalltalk and Python has shown interesting
features \(closures, mixins etc\.\) that Java does not have \(yet\) but
that are available in e\.g\. Ruby, Groovy etc\. I still think having...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [155] Corrections to ADL Workbench help](https://discourse.openehr.org/t/ref-impl-eiffel-155-corrections-to-adl-workbench-help/12221)
> Revision: 155
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [154] Slight adjustments to ADL workbench what's new presentation.](https://discourse.openehr.org/t/ref-impl-eiffel-154-slight-adjustments-to-adl-workbench-whats-new-presentation/12220)
> Revision: 154
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [153] Add ADL workbench help for merged repositories and inheritance view.](https://discourse.openehr.org/t/ref-impl-eiffel-153-add-adl-workbench-help-for-merged-repositories-and-inheritance-view/12219)
> Revision: 153
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [152] Update version; update ADL workbench .msi project](https://discourse.openehr.org/t/ref-impl-eiffel-152-update-version-update-adl-workbench-msi-project/12218)
> Revision: 152
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [151] Rename C_QUANTITY to C_DV_QUANTITY, C_ORDINAL to C_DV_ORDINAL.](https://discourse.openehr.org/t/ref-impl-eiffel-151-rename-c-quantity-to-c-dv-quantity-c-ordinal-to-c-dv-ordinal/15905)
> Revision: 151
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem in History.setEvents(...)](https://discourse.openehr.org/t/problem-in-history-setevents/12211)
> This is similar with previous mail, if you look at the code, you
recognize the problem immediately, the solution is five minutes away
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [150] Working version of inheritance view of node display with automated roll-up of inherited sub-trees.](https://discourse.openehr.org/t/ref-impl-eiffel-150-working-version-of-inheritance-view-of-node-display-with-automated-roll-up-of-inherited-sub-trees/15904)
> Revision: 150
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [149] Added new ADL workbench icon variants for redefined nodes](https://discourse.openehr.org/t/ref-impl-eiffel-149-added-new-adl-workbench-icon-variants-for-redefined-nodes/12214)
> Revision: 149
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [148] Re-organise ADL workbench icons](https://discourse.openehr.org/t/ref-impl-eiffel-148-re-organise-adl-workbench-icons/12213)
> Revision: 148
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [trunkCounter in VersionedObject.java](https://discourse.openehr.org/t/trunkcounter-in-versionedobject-java/16642)
> openehr\-rm/src/main/java/org/openehr/rm/common/changecontrol/VersionedObject\.java
As far as I understand, it is only used once, in comparison in
addVersion, also I found it is never initialised\.
This looks to me like a bug\.
Rong or someone else, can you please comment on this
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [147] Improved visualisation of archetype slots in ADL node map.](https://discourse.openehr.org/t/ref-impl-eiffel-147-improved-visualisation-of-archetype-slots-in-adl-node-map/12212)
> Revision: 147
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [User input validation](https://discourse.openehr.org/t/user-input-validation/12215)
> Hi!
This posting is spawned from from thread "Hibernate and RM". It deviates from that thread in the sense that it does not directly concern the DbC discussion there.
Domain models like the openEHR-RM often throw errors/exceptions (from custom written error checking code or from DbC frameworks) if treated in bad ways (being called with nulls, bad values/formats etc). These errors/exceptions are usually aimed at other developers and this is OK since it is probably developers (not the end...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [splitting the openehr-rm component to several smaller components](https://discourse.openehr.org/t/splitting-the-openehr-rm-component-to-several-smaller-components/12210)
> Dear all,
Through the recent discussions on the Java list and local prototyping work in Sweden, the need to split the openehr-rm component into several even smaller components has been recognized. Currently the openehr-rm consists of the Java implementation of all openEHR Information Models, namely Common, Support, Data Types, Data Structures, EHR, Demographics. The idea is to divide all-in-one RM component into several smaller components that are either mapped exactly to the sub Information...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [145] Adjust semantics of setting pattern or string constraints in C_STRING](https://discourse.openehr.org/t/ref-impl-eiffel-145-adjust-semantics-of-setting-pattern-or-string-constraints-in-c-string/12208)
> Revision: 145
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [144] Changed comments](https://discourse.openehr.org/t/ref-impl-eiffel-144-changed-comments/12207)
> Revision: 144
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [143] Missed class in DV_PROPORTION change](https://discourse.openehr.org/t/ref-impl-eiffel-143-missed-class-in-dv-proportion-change/12206)
> Revision: 143
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [142] Initial version of new Extract classes](https://discourse.openehr.org/t/ref-impl-eiffel-142-initial-version-of-new-extract-classes/12205)
> Revision: 142
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [141] Delete old EHR_EXTRACT classes](https://discourse.openehr.org/t/ref-impl-eiffel-141-delete-old-ehr-extract-classes/12204)
> Revision: 141
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [140] Missed class for DV_PROPORTION (was DV_RATIO)](https://discourse.openehr.org/t/ref-impl-eiffel-140-missed-class-for-dv-proportion-was-dv-ratio/12203)
> Revision: 140
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [139] Correct ARCHETYPE_ID for archetype directory merge changes](https://discourse.openehr.org/t/ref-impl-eiffel-139-correct-archetype-id-for-archetype-directory-merge-changes/12202)
> Revision: 139
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [138] Add DV_RATIO](https://discourse.openehr.org/t/ref-impl-eiffel-138-add-dv-ratio/12201)
> Revision: 138
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [136] Add precision to C_QUANTITY](https://discourse.openehr.org/t/ref-impl-eiffel-136-add-precision-to-c-quantity/12196)
> Revision: 136
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [135] Further pathing modifications](https://discourse.openehr.org/t/ref-impl-eiffel-135-further-pathing-modifications/12195)
> Revision: 135
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [134] Initial working version of merged archetype directory tree; handles reference and work repository.](https://discourse.openehr.org/t/ref-impl-eiffel-134-initial-working-version-of-merged-archetype-directory-tree-handles-reference-and-work-repository/12572)
> Revision: 134
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Smal detail in DV_DATE_TIME](https://discourse.openehr.org/t/smal-detail-in-dv-date-time/16707)
> Rong and others,
Chunlan at the Ocean development group just noticed that
DV\_DATE\_TIME\.magnitude returns number of seconds, but to\_quantity
returns a number of days; what has been implemented by others? The
suggestion is to make them both the same, either days or seconds \(both
make sense in different ways\)\.
\- t
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [proposed small change to C_QUANTITY](https://discourse.openehr.org/t/proposed-small-change-to-c-quantity/16643)
> As part of the finalisation of fixes to the Archetype Editor, ADL and
ADL parsers, Sam has proposed to add a precision attribute to
C\_QUANTITY\. This would be of type Interval<Integer>, although in the
archetypes he is currently doing, only a single value is needed\. The
typical example is to allow/disallow decimals, such as for blood
pressure values \(where they are never used\), so the precision would be 0\.
I will add this to the Eiffel parser so that he can put it in the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [DbCProxy](https://discourse.openehr.org/t/dbcproxy/12194)
> Is a tool for DbC during test and development phase\.
It is not recommended to use during production
Are there any thoughts about this?
Regards
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Suggestions re Term binding in Archetype Editor](https://discourse.openehr.org/t/suggestions-re-term-binding-in-archetype-editor/14597)
> Hi,
I am currently working my way slowly through the Scottish Cardiac dataset,
converting it to archetypes as proof\-of\-concept, using the OE editor\.
Term binding \(to SNOMED\) will be a crucial aspect from our perspective,
especially binding local \(interface\) terms to SNOMED concepts\.
This would be much easier within the editor if the Term bindings screen
displayed the node name as well as the Node ID, as it is easy to forget
which local term you are trying to bind by the time you...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Possible change request for Ocean Archetype Editor](https://discourse.openehr.org/t/possible-change-request-for-ocean-archetype-editor/14603)
> Dear Sam,
I personally feel that the publication status is not obvious enough to be well-used, and would suggest that this goes onto the front screen.
I have a less strong view about the other descriptive information being moved, since the tab for it is clearly visible at all times, but the feedback I have had recently suggests that a clear description of the purpose/use is a headline item that might also be nice on the first screen. However, I could understand if you would not wish to...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [applications built on top of the openEHR Java kernel](https://discourse.openehr.org/t/applications-built-on-top-of-the-openehr-java-kernel/12193)
> Hi All,
I am preparing a submission to Medinfo 2007 regarding the openEHR Java
Reference Implementation\. Within the paper I will include a list of
applications that are built on top of the Java kernel\. If it's the case
with your application/project, I would very much appreciate that you
could contact me and give a short description about your applications\.
Since the deadline is next Monday, so a quick response will be most
appreciated\.
You could either reply on the list or send a...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Multiple terminologies](https://discourse.openehr.org/t/multiple-terminologies/14602)
> Dear all,
I need some help/explanation/advice on how to attach multiple
terminologies to the same entry\. If I understand the concept
correctly it seems that there are two manners to do so\. Let me
explain first what I would like to do:
In the Dutch archetype for 'medication' I'm trying to make, I would
like to attach several terminologies to the same medicine\. In the
Netherlands we use the G\-standard which comprises of many sub
terminologies\. For instance there is a...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Hibernate and RM](https://discourse.openehr.org/t/hibernate-and-rm/16644)
> Maybe it is an idea to wrap the classes in interfaces, and leave the
hibernate\-supporting methids and getters outside the interface, and tell
people to only use the interfaces\.
Bert
Bert Verhees schreef:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_QUANTITY_RATIO - remove from specification](https://discourse.openehr.org/t/dv-quantity-ratio-remove-from-specification/14593)
> Dear All
We have been working on the data types as we have known that there is a need to deal with fractions, ratios and percentages when the idea is of proportion - ie there is no units. Since the DV_QUANTITY_RATIO points to anything Quantified (ie count, date_time, duration) there are many non-sensible possibilities and although it has been around since the GEHR days, we have not used it for anything other than the idea of the new DV_PROPORTION type (which will be available in 1.0.1).
I...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [HierachicalID](https://discourse.openehr.org/t/hierachicalid/12192)
> This is really a tricky one
reflection optimizer disabled for:
org\.openehr\.rm\.support\.identification\.HierarchicalObjectID,
BulkBeanException: null \(property setValue\)
It means, that Hibernate tries to set null in value, and if it succeeds,
it puts un the optimizer\.
In case of HierarchicalID this fails, gives an exception, bwecause of
the calleds method loadValue wihch is called from within setValue
Bert
You find a discussion about...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [private and protected setters, or missing contructors, etc.](https://discourse.openehr.org/t/private-and-protected-setters-or-missing-contructors-etc/12191)
> These give a non fatal BulkBeanException, which means that
reflection\-optimizer will be disabled\.
There are a lot of them, below, this list can be nearly complete
regards
bert
\-\-> \- reflection optimizer disabled for:
org\.openehr\.rm\.datatypes\.quantity\.DvInterval, BulkBeanException:
Property is private \(property setInterval\)
\-\-> \- reflection optimizer disabled for:
org\.openehr\.rm\.composition\.content\.entry\.AdminEntry, BulkBeanException:
tried to access...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [EhrExtract](https://discourse.openehr.org/t/ehrextract/15899)
> setters for the whole bunch,
but as I come to think of it now, there may be no need to store
Ehr\-extract\-classes, sometimes I am to much fixed on techniques that I
forget, the meaning\.
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Regular expressions?](https://discourse.openehr.org/t/regular-expressions/16638)
> Hi,
I have noticed that instruction archetypes have different ways of adding constraints on archetype IDs and domain concepts. Here's an example:
INSTRUCTION[at0000] matches { -- Imaging request
activities cardinality matches {0..*; unordered} matches {
ACTIVITY[at0001] occurrences matches {1..*} matches { -- Imaging activity
action_archetype_id matches {"/imaging\.v1/"}
description matches {
allow_archetype ITEM_TREE occurrences matches {0..1} matches {
include
domain_concept matches...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Could not find a setter for property normalRange in class org.openehr.rm.datatypes.quantity.DvOrdinal](https://discourse.openehr.org/t/could-not-find-a-setter-for-property-normalrange-in-class-org-openehr-rm-datatypes-quantity-dvordinal/12189)
> Hibernate complains in derived classes because there are no setters for
normalRange and referenceRanges in class DvOrdered\.
What shall I do about this, is this going to change or do I
misunderstand something?
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Constraint references](https://discourse.openehr.org/t/constraint-references/12199)
> Hi all,
I'm wondering what the difference is between a CONSTRAINT_REF and a C_DV_CODED_TEXT that has the query attribute set? The descriptions of the two are the following:
CONSTRAINT_REF class description:
Reference to a constraint described in the same archetype, but outside the main constraint structure. This is used to refer to constraints expressed in terms of external resources, such as constraints on terminology value sets.
Description of query attribute of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [List of errors in XML schema spec of AOM](https://discourse.openehr.org/t/list-of-errors-in-xml-schema-spec-of-aom/14596)
> Hi again,
As promised, I will provide a list of errors in the XML schema specification of the AOM.
1. Element name 'rm_type_name' should be renamed to 'rm_attribute_name' for the C_ATTRIBUTE entity so that the naming follows the AOM specification.
2. The C_ATTRIBUTE has an attribute called 'unbounded' which follows the AOM specification the existence attribute which is an Interval, but is it really needed in the XML spec, i.e. will there ever be a case where the existence is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EHR specification](https://discourse.openehr.org/t/ehr-specification/14595)
> Hi all,
I found there is an error at page 42 in the class description of CONTENT_ITEM in the EHR specification. As you can see in the inherit field, the class inherits itself, but it should inherit the class LOCATABLE from the common package instead.
Another thing I would like to be clarified is that the archetype_details field of LOCATABLE is mandatory for all archetype root points. The COMPOSITION and ENTRY classes have the following invariants respectively:
Is_archetype_root:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EPD Problems at Kaiser Permanente](https://discourse.openehr.org/t/epd-problems-at-kaiser-permanente/15894)
> Information about the failing of a world famous 4 billion costing EHR
I found these links on a closed \(payed dutch\) mailing list\. Maybe
someone finds this...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [[[os-wg] Open source license for the Foundational Model of Anatomy (FMA) ontology]](https://discourse.openehr.org/t/os-wg-open-source-license-for-the-foundational-model-of-anatomy-fma-ontology/12188)
> FYI
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [feederAudit in Locatable](https://discourse.openehr.org/t/feederaudit-in-locatable/12184)
> Please, I like to inform that there is an inconsistency in the UML
http://www.openehr.org/uml/release-1.0.1/Browsable/indexLeft.html and
the documentation and Java\-source
feederAudit is in a SET in the UML, while it is a single property in the
doc and Java\-sources, I assume there is an error in the UML\.
Just wanted to say that
Thanks\.
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML serializer (retry due to too large message)](https://discourse.openehr.org/t/xml-serializer-retry-due-to-too-large-message/14601)
> Hi all,
I've just finished implementing an XML serializer. I have followed the XML schema specifications carefully, but I've deviated from some parts, particularly the ontology section. In the terms element (defined as [ARCHETYPE_TERM](http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/its/XML-schema/documentation/Archetype.xsd.html_h-47810521.html) [1..*]) found in language_set of term_definitions and constraint_definitions I found the definition...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Interesting Article in "Government Health IT" about semantic interoperability](https://discourse.openehr.org/t/interesting-article-in-government-health-it-about-semantic-interoperability/12187)
> A new scheme for data sharing
Semantic interoperability aims to ease data sharing among disparate
health systems
BY John Moore
Published on Nov\. 13, 2006
can be accessed via:
http://www.govhealthit.com/article96736-11-13-06-Print
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updated Architecture overview](https://discourse.openehr.org/t/updated-architecture-overview/12198)
> Some small but possibly important updates to the Overview are now
available; See the hotlinks on the home page\. The additions concern
identification of EHRs and parts of EHRs\. In the HTML version, the
changes are visible in the following...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Proposal for setting uid in top-level openEHR objects](https://discourse.openehr.org/t/proposal-for-setting-uid-in-top-level-openehr-objects/15896)
> Dear all,
during a recent Ocean design meeting in Adelaide, it became clear that it would be useful if all "top-level" objects in openEHR (defined as per this page: [http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/html/architecture/overview/Output/design_of_ehr.html#1154670](http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/html/architecture/overview/Output/design_of_ehr.html#1154670)) had their uid attribute set to the value of the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML archetypes](https://discourse.openehr.org/t/xml-archetypes/14594)
> Hi,
I am doing some experiments on a XML serializer for the Java archetype editor. I wonder if there are any example XML archetypes that I can look at to verify that I follow the XML-schema documentation correctly?
Regards,
Mattias
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ISO TIME DATE classes](https://discourse.openehr.org/t/iso-time-date-classes/15893)
> Hi,
The ISO8601 classes are not yet implemented in the Java\-kernel\.
Is there a reason for it, or is there a plan to for doing so in the future?
Thanks
Bert
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Java RC 1.01](https://discourse.openehr.org/t/java-rc-1-01/15895)
> Please allow me a question\.
There is a Message\-class
and in that class is a list of MessageContent
In the Java\-source, MessageContent is abstract, and I did not find any
descendants\. So they cannot be instantiated
Am I right or did I overlook something?
Thanks
Bert Verhees
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Change of my e-mail address](https://discourse.openehr.org/t/change-of-my-e-mail-address/12181)
> Was previously <francois\.mennerat@wanadoo\.fr>, now preferrably <francois@mennerat\.eu>
Many thanks
François Mennerat
Dr\. François MENNERAT, MD, PhD
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
Adresse préférée \- Favourite address : <francois\(at\)mennerat\.eu>
Le courrier électronique reste un mode de communication asynchrone et n'est pas sûr\. L'éviter pour tous sujets urgents ou sensibles\.
Electronic mail remains an...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype questions](https://discourse.openehr.org/t/archetype-questions/14600)
> Hi,
I'm currently working in a group that has been evaluating archetypes and they found out that there in archetypes may be needed to add external nodes from other archetypes instead of only adding complete archetypes as slots. Does the current ADL specification allow that external parts from other archetypes can be included? I think the openEHR templates allow to cut off parts in a slot, but I'm not sure if they can exclude everything except a single item.
The group also found out that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CEN 13606](https://discourse.openehr.org/t/cen-13606/14598)
> Apologies that this is perhaps not the right forum, but
I sense there is a fair crossover between the CEN and
openehr communities so I thought this might reach
the right ears\.\.
I have been perusing the draft cen 13606\-1 specification
in my exploration of all things openehr related \(given the
large overlap in ideas\.\. two level modelling etc\)\. I was
wondering if anyone had any ADL archetypes based on
the 13606\-1 reference model? I am going to hand craft
some as an experiment but would...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Typo in Entry.java](https://discourse.openehr.org/t/typo-in-entry-java/12179)
> It says workflwoID instead of WorklowID, I repaired it in my code, but
please repair it also on the SVN code\-tree
thanks
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ISM_TRANSITION](https://discourse.openehr.org/t/ism-transition/12177)
> Hi,
I started wondering about different representations of ISM_TRANSITIONs of the ism_transition attribute in the ACTION archetypes. I found that the below example:
ISM_TRANSITION matches {
current_state matches {
CODED_TEXT matches {
code matches {[openehr::524]}
}
}
careflow_step matches {
CODED_TEXT matches {
code matches {[local::at0001]} -- Planned
}
}
}
ISM_TRANSITION matches {
current_state matches {
CODED_TEXT matches {
code matches {[openehr::524]}
}
}
careflow_step matches...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [133] Add missed classes for C_DURATION changes](https://discourse.openehr.org/t/ref-impl-eiffel-133-add-missed-classes-for-c-duration-changes/12180)
> Revision: 133
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Uncaught bounce notification](https://discourse.openehr.org/t/uncaught-bounce-notification/16687)
> The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it\. This mailing list has been configured to send all
unrecognized bounce messages to the list administrator\(s\)\.
For more information see:
http://www.chime.ucl.ac.uk/mailman/admin/openehr-implementers/bounce
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [security information model](https://discourse.openehr.org/t/security-information-model/12183)
> hello,
I'm reading through the specification of the reference model, in the
architecture overview is written that every package of the RM
overview \(figure 10\) has its own document\. but I can't find the
specification for the security information model, or is it just
chapter 7 of the architecture overview?
I hope someone can give me a hint\.
thanks in advance
markus
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [132] Added C_DURATION test case;](https://discourse.openehr.org/t/ref-impl-eiffel-132-added-c-duration-test-case/12178)
> Revision: 132
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [131] Delete ADL cmd line app](https://discourse.openehr.org/t/ref-impl-eiffel-131-delete-adl-cmd-line-app/15892)
> Revision: 131
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [130] Delete ADL cmd line app](https://discourse.openehr.org/t/ref-impl-eiffel-130-delete-adl-cmd-line-app/12525)
> Revision: 130
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New version of ADL workbench](https://discourse.openehr.org/t/new-version-of-adl-workbench/16639)
> The new version includes the following changes, mainly to do with path
extraction and viewing\. Generic types are now supported in ADL archetypes\.
Version 129
Further corrections to paths:
ensure '/' path generated correctly in OG\_ITEM;
include "unknown" node\_ids in paths where required to differentiate
between unnamed siblings
make tooltips responsive to Basic/Technical button\.
Version 128
Rename C\_CODED\_TERM to C\_CODE\_PHRASE & update installer VS project;
Fix...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Release-1.0.1 Release Candidate](https://discourse.openehr.org/t/release-1-0-1-release-candidate/14605)
> Dear all,
I am glad to announce that the update of the Java reference implementation according to the latest specifications has finally completed!
All updated Java components are moved from the sandbox branch to the trunk for further development and copied to the branch Release-1.0.1-RC (Release Candidate).
Thanks everyone that are involved in the process for the hard work, particularly Yin Su from UCL who has done substantial work on the update of the reference model implementation. Both...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [webpages](https://discourse.openehr.org/t/webpages/16641)
> The webpages for the java\-ref\-implementation don't look wel on my
computer, while the rest of the internet seems ok
bert
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Question about action archetypes](https://discourse.openehr.org/t/question-about-action-archetypes/15891)
> Hello,
I have a question about some properties of the ISM\_TRANSITION entity
in the action archetypes\. I noticed that the current\_state attribute
can have several codes to choose from, i\.e\. alternative states for the
'Initial' and 'Active' states\. The 'Initial' can have an alternative
state 'Active' and the 'Active' state can have an alternative state
'Initial'\. Now in the archetypes created by the Ocean editor, the only
way to separate...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [129] Further corrections to paths:](https://discourse.openehr.org/t/ref-impl-eiffel-129-further-corrections-to-paths/15889)
> Revision: 129
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [blood film observation archetype](https://discourse.openehr.org/t/blood-film-observation-archetype/14590)
> We've been running throuh the "normal" and possible ranges of values for
lab tests and found that the archetype I mention in the subject does not
state but a "bigger than 0" restriction for Haemoglobin, RCC, etc\.
I decided to take a look because ranges provided to me indicated
diferent "possible" ranges for male and female patients and was
wondering how would archetypes model this issue\.
This is a very similar question to another one I did some time...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [128] Rename C_CODED_TERM to C_CODE_PHRASE & update installer VS project;](https://discourse.openehr.org/t/ref-impl-eiffel-128-rename-c-coded-term-to-c-code-phrase-update-installer-vs-project/15888)
> Revision: 128
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Error in C_DV_CODED_TEXT](https://discourse.openehr.org/t/error-in-c-dv-coded-text/15890)
> Dear all,
I was staring at the ADL and openEHR archetype profile and realised there is an error in class naming. C_DV_CODED_TEXT should be named C_CODE_PHRASE. I think Mattias may have already pointed out something like this, but it took me until only a week ago to realise the error. It has occurred because we put custom syntax into ADL before defining any C_XXX types. But as you cna see if you review any of the archetypes, where the custom syntax occurs e.g. from...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [127] Add generic types to ADL;](https://discourse.openehr.org/t/ref-impl-eiffel-127-add-generic-types-to-adl/15887)
> Revision: 127
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR-implementers post from hyslop@aus.xerox.com requires approval](https://discourse.openehr.org/t/openehr-implementers-post-from-hyslop-aus-xerox-com-requires-approval/12176)
> As list administrator, your authorization is requested for the
following mailing list posting:
List: openEHR\-implementers@openehr\.org
Reason: Post by non\-member to a members\-only list
At your convenience, visit:
http://www.chime.ucl.ac.uk/mailman/admindb/openehr-implementers
to approve or deny the request\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Propoer use of lists](https://discourse.openehr.org/t/propoer-use-of-lists/12182)
> Dear all,
just a small request from our sysadmin:
please be careful when hitting reply\-all \- in particular, do not cc: to
addresses containing "\-bounces" \- these are used by the Mailman list
manager to detect faulty email addresses\.
thanks,
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR and Prodigy DSS](https://discourse.openehr.org/t/openehr-and-prodigy-dss/14591)
> Hi,
I noticed with interest that one of the older Service Model documents \(2003\)
mentions an interface between the Prodigy DSS and the OpenEHR architecture\.
The section was blank\.
Is there any other pertinent information as I am about to start an MSc
dissertation looking at exactly this piece of work?
Dr Ian McNicoll
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Java Parser Trunk/Sandbox](https://discourse.openehr.org/t/java-parser-trunk-sandbox/12185)
> Hi Rong,
We would like to use the Java-Parser to parse all archetypes and extract the required information for the Archetype Finder.
The only problem is that we need to get started with it now.
Would you agree that using the current TRUNK-version now (and just ignore those archetypes that are not parsable) and upgrading this to the new Sandbox-components once a new version of the parser is available would be the best way to go?
Kind regards
Sebastian
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updated Architectural overview](https://discourse.openehr.org/t/updated-architectural-overview/14589)
> The Architectural Overview document has been updated to include a better
explanation of how archetypes and templates work\. See the home page
hotlinks section\. The HTML view of the updated chapter is here \-
http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/html/architecture/overview/Output/archetyping.html#1135484
As usual, all comments and feedback are welcome\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [HL7 templates/archetypes](https://discourse.openehr.org/t/hl7-templates-archetypes/14585)
> Hi,
I'm writing my diploma thesis at the Vienna Medical University and I have a question concerning the HL7 templates/archetypes. I'm aware that this sites are related to the openEHR but maybe somebody can answer the following question:
Which model (RIM, R-MIM, ...) and which formalism (ADL, OCL, OWL, ...) should be used for the description and creation of the entry-level templates?
Thanks for a brief answer!
Best regards
Dana Prochazkova
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Versioned Object](https://discourse.openehr.org/t/versioned-object/14588)
> Hi,
I am at this moment busy on VersionedObject and studying the differences
between this and its predecessor VersionRepository\.
Some changes I think I understand by looking at the history in SVN of
this file and the Eiffel equivalent\.
But two things I don't understand\.
What happened to the function firstVersion?
Is there no need to find the firstVersion or is there another way to
find it\.
Also wondered about what happend to the method "commit", it also
dispapeared\. Is...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [DV_STATE](https://discourse.openehr.org/t/dv-state/12512)
> Hi,
I'm wondering where the DV\_STATE is used in archetypes? I have only
seen the ISM\_TRANSISTION state in the ACTION archetypes, but that is
probably something else\. I noticed there is a class C\_DV\_STATE in the
archetype profile that constrains allowed values of the attribute
'value' of the DV\_STATE, but I don't know what syntax a parser need to
find in order to create an instance of a C\_DV\_STATE\.
If the ISM\_TRANSITION is only supposed to correspond to an instance...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [126] Add functions to properly check for paths to objects and attribute separetely;](https://discourse.openehr.org/t/ref-impl-eiffel-126-add-functions-to-properly-check-for-paths-to-objects-and-attribute-separetely/12511)
> Revision: 126
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [125] Correct C_QUANTITY to allow no constraints beyond just the type itself.](https://discourse.openehr.org/t/ref-impl-eiffel-125-correct-c-quantity-to-allow-no-constraints-beyond-just-the-type-itself/12175)
> Revision: 125
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ResourceDescriptionItem](https://discourse.openehr.org/t/resourcedescriptionitem/14587)
> Hi, please allow me a small question\.
If you rather see me ask this kind of implementation\-specific questions
to the list, I can do that, but for now, I ask you personally
I noticed something strange\. Maybe I am wrong, so please explain to me\.
I was looking at the code in the sandbox\-branch of the
Java\-implementation, and I discovered that the class
ResourceDescriptionItem has TerminologyService terminologyService in its
constructor\. This property may not be empty\.
But I don't...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [2 months...](https://discourse.openehr.org/t/2-months/14586)
> Hi all,
Today is exactly 2 months since something was committed on the
ref\_impl\_java trunk\. It troubles me that nothing has happened since
then\. I've been waiting for a long time to see support for action and
instruction archetypes and archetype slots but nothing seem to happen\.
Projects which haven't had any updates in two months can be thought of
as dead in the open source world\. I don't want that to happen\!
Isn't it possible to allocate some resources from UCL to...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Assumed values etc.](https://discourse.openehr.org/t/assumed-values-etc/14584)
> Hi,
I have found some issues which concerns the Ocean Archetype Editor\.
When editing the person state, it is possible to set assumed values
for C\_DOMAIN\_TYPE data types\. However, I haven't found it is possible
to specify assumed values for these data types when I looked through
the openEHR archetype profile specification\. The only data types it
should be possible to set assumed values for are C\_PRIMITIVE data
types\. This seems to be an error in the editor, so if we need...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [123] Update help for diff test.](https://discourse.openehr.org/t/ref-impl-eiffel-123-update-help-for-diff-test/15886)
> Revision: 123
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [122] Move any_allowed to C_DEFINED_OBJECT, ARCHETYPE_SLOT and C_ATTRIBUTE; implement as a function;](https://discourse.openehr.org/t/ref-impl-eiffel-122-move-any-allowed-to-c-defined-object-archetype-slot-and-c-attribute-implement-as-a-function/12169)
> Revision: 122
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [121] Revert path extraction algorithm to always include node_ids;](https://discourse.openehr.org/t/ref-impl-eiffel-121-revert-path-extraction-algorithm-to-always-include-node-ids/15885)
> Revision: 121
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release of Java Archetype Editor v0.4](https://discourse.openehr.org/t/release-of-java-archetype-editor-v0-4/15884)
> Dear all,
The Java Archetype Editor v0\.4 has now been released\. Both the binary
and the source code is available for download here:
http://www.imt.liu.se/mi/ehr \.
Please take your time to read the release notes before installing the program\.
The Archetype Editor was developed within the framework of the
EU\-funded Network of Excellence entitled Semantic Interoperability and
Data Mining in Medicine\. Read more about Semantic Mining at
http://www.semanticmining.org \.
Best...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [single-valued and container cardinality](https://discourse.openehr.org/t/single-valued-and-container-cardinality/12500)
> The ADL spec \(section 4\.3\.3\) says that
"with no cardinality, the meaning is that each child object
constraint of the attribute in question is a possible
alternative for the value\.\."
i\.e\. that this attribute is "single\-valued" and the
types are multiple alternatives\.
It then gives an example and says
"here, the cardinality of the value attribute is 1\.\.1
\(the default\), which the occurrence of both QUANTITY
constraints is optional\.\.\."
I just...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [UML model](https://discourse.openehr.org/t/uml-model/12501)
> Hello all,
From the openEHR Modelling Guide, "The primary models are also
losslessly translated to a UML\-2\.0 compliant XML instance form\."
Is this available anywhere?
Thanks,
Ken McKee
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [a zero existence constraint](https://discourse.openehr.org/t/a-zero-existence-constraint/15214)
> For the case where an attribute is constrained to '0'
existence i\.e\.
state existence matches \{0\} \.\.\.\.\.
what should follow as the rest of the attribute
constraint? Technically, the rest of the definition
is superfluous as we have already stated that the
attribute must not exist, but the
'matches' clause needs to exist in the grammar\. Should
it be matched to \*, or should it be empty?
state existence matches \{0\} matches \{\*\}
or
state existence matches \{0\}...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype blood_pressure: Data <-> State <-> Protocol - correlation](https://discourse.openehr.org/t/archetype-blood-pressure-data-state-protocol-correlation/14583)
> Hi,
I am writing my diploma thesis at the Vienna Medical University\. I have
two questions concerning the openEHR\-EHR\-OBSERVATION\.blood\_pressure\.v1
Archetype \(Date 22/03/2006\) and would be very thankful if someone could
answer them briefly\.
1st:
I read in the "The openEHR Reference Model \- EHR Information Model"
\(openehr\_ehr\_im\.pdf Revision: 5\.1\.0\) in chapter "8\.2\.3\.4 Two ways of
Recording State" that there are two ways to record States inside a...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - ['not' matches](https://discourse.openehr.org/t/not-matches/12171)
> How does the
not matches \{ \.\.\. \}
and \~ is\_in \{ \.\.\. \}
for attributes
mentioned in the ADL document 4\.2\.1
transform into AOM? Shouldn't there be a
'negate' field on C\_OBJECT or
C\_ATTRIBUTE?
Andrew
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADLParser exception :-/](https://discourse.openehr.org/t/adlparser-exception/14582)
> Hello all
I have set up a simple project where i am using the following code to
read and parse an archetype:
File ADLFile=new file\("/blah
blah/openehr\-demographic\-person\.person\.draft\.adl"\);
ADLParser parser=new ADLParser\(ADLFile\);
Archetype MyArchetype=parser\.parse\(\);
When i try to run this, i get:
Exception in thread "main"
se\.acode\.openehr\.parser\.ParseException:Encountered...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [119] Widen combo boxes in ADL Workbench MAIN_WINDOW;](https://discourse.openehr.org/t/ref-impl-eiffel-119-widen-combo-boxes-in-adl-workbench-main-window/15882)
> Revision: 119
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 candidate XML-schemas now published.](https://discourse.openehr.org/t/release-1-0-1-candidate-xml-schemas-now-published/12170)
> The XML-schemas for the Release 1.0.1 candidate are now available from the hotlinks section of the openEHR home page, [http://www.openEHR.org](http://www.openEHR.org), or go directly there: [http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/its/XML-schema/index.html](http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/its/XML-schema/index.html)
Two new schemas are now included:
- a schema for the VERSION and related classes, enabling...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [118] Correct export settings on serialiser classes based on ES 5.7 beta parser error.](https://discourse.openehr.org/t/ref-impl-eiffel-118-correct-export-settings-on-serialiser-classes-based-on-es-5-7-beta-parser-error/12168)
> Revision: 118
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [the periodic definition in data structures IM](https://discourse.openehr.org/t/the-periodic-definition-in-data-structures-im/14573)
> The HISTORY IM has a definition for a period which
is meant to represent the time between contained
events\. However, in the case where this
period is filled in, the spec makes no restriction on the
EVENT\.time field \- i\.e\. what is the meaning of
a HISTORY object with a period set, but yet which
contains EVENTs that are not according to this
periodic duration? It would be good if the spec
clarified what the indented behaviour of an openEHR
system that encounters such data should be\.
Andrew
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New release of ADL Workbench](https://discourse.openehr.org/t/new-release-of-adl-workbench/15883)
> The ADL Workbench, a tool for viewing and testing archetypes has had a
major upgrade\. The download link, screen shots and help can be found at
http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm
A Mac OSX version is under test and should be available in the next few
weeks\.
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [117] Fix download links on project page](https://discourse.openehr.org/t/ref-impl-eiffel-117-fix-download-links-on-project-page/12167)
> Revision: 117
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [116] Update link to ADL Workbench to .msi link](https://discourse.openehr.org/t/ref-impl-eiffel-116-update-link-to-adl-workbench-to-msi-link/12166)
> Revision: 116
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [115] Remove manifest file (not needed);](https://discourse.openehr.org/t/ref-impl-eiffel-115-remove-manifest-file-not-needed/12165)
> Revision: 115
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Antw: Re: Antw: Re: Antw: Re: Antw: Re: EHRcom/openEHR the new exciting parad...](https://discourse.openehr.org/t/antw-re-antw-re-antw-re-antw-re-ehrcom-openehr-the-new-exciting-parad/12164)
> In een bericht met de datum 25-9-2006 20:29:08 West-Europa (zomertijd), schrijft sam.heard@oceaninformatics.biz:
> William
> I think targets are more complex than setting a mood code, but I might be wrong. The Goal is 130/90 - is it greater than this or less than this? What if the BP is 40/20 - does this meet the goal - how does the computer know?
> It is hard to get this right - but very important if we are to make use of computers.
> Cheers, Sam
You are right, Heath pointed out that we...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [114] Remove use of leading 'T' in ISO8601 date/time constraint patterns; allow on read, but remove on write.](https://discourse.openehr.org/t/ref-impl-eiffel-114-remove-use-of-leading-t-in-iso8601-date-time-constraint-patterns-allow-on-read-but-remove-on-write/12162)
> Revision: 114
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [problem with ADL in sample archetype library](https://discourse.openehr.org/t/problem-with-adl-in-sample-archetype-library/14572)
> > From the sample archetype repository is this ADL construct
\(its actually used in quite a few of the evaluation archetypes\)
openEHR\-EHR\-EVALUATION\.problem\-diagnosis\-histological\.v1\.adl
ELEMENT\[at0005\] occurrences matches \{0\.\.1\} matches \{ \-\- Severity
value matches \{
ORDINAL matches \{
value matches \{
1|\[local::at0006\], \-\-...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [113] Remove Visual Studio user prefs file.](https://discourse.openehr.org/t/ref-impl-eiffel-113-remove-visual-studio-user-prefs-file/15881)
> Revision: 113
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [112] Add Peter Gunmmer's fixed Macosx Ace file;](https://discourse.openehr.org/t/ref-impl-eiffel-112-add-peter-gunmmers-fixed-macosx-ace-file/15879)
> Revision: 112
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [syntax path, for itemAtPath](https://discourse.openehr.org/t/syntax-path-for-itematpath/14563)
> Hi, I cannot find how the path in itemAtPath, which is a part of a
RMObject is constructed\.
For example, I have this archetype
PERSON\[at0000\] matches \{ \-\- simple person
identities cardinality matches \{0\.\.\*; unordered; unique\} matches \{
PARTY\_IDENTITY\[at0001\] matches \{ \-\- person...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR and HL7 – some thoughts on the current discontents from Chair of openEHR](https://discourse.openehr.org/t/openehr-and-hl7-some-thoughts-on-the-current-discontents-from-chair-of-openehr/14491)
> I returned from a week of sailing to discover flames leaping from
the openEHR list server in the machine room opposite my office\! I’m with
many recent correspondents on the lists in welcoming the positive side
of the debate whilst regretting some of the evidence of raw feelings in
play\. I’m sure many are wondering or reflecting on what this is all
about\. From my perspective, there’s no need for a lot of new words
about openEHR and HL7, per se, but a great need to keep hearts and minds
in...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [shortened matching types in cADL](https://discourse.openehr.org/t/shortened-matching-types-in-cadl/15880)
> > From the spec 4\.4
While constraints on complex types follow the rules
described so far, constraints on attributes of
primitive types in cADL can be expressed
without type names, and omitting one level of braces, as
follows:
some\_attr matches \{some\_pattern\}
rather than:
some\_attr matches \{
BASIC\_TYPE matches \{
some\_pattern
\}
\}
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [HIER_OBJECT_ID in JAVA](https://discourse.openehr.org/t/hier-object-id-in-java/14578)
> Some questions regarding this class's implementation in Java\.
I've noticed that the HierarchicalObjectID in java has nothing to do
with the specs,
so which one is out of sync?
I've also noticed some very precise string handling there\. I assume it
was programmed following some kind of ID pattern in mind\.
is this pattern propietary or can you share it?
we are going to use your classes so adjusting to your idea will save us
work\.
cheers
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [cardinality question](https://discourse.openehr.org/t/cardinality-question/14316)
> Please allow me a tiny question, I cannot find it in the docs\.
PARTY\_IDENTITY\[at0001\] matches \{ \-\- person name
29 name matches \{
30 DV\_TEXT matches \{
31 value matches \{"legal identity"\}
32 \}
33 \}
34 details matches \{
35 ITEM\_LIST\[at0002\] matches \{
What is the cardinality of details \(so, what is the default...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [integer intervals](https://discourse.openehr.org/t/integer-intervals/14307)
> According to ADL spec 4\.4\.2\.2, intervals of integer values
can be combined using the semi colon character as follows;
critical\_range matches \{|5\.\.9; 101\.\.110|\}
Yet, the AOM definition for C\_INTEGER only allows one
range to be specified\. Should the AOM be extended
to allow multiple integer ranges or is this syntax
deprecated?
Andrew
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [list of time/dates and the AOM](https://discourse.openehr.org/t/list-of-time-dates-and-the-aom/14291)
> > From the ADL spec
4\.4\.6 Constraints on Dates, Times and Durations
Dates, times, date/times and durations may all be constrained
in three ways: using a list of values, using intervals,
and using patterns
However, the C\_DATE, C\_TIME etc classes for the AOM
only have a 'range' slot and not a 'list' slot\. In constrast, the
C\_INTEGER, C\_REAL have both a 'range' and a 'list'\.
Is there a different way of representing lists of
dates in AOM?
Andrew
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ErrorType UNKNOWN](https://discourse.openehr.org/t/errortype-unknown/14577)
> Maybe Rong can help me, but maybe others also, if Rong is too busy, or
does not read the email
I get all the time in a specific archetype the ErrorType UNKNOW, when I
print the ErrorMap\.
I get it very much on top of the archetype:
\{/\[at0000\]/details\[at0001\]/=UNKNOWN
Is it possible to indicate what this error means\.
I found the enum ErrorType, but it was not documented in the code
However, most of them speak for themselve, but some don't
MISSING, BAD\_INDEX, BAD\_FORMAT,...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ISO 8601 time values](https://discourse.openehr.org/t/iso-8601-time-values/14273)
> I'm a bit confused about the ISO 8601 time values\.\.
when are they meant to be preceeded by a 'T' and
when are they not? I understand that when you
have a complete DateTime value, the 'T' character
splits the date and time\. But when you have a
time by itself, I'm not sure what is meant to
happen\. The ADL documents seem to be
inconsistent regarding this \- and the reference
grammar seems to have the T in the comment
but then doesn't have it in the actual lex...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 candidate UML now online](https://discourse.openehr.org/t/release-1-0-1-candidate-uml-now-online/12159)
> Dear all,
The online UML of the Release 1\.0\.1 candidate of the openEHR
specifications is now available\. This work has been done by David Lloyd
at CHIME, UCL, for which we are extremely grateful\.
Please see the openEHR home page http://www.openehr.org/ under the
Release 1\.0\.1 candidate heading \- UML printable / browsable links\. The
printable is a single page HTML view, while the browsable is a
tree\-based view\.
We would appreciate members of the openEHR community having a good...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [wishlist workbench](https://discourse.openehr.org/t/wishlist-workbench/12145)
> \(good for documentation purposes\)
\- possibility to export an image of the node\-map\.
\- possibility to copy node\-map as image to clipboard
\- possibility to maximize the window
thanks
bert
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [registration // password reminder](https://discourse.openehr.org/t/registration-password-reminder/12476)
> Hi,
Can you register me for the java-implementation list please?
I tried to register using [s.garde@cqu.edu.au](mailto:s.garde@cqu.edu.au) but never received a registration mail with my password and using the password reminder function doesn't work either...it says an email has been sent to you, but it does not arrive.
Kind regards
Sebastian
Dr Sebastian Garde
Faculty of Business and Informatics, Central Queensland University
Austin Centre for Applied Clinical Informatics
Austin...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[60] readme](https://discourse.openehr.org/t/60-readme/12155)
> Revision: 60
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[59] create sandbox area](https://discourse.openehr.org/t/59-create-sandbox-area/12153)
> Revision: 59
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Notice of listserver changeover](https://discourse.openehr.org/t/notice-of-listserver-changeover/12158)
> Dear all,
this list will be changed over in the next 24h to Mailman, from Majordomo\. You should not notice anything\. However, if you have problems posting, receiving etc, please email openehr\-implementers\-owner@openehr\.org
\- thomas beale
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL workbench wish list](https://discourse.openehr.org/t/adl-workbench-wish-list/12151)
> It should remember the last directory I was
thanks
Bert
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL-workbench](https://discourse.openehr.org/t/adl-workbench/12150)
> Maybe a file missing?
Error code: VTCT
Error: type is based on unknown class\.
What to do: use an identifier that is the name of a class in the universe\.
Class: ADL\_TEST\_ARCHETYPE\_TREE\_CONTROL
Unknown class name: ARCHETYPE\_DIRECTORY\_ITEM
Thanks
Bert
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype Editor question](https://discourse.openehr.org/t/archetype-editor-question/14571)
> Since both Archetype\-editors share the same GUI concept, my question applies to both\.
Where do I edit the "existence\-constraint"
Al I can see is a possiblity to edit the occurences constraint\.
Maybe it happens implicitely by choosing some option\.
Can someone please explain?
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [111] Add Repository menu and dialog;](https://discourse.openehr.org/t/ref-impl-eiffel-111-add-repository-menu-and-dialog/12149)
> Revision: 111
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype-editors](https://discourse.openehr.org/t/archetype-editors/14570)
> Hi, I have three archetype\-editors, the overal quality is low\. This is a bad thing\.
I use the written in Eiffel Archetype Workbench
The in VB\.DOTNET editor from Ocean
and the Java\-editor\. I wonder if images come through in this list, this is my archetype, still building\.
The ocean error produces an error message, when loading an archetype created in the ADL\-workbench\. I print the error\-message below\.
The Java\-editor changes the archetype \(very dangerous\), without warning
The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [questions about string literals](https://discourse.openehr.org/t/questions-about-string-literals/14567)
> I am having trouble with the exact definition of the
string literal\.\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [No religion, but discussion based on argumentation, dealing with the real issues](https://discourse.openehr.org/t/no-religion-but-discussion-based-on-argumentation-dealing-with-the-real-issues/12451)
> Dear Gerard,
Thank you very much for bringing up the point of religious fanatism in relation to standards development and application.
It is a word from my hearth in this ongoing debate with you. :-)
I want to analyse both standards (13606/OpenEHR and HL7 v3), look at each strenght and weakness and make sure that we achieve semantic interoperability in an intelligent way, by applying scientifically derived methods, evaluating approaches and results, and harmonize the work on standards....
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest openEHR Architectural Overview](https://discourse.openehr.org/t/latest-openehr-architectural-overview/16637)
> Hi Thomas
I'm newbie to openEHR.
My few cents to the Architecture document.
Would it be possible to have visualization of runtime usecase scenarios
which would include
1) adding new archetypes & templates to the system( parsing-storing to repository.)
2) how a template is used in the system, for example when an observation event happens.
rgds
minreddy
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [110] Minor improvement to help page text.](https://discourse.openehr.org/t/ref-impl-eiffel-110-minor-improvement-to-help-page-text/12148)
> Revision: 110
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [109] Update project page;](https://discourse.openehr.org/t/ref-impl-eiffel-109-update-project-page/12147)
> Revision: 109
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [108] Correct errors in help page.](https://discourse.openehr.org/t/ref-impl-eiffel-108-correct-errors-in-help-page/15873)
> Revision: 108
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [107] Additional changes for ADL workbench tester additions:](https://discourse.openehr.org/t/ref-impl-eiffel-107-additional-changes-for-adl-workbench-tester-additions/15872)
> Revision: 107
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [106] Addition of test functionality to ADL workbench, to replace ADL command line utility; includes:](https://discourse.openehr.org/t/ref-impl-eiffel-106-addition-of-test-functionality-to-adl-workbench-to-replace-adl-command-line-utility-includes/15871)
> Revision: 106
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Archetype-versions](https://discourse.openehr.org/t/archetype-versions/14562)
> I is starting to stress me really\. There are so many Archetypes available, and there are three tools in use by me to open them\.
One is an archetype\-analyzer, I wrote myself, a syntax checker\.
The other is an Archetype Editor, written by those Swedish guys,
And one is an Archetype Editor from Ocean\.
I wish there was a consistent set of Archetypes which can be opened by one or the other, and that it was documented as such\.
I know, the problem is the moving target of changing ADL...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Sources of information on HL7 EHR/OpenEHR](https://discourse.openehr.org/t/sources-of-information-on-hl7-ehr-openehr/14561)
> Hello,
Are there any documents anywhere that describe or compare and contrast the
OpenEHR initiative and the HL7 EHR effort? I have seen a couple of references
to the fact that there are efforts to achieve harmonization but I was
wondering if there is a detailed comparison anywhere\.
We are in the process of working through the OpenEHR specification documents
and implementation code as well as the specification documents coming out of
the HL7 EHR effort so, I was wondering if there are is a...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [105] Add new directories for archetype_directory component](https://discourse.openehr.org/t/ref-impl-eiffel-105-add-new-directories-for-archetype-directory-component/12450)
> Revision: 105
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest Architecture Overview + new HTML browsable](https://discourse.openehr.org/t/latest-architecture-overview-new-html-browsable/15874)
> A chapter on terminology has been added to the openEHR Architecture
Overview, and the document is now available in a new online multi\-page
HTML form
\(http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/html/architecture/overview/Output/front.html).
Both links are available in the hotlinks section on the right hand side
of the home page\.
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [104] Add download links to help page.](https://discourse.openehr.org/t/ref-impl-eiffel-104-add-download-links-to-help-page/12146)
> Revision: 104
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [103] Corrected mime-types on help image files;](https://discourse.openehr.org/t/ref-impl-eiffel-103-corrected-mime-types-on-help-image-files/12141)
> Revision: 103
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [archetype in memory creation](https://discourse.openehr.org/t/archetype-in-memory-creation/14566)
> Hi, I wonder about this,
If one creates an Arcehtype in Memory, and writes it out to an ADL-file. (This possible in the Java-implementation using ADLOutputter),
and then read it back, into memory, if one has the same Archetype in memory?
I have this in...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [License violation](https://discourse.openehr.org/t/license-violation/14564)
> I found the license box in the Archetype Editor which states it is an open source product, licensed under GPL\. \(version 3\)
Version: MPL 1\.1/GPL 2\.0/LGPL 2\.1
I hope the sourcecode will be published soon, because at this moment, the GPL is violated, which is a bad thing to see happen\.
regards
Bert Verhees
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [102] Further minor GUI appearance improvements](https://discourse.openehr.org/t/ref-impl-eiffel-102-further-minor-gui-appearance-improvements/12140)
> Revision: 102
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Implementation Questions](https://discourse.openehr.org/t/implementation-questions/14554)
> Dear All
My name is Athanasios Anastasiou and i am with the Signal Processing and
Multimedia Communications Research Group at the University of Plymouth, UK\.
The university is currently leading a 31 institutions partnership in a 4
year European FP6 program called BIOPATTERN\. More information can be
found in http://www.biopattern.org or our revised website at
http://www.biopattern.org/Test1 by following the link, "About the NoE\."
I have been reading the rather detailed specs...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [openEHR terminology](https://discourse.openehr.org/t/openehr-terminology/14560)
> Hi all,
I think there is a need to improve the computable openEHR terminology
available here:
http://svn.openehr.org/specification/TRUNK/publishing/architecture/computable/terminology/terminology.html
\.
I would like to add bindings in archetypes from SNOMED Clinical Terms,
2006 but it isn't available in the Terminology\.xml file, only SNOMED
International Clinical Terms, 2002, which is pretty old\. I think the
computable terminology can be improved a lot by adding more
translations...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [EMail Woes](https://discourse.openehr.org/t/email-woes/12139)
> It appears that when I changed my email address in the profile at openEHR\.org it correctly unsubscribed me from all the mailing lists\. I received notices to that fact\.
However, I do not think it resubscribed me to the lists though I did check the boxes\.
Of course my email address hasn't been changed for the ARB list either\.
Can you help with these issues?
Thanks,
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [List change-over](https://discourse.openehr.org/t/list-change-over/12142)
> Dear all,
this list is to be converted from Majordomo to Mailman in the next 24
hours\. We have been testing this change on some other lists, and believe
we have the process right\. We expect the change to be invisible to
subscribers, so you should not notice anything\. Nevertheless as we all
know, unexpected gremlins may appear\. If problems occur, please report
them to the list administrator using the email address
openehr\-technical\-owner@openehr\.org \.
thanks
\- thomas beale
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [101] Continued file renaming](https://discourse.openehr.org/t/ref-impl-eiffel-101-continued-file-renaming/12138)
> Revision: 101
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [100] More file renaming for ADL workbench help](https://discourse.openehr.org/t/ref-impl-eiffel-100-more-file-renaming-for-adl-workbench-help/12137)
> Revision: 100
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype Modification](https://discourse.openehr.org/t/archetype-modification/14569)
> Let's say I have an archetype being used for some time and it needs to be modified in a way that alters paths to inputs.
I cannot replace the original archetype with the new one because all previous data recorded and probably templates created based on the original template would stop working. So I would have to keep the old one and start work with the second one, and adjust templates or create new ones.
In any case it is not clear to me what the full impact of these changes would be.
Is...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [99] File extension renaming continued (test 1 file)](https://discourse.openehr.org/t/ref-impl-eiffel-99-file-extension-renaming-continued-test-1-file/12438)
> Revision: 99
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [98] Fix help graphics file extensions.](https://discourse.openehr.org/t/ref-impl-eiffel-98-fix-help-graphics-file-extensions/12437)
> Revision: 98
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [97] Attempt to fix png image type problem](https://discourse.openehr.org/t/ref-impl-eiffel-97-attempt-to-fix-png-image-type-problem/15870)
> Revision: 97
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [96] Cleaner description interface image](https://discourse.openehr.org/t/ref-impl-eiffel-96-cleaner-description-interface-image/15868)
> Revision: 96
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [BOUNCE openehr-implementers@openehr.org: Non-member submission from [Tim Cook ]](https://discourse.openehr.org/t/bounce-openehr-implementers-openehr-org-non-member-submission-from-tim-cook-timothywayne-cook-gmail-com/15869)
> \[Tim \- you are bouncing at the moment \- are you posting from the address you are currently subscribed under?\]
> Hi Bert,
>
> Could you tell me where you found that restriction? AFAIK any ISO8601 compliant format is allowed\.
>
> Thanks,
> Tim
>
> Bert Verhees wrote:
>
>> Hi,
>>
>> As I read in the ADL document, the notation for dates has always dashes in between\.
>> Like yyyy\-MM\-dd
>>
>> I wonder why this is, and if other date\-notations will be permitted in the future\....
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [95] Add links to project page for mailing list](https://discourse.openehr.org/t/ref-impl-eiffel-95-add-links-to-project-page-for-mailing-list/15867)
> Revision: 95
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[58] Update project page to include mailing list link](https://discourse.openehr.org/t/58-update-project-page-to-include-mailing-list-link/15866)
> Revision: 58
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [94] Correct absolute icon path to be relative.](https://discourse.openehr.org/t/ref-impl-eiffel-94-correct-absolute-icon-path-to-be-relative/12136)
> Revision: 94
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [93] Added link from ADL workbench application to online help page.](https://discourse.openehr.org/t/ref-impl-eiffel-93-added-link-from-adl-workbench-application-to-online-help-page/12135)
> Revision: 93
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [92] Added new help page for ADL workbench.](https://discourse.openehr.org/t/ref-impl-eiffel-92-added-new-help-page-for-adl-workbench/12134)
> Revision: 92
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [91] Add ADL workbench help page image directory and thumbnails](https://discourse.openehr.org/t/ref-impl-eiffel-91-add-adl-workbench-help-page-image-directory-and-thumbnails/12133)
> Revision: 91
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [90] ADL workbench GUI improvements:](https://discourse.openehr.org/t/ref-impl-eiffel-90-adl-workbench-gui-improvements/12132)
> Revision: 90
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Instruction, and Action in Java.](https://discourse.openehr.org/t/instruction-and-action-in-java/12143)
> This message will probably be best answered by Rong, I guess\.
I've been working today to understand the semantics of the instruction and action classes\. When done I went to take a look to the java implementation nad found that ACTION, ACTIVITY, ISM\_TRANSITION and INSTRUCTION\_DETAILS re not implemented\.
INSTRUCTION is implemented but it's public methods and attributes do not match the ones in the specs\.
Are this classes going to be implemented soon following the specs? or are...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [todo list on ref_impl_java project](https://discourse.openehr.org/t/todo-list-on-ref-impl-java-project/15529)
> Hi all,
Some notes from our openEHR implementor gathering at Maastriht MIE
conference\.
Rong
TODO List
1\. Roadmap for the Java land
2\. Quick start doc for new developers
3\. Demo application driving by archetypes
4\. Dev tools / environment
\* build system \- make nightly build \+ integration...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[57] fixed dependencies to the kernel on parser and serializer](https://discourse.openehr.org/t/57-fixed-dependencies-to-the-kernel-on-parser-and-serializer/12428)
> Revision: 57
Author: rong\.chen
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Normal and other ranges](https://discourse.openehr.org/t/normal-and-other-ranges/14559)
> I see DV\_ORDERED can optionally have specified normal and other ranges\.
While the other ranges are said to be dependant on the measuring context\.
normal range it seems to me, coud be defined as allways the same?
I'm thinking about laboratory resullts\.
Anyway, is there a way to define this ranges in Archetypes?
Or should a decission support module be responsible for this?
thank you
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL parser](https://discourse.openehr.org/t/adl-parser/14558)
> Hi
'GUI Archetype Editor uses Eiffel reference ADL parser' as stated in this page http://svn.openehr.org/knowledge_tools_java/TRUNK/project_page.htm
Is there any ADL parser written in Java?
Is anybody working on that?
rgds
minreddy
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [89] Small fixes:](https://discourse.openehr.org/t/ref-impl-eiffel-89-small-fixes/12131)
> Revision: 89
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[56] project page updated](https://discourse.openehr.org/t/56-project-page-updated/12130)
> Revision: 56
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [More doubts about assertions](https://discourse.openehr.org/t/more-doubts-about-assertions/14568)
> Specs and documentation state that assertions should be used in reference to information **inside** the archetype they are defined in.
does this mean I cannot create an assertion in composition to validate some relation between two observations which are part-of the composition?
This situation came up while I was thinking on how to model the following, "perinatology reports should not be recorded for male patients".
How would you represent this restriction with RM and archetypes?
thank you
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Building RM Objects in JAVA](https://discourse.openehr.org/t/building-rm-objects-in-java/14557)
> We've found a set of classes apparently aimed at building RM objects.
There is not any explanation on how to use them and it is hard for us to work out how complete this package is.
more information on this would be very welcome.
After studying the package we could not decide if the it uses paths as inputs or not.
I was wondering, why not create a method **setItemAtPath** analogous to **itemAtPath** in locatable?
any thoughts?
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Problem displaying a self constructed archetype](https://discourse.openehr.org/t/problem-displaying-a-self-constructed-archetype/16634)
> Hi,
I have constructed a archetype, not following any known schema but on syntax correct, I believe.
I constructed it using objects and methods.
It is a very simple archetype, with one CComplexObject, called "AD", a attribute-list, and there only one CAttribute, and there only one Element, a DvBoolean, and no ontology.
If I do a archetype.toString() it shows all the things, a bit on Java-level, which are in it. I printed it below in a fixed width character (for readability), the DvBoolean...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parsing TEXT](https://discourse.openehr.org/t/parsing-text/14200)
> just catching up\.\.\.\.
> Newton Aird wrote:
>
> Hi,
> I am trying to figure out what should be the correct production in
> the AOM for the following ADL code\. What bothers me most is the
> TEXT matches \{\*\} construct\.
>
> ELEMENT\[at0002\] matches \{ \-\-...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [pathAtItem in Compositions Context](https://discourse.openehr.org/t/pathatitem-in-compositions-context/14556)
> Sorry Sam, I was referring to the Java kernel implementation, not the specs.
Sam Heard wrote:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ITEM_LIST implementation in JAVA_KERNEL](https://discourse.openehr.org/t/item-list-implementation-in-java-kernel/11995)
> Hi there,
We've been building some RM objects and have found that the implementation of ITEM_LIST differs from the spec. In the SPEC ITEM_LIST is composed of ELEMENTs whereas in the implementation it is composed of CLUSTERs.
Some questions:
Why did you decide to implement it this way?
In order to provide more generality should ITEM_LISTs not be composed of abstract ITEMS?
Does this not impose that archetypes containing ITEM_LISTS will have to define clusters and then ELEMENTS?
thank you
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[54] move am.archetype.description package to rm.common.resource](https://discourse.openehr.org/t/54-move-am-archetype-description-package-to-rm-common-resource/15865)
> Revision: 54
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[53] renaming release-1.0 branch](https://discourse.openehr.org/t/53-renaming-release-1-0-branch/15864)
> Revision: 53
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [AUDIT_DETAILS](https://discourse.openehr.org/t/audit-details/16636)
> I'm trying to understand where audit details are used and how\.
My first thought was that it had to be an attribute of contribution which is correct, but then I found it is also an attribute of the VERSION class\.
Then I thought, ok this is better, let's audit each version and we are done\. The first version holds the info about the original "submission", the second for the second version, etc\.
But why do we need it in contribution? of course I'm missing something...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[52] Modified test cases to cope with different values of default time zone](https://discourse.openehr.org/t/52-modified-test-cases-to-cope-with-different-values-of-default-time-zone/15863)
> Revision: 52
Author: yinsu\.lim
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[51] Remove tests that are system time zone dependent](https://discourse.openehr.org/t/51-remove-tests-that-are-system-time-zone-dependent/15862)
> Revision: 51
Author: yinsu\.lim
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[50] Second attempt for Rel 1.0.1, no changes committed for AM package](https://discourse.openehr.org/t/50-second-attempt-for-rel-1-0-1-no-changes-committed-for-am-package/12128)
> Revision: 50
Author: yinsu\.lim
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[49] Initial commit to upgrade reference model to 1.0.1.](https://discourse.openehr.org/t/49-initial-commit-to-upgrade-reference-model-to-1-0-1/12417)
> Revision: 49
Author: yinsu\.lim
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[48] fixed bugs on multi-terminology and multi-language](https://discourse.openehr.org/t/48-fixed-bugs-on-multi-terminology-and-multi-language/12416)
> Revision: 48
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[47] missed test adl](https://discourse.openehr.org/t/47-missed-test-adl/12127)
> Revision: 47
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[46] externalized test adl](https://discourse.openehr.org/t/46-externalized-test-adl/12124)
> Revision: 46
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[45] test svn tag](https://discourse.openehr.org/t/45-test-svn-tag/12123)
> Revision: 45
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[44] re-organized the testcases of adl-serializer](https://discourse.openehr.org/t/44-re-organized-the-testcases-of-adl-serializer/12122)
> Revision: 44
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[43] externalized the ADLOutputter and made it a standalone component called adl-serializer](https://discourse.openehr.org/t/43-externalized-the-adloutputter-and-made-it-a-standalone-component-called-adl-serializer/12121)
> Revision: 43
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Class Archetype, eo](https://discourse.openehr.org/t/class-archetype-eo/16706)
> I noticed that in the code I use, the class Archetype is immutable \(no setters, only betters\)
I also noticed that in, f\.e\. in Visual basc written Archetype Editor from Ocean Informatics, there is a class ADL\_Archetype \(this has setters\), which inherits from class Archetype, but also the ancestor has setters\. So the ArchetypeEditor has a lot more setter\-functionality, this is of course very explainable\.
I wonder, could the code\-concepts be used to generate Archetypes from HL7...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [please one more question](https://discourse.openehr.org/t/please-one-more-question/14565)
> Hi, I am getting good along with the java\-tests and really start to
understand\. I understand java\-code better then documentation, I noticed\.
I have one thing found which I don't understand, if it is to long to explain,
please point me to the docs where I can find the answer\.
It is in the Java\-code, in the testfile: ChildPatientV1Test\.Java\.
It is doing tests with archetype openEHR\-demographic\-PERSON\.child\_patient\.v1
It is inserting data and building RMObjects\.
If there an...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Mapping Archetypes to HL7 and vv [from Heath Frankel]](https://discourse.openehr.org/t/mapping-archetypes-to-hl7-and-vv-from-heath-frankel/14555)
> \[Something funny going on with the list server right now; this post is from Heath Frankel in response to Bert Verhees\.\.\.\.\]
Bert,
Sorry I have been meaning to respond for some time but have been considering
how to do so\.
To be blunt, I would suggest that your approach should be reversed\. When
working in the EHR messaging space I consider openEHR/CEN 13606 reference
models and archetypes as logical models rather than implementation models
and HL7 becomes the ITS\. So what you are...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [88] Minor further ISO 8601 date/time corrections](https://discourse.openehr.org/t/ref-impl-eiffel-88-minor-further-iso-8601-date-time-corrections/15861)
> Revision: 88
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Java2Archetypes](https://discourse.openehr.org/t/java2archetypes/15860)
> Related to my previous message:
Is there any software which is able to build archetyps from Java\-classes
\(code or compiled \(f\.e\. using reflection\)\)
Thanks
Bert
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [87] Remove unimplemented app_interactive_mode function;](https://discourse.openehr.org/t/ref-impl-eiffel-87-remove-unimplemented-app-interactive-mode-function/15858)
> Revision: 87
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Mapping Archetypes to HL7 and vv](https://discourse.openehr.org/t/mapping-archetypes-to-hl7-and-vv/14549)
> Hi,
I am busy mapping HL7 CMETS to archetypes\. This is for a project I am
working on\. In fact, I am preparing the mapping\.
I am working on a special Dutch message based on Primary Care DMIM, the
message contains a complete patient file\.
It looked very promising in the beginning, with JAXB \(on advise of Rong\)
I translated the involved HL7\-XSD's to Java classes\.
The purpose is to create archetypes and give them the name of the HL7
CMETs, for example:
COCT\_MT090000NL2\.Person,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [birth_weight, pregnancy, adl](https://discourse.openehr.org/t/birth-weight-pregnancy-adl/14546)
> Omer
The pregnancy archetype is a new approach and therefore draft - but I think it will be a more common approach in the future - I could be wrong! We are debating this at the moment and I am not sure of the final outcome. The pregnancy archetype has the benefit, at the moment, of keeping key information about a pregnancy in one place - a coherent data set that can persist over a long period, be shared and copied - find its way into the baby's health record etc. It is an evaluation, as it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [On alerts and medication interaction](https://discourse.openehr.org/t/on-alerts-and-medication-interaction/15859)
> Hello,
I was wondering how AOM and arquetypes may help in detecting dangerous situations within the clinical activity.
For example, let's say a group observations are recorded and the values indicate that there is a dangerous condition, so some alert should be fired.
Another example refers to medication instructions.
if a medication instruction is repeated in a very short period, can we detect it from the archetype definition?
rephrased, can an assertion check to see if another very similar...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[42] update of iso datetime pattern in the parser](https://discourse.openehr.org/t/42-update-of-iso-datetime-pattern-in-the-parser/15857)
> Revision: 42
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[41] updated Archetype class for attribute adl_version and concept; added support for point interval in the parser; added support for adl_version in the parser](https://discourse.openehr.org/t/41-updated-archetype-class-for-attribute-adl-version-and-concept-added-support-for-point-interval-in-the-parser-added-support-for-adl-version-in-the-parser/15856)
> Revision: 41
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [86] Fix rm commands in makefiles](https://discourse.openehr.org/t/ref-impl-eiffel-86-fix-rm-commands-in-makefiles/12120)
> Revision: 86
Author: thomas\.beale
Log Message:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Release 1 candidate of the openEHR archetype editor](https://discourse.openehr.org/t/release-1-candidate-of-the-openehr-archetype-editor/12119)
> Well done Sam and team. Now how is that blood pressure archetype going!!
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[40] bug fix for c_dv_quantity in adl outputter](https://discourse.openehr.org/t/40-bug-fix-for-c-dv-quantity-in-adl-outputter/12118)
> Revision: 40
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[39] commit missing test code](https://discourse.openehr.org/t/39-commit-missing-test-code/12117)
> Revision: 39
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[38] bug fix for c_dv_quantity; added assumed value for c_coded_text](https://discourse.openehr.org/t/38-bug-fix-for-c-dv-quantity-added-assumed-value-for-c-coded-text/12116)
> Revision: 38
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[37] added support for adl_version and controlled](https://discourse.openehr.org/t/37-added-support-for-adl-version-and-controlled/12115)
> Revision: 37
Author: rong\.chen
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [adl_version of ARCHETYPE class](https://discourse.openehr.org/t/adl-version-of-archetype-class/14551)
> Hi Thomas,
I am updating the parser for handling adl\_version in the header part\. On
page 8 of AOM doc "added a new attribute adl\_version: String to the
ARCHETYPE class", but there is no adl\_version attribute in the ARCHETYPE
class description on p14\. Maybe it's an overlook?
Rong
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [85] Purely cosmetic fix to code](https://discourse.openehr.org/t/ref-impl-eiffel-85-purely-cosmetic-fix-to-code/12391)
> Revision: 85
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [C_CODED_TEXT, C_COUNT, C_QUANTITY, C_ORDINAL?](https://discourse.openehr.org/t/c-coded-text-c-count-c-quantity-c-ordinal/13490)
> Hi there,
Working with Pablo, we fount these classes C_CODED_TEXT, C_COUNT, C_QUANTITY, C_ORDINAL in the AOM Java implementation of the CONSTRAINT package.
These classes are not present in the spec, so some information about the would be useful.
These are the questions we have:
- What are they needed for? shouldn't their functionality be covered with assertions and AOM.Primitive package?
- It seems that there is a mapping between these classes and the RM.DATA_TYPE package classes, if this...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [84] Move command line check for resources to SHARED_RESOURCES class](https://discourse.openehr.org/t/ref-impl-eiffel-84-move-command-line-check-for-resources-to-shared-resources-class/12114)
> Revision: 84
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[36] implmented openEHR Archetype Profile; updated C_DV_QUANTITY and C_DV_ORDINAL support in the parser; updated ADLOutputter accordingly](https://discourse.openehr.org/t/36-implmented-openehr-archetype-profile-updated-c-dv-quantity-and-c-dv-ordinal-support-in-the-parser-updated-adloutputter-accordingly/12113)
> Revision: 36
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.0.1 drafts](https://discourse.openehr.org/t/release-1-0-1-drafts/12125)
> Dear all,
Release 1\.0\.1 is nearly complete\. A lot of small fixes have been made due to implementers finding errors in the models, which is fantastic \- this is exactly the feedback loop we need to maintain good quality, implementable specifications\.
We have also \(I believe\) significantly improved the text of most of the specifications, particularly the Architecture Overview\.
We expect to publish this release in the next 2 weeks, so there is time to make further comments\. The...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [list of C_DV_ORDINAL](https://discourse.openehr.org/t/list-of-c-dv-ordinal/14547)
> Hi Thomas,
Is there any specific reason that the attribute list from C\_DV\_ORDINAL
has to be Set? I wonder if List would be better since it's good to keep
the the order of member element in the list\.
Secondly, should the member be Ordinal or DvOrdinal\. I found it is
difficult to create DvOrdinal directly in the parser\. It was Ordinal in
the previous specification and your Eiffel code\.
Regards,
Rong
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [More issues with archetype profile](https://discourse.openehr.org/t/more-issues-with-archetype-profile/16635)
> Hi Thomas,
More on openehr\_archetype\_profile:
1\. The following invariant on p18 doesn't seem to be correct,
terminology\_id is of type TERMINOLOY\_ID, how can it be empty?
Terminology\_id\_valid: terminology\_id /= Void implies not
\(terminology\_id\.is\_empty or code\_list = Void\)
2\. on page 21 near the bottom, class C\_DV\_ORDINAL "Inherit
C\_DV\_ORDERED", according to the class diagram the super class should be
"C\_DOMAIN\_TYPE" same as the that of...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Transitions_valid invariant of STATE class](https://discourse.openehr.org/t/transitions-valid-invariant-of-state-class/12126)
> Hi Thomas,
I am implementing Date\_types\.basic package and trying to create a test
C\_DV\_STATE with the medication order sample on p11 of openEHR Archetype
Profile document, rev1\.0\.
What I found is it is not possible to create the last state 'COMPLETED'
if the invariant of STATE class "Transitions\_valid: transitions /= Void
and then not transitions\.is\_empty" is in place\. Since it is the end
state, there is no more transition for that state\. Should the invariant
be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [what is the use of the reference model?](https://discourse.openehr.org/t/what-is-the-use-of-the-reference-model/15212)
> I've been going round in circles about this question all weekend, and have two ideas.
1. It's basic and most important use is to provide reference to check the correctness of the arquetypes.
2. It is needed for some types of persistence design
Why am I asking myself this? because once assertions are implemented, all that may be needed for validating real data may be included in archetypes, can't it?
am I missing something?
thank you
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Open sourse web based Patient Health Record](https://discourse.openehr.org/t/open-sourse-web-based-patient-health-record/12105)
> Does anyone know where I can find an open source Patient Health Record to configure for a special new not for profit program to organize PHR for poeple under poverty level. Please send info to: Anthony.Oloni.MD@PHICON.org
Anthony O. Oloni, M.D.
Medical Director
PHICON Corporation
(Public Health Informatics Consultants, USA)
Box 2822, Acworth GA 30102
Phone: Cell 678 886 7992; Office 678 354 6144; Fax 678 355 0462
Email: Anthony.Oloni.MD@PHICON.org | Company Web: www.PHICON.org
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [82] Remove Gobo as a dependency from project pages - it is now included in Eiffel, and the openEHR Ace files have been fixed.](https://discourse.openehr.org/t/ref-impl-eiffel-82-remove-gobo-as-a-dependency-from-project-pages-it-is-now-included-in-eiffel-and-the-openehr-ace-files-have-been-fixed/15854)
> Revision: 82
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [some questions about openEHR - AOM](https://discourse.openehr.org/t/some-questions-about-openehr-aom/14552)
> Hi Rong, my name is Pablo Pazos and i'm working at the NIB with Rodrigo Filgueira.
We are trying to understand the openehr from the bottom, that's the reason im implementing the AOM based on teh specification and taking your implementation as reference.
We based our implementation of AOM in *OpenEHR AOM Release 1 Revision 2.0.1* and took the *Branches Implementation Release 1.0 as a reference.*
I have some questions and Im sure you can help me with them. The questions are separated...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Public release of Java Archetype Editor v0.3](https://discourse.openehr.org/t/public-release-of-java-archetype-editor-v0-3/15853)
> Dear all,
With this message I am happy to announce that the Java Archetype Editor has been publicly released and is available to download from [http://www.imt.liu.se/mi/ehr](http://www.imt.liu.se/mi/ehr). Please read the release notes before installing the editor.
Feedback about the editor is welcomed, both positive and negative.
Open source distribution of the editor will not take place yet, but the source code will be released as soon as we feel it's mature enough.
The Archetype Editor...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [81] Implement openEHR ISO8601 deviation](https://discourse.openehr.org/t/ref-impl-eiffel-81-implement-openehr-iso8601-deviation/12112)
> Revision: 81
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [potential use of openPGP in openEHR](https://discourse.openehr.org/t/potential-use-of-openpgp-in-openehr/14548)
> An initial suggestion \(currently in the Release 1\.0\.1 candidate drafts\) is that openPGP should be used in openEHR for generating digests and signatures\. openPGP is defined at http://www.ietf.org/rfc/rfc2440.txt and a lot of other information can be found at http://www.pgpi.org/ , http://www.gnupg.org/ \.
My proposal is that the openPGP message specification makes sense for defining signature and hash values in openEHR because openPGP fully defines the result string...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[35] support for property attribute of c_dv_quantity in the form of openehr::125](https://discourse.openehr.org/t/35-support-for-property-attribute-of-c-dv-quantity-in-the-form-of-openehr-125/12111)
> Revision: 35
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Progress on Release 1.0.1](https://discourse.openehr.org/t/progress-on-release-1-0-1/12100)
> Dear all,
we are very close to being able to publish Release 1\.0\.1 of openEHR\. Recent changes have mostly been to do with making openEHR compliant to ISO 8601, the standard for dates and times\. We have made quite a few changes to improve the documents in this regard, including:
\- moving the assumed ISO 8601 semantics to the support IM document \(http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/support_im.pdf)
\- simplifying the class model...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[34] initial support for unicode (UTF-8 encoding) in the parser](https://discourse.openehr.org/t/34-initial-support-for-unicode-utf-8-encoding-in-the-parser/12107)
> Revision: 34
Author: rong\.chen
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [80] Further corrections to date/time library routine naming (is_valid_xxx becomes valid_xxx).](https://discourse.openehr.org/t/ref-impl-eiffel-80-further-corrections-to-date-time-library-routine-naming-is-valid-xxx-becomes-valid-xxx/12106)
> Revision: 80
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [79] Corrections to Ace files to use $ISE_EIFFEL/library/gobo/library instead of $GOBO](https://discourse.openehr.org/t/ref-impl-eiffel-79-corrections-to-ace-files-to-use-ise-eiffel-library-gobo-library-instead-of-gobo/12378)
> Revision: 79
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [78] Updates for latest Common IM change_control, generic, resource packages.](https://discourse.openehr.org/t/ref-impl-eiffel-78-updates-for-latest-common-im-change-control-generic-resource-packages/12104)
> Revision: 78
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [77] Numerous small improvements to do with making dates & times ISO compliant:](https://discourse.openehr.org/t/ref-impl-eiffel-77-numerous-small-improvements-to-do-with-making-dates-times-iso-compliant/12103)
> Revision: 77
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Date/times in dADL](https://discourse.openehr.org/t/date-times-in-dadl/14544)
> Dear all,
I have just noticed that in the dADL part of the ADL spec it says that
partial date/times are expressed in a form using "??" characters rather
than the standard ISO8601 format, which is to simply leave out missing
parts\. E\.g\. april 1954 is 1954\-04 in ISO8601, but the dADL spec
currently says it should be 1954\-04\-??\. While I wish the ISO8601
standard was like this, it is not, and in fact in our Eiffel parser, we
have implemented the standard\. We can't handle...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Some questions](https://discourse.openehr.org/t/some-questions/12108)
> Hello again,
I have some questions regarding archetypes.
First, I wonder if I can start implementing support for Demographic archetypes in the Java archetype editor or if I am dependent of some parts that need to be implemented in the Java reference implementation?
Second, I have a tendency to stumble upon new attributes of the different archetypes that are specified in the EHR IM document. There are several attributes there that don't exist in any archetypes yet and I believe some aren't...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Implementation planning](https://discourse.openehr.org/t/implementation-planning/14550)
> Hello development team,
I think we need to start a discussion on possible changes/updates to the current implementation plan for the Java reference implementation. What I've seen this far is that the UCL team has done a fair part of the RM and I wonder if the team can possibly implement some parts in the AOM and the parser in the near future.
Personally I believe the assertion package of the AOM and its link to the parser is important to implement so that the Java archetype editor can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Example or description on the Specification](https://discourse.openehr.org/t/example-or-description-on-the-specification/16633)
> Hi,
I'm using Python to implement the specification of OpenEHR 1\.0\.1
I have a lot of problems in understanding how some functions should be
worked like\.
Here is one; in LOCATABLE class, the function:
path\_of\_item\(a\_loc:LOCATABLE\): String
can u give a example to demonstrate how the function can work out a answer?
because "The path to an item relative to the root of this archetyped
structure\." doesn't help me to solve that\.
similarly, the function...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [76] minor fixes to correct directory routines.](https://discourse.openehr.org/t/ref-impl-eiffel-76-minor-fixes-to-correct-directory-routines/12102)
> Revision: 76
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [About the Archetype lifecycle state](https://discourse.openehr.org/t/about-the-archetype-lifecycle-state/14545)
> Hello everybody,
I have a question about the archetype lifecycle state. This may not be a fundamental question, but it is important to formalize all the aspects regarding to an archetype system. This is what I have found about this topic reading through all the documentation.
First, at the ADL2 document, the section related to the Archetype Identifier references to the Archetype System document. There we can find a clear description of the Multiaxial Archetype Identifier. Well, clear except...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Re:](https://discourse.openehr.org/t/re/15852)
> Stef Verlinden wrote:
>
> Maybe I'm inpatient, but since I didn't get an answer on my question via the Clinical list, I'll try it again via the Implementers list:
>
> \-\-\-\-
>
> I'm trying to learn how to create archetypes with the Ocean Informatics archetype editor\.
>
> I've noticed that since version 0\.99\.5a a new entry subtype is added: 'action'\.
>
> Can I somewhere find a description and/or definition of this subclass? I can't find it in the Archetype...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype editor 0.99.7b](https://discourse.openehr.org/t/archetype-editor-0-99-7b/12109)
> Dear All
Thanks for your comments and bugs with the release candidate alpha Archetype Editor. This is getting close to being robust. There have been some errors with backward compatibility - please upload any archetypes that cause errors so we can check this.
0.99.7 had a major bug with a new function in the parser - cleaning up unused codes. This is removing excessive codes so for the moment a new alpha has been put up (0.99.7b) with this call removed. If you downloaded 0.99.7 then please...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [75] Correct bug that causes application death if logging directory not there.](https://discourse.openehr.org/t/ref-impl-eiffel-75-correct-bug-that-causes-application-death-if-logging-directory-not-there/15851)
> Revision: 75
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [74] Add out routine to TOKEN_STRING](https://discourse.openehr.org/t/ref-impl-eiffel-74-add-out-routine-to-token-string/15850)
> Revision: 74
Author: thomas\.beale
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL/AOM to XSD code](https://discourse.openehr.org/t/adl-aom-to-xsd-code/16705)
> \(sorry for the resend \- not sure my first one went
through\)
Hello all, long time lurker \- first time poster\.\.
I have been playing around with the Java reference
implementation and was wondering if anyone could
clarify some of my thinking\. I'll just write down some
statements which is what I believe to be true and
if any of them are wrong, setting me straight will sort
out my misconceptions \(there is a question
at the end\)\.
\- The XML ITS defines the on\-the\-wire format for...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [73] Correct bug where spaces not treated as white space in TOKEN_STRING](https://discourse.openehr.org/t/ref-impl-eiffel-73-correct-bug-where-spaces-not-treated-as-white-space-in-token-string/12101)
> Revision: 73
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Relationship between the archetypes and the underlying data model](https://discourse.openehr.org/t/relationship-between-the-archetypes-and-the-underlying-data-model/16631)
> Hi,
Im new to openEHR and archetypes and have some question I hope you can help me with.
1. I dont understand the relationship between the archetypes and the underlying data model. If an archetype is changed, will the underlying data model change?
2. If an archetype is changed, how will this affect the data stored based on the old archetype?
3. In what format is data stored? (In a DBMS, as XML file or something else?)
4. Are there any running implementations using archetypes? Are there...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Revival](https://discourse.openehr.org/t/revival/16632)
> Hello,
I'm wondering what is happening to the Java kernel at this moment. This list has been quite dead for the last couple of weeks... Rong, could you give a status report on your job? I haven't seen any updates committed in quite some time. Have you gone away on some business trip?
Hope something happens soon, I would really appreciate if the update of the kernel (especially the AM and ADL outputter) could progress a little faster. There are tons left to do (sorry if I'm being...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [70] Add a flag to event log initialisation to enable graceful failure if event log failed.](https://discourse.openehr.org/t/ref-impl-eiffel-70-add-a-flag-to-event-log-initialisation-to-enable-graceful-failure-if-event-log-failed/12097)
> Revision: 70
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [69] Some small changes to enable reading unicode files - a BOM stripper for UTF-8 files, and UTF-8 character matching in the dADL scanner](https://discourse.openehr.org/t/ref-impl-eiffel-69-some-small-changes-to-enable-reading-unicode-files-a-bom-stripper-for-utf-8-files-and-utf-8-character-matching-in-the-dadl-scanner/12090)
> Revision: 69
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Another moddeling question - changing compositions.](https://discourse.openehr.org/t/another-moddeling-question-changing-compositions/11993)
> I've encountered another situation which I find hard to model based on archetypes and the RM.
we are building software for an ICU, and there is a form which is used to control significant physiological values over time.
Now if we think of one column of the table we will have a set of observations to be recorded at a precise point in time, which could be modelled as a Composition.
The problem with this situation is that the set of observations varies from time to time for the same patient and...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [66] Small correct to allow ISO Duration strings without the 'T' character to be silently fixed during by the cADL scanner;](https://discourse.openehr.org/t/ref-impl-eiffel-66-small-correct-to-allow-iso-duration-strings-without-the-t-character-to-be-silently-fixed-during-by-the-cadl-scanner/12087)
> Revision: 66
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Announcement: forthcoming Release 1.0.1](https://discourse.openehr.org/t/announcement-forthcoming-release-1-0-1/12093)
> Dear all,
this message is to signal a minor Release 1\.0\.1 of the openEHR specifications within the next two weeks or so\. Based on feedback during the last 3 months, this release fixes errors, typos etc in Release 1\.0, and includes changes to make openEHR properly ISO8601:2004 compliant\.
The Release 1\.0\.1 specifications are at http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.html
The CRs that have been executed are visible at:...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [65] Update project page](https://discourse.openehr.org/t/ref-impl-eiffel-65-update-project-page/12352)
> Revision: 65
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [64] Corrected some errors in ARCHETYPE.ontology_remove_unused_codes;](https://discourse.openehr.org/t/ref-impl-eiffel-64-corrected-some-errors-in-archetype-ontology-remove-unused-codes/15849)
> Revision: 64
Author: thomas\.beale
Log Message:
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel [63] Finished & tested various enhancements toward ADL 1.4 compliance:](https://discourse.openehr.org/t/ref-impl-eiffel-63-finished-tested-various-enhancements-toward-adl-1-4-compliance/12086)
> Revision: 63
Author: thomas\.beale
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specification of ITEM_TABLE](https://discourse.openehr.org/t/specification-of-item-table/14543)
> Hello,
I'm trying to add support for ITEM_TABLE in the Java Archetype Editor and I have looked at the only archetype I've found that contains a data structure like this. It is openEHR-EHR-OBSERVATION.tendon_babinski_reflexes.v1.adl and it can be found here [http://oceaninformatics.biz/archetypes/](http://oceaninformatics.biz/archetypes/). When I compared the attributes for the ITEM_TABLE in the data structures specifications (found here...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Subversion check-in information](https://discourse.openehr.org/t/subversion-check-in-information/12094)
> Dear all,
Automatic subversion check\-in notifications are posted to the project lists used by the project teams \- currently ref\_impl\_java, and ref\_impl\_eiffel\. Do members on this main implementers list want to see these posts? They can easily be cc:d\. Doing that would give a better idea of progress on these projects, but on the other hand, will generate more posts\.\.\.\.but then again, it is an implementers list\.\.\.\.
who would prefer this to happen? In the future, I would...
**[Reference Implementation: Eiffel (archive)](https://discourse.openehr.org/c/reference-implementation-eiffel-archive/161)** - [ref_impl_eiffel Initial post](https://discourse.openehr.org/t/ref-impl-eiffel-initial-post/14535)
> I'm afraid I forgot to subscribe myself to this list until just now
\(being the list owner and all;\-\), so I missed the previous posts from
Bert\. Bert \- can you resend them \- sorry about that, but at least the
threading will be more normal if we do that\.
\- thomas
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Lifestyle: substance_use archetype](https://discourse.openehr.org/t/lifestyle-substance-use-archetype/12095)
> Sam,
I believe the broad archetype is better in this instance, at least unless we could come up with a generic archetype that is sufficiently meaningful especially with regard to 'Consumption'
It would then still be possible to specialise the 'other substance' in the broad archetype e.g. for use in a drug treatment centre. Should maybe add a generic 'consumption' and a 'type of substance' concept for 'other substance'.
Sebastian
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Lifestyle: substance_use archetype](https://discourse.openehr.org/t/lifestyle-substance-use-archetype/14538)
> Dear All
I have been working on the archetypes for lifestyle and have approached them with trepidation. I am aware that there are lots of things that a person might like to record, and a lot of preferences. So we need to have a rich model for these things.
The first one I have published is substance use and as designed includes alcohol, tobacco, caffeine and others - it is possible to nominate the others and have as many as you wish.
The substance archetype is on the Ocean...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [ADL versions again](https://discourse.openehr.org/t/adl-versions-again/14534)
> Hi
I am looking at
http://svn.openehr.org/knowledge/archetypes/dev/index.html
I see a lot of archtypes, very interesting\. Very good is that it is possible to open them in colored view, which makes them "very" readable, as far as an archetype can be readable\.
I am reading the docs, and probably it must be clear, but I can't find it\.
So please allow me some more stupid questions, so that I can go on with my work\.
I try to put my questions in such a way that answers can be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[Modelling Medication Administration Control]](https://discourse.openehr.org/t/modelling-medication-administration-control/12092)
> Maybe I sent it to the wrong place originally.
Any ideas?
thank you
[details="(attachments)"]
[Modelling Medication Administration Control|attachment](upload://qLigiCul5LDXLsAFvW166POA4Io) (1.3 KB)
[/details]
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Better UML model](https://discourse.openehr.org/t/better-uml-model/15844)
> Hi,
I'm interested in obtaining a better machine\-readable/processable UML model for OpenEHR\. The published one for MagicDraw 9\.5 is based on UML1\.4 and serialised as the very old and verbose XMI 1\.0
I gather from modelling guide that it is automatically generated from "Eiffel source" using eif2uml? However, I can't find any further information about this to begin working on an updated version \(and I'd rather not write XSLT to map from the current XMI1\.0 to...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[33] added TerminologyUtil to be able to create property attribute of CDvQuantity in the parser](https://discourse.openehr.org/t/33-added-terminologyutil-to-be-able-to-create-property-attribute-of-cdvquantity-in-the-parser/15847)
> Revision: 33
Author: rong\.chen
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [uncomplete Eiffel-code?](https://discourse.openehr.org/t/uncomplete-eiffel-code/15845)
> Hi,
While reading the eiifel code I find in
ref\_impl\_eiffel/libraries/openehr/src/am/archetypes/assertion/expr\_constraint\.e
that in this class is a property "expression" of type ADL\_EXPR\_ITEM
I cannot find the implementation of this class ADL\_EXPR\_ITEM, maybe missing?
thanks
Bert
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype conceptual and technical operational are 2 different things](https://discourse.openehr.org/t/archetype-conceptual-and-technical-operational-are-2-different-things/14537)
> These are archetypes in which the clinicians materials are sorted out, coded etc\.
They currently are made operational for use in a message\. Sam has worked with the Barthel index, which based on this example for R\-MIM, however based on the tables, could be written up in ADL language in less than 15 minutes, where the sorting out of Barthel for clinical and making the variable / coding tables etc took about 8 days of work due to many variants in practice\.
How these can obey to the model...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[32]](https://discourse.openehr.org/t/topic/12336)
> Revision: 32
Author: yinsu\.lim
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[31] Commit project.xml (with joda library added and test cases commented out).](https://discourse.openehr.org/t/31-commit-project-xml-with-joda-library-added-and-test-cases-commented-out/15843)
> Revision: 31
Author: yinsu\.lim
Log Message:
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Java kernel imlpementation and SVN](https://discourse.openehr.org/t/java-kernel-imlpementation-and-svn/14533)
> I believe that the names chosen for branches and tags are totaly confusing. For example the tag Release-0.95 should have be named Release-0.95.0 in order to allow later the existence of a bug-fix tag/release Release-0.95.1. Furthermore the TRUNK should have been already targeted to either 0.95.1 or 1.0.0.
Additionally, the artifacts of the java kernel project (currently openehr-kernel-1.2.5-SNAPSHOT.jar and adl-parser-1.0.2-SNAPSHOT.jar) follow different numbering schemes. I do believe that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [{Fraud?} {Disarmed} Antw: Re: [GPCG_TALK] Archetype Maintenance](https://discourse.openehr.org/t/fraud-disarmed-antw-re-gpcg-talk-archetype-maintenance/14532)
> Williamtfgoossen@cs\.com wrote:
> In een bericht met de datum 8\-1\-2006 21:31:57 West\-Europa \(standaardtijd\), schrijft gfrer@luna\.nl:
>
>> Information is exchanged in communities\.All clinical information belongs to the healthcare domain\.
>>
>> When clinical concept models \(Archetypes\) are expressed using an Open International Standard like the CEN/tc251 Archetypes,
>> both the Archetype expression and the constituting clinical concept models are not owned in a commercial...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Java release-1.0](https://discourse.openehr.org/t/java-release-1-0/12085)
> I found following message on SVN, cannot be Western\-Europe\-time\.
But that is not important, what I wonder about is the message that
"All the classes should compile now"
I wonder what I am doing wrong, I miss f\.e\. org\.openehr\.rm\.common\.archetyped\.Archetyped
But I miss many more, TerminologyServer, DvDate, and more\.
How an I get SVN \(I use the latest version\) so far, it will get me all the files\.
I have the same problem on my Linux machine, where it did not get me the...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[29] Java implementation Release 1.0 first commit.](https://discourse.openehr.org/t/29-java-implementation-release-1-0-first-commit/12083)
> Revision: 29
Author: yinsu\.lim
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [please move implementer discussions to implementer group!](https://discourse.openehr.org/t/please-move-implementer-discussions-to-implementer-group/12080)
> Dear all,
we don't have many groups, but I think the community will appreciate us respecting the ones that are there\. To that end, I would like to move the very useful \(but implementation oriented discssions on Eiffel, Java, ISO 8601\) to the implementers list\.
thanks,
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CR java kernel implementation: DvEncapsulated](https://discourse.openehr.org/t/cr-java-kernel-implementation-dvencapsulated/12091)
> The DvEncapsulated class and its subclasses accept at their full constructor the size as an argument.
I believe that the size should be a calculated attribute and not a constructor argument. In my opinion, it is the responsibility of DvParsable and DvMultimedia to calculate the size of their content.
By the way, the xml schema defintion of DV_ENCAPSULATED, correctly does not declare the size attribute, because it should be calculated.
My suggestion is that:
1) Remove the size attribute from...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CR for the XML Schema definition and Java implementation of DvDuration](https://discourse.openehr.org/t/cr-for-the-xml-schema-definition-and-java-implementation-of-dvduration/14531)
> Although the latest spec defines that the DvDuration
has attributes such as days, hours etc the class lacks
the attribute years\.
On the other hand, the draft XML Schema definition of
DvDuration \(element DV\_DURATION of BaseTypes\.xsd\),
defines the value of DvDuration as "xsd:duration",
which supports the notion of years\.
In my opinion, this inconsistency may result to
ambiguous mapping of DV\_DURATION element to DvDuration
class, and I propose to either restrict the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ace or project files](https://discourse.openehr.org/t/ace-or-project-files/14530)
> Hi,
I have some problems with the Eiffel\-sources\.
I made my way to understanding and even loving the Eiffel compiler, and now I want to use its power for better understanding of the openehr kernel\.
I start puzzling what belongs to what and, oh, I discover classes with duplicate names\.
I found now duplicate
APPLICATION, both in file application\.e \(on different locations\)
and
VERSIONED\_FOLDER
one in
ref\_impl\_eiffel\\libraries\\openehr\\src\\rm\\ehr\\ehr\_directory\.e
and one...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes](https://discourse.openehr.org/t/archetypes/14528)
> Hi,
I was looking for archetypes, and I found this link:
[http://oceaninformatics.biz/archetypes/](http://oceaninformatics.biz/archetypes/)
on the openehr website
I found descriptions, but no archetypes:
# Not Found
The requested URL /ADL/evaluation/openEHR-EHR-EVALUATION.directive-medication.v1.adl was not found on this server.
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[28] added equals() to DvParagraph](https://discourse.openehr.org/t/28-added-equals-to-dvparagraph/12323)
> Revision: 28
Author: rong\.chen
Log Message:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Java Kernel Implementation CR: Implement equals on DvParagraph](https://discourse.openehr.org/t/java-kernel-implementation-cr-implement-equals-on-dvparagraph/15840)
> The current implementation of DvParagraph \(rev\. 27\)
does not implement "equals\(Object\): boolean" method\.
Because all DataValue's are implemented as immutable
transfer object, the absence of the method causes
problems with frameworks that manipulate beans \(for
instance Hibernate, JAXB etc\)\.
A sample implementation could be:
public boolean equals\(Object object\) \{
if \(this == object\) \{
return true;
\}
if...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [implementation examples](https://discourse.openehr.org/t/implementation-examples/16629)
> Hello,
I've been trying to understand and work with openEHR for some time now but apart from the theory, I could not find any definite information about how all of this is implemented. I was wondering if there are any existing tools regarding the persistent storage of archetypes as well as archetype querying. Basically, any sort of tools in general or any source of information to guide someone wishing to implement an openEHR system.
Any help would be greatly appreciated!
Thanks in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New alpha of release 1.0 archetype editor](https://discourse.openehr.org/t/new-alpha-of-release-1-0-archetype-editor/14529)
> Hi Everyone
I have posted a new exe of the release 1.0 archetype editor on the Ocean site with sample archetypes.....a little more to do but it is getting very close. I would appreciate testing and comments back via the reporting menu item on the editor.
Cheers, Sam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [removal of data](https://discourse.openehr.org/t/removal-of-data/14536)
> Let me enlighten my question
Bert Verhees schreef:
> Thanks again for the help with the authorization\-question, I was lost in the wrong document of the specs\.
> I must say, reading the specs, really is not something for a rainy afternoon, but it is worth it\.
>
> I have another question, probably it also is in the specs, but I didn't find it\.
> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
> Is it possible to delete a composition in a way that is not traceable anymore?
What happens on...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Resolution](https://discourse.openehr.org/t/resolution/14539)
> A few months ago, I posted a proposed resolution and
asked for comments, and many of you kindly reponded\.
When this came up for debate on the floor of the
Pennsylvania Medical Society House of Delegates, here
was an unsuccessful movement to remove all the
references to open source, but it was adopted without
amendment, but only for referral for decision by the
Board of Trustees\. It was not adopted by the House of
Delegates \(except for referral\), primarily because
most of the Delegates...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Authorisation](https://discourse.openehr.org/t/authorisation/14174)
> Hi,
Have there ever been some thoughts on authorisation, and how to implement this\.
Maybe I missed the subject in this list, or on the website\.
I need some advise about how to implement authorisation for reading/writing openehr data\.
I realize that there are many ways to do this, but what is the best advise?
Thanks in advance for any hint/answer
Bert Verhees
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg#6 - Archetypes for mathematicians?](https://discourse.openehr.org/t/msg-6-archetypes-for-mathematicians/14161)
> > Forgive the cross\-post, but the topic of archetypes has come up
> Hardhats, and once again, I find the language used to describe the
> concept vague and \(at times\) mysterious\. If you'll forgive me for the
> use of some mathematical jargon here, I'd like to revisit the concept
> of abstracting measurements away from a particular choice of units\. A
> familiar mathematical structure used to discuss the concept of distance
> is the metric space, defined as follows:
>
> A metric...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg#5 - Software Archetypes - single vs double systems](https://discourse.openehr.org/t/msg-5-software-archetypes-single-vs-double-systems/15841)
> systems
> Hi Greg,
>
> Greg Woodhouse wrote:
>
> > What I find most frustrating about discussion of
> > archetypes is that it is so often vague and intuitive
> > in nature, making it rather hard to decipher\.
>
> I didn't know what level of detail was desired\. Also, I'm not an expert
on
> archetypes and, as you'll see below, have no intention of putting myself
> forward as such\. Just thought I'd provide what information I could\. I
> didn't mean to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg#4 - Software Archetypes - single vs double systems](https://discourse.openehr.org/t/msg-4-software-archetypes-single-vs-double-systems/14133)
> systems
> What I find most frustrating about discussion of archetypes is that it
> is so often vague and intuitive in nature, making it rather hard to
> decipher\.
>
> > Software Archetypes \- single vs double systemsHi Lorie,
> >
> > Archetypes provide a capability that's very familiar to programmers,
> > but take it to the next level\. At the most basic level, it's about
> > decoupling\. An RDBMS shields programs from the need to know about
> > the underlying...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg#3 - Software Archetypes - single vs double systems](https://discourse.openehr.org/t/msg-3-software-archetypes-single-vs-double-systems/15839)
> Hi Lorie,
Archetypes provide a capability that's very familiar to programmers, but take it to the next level. At the most basic level, it's about decoupling. An RDBMS shields programs from the need to know about the underlying structure of the data. A program needs only know about the db schema. Views provide another level of abstraction, shielding programs from changes in the schema. Archetypes (which I believe do not depend on an RDBMS implementation) provide a similar capability, but take...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg#2 - Software Archetypes - single vs double systems](https://discourse.openehr.org/t/msg-2-software-archetypes-single-vs-double-systems/15838)
> I'm really mot familiar with this approach (frankly, I find the presentation hard to follow, though the longer paper [http://www.deepthought.com.au/it/archetypes/archetypes.pdf](http://www.deepthought.com.au/it/archetypes/archetypes.pdf), is easier to follow), but the problem is certainly a familiar one. A significant problem with VistA (and just about any other EHR) is that domain specific knowledge is embedded into code or intermixed with operational data all over the place.VistA has...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Msg #1 - Software Archetypes - single vs double systems](https://discourse.openehr.org/t/msg-1-software-archetypes-single-vs-double-systems/12074)
> Greetings,
The posting below showed up on the hardhats list this morning. I responded (after a brief, confirmatory exchange with Thomas) with a brief, high-level explanation of what archetypes "bring to the party". That triggered a couple of additional exchanges with another poster (the original poster has yet to respond). As you'll see, the additional exchanges led to a committment on my part to ask the experts (that's you folks). I'll be forwarding those postings here in hopes you can /...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [automatic Subversion commit emails](https://discourse.openehr.org/t/automatic-subversion-commit-emails/12077)
> I have put in place a post\-commit script to automatically email
something sensible to this list next time a commit is done\. I think this
should come through\. I did a couple of dummy commits \(well, real
commits, just changed the Readme file in a trivial way\)\. This means that
\(hopefully\) we don't have to write messages to the list to alert everyone\.
Now, if everyone will write good quality check\-in messages \(as Rong has
done\), then we should all know what has happened, with no...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [[27] 2nd test on post-commit hook](https://discourse.openehr.org/t/27-2nd-test-on-post-commit-hook/12073)
> Revision: 27
Author: thomas\.beale
Log Message:
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [another update on the parser](https://discourse.openehr.org/t/another-update-on-the-parser/14522)
> Hi all,
I just made a new commit on the TRUNK of ref\_impl\_java\.
Changes:
1\. Better support of C\_QUANTITY in the parser \(also resulting a new
CDvQuantity in the new openehrprofile package in AOM\)
2\. Corrected ADL path grammar in the parser
3\. Adjusted the archetype description again
4\. Big fix in the ArchetypeID \(initially reported by LiU group\)
5\. Added a batch parsing method into command\-line interface of the parser
6\. Rearranged the unit test code a bit
All these...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [doing date and time in Java](https://discourse.openehr.org/t/doing-date-and-time-in-java/15731)
> Dear all,
It seems I am not the only person who thinks date and tme handling is
bad in Java\.\.\.\.see the Joda effort at
http://joda-time.sourceforge.net/index.html
I think we should use these libraries \- they claim to get rid of many of
the bugs etc of Java calndar classes; also they are directly ISO8601
based \- excatly what we want in openEHR\.
Rong and others \- do you have any objection to using this library in the
Release 1 upgrade? I think it will reduce the coding time, and...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [assumed values](https://discourse.openehr.org/t/assumed-values/15834)
> Hi all,
Support for assumed values has been implemented in the AOM and the ADL
parser\.
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Proposal for the adoprion of Maven2 in Java kernel reference implementation](https://discourse.openehr.org/t/proposal-for-the-adoprion-of-maven2-in-java-kernel-reference-implementation/15837)
> Since many developers are using Maven2 instead of
Maven1, I would to propose the adoption of Maven2 as
the build tool of the reference kernel implementation
in java\.
I am attaching two basic Maven2 project descriptors
for the kernel and the adl\_parser, that can replace
the relevant Maven1 project descriptors and property
files\.
The file "pom\-for\-libraries\.xml" has to be copied into
"libraries" directory and renamed to "pom\.xml"\.
The file...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [parser updated](https://discourse.openehr.org/t/parser-updated/15835)
> Hi all,
The updates on the parser has just been checked into the trunk\.
Some summary:
1\. The parser now supports latest syntax for archetype description and
ontology \(Yes\! the issue with \[\] should be gone in these two parts\)\. So
basically the archetypes from openEHR knowledge repository should be
supported out\-of\-box except two things: \(1\) c\_quantity \(2\)
assumed\_values, these two will be fixed in the next round\.
2\. All the test archetypes and test cases are also updated \-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Please remove from mailing list..................](https://discourse.openehr.org/t/please-remove-from-mailing-list/15833)
> Louis B\. Silk, M\.D\.
Research Analyst
Devon Health Services, Inc\.
610\.757\.4104
lsilk@devonhealth\.com
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about Composition archetypes](https://discourse.openehr.org/t/question-about-composition-archetypes/15836)
> Hello,
I've just compared some Composition archetypes from Ocean Informatics with the specifications at openEHR\.org and I have some questions\. The specifications from 0\.9 to 1\.0 all agree about one thing for COMPOSITION classes and that is that the attribute "context" in the COMPOSITION class should point to a class called EVENT\_CONTEXT\.
However, this is not the case for the archetypes I've seen so far\. Instead, the "context" attribute in the archetypes...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [workplan and branching strategy](https://discourse.openehr.org/t/workplan-and-branching-strategy/14514)
> Dear all,
In short term \(4\-6 weeks?\), we need to upgrade both the parser and
kernel to Release 1\.0 in the current coding style\. The work can be
divided into two parts: 1\. parser \+ AOM update; 2\. RM update\. It is
possible for two teams take one task each and don't have too much
dependency on each other\. It seems to be good for these two teams
working on separate branches\.
So here is my proposal:
1\. The release\-0\.95 branch will receive no further development except
bug...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Wish list updated and current status of the Java Archetype Editor](https://discourse.openehr.org/t/wish-list-updated-and-current-status-of-the-java-archetype-editor/14520)
> Hi all,
Status:
Currently our editor supports Composition and Section archetypes to the extent that the kernel allows.
It also supports event series in Observation archetypes and some bugs have been fixed.
The most severe issues are:
1. Kernel and parser don't support archetype slots fully which means the included or excluded archetypes aren't parsed, stored nor outputted.
2. The new archetype format with [] isn't supported by the kernel and parser.
3. Instruction and Action archetypes...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Strategy from here for RM](https://discourse.openehr.org/t/strategy-from-here-for-rm/14519)
> Rong and others,
my feeling for the way we should be going here is as follows. In the medium term (say by mid-year), we should aim to have:
- RM & AM upgraded to Release 1.0
- all test cases up to date and working
- contracts in all the code. (See below)
- potentially some changes to the general design of the core classes
In the short term, what we need is to have the classes upgraded in the current programming style to Release 1.0, with the test cases upgraded as well. We can do this at...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Some help with Subversion branching and tagging](https://discourse.openehr.org/t/some-help-with-subversion-branching-and-tagging/12078)
> See http://www.openehr.org/developer/t_svn_um_top.htm ; follow the
Project Leader link\.
\- t
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Bug in Java Kernel class ArhcetypeOntology](https://discourse.openehr.org/t/bug-in-java-kernel-class-arhcetypeontology/14525)
> The class ArchetypeOntology, does not stores in the
internal Map \- definitionsMap, the term defintion
items, but only constraint definition items\.
The bug is in line 73 where the
codeMap = new HashMap<String, DefinitionItem>\(\);
should be replaced by
codeMap = map\.get\(defs\.getLanguage\(\)\);
if \(null == codeMap\) \{
codeMap = new HashMap<String, DefinitionItem>\(\);
\}
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Persistence design notes](https://discourse.openehr.org/t/persistence-design-notes/14523)
> I have uploaded a set of persistence design notes at http://www.openehr.org/FAQs/t_persistence_notes.htm
Comments & contributions welcome\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Release 1.1 candidate area](https://discourse.openehr.org/t/release-1-1-candidate-area/12075)
> The openEHR release 1\.1 candidate area is now available online \- see the Release\-1\.1\-candidate link on the specification project page at http://svn.openehr.org/specification/TRUNK/project_page.htm
This release will contain 3 kinds of changes
\- improvements to the explanatory text and typographical fixes
\- a small number of CRs to improve mainly the Quantity types for more recently discovered requirements
\- the redeveloped EHR Extract
The roadmap page indicates what has been updated...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [online UML for openEHR now available](https://discourse.openehr.org/t/online-uml-for-openehr-now-available/12299)
> Please see last hotlink on the right\-hand side of home page http://www.openEHR.org
David Lloyd at CHIME, UCL in London was responsible for the enormous task of entering the model and customising the publishing scripts so that we could have this site, and I am sure it will be highly appreciated by the whole community\.
\- thomas beale
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [Running this project group](https://discourse.openehr.org/t/running-this-project-group/14517)
> Dear all,
here is what I would like to see happen:
- we elect a project leader - by default Rong. Doesn't matter if the leader can't take much time for coding, the point is to organise / synchronise work done by the team as a whole. Rong, if you don't accept, we will have to have a proper election! Responsibilities of the leader include doing / facilitating:
- helping to plan and synchronise work done by the team- deciding on when to do a branch- deciding on acceptance criteria for changes...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [ADL / archetype wish list](https://discourse.openehr.org/t/adl-archetype-wish-list/14515)
> Just to record a few previous emails in the list....
Hi all!
Our priority wish-list is as follows:
1. Fix the parser so it can parse the archetypes at openEHR homepage
1. Embedded dADL support in the parser (primarily to be able to _parse_ archetypes containing embedded dADL without parse errors. Object instansiation can wait)
1. Support for instruction and its related parts in the AOM
1. Support for action and its related parts in the AOM
It would be nice if the above things can be...
**[Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154)** - [getting started on this list](https://discourse.openehr.org/t/getting-started-on-this-list/14524)
> Dear all,
I think most of us are now on this list\.\.\.\.can we just have some
responses to this so I am sure who is here?
\- thomas
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [New CRs for minor release to openEHR specifications](https://discourse.openehr.org/t/new-crs-for-minor-release-to-openehr-specifications/12076)
> Dear all,
a small number of CRs are being proposed to improve a couple of details in the openEHR Reference Model\. As promised in the Release Notes for Release\-1\.0, we want to be sure that the implementation community does not object\. Three of the changes are visible here:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Version and commit](https://discourse.openehr.org/t/version-and-commit/12068)
> Dear All
Heath and I have been discussing issues about commiting and attesting data. We want to be able to attest something that is immutable - the data of the composition and the commit details. There are two types of versioned data (page 41 of the Common IM) - the Version and the imported version.
The parts that need to be immutable are:
- UID
- preceding_version_id
- lifecycle_state
- create_audit - (presently a function which calls the commit_audit if not imported and the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [persistence layer](https://discourse.openehr.org/t/persistence-layer/14526)
> Are there plans to work out concepts for an persistence layer
Thanks in advance for an answer
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [openEHR Java kernel - Release 1.0 update](https://discourse.openehr.org/t/openehr-java-kernel-release-1-0-update/12063)
> I saw a message that seemed to have bounced due to being a non\-member post; it asked the question about the future of the Java kernel\.
At UCL we are currently working on upgrading the kernel classes to Release 1\.0 of openEHR\. We expect to set up the development team more formally and give it its own mailing list as well\. My guess is that the reference model and archetype model classes will be upgraded to Release 1\.0 in less than 6 weeks \(other work is going on in parallel\)\.
\-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology numeric values not supported in DV_Quantity](https://discourse.openehr.org/t/pathology-numeric-values-not-supported-in-dv-quantity/14516)
> Hi everyone,
We want to report an issue that has arisen in data processing in Australia.
The issue is the somewhat random ability of systems to report a >xx or The openEHR architecture overview document has been significantly updated; see the second hot link on the home page \(http://www.openEHR.org\)\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [password question on website](https://discourse.openehr.org/t/password-question-on-website/12060)
> Received: from smtp\-vbr10\.xs4all\.nl \(smtp\-vbr10\.xs4all\.nl \[194\.109\.24\.30\]\)
by chime\.ucl\.ac\.uk \(8\.13\.4/8\.13\.4\) with ESMTP id k1GMOkOS020511
for <openehr\-technical@openehr\.org>; Thu, 16 Feb 2006 22:24:47 GMT
Received: from \[127\.0\.0\.1\] \(213\-84\-254\-61\.adsl\.xs4all\.nl \[213\.84\.254\.61\]\)
\(authenticated bits=0\)
by smtp\-vbr10\.xs4all\.nl \(8\.13\.3/8\.13\.3\) with ESMTP id k1GMOaqb011269
for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New member on the Architecture Review Board](https://discourse.openehr.org/t/new-member-on-the-architecture-review-board/12066)
> The openEHR Foundation board has appointed a new member, Eric Browne, to the Architectural Review Board \(ARB\)\. Eric has long\-standing expertise in software engineering and health informatics, including a recent PhD in workflow modelling\. See http://www.openehr.org/about_openehr/t_arb.htm for details\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [fm file-extension](https://discourse.openehr.org/t/fm-file-extension/12284)
> I guess it is framemaker
Do I need these files, SVN downloaded many of them, or is the information already elsewhere in other files \(and up to date\)?
regards
Bert Verhees
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Terminology](https://discourse.openehr.org/t/openehr-terminology/15830)
> Dear All
We have placed the openEHR terminology on the web as an XML file (with attendant schema). These can be found at:
[http://svn.openehr.org/specification/TRUNK/publishing/architecture/computable/terminology/terminology.html](http://svn.openehr.org/specification/TRUNK/publishing/architecture/computable/terminology/terminology.html)
This file contains the languages, the terminologies and many other domain vocabularies required to use openEHR. It is based, where possible, on other...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [XML Schema candidate](https://discourse.openehr.org/t/xml-schema-candidate/15832)
> Dear All
I have placed the Release 1.0 XML schemas on the web for comment. The documentation is at:
[http://svn.openehr.org/specification/TRUNK/publishing/its/XML-schema/index.html](http://svn.openehr.org/specification/TRUNK/publishing/its/XML-schema/index.html)
You will see that the schema is presented as 4 separate files - this enables the query engine to validate whether returning full compositions, sections, entries, structures or even data types. The schema files are also linked to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Suggestion about the Multi-axial Archetype Indentifier](https://discourse.openehr.org/t/suggestion-about-the-multi-axial-archetype-indentifier/15729)
> Hello everybody,
We'd like to make a suggestion related to the Archetype Identifier syntax.
At 'The openEHR Archetype System' document we can find the definition for a multi-axial archetype identifier. One of its parts is the model_name label. We think that it should be necessary to add there the model version we are using as basis for defining the archetype. This would be the only way to check if the archetype definition structure is valid.
For example, we can create an archetype based on...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Correct Subversion location for Release 1.0](https://discourse.openehr.org/t/correct-subversion-location-for-release-1-0/12065)
> It has come to my attention that some people are probably still pulling a copy of the specification project documentation from the BRANCHES directory, where the Release 1\.0 candidate document set was being developed\. You need to change this to pull from one of the URLs described on the project page \- http://svn.openehr.org/specification/TRUNK/project_page.htm
This may mean removing your current local subversion directory for this project, or it may mean you are already updating a copy of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR Release 1.0](https://discourse.openehr.org/t/openehr-release-1-0/14521)
> Dear all,
we published openEHR Release 1\.0 last night \(GMT\) \- see the home page http://www.openEHR.org. Some of you will notice that we have not yet put a subversion tag in to mark the release\. My intention is to wait a week or two during which I hope the community will spot any broken links, major document publishing problems and so on, and we can fix those before declaring the tag\. We are also expecting to put up the XML\-schemas on the weekend\.
For subversion users, the release is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEhr comparison to GEHR](https://discourse.openehr.org/t/openehr-comparison-to-gehr/12061)
> Hi,
Is it possible to find information about the pro's and contra's of OpenEhr
compared to GEHR \(HealthOne\)?
HealthOne has the advantage that it already is build on a proven concept, and
has binaries which are thoroughly tested on the market\.
But it is not OpenSource, which is a disadvantage\.
Besides that, more important is how OpenEhr differs as a result now or in
future\.
Let me explain what I have seen from Healthone\.
It has an archetype\-kind of layer\. it will be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [dictionary](https://discourse.openehr.org/t/dictionary/14507)
> Hi,
I have a question, maybe a stupid question, don't hesitate to tell me \(I can handle that\), as long as you give the answer with it\.
Today I had the opportunity to have a good look at HealthOne, a GEHR system, many on this list will know it\.
One thing looked smart to me\.
They have a kind of Dictionary with 6000 words, \(also these words are possibly related to each other, that makes it an extra strong feature\)\. The relationship between the words is not hard coded and is not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [experience / opinions](https://discourse.openehr.org/t/experience-opinions/16704)
> Does anyone have any experience with / opinions about the suitability of Ruby and Rails as implementation platforms for openEHR?
Thanks,
Bill
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [specification repository](https://discourse.openehr.org/t/specification-repository/12064)
> Dear all,
we have rebuilt the specification subversion repository after the corruption which occurred recently, however, it is not compatible with the previous incarnation \- we had to remove revision 51 from the repository and recommit the content, but of course the commits were not exactly the same as the first time round\.
Practically this means that anyone who is tracking this repository will have to destroy their copy and do a new check\-out from scratch\. For people just tracking the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [minor delay to Release 1.0 publication](https://discourse.openehr.org/t/minor-delay-to-release-1-0-publication/15827)
> To all those waiting on Release 1\.0 of the openEHR specifications\.\.\.\.
the specification work is nearly ready for publication\. However, we have suffered a subversion problem in the specification project repository \- some of you who copy this repository will have noticed problems in doing checkouts and updates\. Our research indicates that this is a known problem, but so far we have not seen any clear advice on how to fix it\. Realistically this is likely to cause some delay, as we are...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [FreeTerminology.org is UP!](https://discourse.openehr.org/t/freeterminology-org-is-up/15825)
> Here is the post I had sent to openhealth forum\.\.\. Will need your support
Best regards,
Dr\. Koray Atalag
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [BOUNCE openehr-technical@openehr.org: Non-member submission from [Melvin Reynolds ]](https://discourse.openehr.org/t/bounce-openehr-technical-openehr-org-non-member-submission-from-melvin-reynolds-melvinr-ams-consulting-co-uk/15824)
> Hi,
I am temporarily keeping a technical watch on the openehr lists\. Your message to the list has been rejected as you are not subscribed to the list\.
Your email claims to come from melvinr@ams\-consulting\.co\.uk, but this email address is not subscribed to the list\. Have you subscribed using another email address, if you have you must use that address to send messages to the list or unsubscribe the old address and resubscribe using this address\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: EHR conference The Hague NL, 6/7 Feb 2006](https://discourse.openehr.org/t/annc-ehr-conference-the-hague-nl-6-7-feb-2006/15823)
> Hello,
can you please send me the status of this conference.
Best regards, Smiljana
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Proposed slightly radical change to CODE_PHRASE in Text package in openEHR](https://discourse.openehr.org/t/proposed-slightly-radical-change-to-code-phrase-in-text-package-in-openehr/14510)
> Dear all,
we just came across a "feature" of the current openEHR Reference Model which, in the light of current implementations \(particularly XML\), it seems would be good to alter slightly\. The change has no semantic effect, only affecting how data are persisted\. We are too close to the Release 1\.0 release date to be making such changes for my liking at least, but on the other hand I suspect that this change would be of universal benefit\.
The class concerned from the current...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Screenshots of newly developed Java Archetype Editor](https://discourse.openehr.org/t/screenshots-of-newly-developed-java-archetype-editor/14509)
> Dear All,
As some of you might know, we are a couple of master's thesis students at Linköping University in Sweden that will be finished with our work of developing an archetype editor in the near future\. The application is developed entirely in java and the source code is to be published as open source when our work with it is done\. The URL below shows a couple of screenshots of the java archetype editor based on the Acode implementation of the openEHR reference...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[GPCG_TALK] Archetype Maintenance](https://discourse.openehr.org/t/gpcg-talk-archetype-maintenance/14508)
> Tim Churches wrote:
>
>> There is another issue buried here \- and that is what happens when a
>> supplier of a
>> commercial EHR goes 'belly up' etc and stops serving the requisite
>> information for a
>> stored archetype to be interpreted from\.
> Yes, and copies of the archetypes managed by this "reference source"
> need to be automatically replicated or mirrored to dozens of other
> sites run by independent entities, so that the world doesn't end if
> the host of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ontology, information models, archetypes - a perspective](https://discourse.openehr.org/t/ontology-information-models-archetypes-a-perspective/12283)
> Hi,
I have not been receiving messages from any of the
openehr lists since 2 months\! Could you please check
this?
thanks\.\.\.
\-koray
> Thomas,
>
> Thanks\.
>
> What you are saying is:
> \- we have the real and other worlds with objects and
> our present
> understanding of it,
> \- and we have the world where we document what has
> happened or will
> happen\.
>
> Gerard
>
> \-\- <private> \-\-
> Gerard Freriks, arts
> Huigsloterdijk 378
> 2158 LR Buitenkaag
> The Netherlands
>
>...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Missing references in documentation](https://discourse.openehr.org/t/missing-references-in-documentation/15828)
> Hello,
I cannot find the references specified in section 2.1 of this document, can anyone help me find these please?
Purpose of Archetypes and Templates Archetype Definitions and Principles
Rev 0.6 [http://svn.openehr.org/specification/BRANCHES/Release-1.0-candidate/publishing/architecture/am/archetype_principles.pdf](http://svn.openehr.org/specification/BRANCHES/Release-1.0-candidate/publishing/architecture/am/archetype_principles.pdf)
Content:
"2 Purpose of Archetypes and Templates
2.1...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [REMOVE ME FROM THIS LIST PLEASE!](https://discourse.openehr.org/t/remove-me-from-this-list-please/15826)
> Send a mail to majordomo@openehr\.org
In the message body write ubsubscribe <listname> \(in this case openehr\-technical@openehr\.org\)
As stated before on another openehr list : it would be usefull to add this to mail footer or website \(at least I couldn't find it there\)\.
Mvgr,
Martin
crylla81@tiscali\.it wrote:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Patches for openEHR java kernel 1.2.4](https://discourse.openehr.org/t/patches-for-openehr-java-kernel-1-2-4/12070)
> Dear All,
These four patches adds the following functionality to the ADLOutputter in the openEHR java kernel 1\.2\.4\.
\- Outputs query bindings and term bindings\.
\- Added getter in superclass OntologyBindingItem
\- Added getter in QueryBindingItem
\- Outputs the list of available terminologies
\- Changed the validation test for ADLOutputter so it will validate available terminologies\.
\- ADLOutputter can save a file now, by flushing and closing the stream\.
You can get the patches at...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about Ocean's Archetype Editor](https://discourse.openehr.org/t/question-about-oceans-archetype-editor/14512)
> Hello,
I'm trying to figure out which reference model Ocean's achetype editor follows. I have an example regarding the data type Quantity, see below. There seems to be great differences depending on what reference model the archetypes follow.
Background:
I'm trying to figure out how to get the property of a quantity but this doesn't seem to be supported by the java kernel I'm using, so I'm asking if anyone has a good idea on how to support this in other ways.
The current problem is that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Parser and kernel patch for TermBindingItem](https://discourse.openehr.org/t/parser-and-kernel-patch-for-termbindingitem/12069)
> Dear All,
I discovered that the openEHR java parser 1\.0\.1 didn't store the local term code correctly in an TermBindingItem \(it stored the external term code \(term\_code\(\)\) in the local code's place\)\. The attached patch corrects this problem\.
I think that a TermBindingItem should have getters, so I attached a patch for this to\.
Any comments?
Best regards,
Johan...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Keeping up to date with openEHR specification documents](https://discourse.openehr.org/t/keeping-up-to-date-with-openehr-specification-documents/12059)
> It is easy to keep up to date with the openEHR specifications\. The steps are described at http://svn.openehr.org/specification/TRUNK/project_page.htm under the "How To" heading\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Remove from the email list please...](https://discourse.openehr.org/t/remove-from-the-email-list-please/12067)
> Please me too\!
Thx\.
Andrej O
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SVN specification repository - update your copy to fix instruction.pdf filename](https://discourse.openehr.org/t/svn-specification-repository-update-your-copy-to-fix-instruction-pdf-filename/12252)
> There is an error in the file name for the Instruction proposal PDF; for the moment, please manually adjust the URL you use to be \_instruction\.pdf\. The URL will be corrected in a few days, but we have to do a tedious 2\-part rename process in Subversion to get rid of the problem\.
\[\-\-\-\- THIS PART only for people who routinely maintain a local copy of the openehr specification repository; OTHERWISE IGNORE\-\-\-\-\]
You should do an SVN update operation on your local specification...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: openEHR Release 1.0 candidate uploaded](https://discourse.openehr.org/t/annc-openehr-release-1-0-candidate-uploaded/14511)
> Dear all,
we have uploaded an initial cut of the emerging Release 1\.0 of the openEHR specifications\.
The index page for viewing documentary forms of the specifications and schemas is at http://svn.openehr.org/specification/BRANCHES/Release-1.0-candidate/publishing/index.html.
Subversion links can be seen from the project \(http://svn.openehr.org/specification/TRUNK/project_page.htm).
Please note that some of the content in the release 1\.0 candidate has not yet been approved by the ARB;...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR XML-schema Questions](https://discourse.openehr.org/t/openehr-xml-schema-questions/14506)
> Dear all,
Sam Heard at Ocean Informatics has built a schema for openEHR, to be published open source on openEHR.org as soon as possible. There remain some open questions about how best to componentise XML-schemas.. The current structure is as three schemas which correspond to 3 pragmatic groupings of classes in the openEHR reference model. The 3 schemas are available (in HTML viewable form) at:
-...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Templates - should we record which are used?](https://discourse.openehr.org/t/templates-should-we-record-which-are-used/14513)
> Dear All,
We have been discussing the issue of templates and whether we keep an identifier of a template in the data. My concern has been that this ID might be seen as an absolute constraint on the data, whereas the precedence of constraint must be:
1. The data must conform to the reference model
1. The data must conform to the archetypes
1. The data must be complete
1. The template can be invoked to ease data entry.
What this means is that when data is already present, even if it does not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question regarding CAttribute](https://discourse.openehr.org/t/question-regarding-cattribute/15662)
> Hi everyone,
There seems to be a lot of RM attribute names, like "pathway\_specification", "protocol", "items", "content" etc\. in archetypes\.
Is there any documentation of those RM attribute names?
Mattias Forss
Johan Hjalmarsson
IMT, LIU
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [parsing error](https://discourse.openehr.org/t/parsing-error/15661)
> Hi
Comments in line\.
Rong Chen wrote:
> Rahil wrote:
>
>> Hi
>>
>> I am trying to parse an ADL file using the ADLParser API\. However, the ADLParser is throwing up an error in the ADL file that Im passing it\. The block of code where the error occurs is :
>>
>> \-\-\-\-\-\-\-\-\-\-\-\-
>> ELEMENT\[at0008\] occurrences matches \{0\.\.1\} matches \{ \-\- Person
>>...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Questions about archetype definition](https://discourse.openehr.org/t/questions-about-archetype-definition/15822)
> Hello,
I have some questions about the archetype definition. Currently, I am using the java parser to get an archetype object and from that object I get the archetype definition, which is a CComplexObject. I then pass this object to a recursive function of mine to get hold of some node id's, reference model type names, reference model attribute names and so on. In the function I first get the attributes of the complex object, then I get the children of each attribute and finally I also get...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: openEHR integration model; HL7v2 & CEN EN13606 interoperability](https://discourse.openehr.org/t/annc-openehr-integration-model-hl7v2-cen-en13606-interoperability/15820)
> Dear all,
A new addition has been made to the openEHR reference model\. It currently has the status of a proposal\. It adds a single class whose purpose is to facilitate integration of CEN EN13606 Extracts, HL7v2 messages, and other legacy data sources\. The document can be found under the 'proposals' heading at http://svn.openehr.org/specification/TRUNK/publishing/index.html.
A second document on methodology will be published in the near future showing in more detail how externally...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [proposed re-arranging of structure of java projects](https://discourse.openehr.org/t/proposed-re-arranging-of-structure-of-java-projects/15819)
> Dear all,
I mentioned a few weeks ago that we would change the structure of the two java projects slightly\. All we want to do is to move the java ADL parser from the knowledge\_tools\_java project to the ref\_kernel\_java project\. Rong has already asked for this change\. The reason for doing is is that the ADL parser is more correctly part of the reference java implementation of openEHR \(for historical reasons, this is known as ref\_kernel\_java rather than ref\_impl\_java\); the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [I need an advice](https://discourse.openehr.org/t/i-need-an-advice/15641)
> Dear Sirs
I am new in the filed of EHR.
I am head of the medical information department of the large clinic in Ukraine. (www.cerebralpalsyukraine.com)
We are treating patients with cerebral palsy and children from many countries of the worlds are coming to us.
In our work we are using the hospital information system with the electronic medical records, developed for us by local software company. This software is rather powerful but it is not possible to share our information with other...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Compiling the java ADL_parser (patches included) (cross-post)](https://discourse.openehr.org/t/compiling-the-java-adl-parser-patches-included-cross-post/12052)
> Re\-posting messages that I sent to the openehr\-implementers list
a week ago \(no response\)\. Maybe they fit better on this list\.
\- \- \-
Hello again\!
One of the first things we tried \(in the projects mentioned in a previous
mail\) was to compile the java ADL\_parser using version 1\.2\.4 of the
kernel, it seems to work \(the included JUnit tests run\) provided that you
change the names of some ADL files used for testing, or change the test
code to match the existing...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ehr-Java-kernel](https://discourse.openehr.org/t/ehr-java-kernel/16703)
> Hi
I am about to estimate how much work it will be to get a running prototype of
the openehr\-kernel, and I need to be able to run a few archetypes\. I already
downloaded the source\-code from ACode, which is a website in Swedish\. I hope
I did understood it well and got the right thing, but it looks like it\.
So I downloaded the source\-code of the ehr\-java\-kernel, which is \(I'm not
surprised\), quite a lot\.
Is there anyone who can tell me if this code should run smooth, this...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Antw: Re: Private response, so OpenEHR list is not for furtherdiscussion?](https://discourse.openehr.org/t/antw-re-private-response-so-openehr-list-is-not-for-furtherdiscussion/15821)
> as answer: William
>
TB: The ultimate point is that there absolutely must be a single set of
> models for clinical concepts\.
WG: I agree\!
Secondly, that it must be possible to express these concepts clearly, and re\-usably\.
WG: I agree\!
TB: Thirdly, that such expressions can be automatically translated for use in any particular deployment technology or circumstance\.
WG: I agree\!
TB:
Having parallel libraries of such concept definitions \(and this will probably be made worse...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [100 HL7 v3 clinical archetypes available: focus on content please](https://discourse.openehr.org/t/100-hl7-v3-clinical-archetypes-available-focus-on-content-please/14504)
> I believe there is some wrong viewpoints expressed below, and will include comments following my initials WG
In a message with datum 18-9-2005 1:47:54 West-Europa (zomertijd), Thomas.Beale@OceanInformatics.biz writes:
TB: from the openEHR point of view, the content of a prescription is in the
record.
WG: This is probably from any patient record system, not exclusively the OpenEHR solution
TB: The 'order' corresponding to a prescription is simply a
WG: so you agree you need some kind of...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Private response, so OpenEHR list is not for further discussion?](https://discourse.openehr.org/t/private-response-so-openehr-list-is-not-for-further-discussion/14505)
> Dear all,
I did not get a respons on my viewpoints about the irrelevance of the HL7 v3 versus OpenEHR debate which is in my opinion, from a clinical and modelling point of view, irrelevant.
I need tools that help clinicians to express clinical needs, data, instruments, vocabulary and that supports their workflow and communication. Neither Open EHR nor HL7 currently can do this all. Both approaches need years of work ahead.
Joint work, especially on archetypes / templates, would both...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [OpenEHR / 13606 and HL7 v3 are doing fundamentally the same](https://discourse.openehr.org/t/openehr-13606-and-hl7-v3-are-doing-fundamentally-the-same/12051)
> OpenEHR / 13606 and HL7 v3 are doing fundamentally the same:
Further debate about the 'Actionability' of orders within OpenEHR
Clinicians care for patients and to do this properly they exchange information, in the current era with use of information and communication technology (ICT).
The document based approach (13606 / CDA), archetype exchange approach (OpenEHR), and message based approach (HL7 v3) are all three attempts to facilitate clinicians use of ICT in storing and exchanging...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Compiling the java ADL_parser (patches included)](https://discourse.openehr.org/t/compiling-the-java-adl-parser-patches-included/12055)
> Hello again\!
One of the first things we tried \(in the projects mentioned in a previous mail\) was to compile the java ADL\_parser using version 1\.2\.4 of the kernel, it seems to work \(the included JUnit tests run\) provided that you change the names of some ADL files used for testing, or change the test code to match the existing names in the subversion repository\. Preliminary patches to change the testcode are provided at the end of this mail \(including a patch to project\.xml if you...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [openEHR Change Management](https://discourse.openehr.org/t/openehr-change-management/12050)
> All,
Please find below the text of an email I sent to the openEHR Technical
list on Friday 2 September, 2005\. I want to ask you to once again help
us manage the change management process the best we can by taking the
few minutes to create a new userid in the desired format\.
The deadline for removal of old ID's is only two days away now\.
If you have any questions please feel free to email me directly\.
Regards,
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Request for comments](https://discourse.openehr.org/t/request-for-comments/14502)
> Attached is a draft of a proposed resolution that I am planning to submit to a professional medical organization\. I would be grateful for any comments, particularly as to whether there is agreement or disagreement with the "WHEREAS" statements, but any and all comments would be welcome\.
Bruce Wilder
[details="(attachments)"]
[2005_Open.doc|attachment](upload://3q2qGkcCZxdHPYOlnwUIRbgQEjj.doc) (24.5 KB)
[/details]
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - ['Actionability' of orders](https://discourse.openehr.org/t/actionability-of-orders/14503)
> Gerard
This area is interesting. At a recent meeting of Standards Australia it was determined that an extract should say if it is for information only or there is, within it, the expectation that some action is required. This should, we felt be boolean ie unambiguous. It took some time to come to this - but an example is an extract containing a medication order that is sent to the pharmacy (action required) and copied to the specialist (no action required).
The *open*EHR instruction class...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: pure Java ADL parser](https://discourse.openehr.org/t/annc-pure-java-adl-parser/14495)
> Hi Thomas
Thomas Beale wrote:
> Links and details of this work can be found on the Java Knowledge Tools home page at http://svn.openehr.org/knowledge_tools_java/TRUNK/project_page.htm.
The link throws up an authorisation dialog\. Is it possible to provide the username/ password so we can have a look at the details\. Also could you please provide the URL to the ADLParser API\.
Thanks
Rahil
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: pure Java ADL parser (MOVE)](https://discourse.openehr.org/t/annc-pure-java-adl-parser-move/12053)
> I was a little incautious when I uploaded this code to the knowledge\_tools\_java repository\. In discussions with A\-code, we have agreed that it would be more sensible in the ref\_kernel\_java repository\. This latter repository actually should be renamed to 'ref\_impl\_java', but I am not sure of how serious the knock\-on effects of such a rename would be\. In any case, logically, the 'ref\_kernel\_java' repository should be thought of as being the main reference...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with ADL_parser](https://discourse.openehr.org/t/problem-with-adl-parser/14499)
> Hello\!\!
I have been working with the release of pure Java ADL parser, but when I try to parse any adl file \(for instance, adl\-test\-entry\.most\_minimal\.test\.adl, located in the res/test folder of the release\) my IDE \(Eclipse\) throws a ParseException saying that the structure of the file isn't the expected\.
I'm using the version 1\.2\.4 of openehr java kernel and windows XP\. I have tried with other adl files with different adl version, but the result is the same\.
What...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Personal Health Information workshop](https://discourse.openehr.org/t/personal-health-information-workshop/12049)
> I apologize for cross-posts
September 30, 2005
New York City
www.release1-0.com/events/
I’m writing to invite you to my Personal Health Information (PHI) workshop on September 30 in New York City. If you care about the business of collection, management and use of personal health information, whether you are an entrepreneur, investor, IT vendor, policymaker or a health-care provider, you will want to participate.
To make effective use of the capital that investors, government and the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFC - CR-000150 - express language etc as a String](https://discourse.openehr.org/t/rfc-cr-000150-express-language-etc-as-a-string/14494)
> As part of the current group of CRs being analysed for openEHR, we are considering CR\-000150 \(http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/150 in the CR system\) which basically says that where we have an attribute in the refreence model which represents language, encoding or territory, we should directly use Strings rather than use CODE\_PHRASE as we do now\.
Current Situation
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: lists functioning properly again](https://discourse.openehr.org/t/annc-lists-functioning-properly-again/14493)
> For those of you who might have been wondering if openEHR had gone silent in the last few weeks, and/or noticed a stream of annoying test messages, we have in fact had a nasty mail list problem which we resolved yesterday\. This problem had the effect of silently failing to email a large proportion of both the clinical and technical lists\. For the technically\-minded, our system administrator uncovered a bug in the bulk mailer software where it silently failed if no domain was found in the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Java ADL Parser API Doc](https://discourse.openehr.org/t/java-adl-parser-api-doc/12056)
> Javier Viguera Muñoz wrote:
> Hello Ron\!\!
>
> I have to make a program in Java for mapping ADL and OWL languages\. Then I need to use the Java ADL parser but i'd like to have the API doc\. Can you help me?
>
> Thanks and regards
>
> Javier Viguera
>
Hi Javier,
I thought you meant the java wrapper of the Eiffel parser\.
Anyway, our java parser, which is based on JavaCC and released under GPL, can be found at the following...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [re: Adl parser samples](https://discourse.openehr.org/t/re-adl-parser-samples/12048)
> Hello,
I have to make a program in Java for mapping ADL and OWL languages\. Then I need to use an adl parser, but I can't find documentation about it\. Where can I find these docs or some example to know how to use the libraries?
I see in the new subversion repository an archetype editor, but the docs folder is empty\.
You replied one month ago that the docs would be in the repository in a few days\. Do you have any new news about it?
Thanks and regards
Javier Viguera
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNOUNCEMENT: Ontolog Forum Panel Discussion Aug. 25, 2005: Health Informatics](https://discourse.openehr.org/t/announcement-ontolog-forum-panel-discussion-aug-25-2005-health-informatics/12047)
> `Folks: I don't know if this of interest but I wanted to make certain everyone was aware of it. `
``
`Dear Colleagues:`
`We are pleased to announce an Ontolog Forum Virtual Panel Discussion`
`on August 25, 2005 on the topic:`
`Healthcare Informatics Landscapes, Roadmaps, and Blueprints:`
`Towards a Business Case Strategy for Large Scale Ontology Projects`
`You can find an abstract and information on how to attend and RSVP...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Validating an objecrt against its archetype](https://discourse.openehr.org/t/validating-an-objecrt-against-its-archetype/14492)
> Jim Alateras wrote:
>
>>> Question 1
>>> ==========
>>>
>>> I use The following code fragment to create an object from an archetype
>>>
>>> rmobj = archetype\.buildRMObject\(valueMap, errorMap, sysmap\(\)\);
>>>
>>> One of my constraints for this archetype is optional, as shown below
>>>
>>> ELEMENT\[at0004\] occurrences matches \{0\.\.1\} matches \{
>>> value matches \{
>>> DVTEXT matches \{
>>> value matches...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Reversengineering java-files in Rose](https://discourse.openehr.org/t/reversengineering-java-files-in-rose/15816)
> It is imppossible for me to import the openehr java files in Rose, it mocks a lot about errors like below
12:01:10| Parser Error: near token < on line 43 occurred in File E:\\openEhr\.org\\ref\_kernel\_java\\TRUNK\\src\\java\\org\\openehr\\am\\archetype\\constraintmodel\\CMultipleAttribute\.java
The error is in the line:
public CMultipleAttribute\(String path, String...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new french translations / nouvelles traductions françaises](https://discourse.openehr.org/t/new-french-translations-nouvelles-traductions-francaises/15817)
> Thanks to Dr Roger Lonjon for organising a further french translation, this time of a short presentation "New Developments in openEHR
\(CEN meeting, Berlin May 2005\)"\. See http://www.openehr.org/translations/fr/d_top_french.htm.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR in the news in Australia](https://discourse.openehr.org/t/openehr-in-the-news-in-australia/15628)
> some may find this interesting\.\.\.http://australianit.news.com.au/articles/0,7204,15675784%5E24169%5E%5Enbv%5E,00.html
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [A useful Java 5 book](https://discourse.openehr.org/t/a-useful-java-5-book/12036)
> For anyone out there who has an interest in using in Java 5.0 and needs a good, concise, quick, reasonably priced and accurate guide to the new features, I found the following extremely useful:
[http://www.amazon.com/exec/obidos/ASIN/0072258543/ref%3Dnosim/deliciousmons-20/002-9381773-9618440](http://www.amazon.com/exec/obidos/ASIN/0072258543/ref%3Dnosim/deliciousmons-20/002-9381773-9618440)
The best thing is that it's less than 200 pages long and gives good, clear illustrations by short...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem Saving an Archetype with 0.99.1a Beta](https://discourse.openehr.org/t/problem-saving-an-archetype-with-0-99-1a-beta/12054)
> Rodrigo
Do you mean a LIST based OBSERVATION/EVALUATION or a LIST structure \(these choices are made on the start up screen\)\.
I cannot reproduce the problem in 99\.2a, so you might try the current build\.
Cheers, Sam
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Further development of archetypes, and a first look at the repository](https://discourse.openehr.org/t/further-development-of-archetypes-and-a-first-look-at-the-repository/15812)
> Dear All
I have had the chance to interact with more people over the past two months on archetypes than previously \- which has lead to some development of archetypes\. These are on display as HTML and downloadable as ADL to view in the editor at:
http://oceaninformatics.biz/archetypes/
You might notice that the Goal archetype has been simplified to include targets within it, rather than only in the specialisation\.
There are a new set of archetypes to make exclusion statements about...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Updated archetype FAQ](https://discourse.openehr.org/t/updated-archetype-faq/15811)
> Dear all,
the archetype FAQ has been updated, to answer a very common question; see http://www.openehr.org/FAQs/t_archetypes_FAQ.htm#mozTocId539566.
New presentations are also available relating to legacy data conversion, and the ontological basis for openEHR modelling\. See http://www.openehr.org/site_map/t_presentations.htm
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest archetype workbench and archetypes](https://discourse.openehr.org/t/latest-archetype-workbench-and-archetypes/14490)
> Dear all,
the latest release of the archetype workbench is in its usual place at http://www.openehr.org/repositories/adl_ref_parser-dev/latest/distribution/tools/windows/adl_tools_index.html. Note that the java wrapped version has not been brought up to date\. The latest changes mainly centre on support for reading and writing of the description section of the archetype, i\.e\. the descriptive meta\-data \(author, purpose, keywords etc\)\. The formal model of this part of an archetype is in...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [position available - associate professor in health informatics at NTNU, Norway](https://discourse.openehr.org/t/position-available-associate-professor-in-health-informatics-at-ntnu-norway/15810)
> Dear all\.
I hope this post not is against the list policy \.\.
Arild Fax
ASSOCIATE PROFESSOR \(HEALTH INFORMATICS\) AT THE NORWEGIAN UNIVERSITY OF SCIENCE AND TECHNOLOGY \(NTNU\),
The Medical Faculty at the Norwegian University of Science and Technology \(NTNU\) in Trondheim, Norway, invites applications for an Associate Professorship in Medicine \(Health Informatics\) for four years\. The position is placed at the Norwegian Centre of Electronic Patient Records \(NSEP\)\.
The Norwegian...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Proposed major changes to ADL syntax (2nd go)](https://discourse.openehr.org/t/proposed-major-changes-to-adl-syntax-2nd-go/15813)
> Dear all,
as part of the ongoing work with archetypes in the openEHR community it has become clear that a change to the syntax would be desirable. The change is essentially to convert ADL archetypes from their somewhat idiosyncratic syntax to being regular dADL documents. The semantics would not change, but it would mean that parsers and serialisers could mechanically convert between ADL documents and AOM instance trees. "ADL" would thus cease to be a special syntax, and would instead denote...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFI: any subversion gurus out there?](https://discourse.openehr.org/t/rfi-any-subversion-gurus-out-there/15814)
> Dear all,
as part of the process of moving to Subversion, we are currently redesigning repository and directory structures for openEHR projects\. While we have a pretty strong understanding of the requirements and general approach to CM, we are just learning Subversion\. If there are people in the community who would like to know more about what we are doing \(before we do it;\-\) and review or comment on it, you are welcome\. Please reply to this post, and we will add you to the relevant...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [{Filename?} Proposed major change to ADL archetype syntax](https://discourse.openehr.org/t/filename-proposed-major-change-to-adl-archetype-syntax/14872)
> **Warning: This message has had one or more attachments removed (openEHR-EHR-OBSERVATION.visual.new.adl). Please read the "CHIME-Attachment-Warning.txt" attachment(s) for more information.**
Dear all,
as part of the ongoing work with archetypes in the openEHR community it has become clear that a change to the syntax would be desirable. The change is essentially to convert ADL archetypes from their somewhat idiosyncratic syntax to being regular dADL documents. The semantics would not change,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes: Medication order, risks and goals](https://discourse.openehr.org/t/archetypes-medication-order-risks-and-goals/14500)
> Dear All
The first instruction \(based on the openEHR instruction model proposal\) is available at:
http://www.oceaninformatics.biz/archetypes
It is not complete and needs more work, but has many of the features of a medication order that are required in the health system\. This is not a prescription \(which is a set of medication orders\) \- all this information relates to a single order\. It deals with the workflow and includes dispensing and administration\.
The model...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Antw: Re: Barthel error](https://discourse.openehr.org/t/antw-re-barthel-error/14498)
> Dear William
Thank you for the succint description of all that you are up to. The real issue here is that if there is a score, it must be the total of all the ordinal values...I think this is correct. So we can say, if there is a Total, that this total value must be the sum of all the elements, each of which must be present.
I believe that an invariant is the way to do this.....Thomas Beale might help us with the invariant statement that we can put into the archetype. Is this sufficient for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR-EHR-COMPOSITION.Report.v1draft](https://discourse.openehr.org/t/openehr-ehr-composition-report-v1draft/16476)
> Hi,
I was looking at the composition archetype for “report” that comes with the archetype editor.
The archetype constrains a composition to include information about a request identifier, requesting clinician, contact details, request date, report identifier, copies to and referrals to.
Many of these things are also in common with standard tags in CDA.
It seems to me that many of these fields actually belong in the reference model and not in an archetype.
Does anyone think we need to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SV: [SPAM] - Re: SubjectOfInvestigation - Bayesian Filter detected spam](https://discourse.openehr.org/t/sv-spam-re-subjectofinvestigation-bayesian-filter-detected-spam/14496)
> Bert,
A starting point might be the distribution of your ten \(or more\) issues to Tom and myself\.
Edgar
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [status of BitKeeper in openEHR](https://discourse.openehr.org/t/status-of-bitkeeper-in-openehr/14497)
> Dear all,
BitMover Inc has recently decided to withdraw its open license, and we are going to be forced to change our CM system for openEHR\. This is a huge disappointment, since BitKeeper really is the rolls\-royce application in its class, and is ideally suited to open development\. However, they have made a decision, and given some leeway for people like us to change\. I am not 100% sure of what you will be experiencing currently if you try to do a pull with your current copy of BK; if...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [SubjectOfInvestigation](https://discourse.openehr.org/t/subjectofinvestigation/15809)
> Hi,
Maybe I misunderstand, I often start an email like this\.
SubjectOfInvestigationGPIC has in its core two classes which are, in my opinion is one redundant and gives programmers extrawork to do\.
There is IdentifiedLivingSubject, which contains the name of the subject, and the ID
And there is SubjectOfCare, which is a generalisation of SubjectOfCarePerson which is a generalisation of PatientExtendedInformation
But SubjectOfCarePerson is also a generalisation of...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [About using 'openEHR Java kernel 1.2 API'](https://discourse.openehr.org/t/about-using-openehr-java-kernel-1-2-api/12042)
> Fan, Sarah wrote:
> Hi Rong,
>
> I am a Java Developer\. As I am new to the API and very interested in exploring it, can I ask a very simple question? How do you construct a RM object based on the constraints defined in an archetype? Does the API has the function to do that, or the developer has to do it himself? Could you give me a simple code example?
>
> Thank you in advance,
>
> Fan,Yue
>
Hi Yue,
I will CC this to openehr\-implementers list so others can follow the discussion as...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetypes & new tool versions](https://discourse.openehr.org/t/archetypes-new-tool-versions/12031)
> Dear all,
for those interested in archetypes, there are new downloads and web pages to look at:
1\. The latest archetype workbench: http://www.openehr.org/repositories/adl_ref_parser-dev/latest/distribution/tools/windows/adl_tools_index.html \(choose the adl\_workbench\.tgz link; Watch out for Windows rewriting the extension to something else\!\!\!\)\.
2\. The latest Ocean Informatics archetype editor: http://www.oceaninformatics.biz/archetype_editor/ArchetypeEditor_download.html
We are...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [emergency](https://discourse.openehr.org/t/emergency/12035)
> > Dear Sam Heard
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes update and FBC (blood_film) - Dates for meetings around Australia](https://discourse.openehr.org/t/archetypes-update-and-fbc-blood-film-dates-for-meetings-around-australia/15249)
> Dear All
I have posted changes to the archetypes as a result of corrections and suggestions and have added full blood count and C\-reactive protein\.
http://oceaninformatics.biz/archetypes/
The Ocean Team will be meeting with the reference group and others around the country \(Australia\) over the next month or so\. If you wish to attend the meetings please contact:
merridy\.pitcher@oceaninformatics\.biz
for more information\.
The dates are:
Adelaide: MAY Tuesday 4th and Wednesday...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [The Uncertainty Decision was: Dr R LONJON Confidence indicator !](https://discourse.openehr.org/t/the-uncertainty-decision-was-dr-r-lonjon-confidence-indicator/14485)
> Arild and Tim
This is clearly an issue\. In the CIP project the group wanted to be able to say that a diagnosis was a working diagnosis\.
We have archetyped a number of concepts that I think will enable the clinician to express these levels of uncertainty without resorting to confidence ratings on all entries in the record\. Arild has shown that you could not possibly do a mastectomy without rating your certainty at 100% \- or you will be sued\. And not treating a pneumonia in a newborn...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [More Archetypes](https://discourse.openehr.org/t/more-archetypes/12041)
> Dear All
The next set of archetypes are for pathology results\. These present a particular design issue because there are many different sorts of result sets that come back, identified by a LOINC code at present\.
The laboratory archetypes are based around common result sets \- deal with the PIT segment as a multimedia object and contain information about the specimen, when it was taken and about any quality issues that arise \- based on Grahame Grieve's suggestions\.
They warrant...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Generalisations vs Associations](https://discourse.openehr.org/t/generalisations-vs-associations/15626)
> Hi,
Maybe I misunderstand, maybe someone can help me with this
In the CENTC251 standard there is a GPIC
IdentifiedLivingSubject\. It has two Generalisations: SubjectOfInvestigation
and SubjectOfCareIdentification
This happens a lot in the Standard\. In my opinion a class can only be a child
of one parent, and if you want it to associate to more classes, you have to
use Association\.
Although multiple inheritance is allowed in UML 2\.0 \(I don't know about
previous versions\), it is...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Archetypes - Diagnosis, Genetic condition and Injury](https://discourse.openehr.org/t/archetypes-diagnosis-genetic-condition-and-injury/12040)
> Dear All
This is the second wave of evaluation archetypes [available as HTML and as ADL](http://oceaninformatics.biz/archetypes/). Any archetypes edited or added since the last email will have a 'new' icon to help you to see which ones are new in the list.
[Diagnosis ](http://oceaninformatics.biz/archetypes/openEHR-EHR-EVALUATION.problem-diagnosis.v1.html)is a specialisation of [Problem](http://oceaninformatics.biz/archetypes/openEHR-EHR-EVALUATION.problem.v1.html) (added references and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Flavour of null](https://discourse.openehr.org/t/flavour-of-null/14479)
> Dear All
A reminder on why flavour of null is at the ELEMENT level: it allows a composition with mandatory data to be saved even if the data is not available, or allows a reason to be stated for data that is missing\. It also allows us to deal with the HL7 flavour of null on the data types\.
I am concerned that the flavour of null is set to DV\_CODED\_TEXT and not DV\_TEXT \(ie\. it has to be coded from a terminology\)\. I agree that some systems will want things coded for safety in some...
**[Implementers (archive)](https://discourse.openehr.org/c/implementers-archive/158)** - [Kernel Test Failed](https://discourse.openehr.org/t/kernel-test-failed/15627)
> I've downloaded maven, openehr kernel and JDK 1.5 update 2 for Windows XP.
Installed JDK and Maven successfully, changed to base project directory and run 'maven test'
First it started to download a lot of software log4j, commons, etc.
Then tests started to be run and this is what I get in the end:
**BUILD FAILED**
**File...... C:\Documents and Settings\rodrigo\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly**
**Element... fail**
**Line...... 181**
**Column.... 54**
**There were test...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CAM do [: Re: [bcm] Todays meeting [Re: OASIS CAM / BCM]]]](https://discourse.openehr.org/t/cam-do-re-bcm-todays-meeting-re-oasis-cam-bcm/15807)
> Thomas et al :
As David acknowledges \(below\) your comments provide food for thought and
further exploration\. I am travelling April 8\-24 \(family gathering in
Australia\) and will pick up on this thread whence I return\.
carl
I do like the possiblity here of mapping from OCL;
actually this kinda validates our approach \- since
the scripting can support higher level representation
models well \- that can then use production rules
to create the various sections of the CAM template\.
Yes...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[bcm] Todays meeting [Re: OASIS CAM / BCM]](https://discourse.openehr.org/t/bcm-todays-meeting-re-oasis-cam-bcm/15805)
> David \(Forslund\) et Al :
FYI \- We informally discussed your comments at the BCM TC meeting today\.
There was general agreement that it would be good if we could work
towards a cooperation that would result in a common definition of how
Templates & Archetypes support e\-Health and other e\-business services\.
Q :
>> Do you have any preliminary examples of Archetypes/Templates that would
>> be applicable to OpenEHR?
A :
Both BCM and CAM promote the use of Templates , will provide...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OASIS CAM](https://discourse.openehr.org/t/oasis-cam/14478)
> Have people looked at the OASIS CAM effort as applied to Archetypes:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cam
It is an interesting approach that has been underway for quite awhile now\.
Dave
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Latest release of ADL reference parser in dotNet and Java-wrapped form](https://discourse.openehr.org/t/latest-release-of-adl-reference-parser-in-dotnet-and-java-wrapped-form/15806)
> The latest release of the openEHR ADL reference parser in various forms can be found at http://www.openehr.org/repositories/adl_ref_parser-dev/latest/distribution/tools/windows/adl_tools_index.html.
This release includes a java\-wrapped version of the parser as a windows DLL, along with a java test program\. The archive at http://www.openehr.org/repositories/adl_ref_parser-dev/latest/distribution/tools/windows/adl_java_dll.tgz when fully unzipped should run directly under Eclipse 3\.0 and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ANNC: java kernel implementation](https://discourse.openehr.org/t/annc-java-kernel-implementation/15808)
> Dear all,
the initial release of a java reference kernel for openEHR is available\. The project page is at http://www.openehr.org/repositories/kernel_java-dev/latest/project_page.htm. This work has been carried out by the Swedish company a\-code, led by Rong Chen and Göran Pestana\. See http://www.openehr.org/projects/t_projects.htm for further information & links on a\-code\. We are indebted to the team for donating their work as open source to the openEHR Foundation, which really means...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Who is using openEHR?](https://discourse.openehr.org/t/who-is-using-openehr/12039)
> Dear openEHRites,
there is a new page showing current use of openEHR that we know of \- see http://www.openehr.org/projects/t_projects.htm. Please visit the page, and give us further information and modifications \- email these to David Lloyd at d\.lloyd@openehr\.org\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [release 0.95 of specifications](https://discourse.openehr.org/t/release-0-95-of-specifications/14483)
> Dear all,
Work has been continuing on the specifications leading up to Release 1\.0, expected sometime in May\. Up to that date, various stages in the work are being baselined as release 0\.95, 0\.96 etc\. The release\-0\.95 baseline was declared today\. See the new specification project home page at http://www.openehr.org/repositories/spec-dev/latest/project_page.htm to see the details of the release plan and stages\.
The latest release is directly available at...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New keystone document: Introducing openEHR](https://discourse.openehr.org/t/new-keystone-document-introducing-openehr/12037)
> Dear all,
there is a new top\-level document describing openEHR now available at http://www.openehr.org/about_openehr/t_home_aims.htm \- see PDF link at bottom of page\. We hope this proves useful for both newcomers and existing members\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Unsubscribing from openehr-technical](https://discourse.openehr.org/t/unsubscribing-from-openehr-technical/12033)
> Could someone, somewhere, post a message indicating how people are to unsubscribe from this list without clogging up the message stream\. I've looked http://www.openehr.org/advice/contents.html#technical and it's not obvious \- as also evidenced by the continual stream of unsubscribe messages to the list\.
Thanks
John\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[OT] - Any Probs ? [was: Re: UNSUBSCRIBE]](https://discourse.openehr.org/t/ot-any-probs-was-re-unsubscribe/15519)
> \-\-\-end quoted text\-\-\-
There seems to be a flurry of "Unsubscribe" requests over the
last few days, posted on list\. Normal logic dictates, that, the
best way to get out of any place is to use the same door you
came in through\.
The web innterface at http://openehr.org and going through the
links: 'Community \-> Membership \-> Login \-> Remove Regn' was
working fine enough\. I tried the 'modify' option, to suspended
my mails for a short ...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [MCAFEE E-MAIL SCAN ALERT!~ADL TO XML SCHEMA](https://discourse.openehr.org/t/mcafee-e-mail-scan-alert-adl-to-xml-schema/15801)
> Hi guys,
Maybe we can help.
As David and Sam know I'm working on archetypes too and for now I've created my very simplified version in an XML format that is converted back and forth in David's OpenEMed COAS server. I've gone one step further and added a front-end using the Apache Cocoon webapplication framework which is based on XML and XSL transformations. This results in a generic EHR system that we have tested with a small group of users in the CVA-domain. We also tested how generic it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EntityNameParts](https://discourse.openehr.org/t/entitynameparts/14480)
> I will come back to the answers I got about II later\.
Thanks for this\.
I have another question: about EntityNamePart in the CEN\-standard\.
There seems to be no way to tell if a certain namepart actually are
name\-initials\.
f\.e\.
Sometimes people often have more firstnames\.
Often they have a name that is used for casual contacts, and they have names
which are in their passport, their official firstnames, which are often long
names\.
Often, these long names are only known by...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New discussion list for Implementers CORRECTED](https://discourse.openehr.org/t/new-discussion-list-for-implementers-corrected/12173)
> Sorry to have to send this again, but some of the links went wrong\.
David
There is now a fourth discussion list available called "implementers"\. Please read about it below\.
If you wish to join this list, please go to Community then Membership and tick the box for this list\. Please also check your other details while you are there, particularly your email address\. \. Thank you\.
Description: This mailing list is for those implementing openEHR to discuss low\-level...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New discussion list for Implementers](https://discourse.openehr.org/t/new-discussion-list-for-implementers/12172)
> There is now a fourth discussion list available called "implementers"\. Please read about it below\.
If you wish to join this list, please go to Community then Membership and tick the box for this list\. Please also check your other details while you are there, particularly your email address\. \. Thank you\.
Description: This mailing list is for those implementing openEHR to discuss low\-level technicalities in detail, including methods of programming, tools, schemas and so...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL to XML Schema](https://discourse.openehr.org/t/adl-to-xml-schema/15565)
> Hello everybody,
We're working at University of Zaragoza \(Spain\) on a EHR system\. We
want to conform to 13606 and make use of ADL\-based archetypes\. We are
just starting and we have lots of doubts about how to implement and
apply all concepts\. These are our questions:
\- How 13606 is applied to built ADL archetypes? Is it already possible?
\- Is it possible to obtain a XML\-Schema based on 13606 from an ADL file?
\- Is ADL parser in openEHR site the only one to make use of it?
We...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype editor status](https://discourse.openehr.org/t/archetype-editor-status/16702)
> Dear all,
there is an anomaly in the openEHR software as of Friday\. The ADL reference parser, archetype workbench, and archetype valdiator have been rebuilt with small improvements to the dADL handling code, and with corrected handling of paths, which now must commence with a '/' in all cases\. The archetypes have also been upgraded\. All of these changes are in the usual places on the openEHR website\.
Unfortunately, there is a small problem in the Ocean Archetype Editor when it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OID once more](https://discourse.openehr.org/t/oid-once-more/14482)
> Two simpel questions, though the answer may be complicated
1\) Is there an OID which can be used if there is no OID known, f\.e\. 0\.0\.0\.0\.0
2\) I work for a comany which wants to use the insurance\-number of a patient
for a special goal\. It only wants the Insurance\-number\.
What is the best way to present this?
Normally, the Insurance\-number is a part of the Identity which is a list of
II, but the items of that list do not contain meta\-information\. How can an
insurance number be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetypes and class constraints](https://discourse.openehr.org/t/archetypes-and-class-constraints/14486)
> If I might ask a rather mundane technical question about archetypes \.\.\.
Looking at the archetype models, there appears to be no way to enforce that the class to be used for some specific piece of information is exactly that class and not one of its subtypes\. For example, what if it is important to have a DVTime used and not a DVPartialTime? Or an ObjectRef that should never an AccessGroupRef or a PartyRef?
My feeling is that the class constraint in an archetype needs an additional...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [HICSS minitrack in Consumer Health Informatics,Patient Safety and Quality of Practice](https://discourse.openehr.org/t/hicss-minitrack-in-consumer-health-informatics-patient-safety-and-quality-of-practice/15800)
> Dear openEHR\-technical:
Please consider the call below \(first call for abstracts, call for
papers will come some time in April\) for HICSS\-39\. The IT in Health
Care track at HICSS \(see http://www.hicss.hawaii.edu/HICSS39/fitcfp.htm)
has this 'Consumer Health Informatics, Patient Safety and Quality of
Practice' minitrack which I run, and there's also a 'Data and Knowledge
Management in Health Care' minitrack\. I'd like to see more detailed
work concerning EHR...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [direcotry/folder support for demographics](https://discourse.openehr.org/t/direcotry-folder-support-for-demographics/15803)
> Hi all,
There is currently no support of directory/folder for demographic classes, it seems good to group PERSON/ORGANISATION in a hierarchical way same as how EHR/VERSIONED\_COMPOSITION are organised\.
It will be possible reuse DIRECTORY/FOLDER from rm\.ehr package after loosen the invariant constraint Owner\_id\_valid: owner\_id\.type\.is\_equal\( EHR \)\. It should probably make sense to move DIRECTORY/FOLDER to some generic package as well\.
Please comment\.
Regards,
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL-Parser](https://discourse.openehr.org/t/adl-parser/15802)
> Hello everybody,
does somebody know when the ADL\-Parser will be published on openehr\.org site?
Last time in the conference in Brussel there were the statement, that this parser
will be ready at the first quartal\. So will it be ready at that time?
Regards
Evgeny Usorov
Kassenärztliche Bundesvereinigung
Herbert\-Lewin\-Platz 2/Wegelystraße, 10623 Berlin
IT\-Bereich / IT in der Arztpraxis
Tel: \+49 \(0\)30\-4005\-2018
Fax: \+49 \(\(0\)30\-4005\-27\-2018
mailto:eusorov@kbv.de
http://www.kbv.de
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Demographics service](https://discourse.openehr.org/t/demographics-service/14481)
> This discussion document is produced by UCL \(CHIME\) to highlight issues that have arisen when designing a Demographics Service component\. This service component will need to conform to the openEHR demographics package and be able to support the requirements of live demonstrator sites in north London\. Any feedback and comments are welcome\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Problem with Datatype: Instance Identifier (II)](https://discourse.openehr.org/t/problem-with-datatype-instance-identifier-ii/14487)
> Hi, I am working with the final drafts of EN 13606, maybe some information I use is obsolete, please let me know if it is.
Maybe, if I misunderstand something, please let me know.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Validating data input](https://discourse.openehr.org/t/validating-data-input/15799)
> Hello everybody,
I've been following the evolution of openEHR and find it really great. As a matter of fact we (at the University) are interested in using it as the basic idea for developing a Critical Care Unit Software.
We are not much to worried about eventually having to make some changes in the future but we are really anxious to test the idea putting some of our own.
I have noticed that there is not much discussion on how the data/archetype validator o comparison process is to be...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [His best hope is early parole](https://discourse.openehr.org/t/his-best-hope-is-early-parole/14477)
> Hi All,
This is an interesting case that prompts questions regarding EHRs surrounding death
of a Patient\. It also serves to illustrate how goverment can alter what should be a rather
clear, concise medical event that must at some time and in some form be entered into
the EHRs\.
The issues here involve 'statutory death', 'State Agency death', 'Judicial death' and
potentially 'extra\-judicial' and 'extra\-statutory death'\. One also has the problem...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR List settings](https://discourse.openehr.org/t/openehr-list-settings/15804)
> PLEASE DO NOT REPLY TO THIS MESSAGE
Dear all,
the following lists have been altered to have reply\-to automatically set to the list\.
\- openehr\-technical
\- openehr\-clinical
The implementers list will also be set up this way\.
This change means you can now reply to the list just by using your "Reply" button \(don't use the Reply\-all button\)
In the event of an email "avalanche" which occasionally occurs due to a badly configured mail server, the offending...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Doubt with time_validity in classes ROLE and CAPABILITY](https://discourse.openehr.org/t/doubt-with-time-validity-in-classes-role-and-capability/12160)
> Hello everyone!!
I have a doubt with the difference in the attribute time_validity in the classes ROLE and CAPABILITY. The description of both in the Revision 1.4.4. of the demographic model (the one I`m using) is the same:
Valid time interval for this role
If this is correct I think that one of the two attributes could be deleted because it referes to the same concept. I think that the ones in CAPABILITY class could be deleted...
But perhaps the correct description for this parameter in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [proposal for gathering community knowledge](https://discourse.openehr.org/t/proposal-for-gathering-community-knowledge/14442)
> Dear all,
one thing that is always a concern in any community is how to retain knowledge and ideas generated by debate and discussion\. I have spent some years in the community informatics arena, and this is a well\-known problem\.
What it comes down to is this\. Interesting, sometimes long discussions occur about topics like "what is an episode", "age", "confidentiality" and so on\. Many good points are made, and there may even be a consensus view reached due...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [CR-000024 - Revert meaning to String in LOCATABLE nodes in openEHR data](https://discourse.openehr.org/t/cr-000024-revert-meaning-to-string-in-locatable-nodes-in-openehr-data/14386)
> Dear all,
this CR has been processed, but since it involves probably the most crucial piece of meta-data in the data - the archetype node ids which are imprinted into their corresponding data nodes - I want to ensure that we are doing the right thing, particularly by implementors. (original CR text - [http://www.openehr.org/repositories/spec-dev/latest/publishing/CM/CRs/CR-000024.txt](http://www.openehr.org/repositories/spec-dev/latest/publishing/CM/CRs/CR-000024.txt))
To refresh your...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [BitKeeper repository name change](https://discourse.openehr.org/t/bitkeeper-repository-name-change/12038)
> Dear all,
the openEHR BitKeeper repository "implem\-dev" has been renamed to "adl\_ref\_parser\-dev"\.
\- thomas beale
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Age and Date of Birth](https://discourse.openehr.org/t/age-and-date-of-birth/14476)
> Hi All,
Date\-of\-Birth is a clear, concise, unequivocal event and can be represented as a simple
variable in a database\. On the plus side, bypassing those cultures that use years instead
of days, most people will accept the DOB at face value\.
The 'true' age of a Patient is impacted by many different factors too numerous to mention
here\. 'Aging' is a process that is not only hard to define but affects individuals and groups
non\-uniformly\. The appearance of ...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR discussion lists](https://discourse.openehr.org/t/openehr-discussion-lists/14484)
> Dear all,
IMPLEMENTERS LIST
a discussion list for early adopters has been set up\. We decided to call it "openehr\-implementers" \(NOTE spelling of "implementers"\!\), rather than "early\-adopters" since in a couple of years' time there will be people on the list who are at a mature stage of development\.
We are testing the list at the moment\. What we need to know from the community is how we should run it\.
Q \- should the list be completely open to any...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR news](https://discourse.openehr.org/t/openehr-news/12024)
> Dear all,
best wishes for the new year\. The fact that I am saying this near the end of January is proof of how busy we are\!
There will be many announcements in the next few weeks\. This year will be an exciting one for the openEHR community\. Some things to look forward to:
\- release 1\.0 of the specifications will be out within weeks\. Most outstanding 1\.0 CRs have been approved by the ARB and have been done\. This includes many changes including from implementation sites\. You will...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Age - Comments prompted by a prior response](https://discourse.openehr.org/t/age-comments-prompted-by-a-prior-response/12022)
> Hi All,
The following are general comments extracted from a private email\.
"\.\.\.
Genomics, environment \(e\.g\., stress, toxics\), family, ancestors, diet, gerontology are a
few of the contributors to age\-sensitive Healthcare issues\. Perhaps the most potent
influence comes from the mind itself, e\.g\., all women in a family tree die at age 62\.
An Electronic Healthcare Record must accurately and precisely capture all relevant,
pertinent information because the next Practitioner...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Age - A reference that might help on age-related triggers](https://discourse.openehr.org/t/age-a-reference-that-might-help-on-age-related-triggers/14475)
> Hi All,
A reference that discusses age\-related triggers:
http://www.separationsnow.com/basehtml/SepH/1,1353,6-1-4-1-0-news_detail-0-619,00.html
\-experiments with yeast
\-compares with empirical eveidence re humans
\-yeast & humans:
"\.\.\. genetic instability shoots up dramatically in the middle to late stage of life\. "
\-yeast:
"\.\.\. equivalent of late middle age \.\.\. 200\-fold surge in the production of genetic changes \.\.\.
may be an ideal model for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Antw: Re: Age, gender and more](https://discourse.openehr.org/t/antw-re-age-gender-and-more/14471)
> In een bericht met de datum 27-1-2005 13:39:00 West-Europa (standaardtijd), schrijft sam.heard@bigpond.com:
> So I was wondering if we should model a class specifically for date of
> birth.....which handles date of birth and age as a function, and which
> takes arguments like date of conception, date of mothers LMP, Expected
> Date of Delivery and stores the normal gestational birthdate as well.
> The class then has a feature called post-conception age as well.
>
> The advantage is that we...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - ['Reply To' setting in openehr posts](https://discourse.openehr.org/t/reply-to-setting-in-openehr-posts/14463)
> This is a request for the List Admin\.
The 'Reply To:' setting for the mailing list is currently set
for the Original Poster \(OP\)\. This results in two things:
o On hitting \[Reply\] on most MUAs the 'To:' address is set for
the OP\. Since the OP would in any case a copy of the mail if
the reply is sent to the list, keeping the 'Reply To:' set
for the list would save all the trouble of doing a Cc to the
list...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Age](https://discourse.openehr.org/t/age/14820)
> Tom and others
The idea of age as a complex notion \- post\-conception, gestational \(LMP\) ie it can involve pre\-birth periods \- even well into life\. This apperas to be important for decision support\.
I wonder if we need to model this as an archetype for demographics \- but it needs to be in the EHR \- age crops up in lots of evaluations \(problem, family history\) so we might need to have it as a formal TYPE\! That is \- we can use it consistently in various settings\.
I would argue...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [nice article...](https://discourse.openehr.org/t/nice-article/15797)
> on human error in healthcare software that was cited on a usability list\. Nice reminder of another level of reality\.
http://tinyurl.com/6jhrx
Denny Adelman
WZ\-Agenda\.net
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR at CEBIT, Hannover (Germany) ?](https://discourse.openehr.org/t/openehr-at-cebit-hannover-germany/15796)
> All,
PeopleWare is a Belgian software development company active in Java
programming\. We are not specifically active in the Heathcare area although
we have plans to do so in the future\.
For one of our customers we are currently developing a "Disease management"
application in Java\. As this application needs to fit in a bigger "system"
we started looking for such a system a couple of months ago\.
At EUROREC 2004 there were presentations of Prof\. Dipak Kalra and Rong...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [some problems with embeded dADL within cADL](https://discourse.openehr.org/t/some-problems-with-embeded-dadl-within-cadl/15794)
> Hello all\!
I try to send some messages to Problem Report List to crs\_prs@openehr\.org as described on http://www.openehr.org/developer/t_PR.htm and
got failure notice \- so I send this here\. Most of this problems is around embeded dADL section within cADL part of ADL\.
1\. \-
C\_QUANTITY sample in "Predefined Type Libraries" section of ADL revision 1\.2 book is obsolete dADL syntax\. Why?
2\. \-
dADL serialiser for embeded cADL...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Design an HTML layout for an archetype](https://discourse.openehr.org/t/design-an-html-layout-for-an-archetype/14472)
> Dear All
I would appreciate it if people could come up with a suitable layout for an HTML page view of an archetype\. I think we should start with an evaluation first as this is simpler \- perhaps problem, and family history\.
This should be a documentation view \- not an interface view\. I think it will need expanding areas for description so that it is not too large\.
Anyway \- let me know any ideas you have\.
Sam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [how is the EHR server work going?](https://discourse.openehr.org/t/how-is-the-ehr-server-work-going/12020)
> hi tom,
sorry mate, I keep bugging you\. how is the work in london going? a quick update would be good\.
did you get the project description? the early openEHR implementors section is a great idea\. when will it be online\.
who do i have to contact regarding my lost login for the openEHR community\. is it david lloyd?
Cheerio,
\-thilo
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFI: early adopters mailing list](https://discourse.openehr.org/t/rfi-early-adopters-mailing-list/15798)
> Dear all,
this is a request to discover implementors of openEHR or related things who would like to have a separate "early adopters" mailing list\. Such a list would give a place for current users to a\) receive early announcements of work being done but not yet published, b\) to talk to each other, and c\) ask detailed questions on timetables, funding and other issues\. The list would probably have to have some controls on it to protect information posted by commercial...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFI: Current R&D using openEHR and/or archetypes?](https://discourse.openehr.org/t/rfi-current-r-d-using-openehr-and-or-archetypes/12023)
> Dear all,
we are trying to find out who is working with or doing research based on openEHR and/or archetypes\. We are setting up one or more web pages which identifies projects, people and institutions\. The idea of these pages is that they will act as a place where anyone can find out who is working with openEHR, but more importantly where people working on it can find others who are working on it\.
For anyone interested in being represented on this web page, we suggest that you send the...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [question from a lurker](https://discourse.openehr.org/t/question-from-a-lurker/15795)
> Hello all\.
Great discussions here, but is it absolutely necessary that every single posting is cross\-posted to the technical and the clinical lists? All the more so that I imagine that the subscriber roster for the two groups is identical\.
TIA
Denny Adelman
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [History paths](https://discourse.openehr.org/t/history-paths/14473)
> Hi Thomas\!
A question regarding implementation of History paths in reference model:
from data\_structures rev1\.4, p26, one of the examples is
"event: | HISTORY\.name | EVENT\.name, e\.g\. |history|event\_3"\.
But class EVENT has no attribute called name, it doesn't inherit LOCATABLE either\. Does this imply that perhaps EVENT \(or its super class EVENT\_ITEM\) should inherit LOCATABLE?
Thanks\!
Rong
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Specification Change Management Plan](https://discourse.openehr.org/t/specification-change-management-plan/15793)
> Hi everyone,
When answering a question from Tony Austin, I ended up at this link :
http://www.openehr.org/repositories/spec-dev/latest/publishing/CM/CM_plan/REV_HIST.html
\(pick the latest version\)
The question I have is about Chapter 7 & 8 \(from now on called
document\)\.
Is the description of the documennt what will be used for every
subproject of openEhr \(with subproject in this case I mean project where
actually programming takes place\) and is this considered a manual...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Modelling Episodes in openEHR](https://discourse.openehr.org/t/modelling-episodes-in-openehr/12002)
> Dear all,
the definitional debate about what an "episode" will of course continue long into the future, and we will not solve it here - indeed there will never be a single definition. But we can in the abstract identify a couple of solid concepts:
- episode of care by a care delivery enterprise / health care provider - provider-centric
- episode of course of illness / situation - patient-centric; finishes at death, return to health, or stabilisation (chronic problems)
A long-term effort...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Systems of Concepts to Support Continuity of Care](https://discourse.openehr.org/t/systems-of-concepts-to-support-continuity-of-care/12030)
> Seen this:
http://www.centc251.org/TCMeet/Doclist/TCdoc00/N00-053.pdf
Arild FAxvaag
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Episodes in openEHR](https://discourse.openehr.org/t/episodes-in-openehr/13786)
> This is part of a discussion that started off the list. The need is to be able to model Episodes in openEHR, while remaining compatible with available structures.
Currently, there is no "Episode" class (although this doesn't necessarily have to remain this way). Up to now, we have never been able to nail down sufficiently 'standard' requirements to satisfy everyone's idea of an "episode". Instead we have suggested that Folders be used as reference containers to Compositions considered to...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype constraints and interfacing instruments/DSS to an OpenEHR system.](https://discourse.openehr.org/t/archetype-constraints-and-interfacing-instruments-dss-to-an-openehr-system/14103)
> Dear all,
I am not sure whether this is premature but I curious as to which part of an
OpenEHR compliant EHR\-S will enforce the constraints that are embedded in an
archetype model \- I note the use of the term data validator on the web
site \- Will the kernel in an OpenEHR server parse data \(for instance to
assess completeness of a communicated extract\) using some sort of constraint
processor \- or will this be up to individual implementers to sort out?
Also, is there any ongoing...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Family History](https://discourse.openehr.org/t/family-history/12029)
> Amnon
Thanks \- a very full email \- I will do my best\.
First, in openEHR the schema is constant \- based on the reference information model \- so we do not have schema's for the archetype\. I do not have any data as yet as this archetype is not in use as yet\.
> Anyway, as for the Family History archetype \- I took a look at it and I'd
> like to map it to what I'm doing in HL7 which is more genomic\-oriented\.
> Anyway, in my design submission I usually send out the model,...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Folders](https://discourse.openehr.org/t/folders/12028)
> Maarten
There are two things here \- keeping tabs on all recordings made while a person was/is pregnant \- keeping clinical track of the fact that the person is pregnant\.
My proposal is to have an archetype for pregnancy \- it will obviously vary a little \(specialisation\) from place to place but there are some consistent data that can be collected for all\.
The traditional manner of keeping key information about a pregnancy is here and there \- throughout the EHR\. The advantage of...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [LAtest ADL and AOM specifications](https://discourse.openehr.org/t/latest-adl-and-aom-specifications/12018)
> Dear all,
Due to CR\-000110 passing a vote in the openEHR ARB \(http://www.openehr.org/about_openehr/t_arb.htm), the Archetype Definition Language \(ADL\) document has had a major update\. The Archetype Object Model \(AOM; a UML model of archetypes\) has also been made official in the specification repository\. You can find these documents at http://www.openehr.org/repositories/spec-dev/latest/publishing/architecture/top.html \(see links in the green section\)\.
The parse specification for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[XML.org Daily Newslink. Friday, 12 November 2004]](https://discourse.openehr.org/t/xml-org-daily-newslink-friday-12-november-2004/15791)
> <sam\.heard@bigpond\.com>, Klein Gunnar <gunnar\.klein@sis\.se>, Magnus Fogelberg <magnus\.fogelberg@fogare\.se>, Mennerat Francois <francois\.mennerat@wanadoo\.fr>, Beale Thomas <thomas@deepthought\.com\.au>, Kalra Dipak <d\.kalra@chime\.ucl\.ac\.uk>, Maskens AP <alain\.maskens@chello\.be>
Loos vd Jan <loos@hislink\.nl>, Verhees Bert <bert\.verhees@rosa\.nl>, Spook Maarten <Maarten\.Spook@2cure\.com>
Hello,
Archetypes are slowly...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question about RM.DATA_TYPE.CANONICAL_FRAGMENT](https://discourse.openehr.org/t/question-about-rm-data-type-canonical-fragment/15790)
> Hello,
I am currently work on implementing the reference model in java\. I have
noticed an issue that I would like to get resolution on\. While looking over
the RM\.DATA\_TYPES\.BASIC package in RM\.DATA\_TYPES\(Revision 1\.8\) and comparing
it to the HTML Model Tree, generated by Eiffel, I noticed something\. In the
model tree there is a data type called CANONICAL\_FRAGMENT which is not in
the 1\.8 Revision\. The CANONICAL\_FRAGMENT has a description of "Abstract
parent type of all...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Observation vs. diagnostic investigations](https://discourse.openehr.org/t/observation-vs-diagnostic-investigations/16701)
> Heath and Eric
Not sure about IMHO but the archetype story is that observations are measurements, clinical options, assessments are evaluations\.
So any report will probably be a composition \- and evaluations will be included with the observations\. These can be as sections in a complex report\.
So Diagnostic Investigation would probably always involve more than one archetype \- still lab test will often as well if there is any clinical evaluation\.
Hope this helps, Sam
Heath Frankel...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Base demographic record](https://discourse.openehr.org/t/base-demographic-record/15792)
> Dear Tom
I have been working on Family history \- and it is clear to me that it is likely that a relative might want to record that someone is alive and well\. We can cope as long as there is something wrong with them\! What I am proposing is a base demographic record in the EHR for Father, Mother \- probably only has optional DOB, alive/dead and optional DofDearth\.
The advantage of having this record is that we can deal with a relative who is alive and well \- ie, the family history can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype based query](https://discourse.openehr.org/t/archetype-based-query/12027)
> Dear Tom and Andrew
It is clear that we need a standard notation for expressing queries into the openEHR space\. I am sure you have this underway but the statements must address queries into both levels of the model \- the reference model and the archetype stamps in the reference model\.
1\. The statements that relate to the Reference Model include:
\- Time \(Composition time, Observation\.History\.Event\.time\) \-
\- Return type...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data types - moving on some issues that are outstanding in the openEHR archetypes](https://discourse.openehr.org/t/data-types-moving-on-some-issues-that-are-outstanding-in-the-openehr-archetypes/12026)
> Dear Tom
The data types thing is on the move\. Issues that I think we should address in openEHR ASAP are:
DV\_Quantity
precision \- should not be manditory
units \- should be able to be empty string \- or optional as this is the only access to a REAL
DV\_Ordinal
limits: mandatory \- are we always going to have access to this in data coming in?
And the DSTC issue\.\.\.\.
Should there be a new class for DV\_Quantity...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Annotations in CEN and openEHR](https://discourse.openehr.org/t/annotations-in-cen-and-openehr/12016)
> Andrew
No doubt Dipak will tell you more about this but we had some lengthy debates about all of these 'qualifiers' or annotations at the meeting. It was the best attended and most productive EHR meeting I have been to - not absolute numbers, but intellectually. I will mention what happenned in these areas.
> :
>
> · negation warnings
It is clear that negation is important. Just how to do it is the issue. In our archetypes so far we have only 2 negation indicators - for Family history and...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Medication Regimens](https://discourse.openehr.org/t/medication-regimens/14470)
> Hello All,
We are currently working on an oncology project in which medication regimens are used\. I would appreciate some guidance on the preferred way to model regimens using openEHR\. Here is an example of a regimen I am modeling:
Regimen Name: CAF
Step 1: Cyclophosphamide 100 mg/m2/day po days 1\-14
Step 2: Doxorubicin 30 mg/m2/day iv days 1 and 8
Step 3: 5FU 500 mg/m2/day iv on days 1 and 8 repeat q 4 weeks
As I see it, there are two possible models:
1\. One INSTRUCTION with an...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest ADL workAtlanta bench and Clinical Archetype Editor](https://discourse.openehr.org/t/latest-adl-workatlanta-bench-and-clinical-archetype-editor/12838)
> Dear all,
The latest versions of these two tools are available at http://www.OceanInformatics.biz. The code is open source, and a binary of the workbench is on the openEHR website, but until we make the site a bit friendlier for downloads, the packages at OceanInformatics\.biz will be easier to use\.
To date we haven't had the resources to build the ADL workbench on Linux or the Mac \(which should be more or less a recompile\); these ports should be available sometime in October\. The...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetype-dev BitKeeper repository regeneration](https://discourse.openehr.org/t/archetype-dev-bitkeeper-repository-regeneration/12015)
> Due to regenerating of the openEHR sample archetype repository, anyone who has cloned the repository via BiKeeper should delete their copy and reclone\. If you have done some work locally, of course you should save this\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OWL vs. ADL](https://discourse.openehr.org/t/owl-vs-adl/14469)
> Hello,
I have a basic question concerning the overlap of ADL and OWL\. Since you're looking to export ADL to OWL, it seems like they overlap quite a bit, but what are the differences?
Also, from the web site I couldn't tell if the HL7 Structured documents were to be published in \*both\* ADL and OWL, or in a \*combination\* of the two\.
Please direct me to a URL if I've missed some pertinent documentation \(admittedly, I've only read the OpenEHR web site so far, not the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Announce: initial version of ADL parser for Java](https://discourse.openehr.org/t/announce-initial-version-of-adl-parser-for-java/14467)
> Dear all,
while working recently with the group at Dr Peter Elkin's Laboratory of Biomedical Informatics at the Mayo Clinic, MN, we succeeded in wrapping the openEHR ADL parser for use in Java environments\. Thanks to Raju Kalidindi and Russ Hamm for their participation and patience in this exercise\. This work is part of a larger project to connect ADL archetypes with the OWL knowledge environment in use at Mayo\. Further results of this work will be forthcoming\.
In the initial...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New release of ADL workbench tools](https://discourse.openehr.org/t/new-release-of-adl-workbench-tools/14818)
> Dear all,
there is a new release of the ADL workbench available. It fixes numerous small bugs, and improves the GUI. See the [release page](http://www.openehr.org/repositories/implem-dev/latest/publishing/index.html). See here for a [Screen shot](http://www.openehr.org/projects/adl_workbench1.JPG). As before, to use the tool, simply download the [binary distribution](http://www.openehr.org/repositories/implem-dev/latest/distribution/tools/windows/adl_workbench.tgz) (windows only at the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetypes in OWL](https://discourse.openehr.org/t/archetypes-in-owl/12007)
> Dear all,
I continue working with archetypes for demographics, and trying to express them in owl.
I have written the archetype for location_address that is provided in the web in ADL format in owl.
It is based in the openEHR information model, written too in owl.
The archetype is in the url:
[http://trajano.us.es/~isabel/EHR/locationaddress.owl](http://trajano.us.es/~isabel/EHR/locationaddress.owl)
I would like to have feed back from you in order to find problems and improve the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [RFC CR-000024 - Revert "meaning" to String - ARB deadline 23 july 2004](https://discourse.openehr.org/t/rfc-cr-000024-revert-meaning-to-string-arb-deadline-23-july-2004/14466)
> Dear all,
here is another important CR to consider in the next few weeks\.
CR\-000024 \- Revert "meaning" to String\. See <http://www.openehr.org/repositories/spec/latest/publishing/CM/CRs/CR-000024.txt>\. This CR is about the meaning attribute defined on the class LOCATABLE \(see Common Model, Archetype package, at <http://www.openehr.org/repositories/spec/latest/publishing/architecture/reference_model/common/im/REV_HIST.html>\)\. This attribute is one of the most...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [proposed ADL and archetype modification](https://discourse.openehr.org/t/proposed-adl-and-archetype-modification/12014)
> Dear all,
after quite a few months of experimentation and reflection, Sam Heard and I have come to the conclusion that a modification is needed in the semantics of the ontology section of ADL archetypes, to do with term bindings\.
The current situation is shown in the example archetype:
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL v 1.2 draft](https://discourse.openehr.org/t/adl-v-1-2-draft/12013)
> A few people have been asking what the latest status on ADL and related
issues is\.
Here is the latest specification\.
http://www.openehr.org/tmp/adl-1_2_draft_d.pdf
It includes:
\- parser production rules
\- equivalent UML diagrams of archetypes \- based solely on UML
this specification has been implemented and tested in the current parser\. It will
be wrapped in Java in the next 8 weeks or so, and is already available in \.net\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Issues with Latest Spec](https://discourse.openehr.org/t/issues-with-latest-spec/14464)
> Hello Everyone,
I discovered the following issues in the latest spec\. I would appreciate your perspectives on them\.
1\. DV\_PARAGRAPH does seem to make any sense as a data type\. This is more of a rendering issue\. A paragraph can contain multiple observations, but the spec indicates that only DV\_TEXT can be in the paragraph\. In my opinion, a paragraph is a higher level construct than ENTRY and seems more synonymous with a SECTION\. On page 24 of the RIM model it shows an example...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [ADL 1.2 proposal](https://discourse.openehr.org/t/adl-1-2-proposal/15681)
> Dear colleagues,
there is a proposed revision of the Archetype Definition Language \(ADL\) v 1\.2 available at http://www.openehr.org/tmp/adl-1_2_draft_d.pdf. Only small changes to ADL itself are proposed, but the explanations have been improved, and complete grammars have been included in the document\. The main change is a complete redesign of the object models corresponding to ADL, informed by previous work in GEHR, ongoing archetype development, and the DSTC team engaged on the...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Message from David Ingram about openEHR](https://discourse.openehr.org/t/message-from-david-ingram-about-openehr/15788)
> Announcement of the Formation of the openEHR Architecture Review Board \(ARB\) and launch of the new openEHR Web Site and Repository
openEHR takes an important step forward here today with the announcement of the formation of the openEHR Architecture Review Board \(ARB\)\.
This is accompanied by the launch of a new, much enhanced web site, on which Version 0\.9 of the openEHR Architecture is released, under open\-source license, housed on the BitKeeper web site and subject to formal change...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Important new developments in openEHR](https://discourse.openehr.org/t/important-new-developments-in-openehr/15787)
> Dear Colleagues,
We are delighted here to inform you of some important new developments from the openEHR Foundation\.
1\) New web site: <http://www.openEHR.org>http://www.openEHR.org
The web site has been completely redeveloped\. It now provides versioned access to all of the openEHR documents and software, significantly improved support material, FAQs, help for new visitors, and of course the community pages, discussion groups and news\.
2\) Formation of the Architectural Review...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Birds of a Feather session - National and International EHR-S Implementation and Interoperability efforts](https://discourse.openehr.org/t/birds-of-a-feather-session-national-and-international-ehr-s-implementation-and-interoperability-efforts/12006)
> Dear OpenEHR members,
The following session might be of interest to you in case you are attending
the HL7 San Antonio meeting\.
Thanks,
Amnon\.
San Antonio HL7 Working Group Meeting Attendees,
Another "Birds\-of\-a\-Feather" session will be hatched at 7:30 p\.m\. on
Tuesday, May 4, 2004\. Attendees will discuss national and international
EHR\-S Implementation and Interoperability \(BOFEHRii\) efforts\.
WHY:
Excellent functional and informational EHR\-S models are the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Demographic Server](https://discourse.openehr.org/t/demographic-server/12011)
> Dear all:
My name is Isabel Román.
I´m working in a demographic server. In a first version only Person information is considered and I´m using Demographic Reference Model to represent it. I would like to know if the Reference Model is going to be extended with PERSON attributes or if it is only a implementation feature.
And another question. Do you have some references to works in this line with public code?
I´ve written the RM in owl (a first version), you can see it in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [semantics of dADL](https://discourse.openehr.org/t/semantics-of-dadl/15665)
> A simple question\. Is order relevant in dADL?, I mean, are these two extracts equivalent?
name = <
forenames = <"Sherlock">
salutation = <"Mr">
>
name = <
salutation = <"Mr">
forenames = <"Sherlock">
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Unsafe for automatic processing](https://discourse.openehr.org/t/unsafe-for-automatic-processing/12096)
> Dear All
There is an issue that I have been thinking about for some time and which has come up again around an openEHR implementation site \- it is this\. Should a clinician be able to mark Entries as unsafe for automatic processing? The idea is that information might appear in the record \- it is not an error in the usual sense \(it is not wrong\) \- but it is wrong from the point of view of queries or decision support\.
The example that made me think this was worthwhile was a patient who...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [character sets and languages in openEHR](https://discourse.openehr.org/t/character-sets-and-languages-in-openehr/14465)
> A couple of technical questions prior to declaring the 0\.9 baseline in openEHR:
One of the major openEHR implementors here in Australia has suggested moving the attributes 'language' and 'charset' in the class DV\_TEXT to some higher level class \- e\.g\. COMPOSITION, since almost all the time it is the same on DV\_TEXT items in a given EHR\. We don't think it should be that high, since language cannot be guaranteed the same throughout a COMPOSITION \(in their scheme,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Need help unsubscribing](https://discourse.openehr.org/t/need-help-unsubscribing/11998)
> Dear Openehr Group,
I would like to move this egroup to another account and would be very
grateful assistance doing so\. Can someone please email me instructions on
how to do this?
> If you have any questions about using this list, please send a message to
d\.lloyd@openehr\.org
I emailed d\.lloyd@openehr\.org but have not heard back\.
Thank you in advance for your assistance\.
Cecilie
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Basic EHR functionality](https://discourse.openehr.org/t/basic-ehr-functionality/14456)
> Dear all,
I would be grateful for some advice on an issue that has been troubling me
for some time\. I am a clinician currently on secondment full time to an EHR
project\. I do not wish to name the software house we are using but they are
a major EHR developer with an interest in the UK\.
The application on which we are currently basing our documentation strategy
seems to have a flaw\. The following is a made up example but I hope it
illustrates a point\.
The application allows the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Propositions?](https://discourse.openehr.org/t/propositions/14453)
> Hello All,
We are making incredible progress with the openEHR framework\! Recently we faced a requirement to create patient\-facing data capture tools\. Unfortunately we can't seem to find a place in the openEHR model where these types of propositions fit cleanly\.
For example if I have a patient intake form that has the question, "Do you have diabetes?" Obviously the patient's answer to the question could be modeled as an observation of "diabetes" mapped by...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [VMR](https://discourse.openehr.org/t/vmr/12003)
> Dear all
I am very interested in the VMR issues from an EHR perspective and would
like to see this work mirrored in the openEHR and CEN space\. This would mean
defining the data in archetypes\.
I have already done work in this area assessing Prodigy's requirements \- but
recognise that systems like IHC have more ambitious decision support \- and
that decision support might even be authored locally\.
I believe that openEHR is the only public approach that is fully sorted in
this regard...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [modelling survey](https://discourse.openehr.org/t/modelling-survey/15783)
> In the process of getting the openEHR specifications upgraded, a number of Change Requests are being processed before the declaration of the 0\.9 Release\. This release is intended to be more or less what is there now, with errors corrected, and a couple of desirable changes made\.
One change which is quite basic, and is supported by all reviewers so far is as follows:
In the Text cluster of the Data Types specification \(a draft is here...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [is there a relation between clinical data sets and archetypes](https://discourse.openehr.org/t/is-there-a-relation-between-clinical-data-sets-and-archetypes/14460)
> See http://www.prorec.it/efmiStc/recommendations.htm
Is clinical datasets identical to archetype repositories?
regards
Arild Faxvaag
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [archetypes & templates](https://discourse.openehr.org/t/archetypes-templates/15779)
> I am a newby in the community of openEHR\. It is not
clear to me the distinction between "archetype" and
"template"\. It seems that a template is based on an
archetype\. Let's start from archetype in fig\. 11, pag\.
26 in REV 2\.2\.1\.
Is it possible to have an example in which the
"new\_value" slot is implemented with a concrete value?
And an example of at least a couple of templates based
on this new defined archetype?
Thank you very much\.
Matteo Piazza
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [latest Archetypes work](https://discourse.openehr.org/t/latest-archetypes-work/15784)
> Dear all,
the following link points to the latest archetypes work done using the ADL language: http://www.oceaninformatics.biz/adl.html
Numerous improvements have been made to the language, including constraints ordinals, coded terms, and dates and times\. The manual \(http://www.oceaninformatics.biz/adl/adl_1_0.pdf) is pretty comprehensive, but no doubt could benefit with a few others reading it critically\. You will see that 'vanilla' ADL has been kept separate from...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [order entry](https://discourse.openehr.org/t/order-entry/15782)
> Sam,
I do not know the openehr rm well so I spend some time
this week to read the documentation\.
I would like to get involved in the detailed debate
about order entry\. From my point of view there are two
different requirements/types for an order entry
instruction in general:
1\. This is the ususal order entry process which is
concerned with process execution \(laboratory order
entry\)\. You send an order and get a result\.
2\. This is the scheduling process of order entry\. This
process is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OrderEntry](https://discourse.openehr.org/t/orderentry/15785)
> Dirk
The idea of an order entry is that it is an instruction\. The class
INSTRUCTION is described in the openEHR reference model
RM\.Composition\.Content\.Entry package\. Tom and I have spent a day last week
reviewing this as we have been under some pressure to do so\. The instruction
has a number of features \- state \(as an internal state machine\) and an
action specification as a STRUCTURE\. It is this class that would be used to
specify exactly what is ordered, the state would describe...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [use case documents from the health care domain - ROLES](https://discourse.openehr.org/t/use-case-documents-from-the-health-care-domain-roles/15781)
> Bill Walton wrote:
> The "Health Care Facility Nominated Trusted Clinician" section on page 5
> contains the sentence "This access will be on a 'need to know' basis\." Here
> in the U\.S\., HIPAA has specifically rejected "need to know" as a valid basis
> for access\. A user of the EHR may only access information the patient has
> granted them the right to access\. This complicates Access Control
> considerably since it requires not only control of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[use case documents from the health care domain]](https://discourse.openehr.org/t/use-case-documents-from-the-health-care-domain/14455)
> Forwarded from Arild Faxvaag <arild\.faxvaag@medisin\.ntnu\.no>
Dear all\.
Has someone tried to establish a collection of use case documents with descriptions of information\-related tasks by health care workers?
Would you developers consider it useful if such a collection existed?
kindly regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [use case documents from the health care domain](https://discourse.openehr.org/t/use-case-documents-from-the-health-care-domain/14454)
> Dear all\.
Has someone tried to establish a collection of use case documents with
descriptions of information\-related tasks by health care workers?
Would you developers consider it useful if such a collection existed?
kindly regards
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EHR Confidentiality](https://discourse.openehr.org/t/ehr-confidentiality/15777)
> This message forwarded on behalf of Prof Bernard Cohen:
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [EHR Confidentiality](https://discourse.openehr.org/t/ehr-confidentiality/15780)
> What is the proposed confidentiality model?
How can patients opt out completely from publishing their data on the EHR?
Having opted out, how can they elect to have specific items published?
If they have opted in \(either by default or by selection\) then how can they
elect not to have specific items published?
Bennett\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology requirements UNITS](https://discourse.openehr.org/t/pathology-requirements-units/15770)
> UNITS
There are a lot of units out there \- it has been our idea to build a
constraint model on units based on the property being measured\. A good
example is frequency can be '/\{time unit\}' \(e\.g\. /min, /hr, /s\) or 'Hz'\. It
is hoped that we can translate from one to the other as much as possible on
this basis\.
It has come to my attention just how many units are out there and that some
units are not translatable to another unit even when the property is the
same...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology requirements TEXTURAL RESULTS TO QUANTITIES](https://discourse.openehr.org/t/pathology-requirements-textural-results-to-quantities/15776)
> TEXTURAL RESULTS TO QUANTITIES
The result of this analysis is that sometimes a single leaf in a tree will
be reported as haemolysed rather than its numeric value \- example: the
results of an electrolyte measurement might have safe results for all
analytes apart from potassium \- the result will be 'haemolysed'\. This can
occur in haematology and other situations \- reporting is required for
medicolegal and billing purposes\.
This presents a problem\. We have a number of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology requirements CONTRIBUTION - 2 versions at once](https://discourse.openehr.org/t/pathology-requirements-contribution-2-versions-at-once/15775)
> CONTRIBUTION \- 2 versions at once
There is a particular problem with results that are deemed to be incorrect
as the specimen is damaged \- haemolysed blood samples being the most common
\(See textural results to quantities thread\)\. If the machine read data is to
be preserved in openEHR then this would need to be over written with the
correct result and both compositions saved at the same time \- otherwise some
other agent might base some process on the interim situation where the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology requirements TIMED MEASUREMENTS](https://discourse.openehr.org/t/pathology-requirements-timed-measurements/12081)
> TIMED MEASUREMENTS
The timed nature of specimens is dealt with in the history and event model
of the RM and available in the archetype editor\. This deals with timed
measurements and interval measurements\. The idea of a 21 day progesterone is
covered in state information relating to the time since the last menstrual
period \- BUT there is still the idea of an untimed sequence of events where
the order is critical\. There are also sequenced events when it comes to
looking for stool...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Pathology requirements](https://discourse.openehr.org/t/pathology-requirements/15771)
> Dear all
I had a detailed meeting with Vince McCauley and Michael Legg in Sydney
about a detailed look at how a pathology system might write direct to an
openEHR server\. A number of issues arose that I think we need to look at and
decide how to address\. I will not talk about the specialisation tree of
archetypes proposed, rather the technical issues\.
TIMED MEASUREMENTS
CONTRIBUTION \- 2 versions at once
TEXTURAL RESULTS TO QUANTITIES
UNITS
Have a look at the ones that are of interest...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR: congratulations!](https://discourse.openehr.org/t/openehr-congratulations/15769)
> Dear Thom, Sam, Dipak and Peter,
I congratulate you with the fact that OpenEHR is part of the HealthConnect
context in Australia
OpenEHR is mentioned in the recent "Interim Research Report" on page 21 and
several other places\.
\(http://www.healthconnect.gov.au/consult.html)
For the CEN/TC251 EHRCOM Task Force this will provide a strong support and
motivation to make much progress the next couple of months on the exciting
and important new European, Australian and HL7 standard...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Antw: Re: Open Source EHR at the Americal Academy of Family Physicians ...](https://discourse.openehr.org/t/antw-re-open-source-ehr-at-the-americal-academy-of-family-physicians/15768)
> \-\-\-snip\-\-\-\-
I said clearly that that was a completely naive and inadequate search strategy \- I
was just pointing out that Google is not the right place to look when it comes to
the biomedical literature\.
Evaluation of SNOMED CT and other classifications/terminologies cuts across
many biomedical disciplines, including medical/nursing/public health informatics,
clinical medicine and clinical nursing, epidemiology, computer science etc\. But
not IT\.
Tim C
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Requested Proposal to the US Uniform State Law Committee](https://discourse.openehr.org/t/requested-proposal-to-the-us-uniform-state-law-committee/15767)
> Hi All,
Submitted a request to the Uniform Law Commissioners \(http://www.nccusl.org/nccusl/DesktopDefault.aspx)
to consider a project for ELECTRONIC HEALTHCARE RECORDS\. The next meeting will be in January, 2004\.
If a project is approved the Commissioners will address a Uniform Code for the 50 states in the US for ELECTRONIC HEALTHCARE RECORDS\. Such a project would consider the legal relationship with the federal government and the current state of HIPAA\.
\-Thomas Clark
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Antw: Re: Antw: Re: Open Source EHR at the Americal Academy of Family Physici...](https://discourse.openehr.org/t/antw-re-antw-re-open-source-ehr-at-the-americal-academy-of-family-physici/15766)
> Hi Thomas,
Are you still googling? I understood that Google is setting up a database of all peoples searches and stores it forever for future analysis. But that is hear say from the grapevine.
Have you thought of re-doing your search with health oriented search engines and / or in PubMed? It might be that research is more likely popping up in these databases than in Google.
Just a half Euro cent (With our Dutch queen on one side only).
:-)
William
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Latest ADL (archetype definition language)](https://discourse.openehr.org/t/latest-adl-archetype-definition-language/16700)
> Dear all,
an update of the ADL language for writing archetypes has been posted.
News:
This language is being proposed to CEN for the archetypes facility in its revised ENV13606,
and will be discussed at the CEN TC/251 Aarhus meeting (29/30 September).
It is also being considered for use in the HL7v3 templates work, and was discussed at the
HL7 Memphis WGM (7-12 September).
A clinician's editor is under construction.
Links:
**Language specification**:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [connection between Reference Model and Archetype Model](https://discourse.openehr.org/t/connection-between-reference-model-and-archetype-model/12071)
> > Can anyone post link or a reference to a document that describes connection between Reference Model and Archetype Model\.
'Design Principles' could be something you're looking for\. You can download it
from www\.openehr\.org/Doc\_html/Model/Principles/design\_principles\.htm
openEHR documents also should be of help\. They're closely related to CEN/ENV\.
All of the docs can be found on website www\.openehr\.org\. Specific details
about EHR Reference Model and EHR Archetype...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Contact with VA and Hospital in Portland](https://discourse.openehr.org/t/contact-with-va-and-hospital-in-portland/15761)
> Hi All,
Made contact with VA Hospital in Portland\. This contact is on the operations side of the VA EHR system\. Will seek to expand this to the Project Manager or representative on the design side\.
Rationale:
The new VA EHR system is being proposed as a public standard \(by the VA\), many of the same issues \(e\.g\., privacy and security\) have been addressed, and they handle a lot of Patients\.
Made contact with a local hospital ITG that is currently handling a HIPAA...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New ADL update](https://discourse.openehr.org/t/new-adl-update/15760)
> Dear all,
we have been working hard on ADL recently, and have posted a new manual and new examples\. The software has not quite caught up to the latest changes, so the \.exe and \.html generated output are off the site for the moment, but will return as soon as we have them done\.
See http://www.oceaninformatics.biz/adl.html
Sam Heard, Peter Schloeffel and myself will be at the HL7 meeting in Memphis explaining ADL, and working with various people in HL7 toward harmonisation with other...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Model Code for EHRs](https://discourse.openehr.org/t/model-code-for-ehrs/15764)
> Hi All,
Reviewing model codes for eCommerce and EHRs\. The most advanced appear to be those in the following entities:
\-EU community
\-Australia
\-New Zealand
\-Canada
Note that eCommerce has been included because the goals, objectives, security and privacy concerns closely parallel those for EHRs\.
I plan on extracting portions from the best sources and putting them in a new document\. Modifications will be made\.
The objective is to see if the product is worth anything\.
Would...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Open Source EHR at the Americal Academy of Family Physicians ...](https://discourse.openehr.org/t/open-source-ehr-at-the-americal-academy-of-family-physicians/14451)
> Forgive me for a late comment, but I would like to clear the record at
little concerning hL7\. HL7 is an accredited ANSI body, and follows ANSI
rules\. Itis an organization that is not funded by any outside group\. As
such, the organization deopends on membership for dues to support the
organization\. I agree that totally free standards would be the best, and I
have argued that position within the HL7 Board\. The best I have been able
to do is to get the draft available free\. At the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [What HIPAA means to you - a brief description](https://discourse.openehr.org/t/what-hipaa-means-to-you-a-brief-description/15755)
> Hi All,
The following link is to a FindLaw reference regarding what HIPAA means to Patients:
http://articles.corporate.findlaw.com/articles/file/00081/002452/title/Subject/topic/Health%20Law_HIPAA/filename/healthlaw_1_335
Enjoy\!
\-Thomas Clark
BTW: Refer to the bit ob Marketing
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Uniform Model Code for Electronic Healthcare Records](https://discourse.openehr.org/t/uniform-model-code-for-electronic-healthcare-records/15765)
> HiAll,
Would appreciate responses regarding legislation regardin non\-EU legal codes on electronic healthcare records\. The EU already has a well\-developed set of codes\.
The US seems to be a problem since there are 50 states, a federal government and special jurisdictions\. They do not necessarily agree on all matters\.
The US should have a Uniform Model Code on Electronic Healthcare Records which should be enacted/modified by the various legislative bodies\. Not yet\! Piecing together...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Question re Information Handling in Patient-Provider Contacts](https://discourse.openehr.org/t/question-re-information-handling-in-patient-provider-contacts/15757)
> Hi All,
Great discussions regard OpenEHR and Patient\-Provider contacts\. The question I have is what are the goals and objectives of these Patient\-Provider contacts, especially from an information and systems theory perspective? The focus seems to be mainly on the Provider\.
Information Systems Theory \(Includes Cybernetics, the science of communications and control for\) would address the Patient and Provider as peers and attempt to optimize information flow between both\. It would not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [HL-7 standards [was Re: Open Source EHR at the Americal Academy of Family...](https://discourse.openehr.org/t/hl-7-standards-was-re-open-source-ehr-at-the-americal-academy-of-family/15759)
> Two lessons from a long professional life:
1. Nothing is for free
2. At the end of the day , people understand that it is better to pay for a product or for a
service.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Free text analysis](https://discourse.openehr.org/t/free-text-analysis/15763)
> Hi All,
I would like to ask Gerard Freriks to post some more information on the tool
for free text analysis he mentioned\.
I think there is an influence on any EHR schema \(even when built with
archetypes\) by the way chosen to retrieve the particular fragment of
information\. I also think archetypes could play an important role on future
health\-related free text analysis\. That's why I thought my request was valid
for a post\.
Since this is my first message to the list I think it...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Open Source EHR at the Americal Academy of Family Physicians ...](https://discourse.openehr.org/t/open-source-ehr-at-the-americal-academy-of-family-physicians/15758)
> Dear friends,
perhaps someone of you knows more about this initiative ?
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [list management Q](https://discourse.openehr.org/t/list-management-q/14452)
> Who would prefer that the openehr list manager be changed to the mode where just hitting "reply" always sends back to the list \(i\.e\. the list manager sets 'reply\-to'\)? I for one prefer that, and would like to reduce teh duplicate posts that come with the "reply\-all" method\.
please RESPOND IF YOU WANT IT CHANGED, and if there are a lot of responses, we can get it changed, else it will remain the way it is\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Request for Comments - Medication Management](https://discourse.openehr.org/t/request-for-comments-medication-management/14448)
> Dr Rusty Maynard has posted a Request for Comments document concerning
open source medication management\. Specifically in TORCH but in a broad
general sense this paper applies to all open source healthcare
applications\.
A copy of his email announcement and \(link to the paper\) is
here:http://www.openparadigms.com/News_Item.2003-08-05.1151
Regards,
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Distributed Records - An approach](https://discourse.openehr.org/t/distributed-records-an-approach/15753)
> Thomas,
This sounds workable to me\. If I am understanding you correctly, we
need one \(and only one??\) registry in which anyone, anywhere \(who is
authorized, of course\) could look up a patient and determine which
"region" had master control at the moment over his record\. If I'm a
provider living in the region where the records are primarily managed,
then when my system attempted to look up, say, the date of his last
Tetanus vaccination, it would find it immediately\. If...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New archetype language](https://discourse.openehr.org/t/new-archetype-language/15752)
> Dear colleagues,
over the last six months or so, Ocean Informatics has been working on a new language for expressing archetypes \- Archetype Definition Language\. This is an evolution of the formalism presented at the HL7 WGM in Cleveland in May this year, and at the CEN TC251 meeting in Oslo a few weeks later\.
The work to date has been posted at http://www.oceaninformatics.biz/adl.html. The page includes a detailed manual describing the language, some example archetypes written in ADL,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [certification and verification of OpenEHR](https://discourse.openehr.org/t/certification-and-verification-of-openehr/14449)
> Hi All,
Been off looking at some operational considerations associated with
supporting, maintaining and updating global EHRs\. The following types of
users were considered:
1\)CREATORS
\-individual, groups or organizations that must, or want to, generate new or
updated EHRs
2\)REVIEWERS
\-overseers, peers and formal reviewers
3\)ADMINISTRATORS
\-Data management/processing
4\)CERTIFIERS
\-Handles tasks associated with correctness, e\.g\., prior to use or archiving
There has to be user...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Family relationships](https://discourse.openehr.org/t/family-relationships/15754)
> After studying the openEHR demographic model, I am stuck now in the section about demographic relationships\. Until now my objective for incorporating family relationships into the EHR was to add an interface at the family history archetype, i\.e\. in the Evaluation Concept for Family History\. However it seems to me that I have two possibilities representing family relationships, either through the Family History archetype \(inside the EHR\) or through the demographic model \(outside the...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Patient Privacy: Impact of Outsourcing](https://discourse.openehr.org/t/patient-privacy-impact-of-outsourcing/15750)
> Hi All,
The following link is to an article appearing in the San Francisco Chronicle
online version, May 14, 2003 entitled:
LAZARUS AT LARGE
Kaiser exporting privacy
http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2003/05/14
/BU307139\.DTL&type=tech
Unfortunately this has been predicted by many\. Rushing out to contact
members of the US congress requesting a new privacy and security bill would
be too late and probably wasted effort\. It should highlight the need...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Introduction and question](https://discourse.openehr.org/t/introduction-and-question/15748)
> Dear list members,
My name is Remko Nienhuis and I am currently working for a small Dutch company named 2Cure, which is an international medical software supplier. At this moment, my major goal in life is understanding the OpenEHR design paradigm and reference models and the way it can or will influence futureous developments on our products. I started studying OpenEHR just a couple of weeks ago, so despite the great documentation, there is still a lot to learn.
One of the things I do not...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [NIST: Automated Security Assessment Tool; need something similar](https://discourse.openehr.org/t/nist-automated-security-assessment-tool-need-something-similar/15751)
> Hi All,
The following is a link to the NIST Automated Security Assessment Tool\.
For OpenEHR one tool will be insufficient\. Something similar is feasible for
the
low\-level \(network/system\) OpenEHR project\.
http://csrc.nist.gov/asset/
\-Thomas Clark
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Updates to the openEHR site](https://discourse.openehr.org/t/updates-to-the-openehr-site/15749)
> Hello
The openEHR website at www\.openehr\.org has new information that you might find of interest, including:
An important announcement about the formation of the openEHR Foundation as a not\-for\-profit company limited by guarantee;
The latest Reference and Archetype model specifications;
Additional explanatory material about Archetypes;
Improved navigation for new visitors\.
With best wishes
David
\* David S\.L\. Lloyd, Technical Consultant
\* CHIME \- Centre for Health...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [interesting article](https://discourse.openehr.org/t/interesting-article/16628)
> Thought some of you might find the article at the link below interesting re: the increased realization of the need for interoperability in medical records systems.
[http://www.baselinemag.com/article2/0,3959,1054863,00.asp](http://www.baselinemag.com/article2/0,3959,1054863,00.asp)
Best regards,
Bill
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [genetics_insurance](https://discourse.openehr.org/t/genetics-insurance/15746)
> Quality is and will remain a key issue for OpenEHR\. The following
link points to a workshop held by the Genetic Interest Group\.
Interesting discussion on relevance; interesting comments on expert
opinion; probably due to the close working relationships with
the law industry that loves inconsistency in medical records\.
http://www.gig.org.uk/docs/genetics_insurance.pdf
\-Thomas Clark
[details="(attachments)"]
[genetics_insurance.url|attachment](upload://zK2NIT2R4d92PXn5QRjPtlYVd7o.url)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [BioMed Central Full text Quality and correlates of medical record documentati](https://discourse.openehr.org/t/biomed-central-full-text-quality-and-correlates-of-medical-record-documentati/15744)
> Follow\-up to the prior posting on lack of in\-depth research on the content
quality of paper and electronic medical records\. Interesting link:
http://www.biomedcentral.com/1472-6963/2/22
Conference discussion groups are more direct\. Some reluctance to openly
discuss shortcomings of another Practitioner's charting and reporting\.
\-Thomas Clark
[details="(attachments)"]
[BioMed Central Full text Quality and correlates of medical record documentation in the ambulatory care...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Envisioning the National Health Care Quality Report -- Executive Summary](https://discourse.openehr.org/t/envisioning-the-national-health-care-quality-report-executive-summary/12045)
> The following link points to a book on the 'National Healthcare Quality
Report", Institute of Medicine:
http://www.nap.edu/execsumm/030907343X.html
It might be helpful at the local as well as the national level\. I have
doubts\.
\-Thomas Clark
[details="(attachments)"]
[Envisioning the National Health Care Quality Report -- Executive Summary.url|attachment](upload://rO9noSPJPpZGDbf3IWASgaQIoo9.url) (157 Bytes)
[/details]
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [US Gov Report: Quality](https://discourse.openehr.org/t/us-gov-report-quality/12044)
> The following link points to a US report on quality\. Not definitive research
but perhaps useful:
http://www.hcqualitycommission.gov/final/chap01.html
\-Thomas Clark
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Encoding concept-relationships in openehr archetypes.](https://discourse.openehr.org/t/encoding-concept-relationships-in-openehr-archetypes/14459)
> Dear Tom et al:
This is my "de\-lurking" for the list\. For those of you who dont' know me, I'm
a computing academic whose area of interest will be adequately characterised by
my question\.\.\.
I'm trying to represent the structure of "normal" values of fields in
archetypes\. I can see that there is of course some provision for a set of
allowed values, a default value and \(in quantities\) min and max\. I want to go
further \(because the information could...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Record Level Data Security; storage plus fixed and mobile transmission](https://discourse.openehr.org/t/record-level-data-security-storage-plus-fixed-and-mobile-transmission/15742)
> Security begins at the data storage level\. Unless it can be protected at
this level more sophisticated techniques applied to transmission and content
will not be as effective as desired\.
Three common approaches are:
1\)Data security
2\)Data management and
3\)Access to storage media\-resident data, e\.g\., somebody's disk drive
These can occur long before access security is needed in a Healthcare
environment, but are also appropriate for data storage and access within a
Healthcare...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [GEHR philosophical background info](https://discourse.openehr.org/t/gehr-philosophical-background-info/14458)
> Hi Sam,
> > BW: This is a really interesting problem space to me. I've been studying HIPAA (the Health care Information Portability and Accountability Act) and have become fascinated with the discussion over how best to balance the needs of the various parties involved in the provision and payment of healthcare services so as to improve the quality and decrease the cost of health care here in the U.S.. Talk about a non-trivial problem! Interestingly, it looks to me like all the nonsense can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [EPR vs. EHR](https://discourse.openehr.org/t/epr-vs-ehr/15741)
> Hi Sam,
> > BW: What's an EPR, what's in it, and what, if any, information overlap does it have with an associated EHR? You introduce EPR in the first example, but there's no definition provided and no reference to an external source.
> SH: Again, we have had a lot to say about this over the years. In openEHR - it is the EHR - so the boundary is the model itself. There is a real problem in the federated approach with addressing this - but I think openEHR gives a clean approach.
I just want...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [normalizing access vs. normalizing denial (was openEHR security)](https://discourse.openehr.org/t/normalizing-access-vs-normalizing-denial-was-openehr-security/15740)
> HI Sam,
> > BW: Related to all of the above, it seems like there are probably a number of circumstances that would require that the control of the Access Control list itself be capable of being over-ridden or delegated. It looks to me like, as currently defined, the only roles that could grant access would be the patient and Next of Kin roles. But assume, for example, that a patient is hospitalized, needs a test performed that can't be performed in the facility, and has designated a Next of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [4th Libre Software Meeting 2003](https://discourse.openehr.org/t/4th-libre-software-meeting-2003/15737)
> Dear Colleague,
We think it would be interesting for you to know that the "4th Libre
Software Meeting 2003" will be held from July 9 to July 12, in Metz \(east of
France, near Germany, Belgium and Luxembourg\)\.
Therefore, I would like you to consider the possibility of participating in
the section for medicine\. The aim of this conference is to present, explore
and evaluate the effects of the integration of the developing with the Libre
Software Health Care Systems \(LSHCS\)...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR security](https://discourse.openehr.org/t/openehr-security/15743)
> I apologize for not having had the time to dig in and find this out for myself yet, but I'd really appreciate it if someone could tell me if security has been addressed in the openEHR architecture and, if so, point me to the documentation. I'm trying to understand the system's capabilities to limit access not only to authorized individuals, but also to limit the access of authorized individuals to specific subsets of an individual's record. Thanks in advance for showing me where to dig.
Best...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [VistA knowledge / comments](https://discourse.openehr.org/t/vista-knowledge-comments/15739)
> Is anyone here familiar enough with the open source VistA system here in the U.S. to offer any comments about it in general and specifically about it's storage subsystem? There's info on VistA at [http://www.va.gov/vista_monograph/](http://www.va.gov/vista_monograph/)
Thanks,
Bill
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New archetypes language paper available](https://discourse.openehr.org/t/new-archetypes-language-paper-available/15734)
> Dear all,
there is a new paper on "A Shared Language for Archetypes and Templates" available at http://www.deepthought.com.au/health/archetypes/archetype_language_2v0.6.2.doc
The language described is a syntax equivalent of the openEHR archetype models being developed \(you can see drafts on the Specification pages at http://www.openehr.org\), but is more general, and could potentially be used for HL7 CDA and CEN 13606\. It is hoped that it will stimulate some debate and progress...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OCL (was: Introducing myself + question)](https://discourse.openehr.org/t/ocl-was-introducing-myself-question/14450)
> Hi Thomas,
I appreciate the trouble you've taken to evaluate OCL, and think several
of the issues are worthy of consideration\.
Just for your information, and for others on this list, the latest
version of the OCL 2\.0 submission is 1\.6 \(as opposed to 1\.0 you reviewed
which is 2\.5 years old\!\)\. This is due to be adopted later today, as it
happens\.
Despite the imminent adoption it is still possible to submit issues to
OMG's Finalization Task Force which is responsible for...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Common RM](https://discourse.openehr.org/t/common-rm/14780)
> These comments refer to V1\.4\.2
3\.1 The class Locatable has a name, which is of type DV\_TEXT\.
DV\_TEXT seems inappropriate here, it includes formatting,
hyperlinks, coded values, etc\. I would've thought that string
was appropriate?
actually, this comment also applies in many other places when
DV\_TEXT is used\. Other cases are the names of the items in
a LIST\_S, and the use of DV\_CODED\_TEXT for a null flavour
Grahame
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data Types RM](https://discourse.openehr.org/t/data-types-rm/15736)
> These comments relate to v1\.7\.1
Section 4\.2 DV\_BOOLEAN\. are the values \{true, false\}
case sensitive? Generally, is openehr case sensitive
or not?
Section 5\.1\.1\. Terminology Id's \- this section doesn't
seem consistent with the Terminology section of
the external package\. Also, terminology versions
aren't included, but this is usually important
Section 5\.1\.5\. includes the following example:
blah blah Ross River infection blah blah blah bronchial...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [External Package](https://discourse.openehr.org/t/external-package/15276)
> Some questions from the External package \(v0\.9\)
section 4\.1: assumed types\. This section is very brief\. It's
a bit of an odd section, as important things are left
unstated \(i\.e\. what are the expectations of whitespace for
the STRING type?\) while trivial things such as cummutivity
of \+ are defined\.
section 5\.3\.1, namespace\. Why doesn't the valid namespace
character set include such characters as :/&\+ that are
valid in URI's?
section 5\.3\.2 & 5\.3\.3:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Intro & Questions: null](https://discourse.openehr.org/t/intro-questions-null/15735)
> Hi all
I have a series of questions about OpenEHR, but I should start with
an introduction\.
I am a software engineer for a health systems vender\. I am currently
implementing something that looks a whole lot like archetypes\.
I'm currently evaluating OpenEHR to see how much of the thinking or
specifics I can use, with the intention of long\-term harmonisation
with OpenEHR\. I'm also an editor of the HL7 V3 data types specification\.
And sadly, my first question relates to data...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR roadmap](https://discourse.openehr.org/t/openehr-roadmap/15732)
> It occurred to me after the recent exchanges that there may be some people out there who do not realise something basic about openEHR, which is that it is working at two levels\. The first level is "abstract specifications" \- i\.e\. the technology\- and platform\-independent specifications mentioned by Dave and Tom C\. earlier\. The specifications which you see on the openEHR website \(Documentation>specifications\) are all in this category \(these will all be upgraded...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Introducing myself + question](https://discourse.openehr.org/t/introducing-myself-question/15733)
> Dear list members,
my name is Vincenzo Della Mea, I'm researcher \(Medical Informatics\) at the University of Udine, Italy, with interests until now directed to telemedicine\.
I'm investigating now how to use OpenEHR as a teaching aid for a Medical Informatics course: as a model, I think is very well developed and educational for what regards the correct implementation of EHRs\.
So, my question is: I read on the web site that there will be some Java implementation available sooner...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Terminology Definitions in Support Package](https://discourse.openehr.org/t/terminology-definitions-in-support-package/15723)
> This question is regarding Section 3\.1 in the Support Package\.
I am using v0\.9
The terminology definitions feel a little incomplete\.
The lists of strings given are reasonable, but the
way the namespaces\(?\) are used seems a little slippery,
and there is no consistency with regard to versioning
in the list\. Am I looking for too much from these
definitions?
I would propose UCUM for Terminology\_id\_Units\_of\_measure\_properties\.
ref: http://aurora.rg.iupui.edu/UCUM
Grahame
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [Syntax and Semantics](https://discourse.openehr.org/t/syntax-and-semantics/15718)
> > <http://www.idealliance.org/papers/xml2001papers/slides/De%20Grauw/05-
04\-01\.ppt>
Thanks for this\. My favourite quote from it:
1 The naive approach \[to interoperability\]
Make a new vocabulary
Make it real real real good\!
Make everybody use it\!\!\!
\[The author then gives examples involving delivery v\. billing addresses
in invoicing sytems: not perhaps the toughest problem...
**[Clinical (archive)](https://discourse.openehr.org/c/clinical-archive/153)** - [need to do something to understand and then hopefuly get involved in the open EHR community](https://discourse.openehr.org/t/need-to-do-something-to-understand-and-then-hopefuly-get-involved-in-the-open-ehr-community/14457)
> I think this community looks very interesting byt need a crash cource in order to learn the "tribe language" and what open EHR is all about\.
I am a physician and has hence approached the field of medical informatics and medical records standardisation from the clinical wiew\.
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Arcetypes and care plans](https://discourse.openehr.org/t/arcetypes-and-care-plans/15707)
> \-\-\-\-\-\-\- Begynnelse på videresendt beskjed \-\-\-\-\-\-\-
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Ontology Standard for Archtypes](https://discourse.openehr.org/t/ontology-standard-for-archtypes/15704)
> Hello All,
I was just looking over W3C's Ontology Web Language \(OWL\), and was
wondering if anyone had thoughts on the subject as it related to
openEHR\.
Should openEHR archetypes be modeled using OWL or another "standard"
syntax?
If openEHR archtypes are compatible with a standardized ontology
description language, then generic ontology viewing and manipulation
tools could be used on them\.
Perhaps the alternative of converting openEHR archetypes into OWL
representations...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Paper on shared archetype formalism](https://discourse.openehr.org/t/paper-on-shared-archetype-formalism/15694)
> Dear all,
I have posted a draft of a paper on how to approach a shared archetype/template formalism which will work for all stakeholders interested in producing such arctifacts\. See http://www.deepthought.com.au/health/archetypes/archetype_language.doc.
Although this work is unfinished, we have decided to publish a version now, before the HL7 San Antonio meeting, so that people participating in the relevant HL7 groups might have time to read it and comment\. I will not be there personally,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Christmas wishes](https://discourse.openehr.org/t/christmas-wishes/15692)
> To everyone out there on the openEHR technical list, I would like to wish
you all well over the Christmas break\.
I would especially like to thank Tom Beale for his many many hours of hard
work on all the openEHR documentation this year and I would also like to
thank all the usual suspects, including Dipak Kalra, Sam Heard and Peter
Schloeffel for their many contributions to openEHR over the last year\.
I am looking forward to an even better year in the openEHR space in the
new...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR XML schemas](https://discourse.openehr.org/t/openehr-xml-schemas/14444)
> Hello All,
I am curious if anyone has made progress on developing openEHR XML
schemas\. The current documentation describes the openEHR theory and
various relevant models quite well, but there are no references to
standard document formats\.
In order to build interoperable openEHR systems there must be a standard
XML schema for archetypes, EHR\_EXTRACTS, and EHRs \(including their
encapsulated TRANSACTIONs, CONTENT, etc\.\)\. I think compatibility with
HL7 CDA schemas should also be a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [[Subject of care]](https://discourse.openehr.org/t/subject-of-care/15696)
> I am forwarding this to the list, since I think this is an important discussion\.
Sam Heard said:
Tom
The donor is definitely anonymous in most settings\. The fetus can be part of the mother \- this is a bit like the local terminologies in archetypes \- we need a way of saying that the relationship is the only defining feature and there is no ID\.
Cheers, Sam
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Introduction](https://discourse.openehr.org/t/introduction/12025)
> Hi to the list,
My name is Philippe AMELINE, and I am the leader of the french project Odyssee and manager of a small company named Nautilus\.
Inside Nautilus, we have been working for several years on the way ontologies can allow large scale sharing of medical datas in order to adress continuity of care\.
The open source Odyssee project has been built in order to have these techniques become a genuine system\.
We are currently working on several knowledge management domains : ontologies,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Categorising EHR Content](https://discourse.openehr.org/t/categorising-ehr-content/15693)
> Aniket,
I have refreshed myself on openEHR's clinical model
terminology, but I still think you miss my point\.
openEHR has three types of EHR\_Entry, namely
OBSERVATION, EVALUATION, INSTRUCTION\.
I am using "event" in the natural language context,
rather than the hijacked Event Summary context\. My
"event" refers to a non\-care event \( predominantly \)\.
Such "events" do not fall under any of the 3 EHR\_Entry
subclasses\. Some examples:
a\. heart...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Model CEN/TC251 13606](https://discourse.openehr.org/t/model-cen-tc251-13606/14445)
> Dear colleagues,
The last week I had a discussion with some colleagues of me at TNO\.
They studied the OpenEhr proposal for a model for the EHR\.
It is their opinion, and I agree with it, that the Kernel is not generic
enough because it contains things like the structure of the document
\(folder, transaction, etc\)
Even things like an organiser archetype must become a real archetype and be
not a part of the kernel\.
With regards,
Gerard
\-\- <private> \-\-
Gerard Freriks,...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Subject of care](https://discourse.openehr.org/t/subject-of-care/14447)
> Dear all
I have been reviewing the subject of care \- over family history\. It is clear
that the following information is potentially useful:
1\. The name of the person so you can refer to them as so\-and\-so
2\. The relationship \(father, mother\) this might or might not include their
genetic relationship \(adoptive\) \- at present I have this in the genetic
relationship boolean value of the family history problem\. I think this is
the most appropriate as it is the only time when it is...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [No known allergies](https://discourse.openehr.org/t/no-known-allergies/15685)
> Dear all
Another issue that is coming up at the moment\. In the EHR recording or
clinical models ontology I have proposed that all allergies be recorded
under the ehr://persistent transactions \(Fld\)/Therapeutic precaustions
\(Tx\)/Known allergies \(Org\) as openEHR\.evaluation\.allergies\. The issue is how
do we know that the organiser is empty because the patient has been asked
about this?
I would propose that we have an 'Empty' entry that is generic and can be
used to show that...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Action specifications](https://discourse.openehr.org/t/action-specifications/15690)
> Dear All
In developing an ontology for health record recordings \- an archetype
ontology \- I have come to the idea that there is a great deal of utility in
the idea of an 'action specification'\. This is the part of an instruction
that says what to do \- not when \(or under what conditions\) to do it\.
Let me give you an example:
A medication order is an instruction:
medication=Amoxycillin: dose=250mg: route=IV: frequency=three times...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Terminology services](https://discourse.openehr.org/t/terminology-services/15691)
> Dear All
There has been an intense discussion \- mainly Tom Beale and Matthew Darlison
going on off line\. I want to share some of my views with others on the
approach to terminologies\. I will deal with them one at a time\.
1\. Language and terminologies\.
It is clear that we need to know what language we are working in to ensure
that the rubric or phrase returned by the terminology service is
appropriate\. I have proposed in our GEHR work that this is kept at the level
of a transaction...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New openEHR site](https://discourse.openehr.org/t/new-openehr-site/15683)
> Dear openEHR participant
I am pleased to announce the newly\-designed site for openEHR, still at the same URL:
http://www.openehr.org \.
You will find there a new membership section, which I would ask you to use to sign up as a Member of openEHR\. Please also use the membership facility to control your subscription to the three mailing lists in future\. To make it easy for existing subscribers to the lists, you will get a simple confirmation that you are already on a list if you check its...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Patient notifications](https://discourse.openehr.org/t/patient-notifications/15687)
> Dear All
I have been developing the idea of part of the record that the patient can
write in \- I have \(Gates style\) called it My Folder \(eh?\) and have two
subfolders in it at present \- consent statements \(as these will be written
by the patient\) and appointments and notifications\.
It is clear that the patient needs to write and interact with these\. I have
thought recently that we may be best to develop a transaction for each of
the patient notifications \- which will have all the...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [New paper on Archetypes](https://discourse.openehr.org/t/new-paper-on-archetypes/15684)
> Dear all,
I have written a new paper on archetypes \(only 17 pages\) at the request of Dr Haim Kilov, for the workshop he is running on Behavioural Semantics at OOPSLA 2002\. It is available at http://www.deepthought.com.au/it/archetypes/archetypes_new.pdf.
I hope it will help to clarify some of the complexities of the idea from the original paper, which itself is being rewritten\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Archetype rules (invariants) in openEHR RM?](https://discourse.openehr.org/t/archetype-rules-invariants-in-openehr-rm/14443)
> Hello all \- I'm new to the list, pls b kind\!
My research group here in Italy is looking to combine an openEHR
archetype\-based design with XUL/Mozilla/XML technology to produce
a prototype electronic patient record system accessible via web clients
of a certain degree of sophistication\.
We've been happily designing archetypes using the DSTC Archetype
Editor and we've been able to "compile" it's output into XUL front\-ends
in an automated scheme that involves...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [openEHR "Silver" Model](https://discourse.openehr.org/t/openehr-silver-model/15686)
> Hi All,
I know this is probably a very politically sensitive topic, but I am
wondering what the path forward for harmonization of openEHR with CEN
13606\. I was talking to Peter Schloeffel yesterday and Peter mentioned
that there are three options:
\- the "bronze" option, which involved fixing a couple of things in the
existing CEN model and adding archetypes to it\.
\- the "silver" option, which simplifies and modifies openEHR and uses that
as a...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_WORLD_TIME and timezone](https://discourse.openehr.org/t/dv-world-time-and-timezone/15688)
> A few weeks ago, we inserted the class DV\_WORLD\_TIME into the data types, as a parent of all date & time types measuring real world \(absolute\) time, i\.e\. all of the types except DV\_DURATION which just measures a time difference or length, however you like to think of it\.
Currently DV\_WORLD\_TIME has only one feature of its own \- timezone:DV\_DURATION\. \(To see a UML diagram of what I am talking about, go to section 6\.1 of...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [OpenEHR Data types new draft](https://discourse.openehr.org/t/openehr-data-types-new-draft/15677)
> Dear all,
\[people waiting for the next "official" release of the openEHR data types can ignore this message\]
New versions of draft proposals for the openEHR Data Types are posted at:
\- no change bars \- http://www.deepthought.com.au/health/openEHR/data_types_1_5_3_clean.pdf
\- with change bars \- http://www.deepthought.com.au/health/openEHR/data_types_1_5_3_change_bars.pdf
From the revision history for the latest version:
Further corrections \- removed derived '/'...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data Types RM document replaced](https://discourse.openehr.org/t/data-types-rm-document-replaced/15682)
> Dear all,
the Data Types RM document I put up yesterday was damaged, and has been replaced\.
See http://www.deepthought.com.au/health/openEHR/data_types_1_5_2.pdf
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New EHR reference model draft](https://discourse.openehr.org/t/new-ehr-reference-model-draft/12010)
> Dear all,
a new draft of the openEHR EHR reference model is available at http://www.deepthought.com.au/health/openEHR/rm/ehr_rm_3_3_1.pdf.
While there is still a lot of work to do, the models are solid enough to start being used\. The main change from previous versions is the addition of a Change\_control cluster to define the semantics of versioning generically, and the use of these semantics for versioning of Transactions\.
All comments welcome\.
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New Data Types draft + open questions](https://discourse.openehr.org/t/new-data-types-draft-open-questions/16626)
> Dear all,
A new proposed draft of the openEHR data types is available at http://www.deepthought.com.au/health/openEHR/data_types_1_5_2.pdf. This draft includes a major rewrite of the explanation of text types \(plain text, coded text and friends\)\. The model is not drastically different, apart from the addition of a new attribute in DV\_TEXT called mappings\. This is an important attribute, as explained in the text, and covers the semantics of classifying terms, equivalents \(HL7...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [new data type class proposal](https://discourse.openehr.org/t/new-data-type-class-proposal/14446)
> Naturally just as we have released a version of the data types, I realised there was a class which should have been included\!
I propose to add an abstract parent of the classes DV\_DATE, DV\_TIME, DV\_DATE\_TIME, called DV\_REAL\_WORLD\_TIME\. Its only features at the moment are timezone: DV\_DURATION, and the invariant for timezone guaranteeing that it is within \-1200 \- \+1200\. The reasons I propose to add it are:
\- it captures the timezone and any other real world time characteristic...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [Latest openEHR data types 1.41](https://discourse.openehr.org/t/latest-openehr-data-types-1-41/12009)
> Dear all,
please find the latest openEHR data types specification at http://www.openehr.org/productDT.htm. Changes since the last posted version are:
1\.41 Changes to DV\_ENCAPSULATED, DV\_PARSABLE invariants\.
1\.4 DV\_ENCAPSULATED\. text\_equivalent renamed to DV\_ENCAPSULATED\.alternate\_text\.
Added invariant for QUANTITY\.precision\.
1\.3 Added timezone to DV\_TIME and DV\_DATE\_TIME and sign to...
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [openEHR compared to ISO TC 215 WG1 EHR requirements](https://discourse.openehr.org/t/openehr-compared-to-iso-tc-215-wg1-ehr-requirements/15673)
> Dear all,
a document comparing the openEHR models and the current version of the ISO TC 215 WG1 EHR requirements \(ISO TR 18308\) can be found on the openEHR website at http://www.openehr.org/ISOAdHoc.htm
This will act as a guide to anyone trying to determine the comprehensiveness and other qualities of the openEHR models\.
Note: this document has been authored by openEHR, so we do not claim it is "independent"\. However, since it is early days, it is doubtful if there is any...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [New data type issue to think about from HL7](https://discourse.openehr.org/t/new-data-type-issue-to-think-about-from-hl7/15679)
> Here is a possible new data type being suggested in HL7, which looks real enough to me\. Original post from Lloyd McKenzie \(HL7 MnM list\) below\. I would not agree with the exact model he has proposed \(modified CE/CD\) but rather a new subtype of CV, or what we call CODED\_TEXT in openEHR \(what was called TERM\_TEXT\)\.
It seems reasonable that we use the coding aproach to represent error or other short messages, including with the idea of parameters, since a\) we want the same language...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [language translation](https://discourse.openehr.org/t/language-translation/14767)
> I have just been contemplating the ISO requirement:
STR4\.6 The EHRA must support the identification of information that has been translated from the language in which it was originally recorded\. Such identification must describe the faithfulness or reliability of the translation\. \(1\.4\.3\)
We have previously said that a new TRANSACTION would be created for the purposes of translation\. Let's imagine that it is necessary to have a portuguese translation of the current Care Plan...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Subject header for this list](https://discourse.openehr.org/t/subject-header-for-this-list/15676)
> Hi all,
May I suggest that if this list can add a prefix to the email's subject line? eg\. \[OpenEHR\-Tech\] <subject>
I am not sure about the rest of you, but this would certainly make my life easier in sorting my incoming email\.
Thanks,
Eddy
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [proposal for contributions](https://discourse.openehr.org/t/proposal-for-contributions/15672)
> A proposal for changes to the modelling of TRANSACTION in the openEHR reference model, based on a more formal notion of contributions, and some corrections of current models can be found at: http://www.deepthought.com.au/health/openEHR/rm/contrib.pdf
For those interested, please review and post any comments\.
regards,
\- thomas beale
**[Announcements (archive)](https://discourse.openehr.org/c/announcements-archive/155)** - [How to remove yourself from openEHR lists](https://discourse.openehr.org/t/how-to-remove-yourself-from-openehr-lists/15671)
> Dear all,
there are apparently a number of people subscribed to one or more of the openEHR mailing lists who do not want to be\. This is probably because some existing mailing lists were converted automatically to openEHR\. Our apologies to those people who were unexpectedly subscribed\.
TO UNSUBSCRIBE:
To stop receiving messages from the OPENEHR\-ANNOUNCE list send a message to majordomo@openehr\.org <mailto:majordomo@openehr.org> with "unsubscribe openehr\-announce"...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Emailing: _0125.htm](https://discourse.openehr.org/t/emailing-0125-htm/15675)
> I think we need a definition of accuracy and precision \- I think it is the
last one in the precision definitons that we are looking for\.
I think that standard error is what we mean by accuracy?? if it is \- what is
the correct expression \- I do not think it has units\.
Cheers,,Sam
Sam
[details="(attachments)"]
[_0125.htm|attachment](upload://4lj7f4HJ06p45iWp7fLv73bCWi8.htm) (636 Bytes)
[/details]
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [data types - QUANTIFIED.accuracy](https://discourse.openehr.org/t/data-types-quantified-accuracy/15674)
> Currently we define DV\_QUANTIFIED\.accuracy as a DV\_QUANTITY\. This means that the accuracy itself can be a quantity just like the quantity referring to it, e\.g\. 85kg \+/\- 2kg, or it can be a percentage, e\.g\. 85kg \+/\- 2%\. Note that the former is absolute \(doesn't change with the magnitude of the value\) and the latter is proportional \(does change\)\. There is an argument that says that only percentages are ever really needed\. If so, this would simplify the model, since we can...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [contributions part 2](https://discourse.openehr.org/t/contributions-part-2/15668)
> I meant to say that an improved discussion of contributions is in section 5 of the draft of the next version of the rference model, at http://www.deepthought.com.au/health/openEHR/rm/ehr_rm_3_2draft.pdf
\- thomas beale
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [The concept of contribution](https://discourse.openehr.org/t/the-concept-of-contribution/14441)
> In the current issue \(3\.11\) of the EHR reference model, we have documented the concept "contribution" as being that collection of TRANSACTIONs corresponding to a single clinical session\. That is to say, due to a patient contact, there could be the following new TRANSACTIONs:
\- patient contact \(this causes a new VERSIONED\_TRANSACTION\)
\- update to family history transaction \(new version in existing VERSIONED\_TRANSACTION\)
\- update to current medications \(new version in...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [TBD_10](https://discourse.openehr.org/t/tbd-10/15666)
> Suggestion: Send DV\_PHYSICAL\_DATA to the bit bucket\.
I agree that those instances should be archetyped\.
Tim Cook
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [DV_ENCAPSULATED](https://discourse.openehr.org/t/dv-encapsulated/15667)
> Is there supposed to be an attribute for 'is\_expanded' ?
Tim Cook
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Data Types](https://discourse.openehr.org/t/data-types/14440)
> DV\_PARTIAL\_DATE \- Purpose: Incorrectly assumes that a 'day' is
unknown with a known or unknown month\.
It is very realistic to see a situation in which a person will
recall that something occurred on the 1st of the month 10 years ago
but cannot recall if it was June or July\. People relate things in
their life and if an event is recurrent on a specific day of the
month they will recall that though they may have no reference to
which month it was\.
DV\_PARTIAL\_TIME \- Purpose:...
**[Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)** - [Format for openEHR](https://discourse.openehr.org/t/format-for-openehr/16627)
> I think so, and we've undertaken first steps in realising the
"vocabulary" transfer\.
Best regards
Bernd
sradford@agora\.co\.uk wrote:
| | | | |