| Name | Kind | Description |
| parent | relation | C_ATTRIBUTE that owns this C_OBJECT. |
| parent | operation | Parent of this node in a compositional hierarchy. |
| parent_archetype | relation | |
| parent_archetype_id | attribute | Identifier of the specialisation parent of this archetype. |
| parent_resource | relation | Reference to owning resource. |
| PARTICIPATION | class | Model of a participation of a Party (any Actor or Role) in an activity. Used to represent any participation of a Party in some activity, which is not explicitly in the model, e.g. assisting nurse. Can be used to record past or future participations. Should not be used in place of more permanent relationships between demographic entities. |
| PARTICIPATION | artifact | |
| participations | relation | Parties involved in the healthcare event. These would normally include the physician(s) and often the patient (but not the latter if the clinical session is a pathology test for example). |
| PARTY_IDENTIFIED | class | Proxy data for an identified party other than the subject of the record, minimally consisting of human-readable identifier(s), such as name, formal (and possibly computable) identifiers such as NHS number, and an optional link to external data. There must be at least one of name, identifier or external_ref present. Used to describe parties where only identifiers may be known, and there is no entry at all in the demographic system (or even no demographic system). Typically for health care providers, e.g. name and provider number of an institution. Should not be used to include patient identifying information. |
| PARTY_IDENTIFIED | artifact | |
| PARTY_PROXY | class | Abstract concept of a proxy description of a party, including an optional link to data for this party in a demographic or other identity management system. Sub- typed into PARTY_IDENTIFIED and PARTY_SELF. |
| PARTY_PROXY | artifact | |
| PARTY_REF | class | Identifier for parties in a demographic or identity service. There are typically a number of subtypes of the PARTY class, including PERSON, ORGANISATION, etc. Abstract supertypes are allowed if the referenced object is of a type not known by the current implementation of this class (in other words, if the demographic model is changed by the addition of a new PARTY or ACTOR subtypes, valid PARTY_REFs can still be constructed to them). |
| PARTY_REF | artifact | |
| PARTY_RELATED | class | Proxy type for identifying a party and its relationship to the subject of the record. Use where the relationship between the party and the subject of the record must be known. |
| PARTY_RELATED | artifact | |
| PARTY_SELF | class | Party proxy representing the subject of the record. Used to indicate that the party is the owner of the record. May or may not have external_ref set. |
| PARTY_SELF | artifact | |
| path | operation | Path of this node relative to root of archetype. |
| path | operation | A string whose format is a function of the scheme. Identifies the location in <scheme>-space of an information entity. Typical values include hierarchical directory paths for any machine. For example, with scheme = "ftp", path might be /pub/images/image_01. The strings "." and ".." are reserved for use in the path. Paths may include internet/intranet location identifiers of the form: sub_domain...domain, e.g. "info.cern.ch" |
| path | attribute | The path to an instance in question, as an absolute path with respect to the object found at VERSION.data. An empty path means that the object referred to by id being specified. |
| path | attribute | |
| path | attribute | |
| path_exists | operation | True if the path exists in the data with respect to the current item. |
| path_of_item | operation | The path to an item relative to the root of this archetyped structure. |
| path_specs | relation | |
| path_unique | operation | True if the path corresponds to a single item in the data. |
| PATHABLE | class | The PATHABLE class defines the pathing capabilities used by nearly all classes in the openEHR reference model, mostly via inheritance of LOCATABLE. The defining characteristics of PATHABLE objects are that they can locate child objects using paths, and they know their parent object in a compositional hierarchy. The parent feature is defined as abstract in the model, and may be implemented in any way convenient. |
| PATHABLE | artifact | |
| pattern | attribute | Regular expression pattern for proposed instances of String to match. |
| performer | relation | The id and possibly demographic system link of the party participating in the activity. |
| period | operation | The period of the repetition, computationally derived from the syntax representation. Extracted from the value' attribute. |
| period | attribute | Period between samples in this segment if periodic. |
| physical_paths | operation | Set of language-independent paths extracted from archetype. Paths obey Xpath-like syntax and are formed from alternations of C_OBJECT.node_id and C_ATTRIBUTE.rm_attribute_name values. |
| pk_fraction | attribute | Numerator and denominator are integral, and the presentation method uses a slash, e.g. 1/2 . |
| pk_integer_fraction | attribute | Numerator and denominator are integral, and the presentation method uses a slash, e.g. 1/2 ; if the numerator is greater than the denominator, e.g. n=3, d=2, the presentation is 1 1/2 . |
| pk_percent | attribute | Denominator is 100, numerator is understood as a percentage value. |
| pk_ratio | attribute | Ratio type. Numerator and denominator may be any value. |
| pk_unitary | attribute | Denominator must be 1 |
| POINT_EVENT | class | Defines a single point event in a series. |
| POINT_EVENT | artifact | |
| preceding_version_uid | operation | Computed version of inheritance precursor, derived as item.preceding_version_uid. |
| preceding_version_uid | attribute | Stored version of inheritance precursor. |
| preceding_version_uid | operation | Unique identifier of the version of which this version is a modification; Void if this is the first version. |
| precision | attribute | Constraint on the precision of the DV_QUANTITY. A value of -1 means that precision is unconstrained. |
| precision | attribute | Precision to which the numerator and denominator values of the proportion are expressed, in terms of number of decimal places. The value 0 implies an integral quantity. The value -1 implies no limit, i.e. any number of decimal places. |
| precision | attribute | |
| previous_version | operation | Version of predecessor archetype of this archetype, if any. |
| primitive | package | Ultimately any archetype definition will devolve down to leaf node constraints on instances of primitive types. The primitive package defines the semantics of constraint on such types. |
| primitive_class_diag (am) | class diagram | |
| primitive_cv | class view | |
| primitive_dv | deployment view | |
| proof | attribute | Proof of attestation. |
| property | attribute | Optional constraint on units property . |
| PROPORTION_KIND | class | Class of enumeration constants defining types of proportion for the DV_PROPORTION class. |
| PROPORTION_KIND | artifact | |
| protocol | attribute | Description of the method (i.e. how) the information in this entry was arrived at. For OBSERVATIONs, this is a description of the method or instrument used. For EVALUATIONs, how the evaluation was arrived at. For INSTRUCTIONs, how to execute the Instruction. This may take the form of references to guidelines, including manually followed and executable; knowledge references such as a paper in Medline; clinical reasons within a larger care process. |
| provider | attribute | Optional identification of provider of the information in this ENTRY, which might be: * the patient * a patient agent, e.g. parent, guardian * the clinician * a device or software Generally only used when the recorder needs to make it explicit. Otherwise, Composition composer and other participants are assumed. |
| provider | attribute | Optional provider(s) who created, committed, forwarded or otherwise handled the item. |
| purpose | attribute | Purpose of the resource. |
| purpose | attribute | Purpose of the mapping e.g. automated data mining , billing , interoperability |