Compact XML format...?

-like) because it works better, and writing a generic transform for CDA level 3 (fully structured) is hard. - thomas beale

Null Flavours, boolean values in openEHR

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

Multiple parents and max number of nested specialized archetypes?

Hi Koray, At the moment we have not seen any need for multiple inheritance in archetypes. Do you have a particular use case? Note that C specialising B means that C conforms to B and to A. Nothing special needed to do that. - thomas beale Koray Atalag wrote: > Hi, > > I have a quest

Multiple parents and max number of nested specialized archetypes?

Grahame Grieve wrote: >> At the moment we have not seen any need for multiple inheritance in >> archetypes. >> > > I see this as very similar to multiple inheritance in objects. > There is no *need*, but there is useful things that can be done. > The question is whether the price is justified

Multiple parents and max number of nested specialized archetypes?

Grahame Grieve wrote: > hi Tom > > We are speaking about data integrity issues at different > levels. Of course the reference model assures data integrity > at that level; I was speaking of data integrity at the of > data aquisition - calibration, methodology, attribution, these > kind of things. >

Multiple parents and max number of nested specialized archetypes?

ed validation up the specialisation lineage. In practical terms, this translates to more maintainable archetypes and a better ability to see the differences between a given specialised archetype and the parent. - thomas beale

Multiple parents and max number of nested specialized archetypes?

y soon. For confluence, we will ust put in some minimal structure to save us from complete disorganisation - it will be an open wki. There will be plenty of opportunity for experts here to contribute and help shape these things - we just want them running in a basic reasonable form so people don't hate us when they see it ;-) - thomas beale

Multiple parents and max number of nested specialized archetypes?

Koray Atalag wrote: > > In my former message, with the question of writing down B and A for > spelicalization section of C, I was proposing to write down the names of all > archetypes till the top level in specialization archetype- like an absolute > specialization path. This I think is not true

Multiple parents and max number of nested specialized archetypes?

Erik Sundvall wrote: > Hi! > > > > Can one share important sub-parts without sharing view on process and > structure. If so, will the information entered using the two different > archetypes be computable in a similar way for e.g. decision support > systems. > this is why we have Cluster & St

Multiple parents and max number of nested specialized archetypes?

Dipak Kalra wrote: > Dear Heather, > > Your 50c worth is really an excellent explanation. Well done, and I > hope many readers on the list will find it helpful. > You should see what Heather can do for $1 - thomas

parsing templates

ng to see how well it works before proclaiming it a specification (or standard...). The draft specification should be available within a few weeks. - thomas beale *

software development & starting out

more questions. > *in a similar vein, you may find this paper useful as well - http://www.openehr.org/publications/health_IT/MedInfo2007-BealeHeard.pdf - thomas beale *

[archetypes.com.au] Functionality to compare two archetypes

Rong Chen wrote: > Hi Sebastian! > > It is a very nice piece of work you and Stefan have done! I fully > agree that we need to make archetypes compatibility checking explicit > and this is a very good start. > > It will be useful to publish the algorithm that you used for > comparison so others cou

Security & Privacy with openEHR

tient record. > > This does shade some light on some of what I said above. Would it help > if access permissions are granted in a durative manner and access rights > are hierachical, prioritised, role-based and scoped such that there is a > scheme for auto-granting of rights that ensures that a cardiologist with > sufficient permissions always gets all the info he needs to create a > full report? however, auto-granting of rights may imply need for > decision support. > > or Artificial INtelligence ;-) See what I said above. - thomas beale

Archetype documentation using XML + XSLT

An HTML attachment was scrubbed... URL:

Archetype documentation using XML + XSLT

An HTML attachment was scrubbed... URL:

Archetype documentation using XML + XSLT

ean you need decent shell and/or other glue languages like make or Ant or whatever, but unix is good at that. - thomas beale

Archetype documentation using XML + XSLT

Adam Flinton wrote: > > Oh & one quick ancillary question > > Does this/ Would this include Template (.oet) > XHTML via XSLT? > > *Adam, The current (simple) .oet XML format for templates will soon be replaced with a proper openEHR XSD (also simple) which is more based on the AOM, and h

Archetype documentation using XML + XSLT

