Clinical Document Architecture V2.0.1
2.1.0 - CI Build
Clinical Document Architecture V2.0.1, published by Health Level 7. This is not an authorized publication; it is the continuous build for version 2.1.0). This version is based on the current content of https://github.com/HL7/cda-core-2.0/ and changes regularly. See the Directory of published versions
Definitions for the SC logical model.
1. SC | |
Definition | An ST that optionally may have a code attached. The text must always be present if a code is present. The code is often a local code. |
Control | 1..* |
2. SC.nullFlavor | |
Definition | If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing. |
Control | 0..1 |
Binding | The codes SHALL be taken from NullFlavor |
Type | code |
3. SC.charset | |
Definition | For character-based encoding types, this property specifies the character set and character encoding used. The charset shall be identified by an Internet Assigned Numbers Authority (IANA) Charset Registration [] in accordance with RFC 2978 []. |
Control | 0..1 |
Type | code |
4. SC.compression | |
Definition | Indicates whether the raw byte data is compressed, and what compression algorithm was used. |
Control | 0..0 |
Binding | The codes SHALL be taken from CompressionAlgorithm |
Type | code |
5. SC.integrityCheck | |
Definition | The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encapsulated data value with reference was created. |
Control | 0..0 |
Type | base64Binary |
6. SC.integrityCheckAlgorithm | |
Definition | Specifies the algorithm used to compute the integrityCheck value. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default choice for the integrity check algorithm. Note that SHA-256 is also entering widespread usage. |
Control | 0..0 |
Binding | The codes SHALL be taken from IntegrityCheckAlgorithm |
Type | code |
7. SC.language | |
Definition | For character based information the language property specifies the human language of the text. |
Control | 0..1 |
Type | code |
8. SC.mediaType | |
Definition | Identifies the type of the encapsulated data and identifies a method to interpret or render the data. |
Control | 0..1 |
Type | code |
Fixed Value | text/plain |
9. SC.representation | |
Control | 0..1 |
Type | code |
Fixed Value | TXT |
10. SC.data[x] | |
Definition | The string value |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
11. SC.reference | |
Definition | A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data. |
Control | 0..0 |
Type | http://hl7.org/fhir/cda/StructureDefinition/TEL |
12. SC.thumbnail | |
Definition | An abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encapsulated data. It allows a user to select data more efficiently before actually downloading through the reference. |
Control | 0..0 |
Type | http://hl7.org/fhir/cda/StructureDefinition/ED |
13. SC.code | |
Control | 0..1 |
Type | string |
14. SC.codeSystem | |
Control | 0..1 |
Type | string |
15. SC.codeSystemName | |
Control | 0..1 |
Type | string |
16. SC.codeSystemVersion | |
Control | 0..1 |
Type | string |
17. SC.displayName | |
Control | 0..1 |
Type | string |