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
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
as OIDs, the only benefit left is the readability, but even that is
becoming hard to do with the
: Friday, 8 April 2011 11:50 PM
To: openehr-technical at openehr.org
Subject: Re: openEHR artifact namespace identifiers
On 08/04/2011 14:28, pablo pazos wrote:
Hi Heath,
Just analysing OIDs vs. URIs:
Usage:
OIDs are in use in health informatics and other areas.
URIs are in use everywhere
://twitter.com/ppazos
Date: Fri, 8 Apr 2011 15:19:47 +0100
From: thomas.be...@oceaninformatics.com
To: openehr-technical at openehr.org
Subject: Re: openEHR artifact namespace identifiers
On 08/04/2011 14:28, pablo pazos wrote:
Hi Heath,
Just analysing
as long as it is properly administered.
Heath
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Thomas Beale
Sent: Friday, 8 April 2011 1:11 AM
To: openehr-technical at openehr.org
Subject: Re: openEHR artifact namespace identifiers
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
Hi Diego,
Very interesting. Is any of the documentation available without paying a
small fortune?
Ian
Dr Ian McNicoll
office +44 (0)1536 414994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
Clinical analyst, Ocean Informatics, UK
-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
From: heath.frankel at oceaninformatics.com
To: openehr-technical at openehr.org
Subject: RE: openEHR artifact namespace identifiers
Date: Fri, 8 Apr 2011 10:10:09 +0930
Hi Erik,
I was suggesting that we enforce OIDs, in fact my
On 08/04/2011 14:28, pablo pazos wrote:
Hi Heath,
Just analysing OIDs vs. URIs:
Usage:
OIDs are in use in health informatics and other areas.
URIs are in use everywhere in form of URLs
Procesing:
OIDs lack internal processing
URIs can be processed
Compatibility with actual
Oids probably are the one kind of id I would not propose for archetypes;
the multi-axial id in current use + the proposed namespace id is
equivalent to an Oid, just with some more constrained rules on what is
on the axes, and readable values. The need for a highly managed id
assignment system
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
11 matches
Mail list logo
