No comments about this one?
2012/1/13 Diego Bosc? :
> As Ian suggested I copy this issue from CKM to the technical list.
> I have seen that in some archetypes (e.g. Apgar or BloodPressure) that
> use DV_Duration restrictions (such as the width of the interval event
> in the blood pressure archetyp
Would this attribute value change depending on where is the archetype
used? i.e. if we use it on a GUI of a smartphone rather than a
standalone or web application
2012/1/25 David Moner :
>
> 2012/1/25 Thomas Beale
>>
>> Maybe another way of understanding this flag is as 'this node can be
>> skipp
We have included in LinkEHR a mindmap (freemind) generic
transformation based on AOM and we also use Freemind Flash Browser to
visualize it. Visualization is not the same as the one in CKM (as I
told is generic, see this example http://i.imgur.com/FlLFY.png) and if
you pass our LinkEHR reference mo
After checking the schema, I have seen some places that the schema
(specifically basetypes.xsd) is missing things that are indeed
supported by ADL (namely assumed_values, lists, etc.)
What is the process to update the schema?
I'm not sure if I have understood your question, but there isn't
already assertion support on the AOM?. just put an assertion of the
restricted and desired condition (in this case something like this:
"|event.time - history[at].origin|=P10M")
I don't really see the big issue about defining thin
Or simply using an assertion on the first place?
2012/1/15 Thomas Beale :
>
> A nicer approach could be as follows:
>
> we allow 'computed' attributes in the RM definition used by archetype tools,
> which will allow archetypes to be very clear and nice, e.g. in the case of
> 'offset'
> in the RM d
No, but they can be used for different things, from creating specific
editors, to mindmaps or sample GUI generation
2012/1/13 Thomas Beale :
> On 13/01/2012 08:46, Diego Bosc? wrote:
>> visible, allowed types, icon...
>
> ok - I understood those were settings relating to the display of that
> kind
visible, allowed types, icon...
2012/1/13 Thomas Beale :
>
> Hi Diego
>
> On 11/01/2012 03:12, Diego Bosc? wrote:
>> If it is really needed for the moment for representing templates then
>> it's OK with me (as long as we agree that this is a temporal thing),
>> but I still feel that having two sep
As Ian suggested I copy this issue from CKM to the technical list.
I have seen that in some archetypes (e.g. Apgar or BloodPressure) that
use DV_Duration restrictions (such as the width of the interval event
in the blood pressure archetype or the famous offset in the apgar
archetype) define them li
If it is really needed for the moment for representing templates then
it's OK with me (as long as we agree that this is a temporal thing),
but I still feel that having two separated places to rule UI
generation is a bad idea.
I think that annotations could work for you (even creating a new
specific
If you still say that properties can be restricted, then current
stable validated bmm files are incorrect, as they are currently
missing 90% of stored properties (all methods without parameters),
like all the ones in ITEM_TABLE.
2012/1/10 Thomas Beale :
> On 10/01/2012 14:32, David Moner wrote:
>>
Oh, this is the first time I have heard that functions can be
constrained. However, AOM specifications say otherwise:
"C_attribute: a node representing a constraint on an attribute
(i.e. UML ?relationship? or
?primitive attribute?) in an object type;" (AOM specifications, page 12)
This
When I was trying to validate an archetype with the reference model
(openEHR-EHR-OBSERVATION.apgar), I found something strange on all
'event' archetypes.
The EVENT class has a function (method) that calculates the offset.
However, in that archetype the offset was restricted as if it was an
attribut
I am using XMLserializer from Java implementation
2012/1/6 Heath Frankel :
> 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?" wrote:
>>
>> In ADL, the a
In ADL, the assumed value of a domain type is marked like this:
defining_code matches {
[local::
at1000, -- Standing
at1001, -- Sitting
at1002, -- Reclining
Put a couple of comments on the wiki, but I think it is a thing that
should be discussed on the list.
In ADL 1.5 a flag 'pass_through' was added. Its definition is 'Allows
nodes required for structuring data but otherwise redundant for screen
display and reporting to be detected by rendering softw
So has AQL been selected as the official openEHR query language?
2012/1/4 Seref Arikan :
> Greetings,
> The AQL grammar from the wiki has direct and indirect left recursion. Which
> means without changes in the grammar, LL parser generators (both JavaCC and
> Anltr) can't generate parsers for this
This is a simple question: Why does a simple archetype slot like this (ADL)
allow_archetype ELEMENT[at0001] occurrences matches {0..*} matches {
-- Archetype slot
include
archetype_id/value matches {/.*/}
}
ends up like this?
ELEMENT
It is not 'wrong', I'm just saying that following the same syntax for
everything would be better. We had already a discussion about this on
this same list regarding same issues on other schema. I was just
pointing them out in case they need to be changed.
2011/12/21 Heath Frankel :
> What is the
ok, then the link of the XSD is pointing to an old version (link on
this page
http://www.openehr.org/svn/specification/TRUNK/publishing/its/XML-schema/index.html).
This is the page that can be reached through the openEHR website menu.
and the second issue is still true: types with CamelCase and
un
I have been doing some tests with the file archetype.xsd available on
the webpage and I have run with some problems.
The main one is regarding BaseTypes.xsd, which supposedly defines
types such as intervalOfInteger, intervalOfDate..., but doesn't
contain them. Documentation
(http://www.openehr.org/
I am reading 1.0.2 IM and it says CARE_ENTRY, not GENERIC_ENTRY. which
one is the good one?
By the way, both ENTRY and CARE_ENTRY are abstract in openEHR. I don't
think you could only make ENTRY non-abstract without making CARE_ENTRY
non-abstract too (I think it has no sense to inherit an abstract
technically speaking, CLUSTER is already simpler in current 13606 model :)
2011/12/15 pablo pazos :
> Great! this will be THE opportunity to think about an IM 2.0, and the first
> topic on my wishlist is the simplification of ITEM_STRUCTURE & children :D
>
> --
> Kind regards,
> Ing. Pablo Pazos G
This is the description from the project in GitHu
(https://github.com/skoba/ruby-impl-openehr)
"This is the beta version 0.9.4 release of Ruby openEHR implementation
project. This release is still experimental preview of our work based
on openEHR specification release 1.0.2. We implemented almost
After reading Pablo's post on domain types I am curious about how
should they be represented on each one of the different formats. I
feel they should be 'expanded' before trying to represent them in any
other format, but I might be wrong. Any ideas or opinions?
2011/12/8 Koray Atalag :
> Oh, just
I have no problems on having different representations. In fact,
having different representations means more happy people, not less
(for example, people has been using RDF to describe archetypes for
some time).
Anyway I love this kind of threads, as are great to see new
perspectives and technologie
and if you want to express something like 'a set with all the past
test results for this patient' (that could have none)?
it would be a constraint as you are only allowing some kinds of
entries (children of a certain Snomed code for example)
2011/12/5 Sam Heard :
> Hi All
>
>
>
> I am going to say
Although this would work, I think that it would make ADL far less
readable and would oblige people to know always the reference model
underneath AND their parent archetype (if for some reason the parent
archetype is not available then you are completely screwed). Even if
you say that people should
':' 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
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
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
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
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
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
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
Good to hear about you! I hope everything is ok in Japan.
I would encourage you to put the archetypes on the CKM anyway, as I would
say that most of the available archetypes on the repository are in the
same situation as your archetypes (the implicit 'use under your own
responsibility')
2011/9/6 S
In my experience. you only need 2 or 3 CKM web services: search (with
different kinds of search) & download. I think those two are really
basic, and are also the ones that every repository must have (and
depending on the application, those are enough). Some of the other web
services (like freemind
My suggestion is for the this point
"Begin an open source software project for tools, web-based if
possible, to author archetypes, templates and terminology reference
sets directly interacting with the Clinical Knowledge Manager and
equivalent repository and review tools"
I agree with the first pa
The archetypes you are talking about are available on this URL
http://kenai.com/projects/openehr-app/sources/subversion/show/SANDBOX/openEHRApp_old/Archetypes?rev=726
Tuberculosis ones need to be translated to English
By the way, I found there some archetypes from usual CKM archetype
authors that
Hello Koray,
ASTM sells the standard + the schema, so I think the only way to
obtain it is to buy it from them
http://www.astm.org/Standards/E2369.htm
regards
2011/7/11 Koray Atalag :
> Hi All, I need CCR model ASAP. has anyone worked on this. Possible to share?
>
>
>
> Cheers,
> -koray
>
>
Thanks, that is what I was looking for
2011/6/21 Thomas Beale :
>
> For the tool, see
> http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html
>
> For the wiki page see here - you can see a lot of examples here.
>
> otherwise see the links on the page I mentioned be
I mean ADLs as referenced here
http://www.openehr.org/224-OE.html
".adls, for 'ADL source' files, allowing specialised archetypes to be
represented 'differentially' (like object-oriented subclasses)"
2011/6/21 Thomas Beale :
>
> Diego,
>
> if you mean the ADL 1.5 format, see the specs at the bott
Hello everyone,
I have been trying to found information about ADLs, but there is no
information on current (1.4) ADL document.
Searching the wiki for 'ADLs' doesn't work as returns all 'ADL' results.
Do you know where the documentation about ADLs can be found?
Regards
And again, why 'closed' and not occurrences {0}? Is really needed to
include a new reserved word when you already have the way of
expressing this?
When you resolve a use_archetype while generating the instance you
will put the data, not a reference to it. On the other hand, the model
tells you tha
Hello Thomas,
Some questions about the example available at the SVN
(http://www.openehr.org/svn/knowledge2/TRUNK/archetypes/openEHR_examples/ehr_extract_template/Working/Templates/ehr_extract/openEHR-EHR_EXTRACT-EXTRACT.t_basic_acute.v1.adls)
- What does the next snippet mean?
use_archetype COMP
I know that a draft is supposed to change, even big breaking changes.
what I don't like is the idea of not being able to describe what I am
using in my system or even describe it and everyone thinking is
another completely different thing
I think the main problem here is that we are using a single
2011/4/28 Thomas Beale :
> On 27/04/2011 10:44, Diego Bosc? wrote:
>
> I still don't see the problem
>
> If we wait until an archetype is published to care about versions then
> you will have v2 or v3 archetypes as much, which in my opinion breaks
> completely versioning purpose. What is the proble
I still don't see the problem
If we wait until an archetype is published to care about versions then
you will have v2 or v3 archetypes as much, which in my opinion breaks
completely versioning purpose. What is the problem with having a v27
archetype? Is it less pretty?
2011/4/27 Ian McNicoll :
>
I am OK with all that, my only problem is that new iterations should
make new versions if changes are enough (even in draft status). If not
all current projects using archetypes will be just wrong with the
'official' current archetype in CKM
The situation of two incompatible archetypes with the sam
So do you mean that only 23 (everything that is not draft) of the
current 270 archetypes on the CKM are 'safe' to be used? Everything
else could be completely changed in the next revision of the draft :(
2011/4/27 Ian McNicoll :
> Hi Diego,
> For those who are not aware, Diego is referring to a sl
Hello,
With the latest Demographic archetypes updates on the CKM I think we
have to be careful with archetype versioning. The new archetypes seem
quite different of the ones that were uploaded some time ago. They are
different on structure but the version of the archetype has not been
improved (an
Hello
I have been working some time in DCM/archetype metadata. Dublin Core
is suitable for that, however, there is an ISO norm (ISO 15699. Health
informatics. Clinical knowledge resources. Metadata ) which is an
extension of Dublin Core for Health informatics and it's even more
suitable. They have
That we are very cautious about reference model version changes
doesn't mean that any other organization does the same.
Look at HL7 v2 & v3 for example ;)
2011/4/8 Thomas Beale :
> On 07/04/2011 12:07, David Moner wrote:
>> Dear Thomas,
>>
>> I agree with your general approach, but you miss two im
Also, some of the restrictions of the identifier name seem arbitrary,
like minimum number of characters or what characters can you put.
2011/4/6 David Moner :
> Hello,
> I like that approach regarding namespaces, it will be needed sooner than
> later.
> Related to archetype identifiers there is an
Maybe we could use as inspiration all the available XML to GUI efforts
that already exist. Mostly to avoid reinventing the wheel
2011/3/25 pablo pazos :
> Hi Koray,
>
> I think we are the core group, and if we can agree some basic notation of
> some basic GUI directives (there are some thoughts of
I was saying that because some of the conditions Thomas said are
really clinical knowledge. I want to be able to express that one value
should be always greater than another, or that a score value of a
scale (norton, barthel...) is the addition of other parts of the
archetype. That's what I think s
I will suggest a new optional section on the ADL, if those conditions
end in the archetype tree structure it could really be a mess.
So if you just want to look for the structure you only have to ignore
that section
2011/3/23 Heath Frankel :
> Hi Seref,
> I agree with you sediments regarding Arch
But then if we want to communicate this coded string outside from our
openEHR system would be impossible to know 100% what it is. I don't
get the point of having 'mappings' (which could also be done by a
terminology service) and not having a 'qualifiers' or whatever.
Doesn't Loinc also allow post-
Hello,
So I was looking to the Text package in the data_types specification
and I was wondering how is supposed a DV_CODED_TEXT to handle a
post-coordinated term (from for example SNOMED). If I understand
correctly is something that relies in a supposed terminology service?
isn't doing that making
I think it is because of parsing collisions. I don't really see
another point to obligate the hours in a date_time
2011/3/18 Ian McNicoll :
> Thanks Peter / Thomas,
> This is quite important and I had not appreciated the limitations on the use
> of partial dates with DV_DATE_TIME. I would agree th
You can define openEHR demographic archetypes with LinkEHR
2011/3/8 Bert Verhees :
> Just for considering,
>
> It would be a nice thing if GENERIC_ENTRY was an option in the
> Archetype-Editor
>
> (also demographics, but that is an old discussion)
>
> Thanks,
> Bert Verhees
> _
For the lack of responses I assume that they are not available. Is
there at least an openEHR XML instance validator? we could try to make
the instances from scratch and validate them.
2011/3/1 Jesus Bisbal
>
> I second that. Very interested.
> I posted a similar request to this list a couple of y
I would be also interested in this.
2011/3/1 Tiago Pedrosa :
> Hi everyone,
> ? ? ? ?I'm looking for sampling OpenEHR records data. I will like to feed my
> repository with some sample data to make some test and try new
> services, does anyone knows where can I get that ?
> ? ? ? ?Thank you for yo
I vote for that :)
2011/2/24 Hugh Leslie :
> This is a great discussion.? I think it would be good to make sure it
> doesn't get lost.? Is it worth setting up a page on the wiki and moving some
> of the discussion there?
>
> On 22/02/2011 1:09 AM, pablo pazos wrote:
>
> Hi Thomas,
>
> Maybe we cou
And just as a comment, in the ADL 1.4 specs the example shows a URL.
Maybe should be better if a URN was shown
2011/2/21 pablo pazos :
> (just to clarify) I know that constraint bindings URIs are not actual
> working URIs that you can get a-la HTTP, I understand that here they are
> used as identi
and also, binding to URL seems like a bad decision for archetype
maintainability
2011/2/21 Andrew Patterson :
> Just to clarify some more, my contention is that you cannot
> look inside a arbitrary URI to pick out values without
> looking at the formal 'scheme' dependent spec.
>
> So in the case o
That was my point, that was a real Snomed attribute, with the spaces.
The result is even more unreadable
2011/2/21 Peter Gummer :
> Diego Bosc? wrote:
>
>> and we have also to deal with spaces!
>>
>
> Spaces are illegal in URIs. The correct form for the subset would be:
>
> ? ? ? ?subset=Antialle
I think the same, Pablo
Another thing, why use a slash ('/') between terminology and version?
why don't use URI modifiers for that also?
or sub-subsets
and we have also to deal with spaces!
2011/2/21 pablo pazos :
> Hi Peter, Diego,
>
> I think the URI way to define constraint bindings can be
If that is the valid way of defining in an URI form, it is
undocumented. the example should be put on the ADL specs.
And again not that difficult to support both kind of bindings. In my
opinion, is way more human
readable and needs the same degree of 'computer interpretation' than
the URI
2011/
I know it is on ADL specs, but why limit it to an URI? Second approach
could also be used to identify a subset
I understand the URI need, but I can think more than one occasion
where you have a defined termset and no URI for it
2011/2/18 Peter Gummer :
> Cati Mart?nez wrote:
>
>> ["ac0001"] = <[C
That seems a clear 'null flavour' use case
2011/2/2 Fabiane Bizinella Nardon :
>
> I came across this problem several times. It became almost impossible to use
> DV_BOOLEAN. The worst problem is that since DV_BOOLEAN has to be always true
> or false, if someone simply does not fill the field, it b
Is much different to change the field from 'test
result:positive/negative' to 'test result positive:true/false'?
If the semantics if not the same then the 'positive/negative' has more
meaning that a simple boolean and I think they should be coded
2011/2/2 Koray Atalag :
> Hi All, I?d like to get f
I'm ok with both number 2 and 3. I also like Tim idea
2011/1/13 Thomas Beale :
>
> The SVN repository at http://www.openehr.org/svn/knowledge2/ contains a
> library of ADL 1.5 reference test archetypes, 13606 test archetypes, openEHR
> RM tool schemas, a draft EN13606 tool schema. It is growing sl
There's also an opensource project called EHRFlex, which is an
archetype-based clinical registry system (EHR) independent of a
particular reference model. It uses clinical archetypes as guidelines
for the automatic generation of web interfaces, oriented to a clinical
use and data introduction.
Curr
The concept (DCM) is the same, but the implementation in different
standards will differ, as two different standards will never have the
same way of representing the same concept. As DCM should be even
broader than archetypes and templates, generating them from the DCM
should not be dangerous at al
>Because I still believe that the Apgar score in HL7 v3 MUST be 100% identical
>to the Apgar score in archetype. If that is not the case, both methods fail to
>do what they are intented for.
I have to disagree with that. The apgar DCM is only one, but the
different representations in each one of
I think the wiki is down
2010/11/22 Thomas Beale
> On 22/11/2010 00:23, Stef Verlinden wrote:
>
> Dear all,
>
> As Ed Hammond said it somewhere earlier in this discussion: It's like
> World Peace - a great idea but probably not achievable.
>
> I agree with Ed if we think along the line of ?o
> shorter Tom Beale: Only by ignoring use cases can one design usable data
> types?
I think is more like "you don't have to look only the use cases to
design usable data types"
> heh. XML forever, it will solve every problem in the world. Just if
> everyone else does it 'my' way, we'll be right.
Hello Jesus,
You can find it under Archetype->Bulk export...
you must be logged in to view that menu (not sure why...)
2010/11/16 Jesus Bisbal
> Dear all,
> I'm sure this question is very easily answered, but I can't find a way
> to download the whole archetype repository available at the
Regarding Cluster, there is a code to tell if a cluster is a table or
a list, so the computer always knows which one was chosen
2010/11/9 Hugh Leslie :
> Hi Andrew
>
> I'm happy to continue to have this discussion with you.? I still am not sure
> whether your objection to openEHR is about the fact
Reading your post I have remembered something I have read sometimes
but I haven't still gotten a satisfactory answer:
If UML and ADL are that similar, why don't we use both? What does UML
can express that ADL can not express that makes some people to dislike
it (and also what can ADL express that U
Shouldn't archetype identifiers and file names be separated?
2010/10/28 Peter Gummer :
> Erik Sundvall wrote:
>
>> openEHR-EHR-EVALUATION.problem.v1.adls
>> ? openEHR-EHR-EVALUATION.diagnosis.v1.adls
>> ? ? ?openEHR-EHR-EVALUATION.diagnosis_sweden.v1.adls
>> openEHR-EHR-LINK.indication.v1.adls
>>
Yeah, freemind XML is quite easy. I created a first version of a ADL (CEN
EN13606) to freemind converter in less than one day.
In my opinion the big drawback Freemind has at this moment is that it
doesn't display UTF-8 labels correctly (well, flash view does, but not
freemind program itself)
2010/
This discussion brings another one to my mind. Should be templates
dependent of the target platform? (or in other words, is visualization
ruled by tamplates?)
2010/9/24 Olof Torgersson :
> Hi,
> That sounds very interesting. I guess the same backend/server-solution could
> be used for making a nat
What about a person that is only used for family history for an
illness? Maybe you only know that the grandparent called 'John'
suffered from the same disease of your patient, but you don't know
much more about him.
2010/8/30 Stef Verlinden :
> Hi Sergio,
> From a non-technical perspective: what's
So is there a final template schema/specification? Last thing I know is that
both Ocean and Zilics had their own schema for templates
2010/1/20 Sebastian Garde
> Dear all,
>
> We have uploaded a new version of the Clinical Knowledge Manager:
>
> The CKM Release 1.1.0 adds initial support for te
Link to the wiki page?
2009/12/4 Erik Sundvall :
> Thanks Sebastian!
>
> You nicely adressed most of my concerns and seem to understand the problems.
>
> Tom & Sam: In this thread on Nov 17 I wrote "Many people start problem
> solving by a using a search engine, so that the discussions need to be
I haven't heard that anyone has developed it yet, but that is a very good idea
2009/10/5 gjb :
> I wonder if anyone has created themselves a syntax highlight file
> for use with Notepad++
> http://notepad-plus.sourceforge.net/uk/site.htm
> and would be willing to share it?
>
> Gavin Brelstaff CRS4
This is the mail that Catalina from Murcia University sent to the other lists
-
Hi,
I presented in the MIE conference at the end of August a poster
(http://www.hst.aau.dk/~ska/MIE2009/papers/MIE2009p0260.pdf) about a
ISO 13606 to OpenEHR and vice-versa converter. Some people asked for
me to
I'm not a CDA specialist, but seems that CDA has its own "archetypes" now
http://motorcycleguy.blogspot.com/2009/09/ihe-profile-proposal-for-document.html
--
Diego Bosc? Tom?s
Grupo IBIME
Instituto ITACA - Universidad Polit?cnica de Valencia
Acceso B
Edificio 8G
C
This reminds me a thing. Would be useful to have at ADL level
something like postconditions? (In your example, something stating how
to obtain or validate MBP from available values). I think this falls
into "knowledge" level.
2009/7/25 Thomas Beale :
> Bert Verhees wrote:
>
> yes - but to do this,
More people than you think still read and write ADL by hand, as
openEHR clinical model is not the only language you can build
archetypes (for instance, you can do archetypes of openEHR
demographics, CEN EN13606 clinical model or demographics). However,
it's true that available tools support or plan
The archetype constraints the reference model, if something isn't
explicit on the archetype definition the default classes and
attributes from the reference model are assumed
2009/5/7 Stef Verlinden :
> I've been working through the demographic AT's that were provided by Sergio.
> It's probably du
For your interest, there is a Research Group in Spain that is
developing an ADL2OWL transformation
http://klt.inf.um.es/~cati/Adl2Owl.htm
Diego
--
Diego Bosc? Tom?s
Grupo IBIME
Instituto ITACA - Universidad Polit?cnica de Valencia
Acceso B
Edificio 8G
Camino Vera
Last Friday I built an XSD schema following the openEHR demographics
model available on the openEHR web. I have been able to import it to
LinkEHR and do some test with the available demographic archetypes
(thanks Sergio) and seems to work well. I've uploaded it to the
LinkEHR webpage so anyone can
Just found a post from a year ago about the topic that I wanted to
ask so I'm refloating it.
Is the openEHR Demographics XSD Schema going to be released soon?
If not, can I have a copy of the draft?
2008/4/22 Heath Frankel :
> Hi Erik,
> Yes there was no demographics XSD schema published as part
301 - 396 of 396 matches
Mail list logo
