openehr / adl2-core Goto Github PK

There is a problem with merge of parent-child archetype. This is related to element with CHOICE.

One example is the two archetypes:
openEHR-EHR-CLUSTER.amount.v1
openEHR-EHR-CLUSTER.amount-range.v1

I think the problem is related to the following method in org.openehr.adl.flattener.ArchetypeMerger:
...
@nullable
private CObject findSpecializedConstraintOfParentNode
...

I found a solution for the archetypes above, but that introduced failure on other tests. The proposed fix was to check for both nodeId and rmTypeName.

I am still looking on this.

Sorry for asking a question in probably improper place.
In the openehr/java-libs project (related to ADL 1.4 and OET) written by Rong Chen I see the SkeletonGenerator class. Do you have something similar for ADL 2?

I installed the project with maven and then I load libraries to a new simple project which I am trying to compile.

(https://cloud.githubusercontent.com/assets/6311636/10074405/686a4dcc-62d8-11e5-9130-c6e84e242cae.jpg)

Then, I read the manual
(https://cloud.githubusercontent.com/assets/6311636/10074413/7e53fcd2-62d8-11e5-8dc6-749bdd9eb875.jpg)

and I am trying to create a very simple project, so:
(https://cloud.githubusercontent.com/assets/6311636/10074435/91139a3a-62d8-11e5-9894-9df379356e60.jpg)

Then I understood that new AdlDeserializer(new OpenEhrRmModel()); creates the error and I do:
(https://cloud.githubusercontent.com/assets/6311636/10074441/a0e11398-62d8-11e5-8440-233be31c5215.jpg)

but I still have error on running this simple project.

Is it easy to give me instruction on how to use this adl parser and what am I doing wrong?

Thank you very much,

I am not sure what is correct with this.

I trying to serialize the Blood Pressure archetype which has an Interval Event.

INTERVAL_EVENT[at1042] 
.... 
width matches {
    DV_DURATION matches {
        value matches {|PT24H|}
    }
}

This is what gets generated:

width matches {
    DV_DURATION matches {
        value matches {[PT24H,PT24H]}
    }
}

The generation of the text {[PT24H,PT24H]} is done in org.openehr.adl.am.mixin.IntervalMixin.
Is this a bug in the IntervalMixin or should the DV_DURATION be treated different in this case?

I am not sure

It seems some of the newer description info is not being parsed such as ip_acknowledgements, custodian_namespace, etc...

I could be a good idea to use some kind of CI tools, TravisCI for example.
It's free for public repositories and can run the tests for all pull requests and pushes to the repository.

Hi
Thanks for the great project.
I just started to look at it. I have done two things:

1. Imported the project into a Jenkins build server on Linux. It worked fine
2. Imported the project on my Windows laptop. One test failed.

The test that failed is:
org.openehr.adl.flattener.OperationalTemplateBuilderTest#testOntologyMerge

The problem is that the order of ComponentOntologies is wrong. The original test is:

assertThat(template.getComponentOntologies().get(0).getArchetypeId()).isEqualTo("openEHR-EHR-COMPOSITION.root_use_archetype.v1");
assertThat(template.getComponentOntologies().get(1).getArchetypeId()).isEqualTo("openEHR-EHR-EVALUATION.alert.v1");

This failes.
But if I change order (like below) the test is ok:

assertThat(template.getComponentOntologies().get(1).getArchetypeId()).isEqualTo("openEHR-EHR-COMPOSITION.root_use_archetype.v1");
assertThat(template.getComponentOntologies().get(0).getArchetypeId()).isEqualTo("openEHR-EHR-EVALUATION.alert.v1");

I will do some more testing to see how this happens.

PS!
The laptop it fails on is Windows 7 and my JDK is :

• java version "1.8.0"
• Java(TM) SE Runtime Environment (build 1.8.0-b132)
• Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)

Bjørn