EN/ISO 13606 & openEHR - harmonisation possibilities

On 12/09/2011 08:51, Diego Bosc? wrote: > ':' are not valid as names in most operating systems, so it would be a > problem even for adl file names. That's why I don't think it is wise > to allow this one in particular. I don't remember anywhere in ADL/AOM where filenames are specified, and ':', c

EN/ISO 13606 & openEHR - harmonisation possibilities

':' are not valid as names in most operating systems, so it would be a problem even for adl file names. That's why I don't think it is wise to allow this one in particular. The other issue was already 'discussed' on the list http://www.openehr.org/mailarchives/openehr-technical/msg05294.html I hav

EN/ISO 13606 & openEHR - harmonisation possibilities

-Original Message- From: Diego Bosc? Sender: "openehr-technical-bounces at openehr.org" Date: Sat, 10 Sep 2011 09:45:17 To: For openEHR technical discussions Reply-To: For openEHR technical discussions Subject: Re: EN/ISO 13606 & openEHR - harmonisation possibilit

EN/ISO 13606 & openEHR - harmonisation possibilities

On 10/09/2011 14:22, Diego Bosc? wrote: > ADL parser. > and I am not saying it should be allowed, just that this kind of > things happen :) > Diego, I am still not clear on the actual problem - if it is the ADL workbench parser, would you mind reporting it here

EN/ISO 13606 & openEHR - harmonisation possibilities

ADL parser. and I am not saying it should be allowed, just that this kind of things happen :) 2011/9/10 Thomas Beale > > Diego, > > I am not sure I understand that one - ':' is indeed illegal in most class / > property identification systems - are you saying it should be allowed? Which > parser

EN/ISO 13606 & openEHR - harmonisation possibilities

yes, what I mean is attributes like ID or even invalid characters in the names (like ':'). This is a problem with the parser (and also with classes identifiers) 2011/9/10 Thomas Beale : > On 10/09/2011 12:59, Diego Bosc? wrote: >> >> This kind of problems has given us a lot of problems when using

EN/ISO 13606 & openEHR - harmonisation possibilities

Diego, I am not sure I understand that one - ':' is indeed illegal in most class / property identification systems - are you saying it should be allowed? Which parser do you mean? - thomas On 10/09/2011 13:45, Diego Bosc? wrote: > yes, what I mean is attributes like ID or even invalid charac

EN/ISO 13606 & openEHR - harmonisation possibilities

