| Name | Kind | Description |
| sample_count | attribute | Optional count of original samples to which this event corresponds. |
| scheme | operation | A distributed information "space" in which information objects exist. The scheme simultaneously specifies an information space and a mechanism for accessing objects in that space. For example if scheme = "ftp", it identifies the information space in which all ftpable objects exist, and also the application - ftp - which can be used to access them. Values may include: "ftp", "telnet", "mailto", "gopher" and many others. Refer to WWW URI RFC for a full list. New information spaces can be accommodated within the URI specification. |
| scheme | operation | The name of the access control scheme in use; corresponds to the concrete instance of the settings attribute. |
| scheme | attribute | Name of the scheme to which this identifier conforms. Ideally this name will be recognisable globally but realistically it may be a local ad hoc scheme whose name is not controlled or standardised in any way. |
| second_validity | attribute | Validity of second in constrained time. |
| second_validity | attribute | Validity of second in constrained time. |
| seconds_allowed | attribute | True if seconds are allowed in the constrained Duration. |
| SECTION | class | Represents a heading in a heading structure, or section tree . Created according to archetyped structures for typical headings such as SOAP, physical examination, but also pathology result heading structures. Should not be used instead of ENTRY hierarchical structures. |
| security | package | The Security Information Model defines the semantics of access control and privacy setting for information in the EHR |
| setting | attribute | The setting in which the clinical session took place. Coded using the openEHR Terminology, setting group. |
| settings | attribute | Access control settings for the EHR. Instance is a subtype of the type ACCESS_CONTROL_SETTINGS, allowing for the use of different access control schemes. |
| short_concept_name | operation | The short concept name of the archetype extracted from the archetype_id. |
| signature | attribute | OpenPGP digital signature or digest of content committed in this Version. |
| size | operation | Original size in bytes of unencoded encapsulated data. I.e. encodings such as base64, hexadecimal etc. do not change the value of this attribute. |
| size | operation | Original size in bytes of unencoded encapsulated data. I.e. encodings such as base64, hexadecimal etc do not change the value of this attribute. |
| size | operation | Size in bytes of value. |
| slot_owner | relation | |
| slot_specs | relation | |
| sm | package | |
| source | attribute | |
| source | operation | |
| source | attribute | |
| specialisation | operation | Name of specialisation of concept, if this archetype is a specialisation of another archetype, e.g. cholesterol . |
| specialisation_depth | operation | Specialisation depth of this archetype; larger than 0 if this archetype has a parent. Derived from ontology.specialisation_depth. |
| specialisation_depth | attribute | |
| start_time | attribute | Start time of the clinical session or other kind of event during which a provider performs a service of any kind for the patient. |
| STATE | class | Abstract definition of one state in a state machine. |
| STATE | artifact | |
| state | attribute | Optional state data for this event. |
| state | attribute | Optional recording of the state of subject of this observation during the observation process, in the form of a separate history of values which may be of any complexity. State may also be recorded within the History of the data attribute. |
| STATE_MACHINE | class | Definition of a state machine in terms of states, transition events and outputs, and next states. |
| STATE_MACHINE | artifact | |
| states | relation | |
| string_expression | attribute | String form of expression, in case an expression evaluator taking String expressions is used for evaluation. |
| subject | attribute | The subject of this EHR. The external_ref attribute can be used to contain a direct reference to the subject in a demographic or identity service. Alternatively, the association between patients and their records may be done elsewhere for security reasons. |
| subject | attribute | Id of human subject of this ENTRY, e.g.: * organ donor * foetus * a family member * another clinically relevant person. |
| subject | attribute | Identifiers for subject of the received information item. |
| subject_is_self | operation | Returns True if this Entry is about the subject of the EHR, in which case the subject attribute is of type PARTY_SELF. |
| subtract | operation | Result of subtracting a differential amount from this quantity. |
| subtract | operation | Subtract a time period from this date. |
| subtract | operation | Subtract a time period from this date_time. |
| subtract | operation | Subtract a duration from this time. |
| summary | relation | Optional summary data expressing e.g. text or image which summarises entire History. |
| support | package | The rm.support package describes the most basic concepts, required by all other packages, and is comprised of the Definitions, Identification, Terminology and Measurement packages. The semantics defined in these packages allow all other models to use identifiers and to have access to knowledge services like terminology and other reference data. The support package includes the special package assumed_types, describing what basic types are assumed by openEHR in external type systems; this package is a guide for integrating openEHR models proper into the type systems of implementation technologies. |
| support_packages_cv | class view | |
| support_packages_OVERVIEW | class diagram | Overview of the classes included in the Support package of the openEHR Reference Model. |
| symbol | attribute | Coded textual representation of this value in the enumeration, which may be strings made from + symbols, or other enumerations of terms such as mild , moderate , severe , or even the same number series as the values, e.g. 1 , 2 , 3 . Codes come from archetype. |
| system_id | attribute | Identity of the system where the change was committed. Ideally this is a machine- and human-processable identifier, but it may not be. |
| system_id | attribute | The id of the EHR system on which this EHR was created. |
| system_id | attribute | Identifier of the system which handled the information item. |