requirements for cc code list type from office of E-Envoy

[Anne Hendry <anne.hendry@sun.com>]

Do you remember reviewing in Montral the code list proposal from the UK 
Office of the eEnvoy?  Paul Spencer has brought their document to CLSC, 
and in reviewing  their requirements again we came across a couple of 
items that indicate a possible lack in the CC Code List type.  I've 
attached the email he sent after the meeting that highlighted the 
requirements we felt needed further deliberation.  Specifically for CCT, 
though, there are two items that we think may require a change to the cc 
code list type.  Drawing from his attached list, they are:

a) under 'Versioning', the ability to say how long the code list is 
valid.  This would require a date (which is in the cctype), but also a 
duration, which is not.

b) under 'Must be able to carry both a code and (optional) value in the 
message".   I only see a place to carry the code in the cc code list 
type (code.content), not any place for an additional descriptive content 
to be delivered along with the code(content).

Who would be the best person/group to further review this (don't say 
clsc, becuase this is where it came from! ;))?

Thanks,
Anne



Subject:
[ubl-clsc] UK Gov Codelist Requirements
From:
"Paul Spencer" <paul.spencer@boynings.co.uk>
Date:
Wed, 28 Jan 2004 20:24:35 -0000
To:
<ubl-clsc@lists.oasis-open.org>

As requested at today's telecon, these are the requirements extracted from
my position paper on codelists that was recently uploaded.

Support long-term archiving of documents
----------------------------------------
Many documents require long-term archiving. To achieve this, the documents
must be able to indicate the version of a code set that is in use. They
should do this both in the code list reference in the instance document (so
the correct set is accessed) and in any document metadata (so that the code
list(s) required can be archived with the document).

Versioning
----------
A code list must indicate its version number. It may also provide dates
between which it is valid. A reference to a code list must indicate the
version to which it refers.

Looking up Code Meanings
------------------------
It must be possible to find the meaning of any code in the code set.

Multiple definitions (e.g. short and long)
------------------------------------------
The mechanism used for holding code sets must support multiple definitions.
Specifically, it must be possible to hold both a short description, a long
description and a symbol (with information on the correct positioning of the
symbol relative to the value).

Multi-lingual
-------------
The mechanism used for holding code sets must support extracting information
in multiple languages.

Must be able to carry both a code and (optional) value in the message
---------------------------------------------------------------------
A requirement in the health service (and possibly elsewhere) is that both a
code and a meaning can be carried in a document. As an example of the use of
this, if a person selects a value from a drop-down list on a web page, the
text selected as well as a code describing it must be transmitted to health
systems for audit purposes, even though the receiving application might
ignore the text and use the indicated code list to look up a meaning.

These are the main requirements, and so the most important part. The rest of
the document goes into detail including proposing a syntax.

Regards

Paul Spencer
Director
Boynings Consulting Ltd
http://www.boynings.co.uk