I currently don't have the norm with me, I'll check it on Monday morning. Second case looks like a typo on the schema, thanks for pointing it out. We will check it and correct it. We created a 13606 XML Schema (because there was none available) trying to follow the specifications (as we also did wi

EN/ISO 13606 & openEHR - harmonisation possibilities

On 10/09/2011 12:59, Diego Bosc? wrote: > > This kind of problems has given us a lot of problems when using ADL to > work with other models like HL7 CDA or CDISC ODM, where there isn't > any kind of rule (for example, in ADL CLASSES must be upercase and the > attributes lowercase, and in CDA this i

EN/ISO 13606 & openEHR - harmonisation possibilities

As Dipak has explained, the attribution in ISO is not available. I believe attribution is a distraction from the task - I have seen lots of slides from others used in this space and ideas transferred here and there. Let's appreciate all work and try and build on it efficiently. Cheers Sam Sent

EN/ISO 13606 & openEHR - harmonisation possibilities

David, no offence was intended (at all). I was trying to point out (badly) in the context of the current discussions on licensing and openEHR that, if CC-BY had been in place in the past, then: * the CEN 13606-2 standard, being a copy of work done by openEHR (with adaptations done to wor

EN/ISO 13606 & openEHR - harmonisation possibilities

Ok, but again, the referenced documents at that epSOS annex are CEN EN 13606 part 1 and CEN EN 13606 part 2. If openEHR has to be mentioned is in those documents, not in this annex since it only deals with 13606 and the archetype/ADL summary is just for clarifying concepts for the reader and not a

EN/ISO 13606 & openEHR - harmonisation possibilities

David, Diego, I just tried to compile the archetype CEN-DEMOGRAPHIC-IDENTIFIED_HEALTHCARE_PROFESSIONAL.HCP_Dispenser.v1 in the ADL Workbench... I had to make a few changes: * IDENTIFIED_HEALTHCARE_PROFESSIONAL has an attribute 'scopingOrganisation' in the standard, but the archetype had

EN/ISO 13606 & openEHR - harmonisation possibilities

Hello Ian, As Diego said, the epSOS case is a different case but a case that surely can happen quite often. The normal approach, as you mention, should be define first the generic archetypes and then reuse and constrain them for specific uses through specialisations or templates. At epSOS the spe

EN/ISO 13606 & openEHR - harmonisation possibilities

On 09/09/2011 19:04, David Moner wrote: > > Thomas, > > Could you please clarify this sentence? > > I'm the main author of that document. As you said, it is a 45 pages > document of which only two and a half are a summary description of ADL > to understand the proposed archetypes. And only there

EN/ISO 13606 & openEHR - harmonisation possibilities

Thomas, Could you please clarify this sentence? I'm the main author of that document. As you said, it is a 45 pages document of which only two and a half are a summary description of ADL to understand the proposed archetypes. And only there we can see some examples of ADL structures (yes, openEHR

EN/ISO 13606 & openEHR - harmonisation possibilities

Well, in all of our projects we use ENTRY level archetypes and slots, but as epSOS defines that the requirement is a full document then it made sense to put everything on the same archetype (to show that all requirements could fit without problems) 2011/9/9 Ian McNicoll : > Hi Diego, > > Yes. I sa

EN/ISO 13606 & openEHR - harmonisation possibilities

What part do you said is copied? ._. Here the archetypes in ADL http://en13606.webs.upv.es/web13606/index.php/activities/ceniso-13606-workshop-mie2011-oslo 2011/9/9 Thomas Beale : > > Diego, > > Are the archetypes online anywhere? > As an aside, it is an interesting document - 45 pages about arche

EN/ISO 13606 & openEHR - harmonisation possibilities

There are already epSOS EN13606 archetypes http://www.epsos.eu/uploads/tx_epsosfileshare/D3.5.2_Appendix_G_EN13606_Implementation.pdf 2011/9/9 Thomas Beale : > On 09/09/2011 14:01, Stef Verlinden wrote: > > Great initiative. Let's go for it. Even though I agree with your previous > remarks that th

EN/ISO 13606 & openEHR - harmonisation possibilities

Thanks Diego, My mistake - that wasn't clear at David's demonstration or from the epSOS appendix. Are the ENTRY level component archetypes available, and are they designed to be for epSos use only or do they support a much broader context of use e.g a full hospital or GP medication use? It woul

EN/ISO 13606 & openEHR - harmonisation possibilities

Hi Diego, Yes. I saw David Moner's presentation on these at the MIE conference in Oslo, and he and Gerard Freriks gave a very powerful account of the power of archetype development in messaging production. However, these archetypes also point to a somewhat different approach (at least for now) be

EN/ISO 13606 & openEHR - harmonisation possibilities

Diego, Are the archetypes online anywhere? As an aside, it is an interesting document - 45 pages about archetypes, including a lot of directly copied openEHR material, and no attribution at all to openEHR! Lucky it is not an academic paper - thomas On 09/09/2011 15:28, Diego Bosc? wrote:

EN/ISO 13606 & openEHR - harmonisation possibilities

On 09/09/2011 14:01, Stef Verlinden wrote: > Great initiative. Let's go for it. Even though I agree with your > previous remarks that this probably won't provide a long term > solution, IMHO it's absolutely necessary in order to secure short term > progress. > > Maybe a dumb question, but is the

EN/ISO 13606 & openEHR - harmonisation possibilities

Great initiative. Let's go for it. Even though I agree with your previous remarks that this probably won't provide a long term solution, IMHO it's absolutely necessary in order to secure short term progress. Maybe a dumb question, but is there a way we can involve people form other standard ini

EN/ISO 13606 & openEHR - harmonisation possibilities

As you may have noticed, the new release of the ADL Workbench enables exploration of multiple reference models and their classes. Although the 13606 schema