Thomas,

Will you bring this topic up in Berlin?

Gerard

-- 
-- 
Gerard Freriks, MD
Convenor CEN/TC251 WG1

TNO Quality of Life
Wassenaarseweg 56
Leiden

PostBox 2215
22301CE Leiden
The Netherlands

+31 71 5181388
+31 654 792800
On 27 Apr 2005, at 13:48, Bert Verhees wrote:

> Op woensdag 27 april 2005 11:21, schreef Thomas Beale:
>> Bert Verhees wrote:
>>>> presented as belonging together,
>>>
>>> it is not that simple, a collection of information can have more 
>>> then one
>>> number, and the CEN-standard does not provide meta-information in 
>>> some
>>> cases, f.e. PatientExtendedInformation carries a Set<II>, which is a 
>>> set
>>> of numbers (identifiers), those numbers in a list do not have
>>> meta-information, except for the OID, but that meta-information can 
>>> only
>>> be resolved over a network-service (which does not yet exist).
>>
>> as I have indicated before, I think that CEN needs the data type we
>> added to openEHR - DV_INDENTIFIER, whose definition is below. I also
>
> It would help me a lot if CEN would take this instead of the original 
> ID, this
> one has all what is suitable for my purpose
>
> Bert
>
>> don't agree that it is realistic to identify everything with OIDs. 
>> There
>> are three reasons, the major one Bert has already given.
>>
>> 1. non-accessibility and/or performance of resolving engine
>> 2. size of ids inside data, particularly data fragments that can never
>> be sensibly accessed globally, only from within the context of some
>> larger blob. E.g. it doesn't make sense to access a single ELEMENT in 
>> a
>> CEN CLUSTER/ELEMENT tree, so why attach a 20 digit Oid to it?
>>
>>
>> class DV_IDENTIFIER
>> inherit
>>     DATA_VALUE
>>
>> feature -- Access
>>
>>     issuer: STRING
>>             -- Issuing agency of these kind of ids
>>
>>     id: STRING
>>             -- The identifier value. Often structured, according to 
>> the
>>             -- definition of the issuing authority?s rules.
>>
>>     type: STRING
>>             -- The identifier type, such as ?prescription?, or ?SSN?.
>>             -- One day a controlled vocabulary might be possible for 
>> this.
>>
>> invariant
>>     issuer_valid: issuer /= Void and not issuer.is_empty
>>     id_valid: id /= Void and not id.is_empty
>>     type_valid: type /= Void and not type.is_empty
>>
>> end
>>
>>
>> - thomas beale
>>
>>
>> -
>> If you have any questions about using this list,
>> please send a message to d.lloyd at openehr.org
>
> -- 
> Met vriendelijke groet
> Bert Verhees
> ROSA Software
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2630 bytes
Desc: not available
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050428/b29ecbf6/attachment.bin>

Reply via email to