My additions to the Code List Design Requirements

[Alan.Stitzer@marsh.com]

Marty,

here you go.  My suggestions (as a starting point) for the code list design
requirements:




[R19] A list of the values (codes) for a code list

The code list must contain at least three (3) valid values to be considered
a code list.  If a code list contains only two values, it should be
considered a "boolean".

[R20] Multiple lists of equivalents values (codes) for a code list (e.g.
integers & mnemonics)

Individual code values must be able to be represented in multiple ways to
account for individual business requirements.

[R21] Unique identifiers for a code list

The code list must contain a unique identifier to be able to reference the
entire code list as an item.

[R22] Unique identifiers for individual values of a code list

Each code within the code list must contain a unique identifier to be able
to reference that particular code without knowing the code value or decode
value for that code.

[R23] Names for a code list

Each code list must have a unique name that adequately describes the
content of the list.

[R24] Documentation for a code list

Each code list must contain documentation which describes, in detail, the
business usage for this code list.

[R25] Documentation for individual values of a code list

Each code value on the code list must not only contain valid values and
decode values, but must also contain a long description which describes, in
detail, the business meaning


and usage for this code value.

[R26] The ability to import, extend, and/or restrict other code lists

Each code list must provide the ability to extend, restrict or import
additional values for this list.

[R28] Support for references to equivalent code lists

Each code list must be able to refer to other code lists that may or may
not be used in place of it.  These references are not necessarily exactly
the same, but may be equivalent based on business usage.

[R29] Support for individual values to be mapped to equivalent values in
other code lists

Each code list value must be able to refer to other code list values that
may or may not be used in place of it.  These references are not
necessarily exactly the same, but may be equivalent based on business
usage.

 [R30] Support for users to attach their own metadata to a code list

Each code list must have the flexibility to have additional descriptive
information added by an individual user to account for unique business
requirements.

[R31] Support for users to attached their own metadata to individual values
of a code list

Each code value must have the flexibility to have additional descriptive
information added by an individual user to account for unique business
requirements.


Hope this helps,





Regards,






____________________
Alan Stitzer
AVP
Marsh USA Inc.
1166 Avenue of the Americas
New York, NY 10036-2774
Phone: (561) 743-1938
Fax: (561) 743-1993
Internet: Alan.Stitzer@marsh.com
____________________


http://www.marsh.com