I'm not sure it is really a bug, but worth discussing because it might be a problem others might face as well.
I have an Observation of the archetype openEHR-EHR-OBSERVATION.pathology_test-ubr.v1 which contains an archetype Event Series that has a list of Events. The problem is that every single Event node has the same Name, using the same archetype_node_id.
When parsing the xml to an Observation instance, the AddItem method at LocatableList.cs has the following code:
if (namedLocatables.Contains(item.Name.Value)) throw new ApplicationException(string.Format("locatable ({0}) name ({1}) already existing in this namedLocatable list", item.ArchetypeNodeId, item.Name.Value));
This code do not allows me add avery Event to the list, because they use the same archetype_node_id and name.
When it is about and Element it does make sense, after all we cannot have
Why is that?!
I'm not sure it is really a bug, but worth discussing because it might be a problem others might face as well.
I have an Observation of the archetype openEHR-EHR-OBSERVATION.pathology_test-ubr.v1 which contains an archetype Event Series that has a list of Events. The problem is that every single Event node has the same Name, using the same archetype_node_id.
When parsing the xml to an Observation instance, the AddItem method at LocatableList.cs has the following code:
if (namedLocatables.Contains(item.Name.Value)) throw new ApplicationException(string.Format("locatable ({0}) name ({1}) already existing in this namedLocatable list", item.ArchetypeNodeId, item.Name.Value));This code do not allows me add avery Event to the list, because they use the same archetype_node_id and name.
When it is about and Element it does make sense, after all we cannot have
Why is that?!