The power of ADL is important to me now as I am in the midst of defining extensions and semantics for specialisation. I originally thought I would do it directly as an object model, but found I had to go back to ADL to understand the semantics properly; changing / enhacing object models will come

Archetype documentation using XML + XSLT

Adam Flinton wrote: > >> Other limitations on using XML - it's a no-show for enterprise scale >> databases >> or information processing. All that wasted space starts to count when you >> have >> to buy two ?20,000 high availability RAID disk arrays instead of oneand >> plus >> the band

Archetype documentation using XML + XSLT

An HTML attachment was scrubbed... URL:

Archetype documentation using XML + XSLT

ueries; portable queries are the basis of decision support having any hope of being able to define queries once and for all into a standardised health record rather than havig to have queries written not just for each target system type, but for each installation, if database schemas differ (and they do in the NHS environment). - thomas beale * *

Regex in Archetypes must include TYPE

Adam Flinton wrote: >> >> No need to do that, Adam, just wrap the regex within parentheses. So taking >> the example you gave, the correctly-wrapped regex would be: >> >> Include entries >> openEHR-EHR-CLUSTER\.(checklist_item-general-cvs1.v1|checklist_item-general-cvs2.v1|checklist_item-general-c

Regex in Archetypes must include TYPE

ed at a technical level - it is just that they might create errors. And there may be some short patterns which are actually correct. I'm not sure how we can formally state this - thomas Peter Gummer wrote: > Thomas Beale wrote: > >> I also agree with Adam. A regex sho

Differential display

> > Cheers, Thilo > > > _______ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-tec

Differential display

especially when the users are used to having two ways of displaying > the same data. > > Heath > > >> -Original Message- >> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- >> bounces at openehr.org] On Behalf Of Thomas Beale >>

Is there a UML class diagram for templates?

icate which one you are after? - thomas beale *

Differential display

the semantics of data in a package like MD translates to archetyped structures, which are independent of the vendor product trying to extract data from the GP dekstop. - thomas beale

[openEHR-announce] UK openEHR training 24/25 July CHIME, UCL (Archway, London)

Paria, See the openEHR home page > Events - thomas beale P?ria Kashfi wrote: > Hi all, > Has anyone any idea about this course? > I want to apply but it seems that the link doesn't work anymore > > Regards > paria > > On Jul 10, 2008, at 12:59 PM, Thom

Is there a UML class diagram for templates?

as you can see from the draft is only a small number of classes. - thomas beale > Thomas Beale wrote: > > Adam Flinton wrote: > > > >> Preferably in Eclipse UML2...? > >> > >> If so does it then include the archetypes class model as well? >

Is there a UML class diagram for templates?

; >> http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes > >> > >> However, if you are after UML for the current .oet file format, I don't > >> think it is published, but I would imagine it already exists - > >> publish

text and description

on within ontology section where used > terminologies are declared explicitly; i.e. "umls": 2008AA version of > NLM UMLS knowledge sources. Perhaps an URI and other details can be > specified (i.e. WSDL). I think it is easier for the community to agree > on such a naming convention. you can already do this - umls(2008AA)::123456 etc - thomas beale

text and description

g number will suffice. > > Will this be the way to go? I didn't know of this body. How does their registry correlate to the UMLS list? How do they handle revisions of terminologies? How do they handle language variants (including ones that are of earlier revisions, or are partial)? - thomas beale

text and description

Ian McNicoll wrote: > Hi Thomas, > > According to Support_IM 5.3.2 > > "Valid identifiers that can be used for this attribute for > terminologies include but are not limited to the > following: > ? "openehr" > ? "centc251" > ? an identifier value from the first column of the US National Library >

ADL workbench - specialisation beta

hr.org/svn/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm). - thomas beale

{Disarmed} Re: text and description

ce for terms that are created only in > the template but for internationalisation. > I would expect to do it in the same way as for archetypes - binidings. Just the same, but in templates. - thomas beale

Q on openEHR XML-schema versioning

course. I am more concerned to correct the version id situation. All feedback welcomed. - thomas beale

Q on openEHR XML-schema versioning

Andrew Patterson wrote: >> 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 >> ;

definition of object_path

