RE: name of language to define OPTs ?

Hi Georg, It is an XML serialisation of the Archetype Object Model. Heath -Original Message- From: openEHR-technical On Behalf Of Georg Fette Sent: Sunday, 13 October 2019 1:41 AM To: For openEHR technical discussions Subject: name of language to define OPTs ? Hello, What is the

RE: FHIR-like terminology 'binding strengths'?

Hi Tom, I agree with Grahame, in over 20 years of implementing real systems, I don’t think I recall having seen one value-set that hasn’t been extended at some point when locally implemented. Even HL7 defined tables in V2 that were supposed to not be extended have been extended. There is a big

Re: openEHR on FHIR and vice versa

XSLT would be a good common denominator although perhaps seen as ancient. Regards Heath From: Heath Frankel Sent: Wednesday, December 19, 2018 8:23:31 AM To: For openEHR technical discussions Subject: Re: openEHR on FHIR and vice versa Thanks Pablo, I second

Re: openEHR on FHIR and vice versa

Thanks Pablo, I second that. Regards Heath _ From: Pablo Pazos mailto:pablo.pa...@cabolabs.com>> Sent: Wednesday, December 19, 2018 3:36 am Subject: Re: openEHR on FHIR and vice versa To: For openEHR technical discussions mailto:openehr-technical@lists.openehr.org>>

Re: Better definition of 'system_id' attribute in openEHR sytems

Hi Thomas, This is an excellent description and is inline with our implementation. Regards Heath From: 3003270n behalf of Sent: Monday, November 26, 2018 11:43 pm To: Openehr-Technical Subject: Better definition of 'system_id' attribute in openEHR sytems

RE: AOM 1.4 - Archetype.uid a UUID or OID?

Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID, ISO_OID or INTERNET_ID. The bigger issue is the HIER_OBJECT_ID is incompatible with UUID from

Re: Could the specs group consider making uid mandatory?

I think it should be a strong recommendation rather than mandatory considering it is currently optional and the need for backward compatibility. I also think it maybe difficult to apply consistently in some cases such as feeder data. There are cases in CDA profiles where there are mandatory IDs

RE: Specs about ACTIVITY.timing still unclear

We have more recently used iCAL for Instruction timing not associated with Medication orders such as service requests. It has served us well so far. Although FHIR has its own Appointment resource, they actually suggest the use of iCal instead of using this resource. I am not sure if iCal could

RE: initial states for instructions / when do we need actions?

Hi Pablo, Some comments below. Heath From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of pablo pazos Sent: Tuesday, 12 July 2016 12:29 PM To: openeh technical ; openehr clinical ;

RE: Shouldn't INSTRUCTION_DETAILS.wf_details be archetypable?

Hi Pablo, Since wf_details is ITEM_STRUCTURE, then yes it can be archetyped. Just because the AE doesn't support it does not change this fact. As is this case in many software projects, functionality in the AE was built on as needed basis so I would suggest that no one has needed it to date.

RE: Composition commit and change types

Hi Pablo, I did include my scenarios re problem list at the bottom of the email. Having said that there had been some movement around what compositions are persistent due to no context issues so problem list may no longer be a persistent composition. There are similar scenarios for other

Re: Composition commit and change types

Hi Ian and Pablo, Although I don't like commenting on how others implement their systems I would hate for this discussion to become the defacto standard on how the API works in the context of persistent compositions. Although I understand Ian's position on best clinical practice of a single

RE: Adressing of i.e. discharge summaries

Hi Bjorn, Yes we have used these archetypes for representing the service request at both the instruction and composition level. Our instruction starts in a care plan so we have to represent the referred to provide in the instruction participations. Then when we send the referral we copy it to

Re: rm_type_name for the DV_DURATIONs primitive object in XML

Hi Sebastian, Does this mean that CKM no longer uses the TD OPT Web Service? I think your suggestion of String is correct as per the specifications, DURATION, DV_DURATION and C_DURATION are clearly wrong. However, I think we need to be considering the XML Schema approach of a restricted string

RE: Usage of Compositoin.Category

