compartmentRepresents some kind of grouping to which a person must belong in order to be granted access to a particular set of resources. For example, a person might play the Structural Role of Pharmacist, a Functional Role of Lead Pharmacist for a VA isolation unit facility, but would need to belong to the Compartment of “national ebola research” in order to access. The Compartment clearance allows the ability to restrict access to those persons who are involved in the project.Security label metadata that "segments" a resource by indicating that access and use is restricted to members of a defined community or project. [HL7 HCS]A compartment value specifies whether there is a "need to know" permission for resource access. The value is in accordance with [HL7 HCS Vocab]. Examples of values are HRCOMPT (Human Resource Compartment), RESCOMPT (Research Project Compartment), and RMGTCOMPT (Records Management Compartment).Note that this was a separate class called Compartment, which was renamed from Group, but it has since been realized that this is a code (i.e., a pointer into a terminology) rather than a stand-alone class.
integritySecurity label metadata that “segments” a resource by conveying the completeness, veracity, reliability, trustworthiness, and provenance of the resource (e.g., anonymized, signed, Subject of Care reported). [HL7 PASS SLS]Integrity values indicate a resource’s trustworthiness and reliability (i.e., mechanisms used to ensure that the resource has not been tampered with or altered in unexpected manner). The values are in accordance with [HL7 HCS Vocab]. Examples of values are DIGSIG (Digital Signature) and CRYTOHASH (Cryptographic Hash Function).Integrity marking includes what types of access is allowed or denied to the resource. For example, allow reading of unsigned notes. [HL7 HCS]In general, integrity markings indicate things such as degree of reliability of the resource (e.g., a hierarchy from very reliable to unreliable) and the status of the resource (e.g., workflow status of a healthcare record from initial to complete to legally attested). [HL7 HCS]
privacyPolicy"Security label privacy tag that species the applicable privacy and security policies governing this term and/or term elements." - HL7 FHIR, Contract.term.securityLabel.category
provenanceSecurity label metadata that provides indicators of a resource’s source, authority, and context. [HL7 PASS SLS] Examples of values are HCPAST (Healthcare Professional Asserted) and CLINAST (Clinician Asserted).Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. [W3C Provenance]
sensitivityFieldSecurity label metadata that indicates the amount of damage that will result from the disclosure of the data and indicates which measures the data requires for protection from disclosure. The amount of damage that results from unauthorized disclosure depends on who obtains the data; the sensitivity label should reflect the worst case. [HL7 HCS, adapted from IETF RFC 1457]A sensitivity value specifies the labeled resource’s level of sensitivity per policy. The value is in accordance with [HL7 HCS Vocab]. Examples of values are DRGIS (Drug Information Sensitivity), PSY (Psychiatry Information Sensitivity), and HIV (Human Immunodeficiency Virus).Note that this was a separate class called Sensitivity, but it has since been realized that this is a code (i.e., a pointer into a terminology) rather than a stand-alone class.