so acceptable. > only absolute paths are allowed (so far; I think anything else will be too complicated and I don't see any strong need) - thomas beale

list_open

ing no typing information at all for basic types in dADL In C_STRING, list_open is a constraint flag that says whether or not only the values in the list are allowed to be used; True = other values possible (i.e. the listed values are just 'preferred'). The same syntax is used, e.g. {"a", "b", ...} is an open list. - thomas beale

{Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL:

{Disarmed} Re: {Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL:

XML 1.0 fifth edition

How much of a problem is the issue reported here to openEHR - http://dpcarlisle.blogspot.com/2008/10/xml-10-fifth-edition.html ? - thomas beale

{Disarmed} Re: Q on openEHR XML-schema versioning

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

{Disarmed} Re: Q on openEHR XML-schema versioning

a new major version (1.1 or later) to change tack on how to manage schema versions. I would suggest that XML experts here would need to develop a bullet-proof approach to this (as opposed to just suggestions), so that we can implement it in a major release. - thomas beale Heath Frankel wrote

{Disarmed} OpenEHR evaluation

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

openehr-technical@lists.openehr.org

h is always the archetypes and templates. The descriptions and diagrams on this page provide a high-level explanation. - thomas beale *

Understanding XML archetypes..

Oxford Partnership wrote: > Erik > > Many thanks for the quick reply. > > I have no issues with the two level models used in OpenEHR, it makes > perfect sense to me to have an underlying RM for all archetypes to be > based on. > > If I am understand you correctly, then : > > - No attributes wit

Understanding XML archetypes..

Heath Frankel wrote: > "An archetype not based on a reference model is impossible (or at least > pointless)." > Erik Sundvall > > Erik, > I love this comment, it should be put up on the openEHR Web Site as the > "Play of the Day". > > So many times I see people trying to use Archetypes without a

persistence

An HTML attachment was scrubbed... URL:

persistence

Bert Verhees wrote: > > People discuss very seriuous all kind of subjects, very deeply, that is > OK, but why do they never discuss a solution to a Persistence-layer-API? > (not the layer itself, only the API.) > Another thing that is never discussed, that is the service-layer-API, > same question,

EQL was: persistence

Bert Verhees wrote: > > But is has, in my opinion nothing to do with that. Maybe when the EQL > definition is ready to use (I don't see much of discussion about this > subject, but maybe the EQL discussion is a private discussion?), than > again a way to implement it must be found,a nd maybe this c

EQL was: persistence

nEHR. This is of more importance than the current standards activities in my view, since the result will have running software behind it and will be known to work. It will also have been designed rather than put together by committee. - thomas beale

persistence

Bert Verhees wrote: > > What I need is a strongly expressed intention to do something in a way I > suggest. > Serious people, not , say, pbublish your thing, and we will see. That is > not good enough. > > If we have a few people which want to join, and they seriously have > thought about in what

EQL was: persistence

Bert Verhees wrote: > Thomas Beale schreef: > >> > Thanks, I am very interested. > Will this be a part of a following version of OpenEhr? > (this is good to know in the context of conformance) > > *yes it will - it will appear in the next minor release as a draft

path of ArchetypeInternalRef

Bert Verhees wrote: > Sam Heard schreef: > >> Heath has said it how it is: >> >> Archetype paths - that is the path to each node in an archetype - is >> unique. This is what the ADL statement you have seen refers to. >> >> In data, in contrast, an individual archetype node which has >> occurrenc

Developing with Archetypes

hat I suspect in a future release we may simply combine the two schemas. Ocean Informatics also has a bidirectional XML <-> ADL parser component which can be open sourced if the funding is available. - thomas beale

{Disarmed} Comparison of EHR models

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: OceanC_small.png Type: image/png Size: 4972 bytes

Iconography & Screen shots.

Oxford Partnership wrote: > 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 to

Redux: Circular Imports

el implementation of the ADL parser this is used ubiquitously. There are other approaches of course. Anyway, it won't hurt your openEHR data not to have these references! - thomas beale

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

te model. but some are not yet. I wonder if we can construct a definitive list? > Artifacts built using that model could then be used for auto > generation of GUIs (whenever that is necessary) and as input to other > steps specifying things more to the "right" in the spectrum like &g

Reusable Archetypes

uantity one for everything. The semantics of the RM that need to be understood in this way probably constitute somewhat over 50% of the total classes and attributes. Probably we need this cut down version to be visible in some way, e.g. as an exported view from a UML tool. - thomas beale *

Computation of time data in openEHR ...

but the semantics of these > time data is quite different, thus this should not be a problem, right? * all of the times you have mentioned occur somewhere on a notional real world timeline concerning the individual patient. Some are built-in to the openEHR reference model because they are universal, e.g. the times in History and Action (it dosn't matter what the data being collected are, these times always make sense). Others are completely dependent on the data being collected and are defined in archetypes. The latter are no less meaningful on the patient timeline however. * - thomas beale

proposal for managing migration to .adls (source form) archetypes

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 arc

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

An HTML attachment was scrubbed... URL:

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

Ian McNicoll wrote: > Hi Thomas, > > Other than the requirement for specialisation, am I correct in > thinking that this would give us 'named choices' which I have > suggested in the past (along with named slots)? This would be very > helpful in understanding the thinking behind the choice const

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

An HTML attachment was scrubbed... URL:

Archetypes including inherited content

tor during the next few months. Other changes that will be included are described in the new specialisation semantics in the ADL specification. See http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes for details. As ever the speed of this work is dependent on funding. - thomas beale

Is there an OpenEHR technical commitee?

n (ADL 1.4) then they should be able to communicate .adl and .xml archetypes. This is indeed currently the case. hope this helps - thomas beale Tim Cook wrote: > Hi Adam, > > On Wed, 2008-07-16 at 13:31 +0100, Adam Flinton wrote: > >> Dear All, >> >> I have rai

archetypes - distniguishing multiple alternative constraints of a single-valued attribute

An HTML attachment was scrubbed... URL:

Where is the Archetype spec?

An HTML attachment was scrubbed... URL:

Where is the Archetype spec?

done under another tool. See http://www.openehr.org/mailarchives/openehr-technical/msg03577.html - thomas Adam Flinton wrote: > Thomas Beale wrote: > >> Adam Flinton wrote: >> >>> Dear All, >>> >>> I have been poking about the openEhr site

proposal for managing migration to .adls (source form) archetypes

An HTML attachment was scrubbed... URL:

Regex in Archetypes must include TYPE

An HTML attachment was scrubbed... URL: -- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 5828 bytes D

Release 1.0.2 change - SPEC-260 - Correct the regex published for the ARCHETYPE_ID type (due date 304/Aug/08)

/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

Regex in Archetypes must include TYPE

Sam Heard wrote: > Hi Thomas > > I had a look at the AOM and did not see anything, just include and > exclude statements - didn't read the ADL spec. The point here is that > we could have a slot that allowed different classes which would > simplify things for the archetype authors. in the AOM a

new draft of ADL 1.5 available

An HTML attachment was scrubbed... URL:

Release 1.0.2 change - SPEC-260 - Correct the regex published forthe ARCHETYPE_ID type (due date 304/Aug/08)

x27;.' V_NUMBER }* > V_NUMBER: [0-9]* > V_NATURAL_DIGIT: [1-9] > V_NAME: [a-zA-Z][a-zA-Z0-9_]+ > > The corresponding regex would be v[1-9](\.\d*)* , which differs from section > 4.3.10's regex in three respects: > > * It allows "v1.10", which surely is good; but > * It allows "v1.", and > * It disallows "v10"! > > So, once the regex is right, the production rules have to be fixed too. > yep...! - thomas beale

Release 1.0.2 change - SPEC-260 - Correct the regex publishedforthe ARCHETYPE_ID type (due date 304/Aug/08)

ssion equivalent of the above is as follows: [a-zA-Z]\w+(-[a-zA-Z]\w+){2}\.[a-zA-Z]\w+(-[a-zA-Z]\w+)*\.v[1-9]\d*(\.\d+){0,2} Peter Gummer wrote: > Thomas Beale wrote: > >>> v1.1.1.1 -- or even more than three parts? >>> >> yes you are right - we probab

Release 1.0.2 change - SPEC-260 - Correct theregex publishedforthe ARCHETYPE_ID type (due date 304/Aug/08)

Peter Gummer wrote: > Thomas Beale wrote: > > >> archetype_id: qualified_rm_entity ?.? domain_concept ?.? version_id >> >> qualified_rm_entity: rm_originator ?-? rm_name ?-? rm_entity >> rm_originator: V_NAME >> rm_name: V_NAME >> rm_enti

DADL optional rm-type

Bert Verhees wrote: > 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. > -- > I want to know, is it in all cases possible to guess the rm-type in a dadl- > construct? I ask this,

DADL optional rm-type

Bert Verhees wrote: > On Thursday 24 July 2008 17:29:41 Thomas Beale wrote: > >> > > Thanks, Thomas, for your reply. > What I am afraid of, is that, when allowing to NOT specify the rm-type name, > error-prone dadl-files can occur. Possibly an application receives erron

Release 1.0.2 change - SPEC-260 - Correct the regex publishedforthe ARCHETYPE_ID type (due date 304/Aug/08)

, I do not think we want 1.1.1 unless > people can come up with a sensible reason to have three levels. I > can't think of any benefit. > > Cheers, Sam > > Thomas Beale wrote: >> I now have the grammar and PERL regex as below. This is slightly >> im

Updating government, commercial and academic use of openEHR

updates for these pages. - thomas beale

openEHR Querying specifications

aterial is therefore intended as a resource for discussion and definition of a query language for openEHR. A team can be defined after sufficient time for the community to react to this material and determine if it makes sense to use AQL as the basis or to seek other solutions or candidates. - thomas beale

openEHR Querying specifications

Stef Verlinden wrote: > I'm not a technical person but to me it seems very cumbersome if such > 'differences' could exist between 2 versions of the same archetypes. > This would mean that for every query one has to go into detail of > every version of that AT which could mean al lot of work. > >

openEHR templates specification draft proposals available

material. - thomas beale

Parsing archetype xml with JAXB

Greg - I think this question would be better on the implementers list - to avoid causing too many heart attacks among the readers of this list on seeing actual code ;-) - thomas beale Greg Caulton wrote: > Hi, > > I used JAXB to generate java files from the XSD files but I am not

Archetypes - regex question

Andrew Patterson wrote: > Sam, without putting words in Adams mouth, I think he was asking about > the precedence of include/exclude sections. It is a common problem is > coming up with rule system like this - for instance one can look at the > allow/deny pattern of the apache2.conf file for how to

Question on the role of EHR reference models for achieving functional interoperability

model becomes more complex. If we want queryable, computable data (e.g. for decision support, research), you have to have models. Otherwise the software doesn't know what the data mean. - thomas beale *

Question on the role of EHR reference models for achievingfunctional interoperability

An HTML attachment was scrubbed... URL:

GUI-hints in openEHR templates? (Was: PatientOS archetype to form demo (of sorts))

I 'hints'. However, there are more semantic indicators being built into the template designer, some based on the NHS CUI project, that will provide good hints on GUI generation, including some temporal workflow aspects. - thomas beale *

Can you open a template (.oet) from an Href?

can be used to create message definitions from, and can be used at runtime. These changes plus the forthcoming standardised template models themselves will come through the openEHR process, so the final results in the template area will most likely differ from the current .oet files. - thomas beale

xml archetypes to xforms

to convert archetypes to Xforms, you want to convert openEHR Templates. The new specifications for templates are underway and drafts will be available in the next few weeks. - thomas beale

TDS, public development on openEHR wiki instead? (Was: Data-entry for OpenEhr)

An HTML attachment was scrubbed... URL:

New directions for openEHR 2008

An HTML attachment was scrubbed... URL:

New directions for openEHR 2008

KOBAYASHI, Shinji wrote: > Dear Thomas, > > > On Sat, 03 May 2008 13:12:59 +0100 > Thomas Beale wrote: > > >> - openEHR Specification Roadmap 2008 - >> http://www.openehr.org/specifications/spec_roadmap_2008.html >> > > I found ADL 1.5 in t

Datatype questions

leave for others... - thomas beale Adam Flinton wrote: > 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/

ARCHETYPE_ONTOLOGY

Tim Cook wrote: > 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_arc

ARCHETYPE_ONTOLOGY

Tim Cook wrote: > On Wed, 2008-05-07 at 18:04 +0100, Thomas Beale wrote: > > >> this attribute is populated in memory when an archetype is deserialised, >> so it points to the actual ARCHETYPE object. In almost every case (of >> the few that there are) that there

  1   2   3   4   5   6   7   8   9   10   >