Hi Bjorn, How did you come up with the concept id of 434? We need to be careful about assigning our own concept ids, we really need openEHR to assign these, I suggest through the SEC process initiated by a Jira card. At present we have two terminology files, as you know we have agreed to use

RE: Template Designer alternatives

Hi Pablo, Since templates are intended to assign terminology bindings for specific implementation, the Template Design skips the step to need to specify a coded text type and allows you to specify a terminology binding using the Value set (terminology) property as shown below.

Re: Strange use of 'offset' as a settable RM attribute

witter: @ianmcnicoll [https://docs.google.com/uc?id=0BzLo3mNUvbAjT2R5Sm1DdFZYTU0=download] Co-Chair, openEHR Foundation ian.mcnic...@openehr.org<mailto:ian.mcnic...@openehr.org> Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 14 Feb

Re: Strange use of 'offset' as a settable RM attribute

Hi Koray, This is a constraint on the value that origin function returns rather than indicating it is a settable attribute. This was how Sam defined the events on an apgar score, 1 min, 5 min, etc. Regards Heath _ From: Ian McNicoll

RE: Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer

Hi Ian, Although it may be worth doing this in the new web tools, there are existing tools being used by many more existing users that need to support this functionality, at least in a lossless manner. Each of the tooling providers need to have the opportunity to be involved in the process and

Re: Binding to multiple terminologies / code systems

It should also be noted that normally constraints on which terminologies can be used in a particular implementation is done in a template. This can be done on the existing DV_TEXT definition or on a DV_CODED_TEXT constraint. This can be expressed in the template designer, again not the best UI

Re: Archetype publication question - implications for implementers

The existing versioning rules allow adding new concepts and opening constraints such as allowing additional units. These change the md5 hash but does require a version /id change. This is why Sebastian's suggestion technically works, the existing obsolete concept still exists and the new

RE: Archetype publication question - implications for implementers

Hi Heather, Although I agree with the idea of obsolete concepts, I wonder if it is necessary in this case of Tilt. Why can’t we just add the additional units as allowed options leaving the existing degrees symbol but in the element description indicate that this is obsolete and the correct

Re: difference and relationship between openEHR and EN13606

Technical, the original grammar for AQL was bound to openEHR RM classes, composition, version, observation, etc. theoretically it could be generalised to be a RM agnostic and should be the goal of the current AQL specification work if it hasn't already been done in the antlr grammar. Regards

Re: VERSION.lifecycle_state options

On 6/11/2015 1:22 AM, Heath Frankel wrote: Hi Sebastian, To your general question, yes we needed something to indicate a version was moved distinct from deleted. This ensured that we couldn't undelete the version. There was a PR for this which included a new change type also. To your usecases, I

Re: VERSION.lifecycle_state options

Hi Sebastian, To your general question, yes we needed something to indicate a version was moved distinct from deleted. This ensured that we couldn't undelete the version. There was a PR for this which included a new change type also. To your usecases, I agree these are necessary but have

ACTION just as event trigger

Hi Pablo, Actions are absolutely necessary and can carry different/additional information than the instruction. An instruction is actually useless without an action. It is the action that puts the action into a particular state at a particular time. When an instruction is created it should

ACTION just as event trigger

Hi David, I haven't been involved in the instruction/action modelling recently but I know that this principle of having the same item structure archetype girl the activity and action was preferred in the early days, it has recently deviated for some archetypes at least as the information

openEHR-technical Digest, Vol 35, Issue 33

Hi Tom, In fact this was demonstrated at MIE in 2007 and again at least once if not twice at HIC as part of IHE showcase that included storing the result in the GE XDS. Chris Lindop and other HL7 members were involved in the overall showcase so they new it existed for real. This had nothing to

CRUD Restlet

I too have looked how the approach used by FHIR could be applied generically to openEHR, but at the entry level using TDDs. I actually went up one level and considered the principals of the HL7-OMG RLUS specification, which is the logical basis of FHIR before they hard coded the resources. RLUS

CRUD Restlet

The approach I took with my FHIR like API was to have a named query with know parameters and result columns. This could be registered internally using AQL or hard coded. This all comes from FHIR principles as they allow registering queries and then executing them. Regards Heath On 20 Jan

Archetype Naming proposals - do we need V0?

I completely agree with this, The number one priority is that all existing clinical data using archetypes published in CKM for the last 2-5 years is not Invalidated by this process. I understand that it was use at your own risk but surely vendors that have taken the risk to be early adopters

Small question about commits and AUDIT_DETAILS.system_id

On 21/08/2014 00:27, Heath Frankel wrote: Hi Thomas Pablo, I am finding the words in the this discussion ambiguous, and the specification does help to clarify. Here is my interpretation of AUDIT_DETAILS.system_id. I have an EHR service, which is used by two different application, one

Commits and Contributions

The commit uid is generated by the ocean EHR client, this is consistent with a git commit. All this is is a GUID so easy to do. Although I set the commit time on the client, I override this on server. Heath Original Message Subject: Commits

Small question about commits and AUDIT_DETAILS.system_id

Hi Thomas Pablo, I am finding the words in the this discussion ambiguous, and the specification does help to clarify. Here is my interpretation of AUDIT_DETAILS.system_id. I have an EHR service, which is used by two different application, one is a hospital system and another a mobile

Ocean's Template Designer and allowedType rules

Hi Pablo, The OET format is an internal format. You should export the template as an OPT and you will get a AOM and RM based output. Heath From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of pablo pazos Sent: Friday, 15 November 2013 1:06 AM To:

Ocean's Template Designer and allowedType rules

: For openEHR technical discussions Subject: Re: Ocean's Template Designer and allowedType rules Hi Heath, I have a related question about OPT. Could you explain path calculation algorithm for OPT? Best wishes, Shinji KOBAYASHI 2013/11/15 Heath Frankel heath.frankel at oceaninformatics.com: Hi

FW: SV: ACTIVITY and timing

We use the HL7 V2 TQ data type representation since it has been used in healthcare systems for 30 years and supports many of the weird and familiar timing scenarios such as BID etc. Regards Heath On 13/08/2013, at 8:34 PM, Thomas Beale thomas.beale at oceaninformatics.com wrote: Hi

Regarding the use of the Demographics Package...

. All the best Athanasios Anastasiou On 02/07/2013 00:43, Heath Frankel wrote: Hi Athanasios, As Sam said, the Ocean Multiprac application suite (www.multiprac.com http://www.multiprac.com) does this. I have a PERSON.person-individual_**provider that has a ROLE.user as well

Regarding the use of the Demographics Package...

Hi Athanasios, As Sam said, the Ocean Multiprac application suite (www.multiprac.com) does this. I have a PERSON.person-individual_provider that has a ROLE.user as well as a ROLE.healthcare_provider, so your user who is a provider has both user roles and healthcare roles. Similarly I have a

Mimetype ADL

Hi Thomas, The value of more specific mime types is that application using the file can determine how to handle the file such as launching an associated application to view it. XML is just text/plain but it is recommended to be application/xml. I suggest we look into the process of registering a

Questions about commit and AUDIT_DETAILS

Hi Erik, I agree and I intended to say in my other response that I think this level of audit trail could be left to individual systems just like you use http-server log and I use an IHE ATNA implementation. Although it may be desirable to standardise the data model of the logs I see no reason to

Questions about commit and AUDIT_DETAILS

I believe that the client application/machine should be recorded in a separate level audit log, something like the ihe atna. The contribution audit is intended to support thr versioning control in a distributed environment of eHR systems do when compositions are exchanged between systems we know

Questions about the XSD-files.

Bert, Items is not a class, it is an attribute. Heath On Nov 27, 2012 8:50 PM, Bert Verhees bert.verhees at rosa.nl wrote: Op 27-11-2012 9:07, Heath Frankel schreef: Bert, You can define elements to be type of an abstract type allowing any concrete subtype in an instance

Questions about the XSD-files.

:07, Heath Frankel schreef: Bert, You can define elements to be type of an abstract type allowing any concrete subtype in an instance. This is the intent of the items element, to allow any rotatable concrete type to be represented in a document with root element of items. Heath Hi Heath

Questions about the XSD-files.

granularity requires having more root elements defined as options in the XSDs. Bert, did I get it? On Tue, Nov 27, 2012 at 7:24 PM, Heath Frankel heath.frankel at oceaninformatics.com wrote: Bert, The rule you reference says nothing about concrete types. As far as I am concerned the items

Questions about the XSD-files.

Heath On Nov 28, 2012 9:07 AM, Bert Verhees bert.verhees at rosa.nl wrote: Verstuurd vanaf mijn iPad Op 27 nov. 2012 om 20:24 heeft Heath Frankel heath.frankel at oceaninformatics.com het volgende geschreven: Bert, The rule you reference says nothing about concrete types. As far as I am

Questions about the XSD-files.

:52 PM, Bert Verhees bert.verhees at rosa.nl wrote: On 11/28/2012 02:35 AM, Heath Frankel wrote: Seref, The items element is provided in the structure.xsd for this very reason but Bert seems to object to it because of its name or its type or some other reason that I have not yet determined

Questions about the XSD-files.

Hi Bert, Sorry but I struggled to understand the issue you have below. Would you mind looking at my comments below and see if I have understood them correctly? Heath -Original Message- From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bert Verhees

Questions about the XSD-files.

Bert, You can define elements to be type of an abstract type allowing any concrete subtype in an instance. This is the intent of the items element, to allow any rotatable concrete type to be represented in a document with root element of items. Heath On Nov 27, 2012 6:19 PM, Bert Verhees

Understanding how to commit contributions to an EHR Server with XML

Hi Pablo, I think we have an excellent opportunity here to take this offline with Erik to work up a combined logical service specification and RESTful technical service specification as a candidate for the openEHR service model. It looks like you?re looking for a Virtual EHR Service. The

Understanding how to commit contributions to an EHR Server with XML

Hi Pablo, You need to understand that some of the RM classes are functional object rather than data objects and hence are not currently considered serializable, VERSION_OBJECT, EHR and perhaps CONTRIBUTION are examples of these. There is no specific statement about this in the specifications,

Understanding how to commit contributions to an EHR Server with XML

Hi Pablo, You need to understand that some of the RM classes are functional object rather than data objects and hence are not currently considered serializable, VERSION_OBJECT, EHR and perhaps CONTRIBUTION are examples of these. There is no specific statement about this in the specifications, and

Understanding how to commit contributions to an EHR Server with XML

Hi Erik, I notice that you have provided a schema for VERSIONED_OBJECT which doesn?t align with the RM class and overlaps with the X_VERSIONED_OBJECT already defined in the extract.xsd. I think we should leave VERSIONED_OBJECT as not serializable and use the X_VERSIONED_OBJECT class as the

Entities Relationships within the EHR

Anthanasios, What we have Don in research based projects is use a persistent composition to record the cohort that the subject belongs too. It could be done using demographics where we have a registration relationship associated with the party but when you want population query on the ehr data you

Should not node identifiers in runtime paths be mandatory?

a semantic function, that of giving a design-time meaning to the node, by equating the node identifier to some description Maybe I've incorrectly generalized this statement. Kind regards Seref On Wed, Aug 15, 2012 at 1:10 AM, Heath Frankel heath.frankel at oceaninformatics.com wrote: Hi

Should not node identifiers in runtime paths be mandatory?

at lists.openehr.org] On Behalf Of Thomas Beale Sent: Wednesday, 15 August 2012 8:02 PM To: openehr-technical at lists.openehr.org Subject: Re: Should not node identifiers in runtime paths be mandatory? On 15/08/2012 01:10, Heath Frankel wrote: Hi Seref/Thomas, Node IDs at0022 and at0023 have

An ACTION or INSTRUCTION referencing an AGEN, is it possible?

Hi Pablo, You news to be clearer about the requirement. Depending on the real requirement the student may be right. Remember that demographic model is recording instances of parties not classes. So if the requirement is to record the specific instance of device recording attributes such serial

How about creating an openEHR test base?

Hi Erik, I think that using an EHR service to store RM instances would be better than storing in SVN or GIT. Ultimately if the service was able to work from a GIT repository we would have the best of both worlds. I had considered offering the Ocean EHR server but I assumed the usual issues

How about creating an openEHR test base?

Hi Pablo, What issues do you have with the XSD? We have been producing valid instances for years. I have tools that can validate these in seconds. I am sitting on hundreds of test instances. Problem is I am not sitting around with nothing to do. If you have a student willing to do some dot NET

How about creating an openEHR test base?

Seref, I think meaningful data is more useful than random maximal or minimal data. I think that using the template data schema approach could be an easier way to produce data by hand if a GUI is not available but I am assuming this is not the case for Pablo. The Ocean Template Designer is free to

How about creating an openEHR test base?

Pablo, This is a good list, I have already commented on 1-3 and I am also interested 4-6. I think a JSON format project would be good to make sure we get consistency earlier than later, it is not like XML where you can publish a schema and I suspect various toolkits will have their variations.

How about creating an openEHR test base?

Once again we have tooling to convert csv files to openEHR using template data schema but someone has to do the hard work of creating the archetypes, templates and transforms to make it all happen. This continues to be the blocker of this kind initiative. Let us know if anyone has the bandwidth.

TerminologyId.Name

Hi Leykum, Looking at your instance closely you will see that you have a ?gastric interventions? ACTION with a ism_transition current_state as follows: current_state valueCompleted/value

Suggestion to replace use of generics with inheritence in future RM versions

On Fri, Mar 23, 2012 at 12:09 PM, Heath Frankel heath.frankel at oceaninformatics.com wrote: I think the topic has drifted slight from Seref's original issue, although Java nor c# can not implement generics as well as Eiffel or as intended by the spec author it is possible to get close enough

Suggestion to replace use of generics with inheritence in future RM versions

I think the topic has drifted slight from Seref's original issue, although Java nor c# can not implement generics as well as Eiffel or as intended by the spec author it is possible to get close enough to be usable. Similar implementation decisions were necessary when specifying the XML schema and

Units, Quantities, etc

Hi Thomas, I had an issue recently were I was receiving HL7 V2 Lab messages with units such as x10^6/L, the equivalent in UCUM is 10*6/l, which was used in the archetype constraint for an RBC element. I translated the HL7 unit into the archetype constrained unit as required to be valid.

openEHR - Persistence of Data

Hi Koray, Yes there was a honours thesis done on using an object database to store and query openEHR data. It was intended to compare our indexed XML blob approach but from memory it ended up comparing two commercial object databases. I will have to ask Chunlan if the paper is publicly available.

Meaningful Use and Beyond - O'Reilly press - errata

Considering the incorrect reference to openEHR in the author's CTO position, without knowing conext of were it is done, perhaps all references were intended to be to openEMR? Heath On 12/02/2012 11:31 PM, Thomas Beale thomas.beale at oceaninformatics.com wrote: It would be interesting to see

Python / Django experience??

www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org On 31 January 2012 23:00, Heath Frankel heath.frankel at oceaninformatics.com wrote: Hi Ian, Interested in how you think RLUS can support a Knowledge

Building software to convert HL7 v2/v3 messaging into archetypes templates

Hi Wo, Not sure if anyone else has some tools for the Job, but my experience in doing this over the last 5 years is that there is no silver bullet for this task. The process is just like any integration mapping, however the commercial mapping tools that I have attempted to use and those I have

pass_through and implementation directives in general

, Erik Sundvall erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733 On Tue, Jan 31, 2012 at 00:07, Heath Frankel heath.frankel at oceaninformatics.com wrote: Hi Erik, No problem with your RDF approach but I agree with Thomas that the purpuse of view directives. (or more

Python / Django experience??

Hi Ian, Interested in how you think RLUS can support a Knowledge service? Heath On 01/02/2012 2:21 AM, Ian McNicoll Ian.McNicoll at oceaninformatics.com wrote: Hi Pablo, Your initial ideas on a possible service layer would be very interesting. I think we are starting to see a need to support

pass_through and implementation directives in general

at oceaninformatics.com: On 30/01/2012 03:16, Heath Frankel wrote: Hi Pablo, ** ** If I understand correctly, the pass_through attribute is only for data displaying on a screen (as you mention the use for data grouping or collapsing). If that's right, I don't think that should be part of the generic

pass_through and implementation directives in general

Heath From: openehr-technical-boun...@openehr.org [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Thomas Beale Sent: Monday, 30 January 2012 11:52 PM To: openehr-technical at openehr.org Subject: pass_through and implementation directives in general On 30/01/2012 03:16, Heath

pass_through attribute in ADL 1.5

David, Pass_through has no relevance to this emphasis concept in any way. It has been a means to collapse container attributes such as items when the hierarchical structure inherited from the RM or Archetype is no longer desired or relevant in a template perhaps because sibling items in a

pass_through attribute in ADL 1.5

Hi Pablo, If I understand correctly, the pass_through attribute is only for data displaying on a screen (as you mention the use for data grouping or collapsing). If that's right, I don't think that should be part of the generic template structure, because templates are meant to represent other

pass_through attribute in ADL 1.5

Hi Pablo, The Ocean Template Desiner is now freely available from https://wiki.oceaninformatics.com/confluence/display/TTL/Template+Designer+R eleases. The pass_through view constraint is not a GUI directive, it is a data view directive which is consistent with archetypes/templates being

Constraints on class methods

name rule is multiple alias party-identity occurences, in fact anywhere where you use a coded name such as a lab observation with multiple occurrences. Adding a suffix makes the value different to the code rubric, which frowned upon in terminology circles. Heath On 11/01/2012 11:25 PM, Heath Frankel

pass_through attribute in ADL 1.5

Hi Paplo, Your suggestion here is too oriented to GUI uses cases. As Tom indicated, pass_through is intended to support other data oriented contexts such as flattening schema and class hierarchies, this is why is was generalised from hide-on-form as used in the template designer. If you look at

Carriage returns in DV_TEXT not allowed

We currently ignore this constraint as most multi line cases don't need the complexity of dv-text and the parsing overhead to get a list of dv-text is significant, and as you say we don't have a container of dv-paragraph unless you use multiple elements which is a heavy solution. I don't think

How is assumed value marked on domain types? (in XML)

Diego, What tool are you using to generate your AOM XML? The tool issue tracker may be a more appropriate place for these tooling issues. Heath On 05/01/2012 10:34 PM, Diego Bosc? yampeku at gmail.com wrote: In ADL, the assumed value of a domain type is marked like this: defining_code matches

Did anybody implement AQL with a LL parser framework?

Hi Seref and Erik, The grammar published on openEHR by Ocean Informatics was what we used with a proprietary third party tool. If people have converted the grammar to work with more standard parsing tools and want to post it to the AQL wiki page for others to use then we too can test it with our

Basetypes (schema/specification)

http://svn.openehr.org/specification/TAGS/Release-1.0.2/ITS/XML-schema is the latest schema. If anything the documentation may be out of sync. The documentation is generate using Oxygen. Heath -Original Message- From: openehr-technical-boun...@openehr.org

Basetypes (schema/specification)

through the openEHR website menu. and the second issue is still true: types with CamelCase and underscores names exist on the same schema 2011/12/21 Heath Frankel heath.frankel at oceaninformatics.com: http://svn.openehr.org/specification/TAGS/Release-1.0.2/ITS/XML-schema is the latest schema

Questions about the relationship between Instruction, workflow and Action

mentioned) with the solution of having messages triggering ACTION creation or recording data on existing ACTIONs. [HL] It is not at all simple to envisage how the flow of INSTRUCTION and various resulting ACTIONS play out, and I can't pretend to have it all 100% clear, but with implementations (and Heath

Could YAML replace dADL as human readable AOM serialization format?

I think previously I had indicated I had no problem with the stringified interval approach in XML, but I am reverting my thinking on this and feel that it would be counter intuitive for those who what to use the XML schemas for code generation purposes. I think in this case the computable

Could YAML replace dADL as human readable AOM serialization format?

Thanks Erik, Interesting to see the line up. Can't believe that XML wasn't the longest file in the list, that kills one of the arguments for JSON vs XML. For someone that is not aware of YAML, are the white space significant. If so, this kinds of kills it for me, otherwise for a Human

occurrences and cardinality in ADL, XML, JSON

Hi Thomas, yes - everyone goes through the same process I think. The P_ classes I now have in the ADL 1.5 compiler are my latest addition in this process. [HKF: ] No, this is something you learn as it sounds like both you, I and others do doubt have learned. The first thing a new comer

occurrences and cardinality in ADL, XML, JSON

I too have no problem with this custom serialisation as I have a hand-coded serializer that does the job (I gave up on the auto-generated ones years ago). However, I think we need to go back a step and get agreement from the community what the most important features of an XML serialization are:

occurrences and cardinality in ADL, XML, JSON

Hi Thomas, The answers to the two questions below seem to be counter to each other. I think if we want to stay true to the RM that we should do this consistently, otherwise there is no reason why we can't deviate in other cases such as the first case below. In fact I would go further and

Questions about the necessity of ITEM_SINGLE

Hi Sam, The problem with this is that we currently use the RM inheritance to assist in these structure constraints, i.e. an ITEM_LIST only contains a CLUSTER containing only ELEMENTs. However, if you think about it, the semantics of CLUSTER and ITEM_TREE are equivalent. It is only the level in

AQL VersionedObject Grammar

Yes, from memory this be about right, but the VERSIONED_OBJECT part is redundant as it is not used anywhere in the query. I notice you are specifying a HIER_OBJECT_ID as the COMPOSITION.uid criteria. Although it is not a specified and not a hard rule, it is recommended that a OBJECT_VERSION_ID

CCR model

Hi Koray, In 2009 I did an IHE Medical Summary profile based Template for the Interoperability Demonstration at HIC. I can't recall the exact relationships between CCR, CCD and IHE Medical Summary profiles but they pretty much cover the same concepts. The template was only a subset of the

openEHR artifact namespace identifiers

April 2011 2:16 AM To: openehr-technical at openehr.org Subject: Re: openEHR artifact namespace identifiers On 08/04/2011 01:49, Heath Frankel wrote: Thomas, Your proposed changes to the archetype Identifiers and governance actually aligns with the same management and inferencing requirements

Archetype versioning on CKM

The problem is that ontologically v1 is not actually a version identifier, it is more like an axis of a concept ID, v1 and v2 have different concepts although they represent the same concept domain (i.e. two different representations of the same concept). The name of this axis is an unfortunate

openEHR artifact namespace identifiers

Exactly, an OID can be used as an URI scheme. Not sure how much simpler you can get then assigning a string of numbers and dots to a system that issues an accession number and appends it the assigned string, CKM already does the first two steps of this.Anyone that can implement a openEHR

openEHR artifact namespace identifiers

be inferred if two concrete artefact instances are really just versions of the same thing. Note that a UUID is massive overkill for a version id of something! But this just shows that simple assignment of UUIDs or Oids is no panacea - thomas On 06/04/2011 01:41, Heath Frankel wrote

openEHR artifact namespace identifiers

Hi Ian, This sounds more sensible to me, I was always worried about the change in identifier when it got escalated to a higher PO. I wonder if we can get a summary of the rest of the SNOMED namespacing scheme so that we can see if it is usable in its entirety. I have always been a

future ADL-versions

Hi Seref, I agree with you sediments regarding Archetypes. However, the AOM still needs to support something like this for templates, in my view this is the level where we will want to start making conditional statements about data constraints (and this is still before we get to the GUI, as I may

C_DATE_TIME and RM instances

Thomas, value xsi:type=DV_DATE_TIME value2011-03-18/value /value this is illegal in ISO 8601 (and therefore openEHR) [HKF: ] This is actually legal in openEHR as it is also in HL7 V2 (well the non-extended 20110318 is legal), it is a documented variation of ISO-8601. and value

  1   2   >