This is implemented as described in ISO 21090.
Specializes
Attributes
| Name |
Data type |
Occurs |
Description |
| code |
CD
|
0..1 |
In the use of the SC datatype as described above there are specific constraints that must be applied to the CD value of the
SC.code attribute. In ISO 21090 there is already a constraint to have no originalText attribute. In the LRA the SC.code MUST
not contain source mappings, the SC.code.codeSystemName MUST provide a identifier as a string consisting of a URL to a maintained
accessible terminology service. The SC.code.codeSystemVersion and SC.code.code strings must act as extensions to that URL
to derive the specific value as specified in SC.Value (e.g. SC.code.codeSystemName = “http://some.ehr.manufacturer/vocabserver/somevocabulary/â€
SC.code.codeSystemVersion = “v1â€, SC.code.code = “Code1234â€. Then the URI “http://some.ehr.manufacturer/vocabserver/somevocabulary/v1#Code1234â€
MUST resolve to SC.Value. - see http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-URI-Vocabulary for further examples.).
At a most basic level this can be an stable HTML page which defines anchored elements for every entry in the local terminology.
|
Constraints
| Type |
Name |
Specification |
| no translations |
Invariant |
inv: translation->isEmpty |
Reference Model Type
