Generated Narrative: ValueSet R3-v3-SecurityControlObservationValue-for-R4B This value set expansion contains 91 concepts. System Version Code Display Definition http://hl7.org/fhir/v3/ActCode 2016-11-11 ANONY anonymize Custodian system must remove any information that could result in identifying the information subject. http://hl7.org/fhir/v3/ActCode 2016-11-11 AOD accounting of disclosure Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested. http://hl7.org/fhir/v3/ActCode 2016-11-11 AUDIT audit Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. http://hl7.org/fhir/v3/ActCode 2016-11-11 AUDTR audit trail Custodian system must monitor and maintain retrievable log for each user and operation on information. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYCC comply with confidentiality code Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYCD comply with consent directive Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYJPP comply with jurisdictional privacy policy Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYOPP comply with organizational privacy policy Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYOSP comply with organizational security policy Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. http://hl7.org/fhir/v3/ActCode 2016-11-11 CPLYPOL comply with policy Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. http://hl7.org/fhir/v3/ActCode 2016-11-11 DECLASSIFYLABEL declassify security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. http://hl7.org/fhir/v3/ActCode 2016-11-11 DEID deidentify Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. http://hl7.org/fhir/v3/ActCode 2016-11-11 DELAU delete after use Custodian system must remove target information from access after use. http://hl7.org/fhir/v3/ActCode 2016-11-11 DOWNGRDLABEL downgrade security label Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. http://hl7.org/fhir/v3/ActCode 2016-11-11 DRIVLABEL derive security label Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. http://hl7.org/fhir/v3/ActCode 2016-11-11 ENCRYPT encrypt Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.) http://hl7.org/fhir/v3/ActCode 2016-11-11 ENCRYPTR encrypt at rest Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. http://hl7.org/fhir/v3/ActCode 2016-11-11 ENCRYPTT encrypt in transit Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means. http://hl7.org/fhir/v3/ActCode 2016-11-11 ENCRYPTU encrypt in use Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user. http://hl7.org/fhir/v3/ActCode 2016-11-11 HUAPRV human approval Custodian system must require human review and approval for permission requested. http://hl7.org/fhir/v3/ActCode 2016-11-11 LABEL assign security label Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes. http://hl7.org/fhir/v3/ActCode 2016-11-11 MASK mask Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". http://hl7.org/fhir/v3/ActCode 2016-11-11 MINEC minimum necessary Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOAUTH no disclosure without subject authorization Prohibition on disclosure without information subject's authorization. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOCOLLECT no collection Prohibition on collection or storage of the information. http://hl7.org/fhir/v3/ActCode 2016-11-11 NODSCLCD no disclosure without consent directive Prohibition on disclosure without organizational approved patient restriction. http://hl7.org/fhir/v3/ActCode 2016-11-11 NODSCLCDS no disclosure without information subject's consent directive Prohibition on disclosure without a consent directive from the information subject. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOINTEGRATE no integration Prohibition on Integration into other records. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOLIST no unlisted entity disclosure Prohibition on disclosure except to entities on specific access list. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOMOU no disclosure without MOU Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU). http://hl7.org/fhir/v3/ActCode 2016-11-11 NOORGPOL no disclosure without organizational authorization Prohibition on disclosure without organizational authorization. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOPAT no disclosure to patient, family or caregivers without attending provider's authorization Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone). http://hl7.org/fhir/v3/ActCode 2016-11-11 NOPERSISTP no collection beyond purpose of use Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited. http://hl7.org/fhir/v3/ActCode 2016-11-11 NORDSCLCD no redisclosure without consent directive Prohibition on redisclosure without patient consent directive. http://hl7.org/fhir/v3/ActCode 2016-11-11 NORDSCLCDS no redisclosure without information subject's consent directive Prohibition on redisclosure without a consent directive from the information subject. http://hl7.org/fhir/v3/ActCode 2016-11-11 NORDSCLW no disclosure without jurisdictional authorization Prohibition on disclosure without authorization under jurisdictional law. http://hl7.org/fhir/v3/ActCode 2016-11-11 NORELINK no relinking Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOREUSE no reuse beyond purpose of use Prohibition on use of the information beyond the purpose of use initially authorized. http://hl7.org/fhir/v3/ActCode 2016-11-11 NOVIP no unauthorized VIP disclosure Prohibition on disclosure except to principals with access permission to specific VIP information. http://hl7.org/fhir/v3/ActCode 2016-11-11 ORCON no disclosure without originator authorization Prohibition on disclosure except as permitted by the information originator. http://hl7.org/fhir/v3/ActCode 2016-11-11 ObligationPolicy obligation policy Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. http://hl7.org/fhir/v3/ActCode 2016-11-11 PERSISTLABEL persist security label Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. http://hl7.org/fhir/v3/ActCode 2016-11-11 PRIVMARK privacy mark Custodian must create and/or maintain human readable security label tags as required by policy. Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." http://hl7.org/fhir/v3/ActCode 2016-11-11 PSEUD pseudonymize Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. http://hl7.org/fhir/v3/ActCode 2016-11-11 REDACT redact Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. http://hl7.org/fhir/v3/ActCode 2016-11-11 RefrainPolicy refrain policy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc. http://hl7.org/fhir/v3/ActCode 2016-11-11 SecurityPolicy security policy Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent http://hl7.org/fhir/v3/ActCode 2016-11-11 UPGRDLABEL upgrade security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. http://hl7.org/fhir/v3/ActReason 2016-11-11 CAREMGT Care Management To perform one or more operations on information for provision of health care coordination. http://hl7.org/fhir/v3/ActReason 2016-11-11 CLINTRCH clinical trial research To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge. http://hl7.org/fhir/v3/ActReason 2016-11-11 CLINTRL clinical trial To perform health care as part of the clinical trial protocol. http://hl7.org/fhir/v3/ActReason 2016-11-11 CLMATTCH claim attachment To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services. http://hl7.org/fhir/v3/ActReason 2016-11-11 COVAUTH coverage authorization To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services. http://hl7.org/fhir/v3/ActReason 2016-11-11 COVERAGE coverage under policy or program To perform one or more operations on information for conducting activities related to coverage under a program or policy. http://hl7.org/fhir/v3/ActReason 2016-11-11 DISASTER disaster To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone. http://hl7.org/fhir/v3/ActReason 2016-11-11 DONAT donation To perform one or more operations on information used for cadaveric organ, eye or tissue donation. http://hl7.org/fhir/v3/ActReason 2016-11-11 ELIGDTRM eligibility determination To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment. http://hl7.org/fhir/v3/ActReason 2016-11-11 ELIGVER eligibility verification To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays. http://hl7.org/fhir/v3/ActReason 2016-11-11 ENROLLM enrollment To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices. http://hl7.org/fhir/v3/ActReason 2016-11-11 ETREAT Emergency Treatment To perform one or more operations on information for provision of immediately needed health care for an emergent condition. http://hl7.org/fhir/v3/ActReason 2016-11-11 FAMRQT family requested To perform one or more operations on information in response to a request by a family member authorized by the patient. http://hl7.org/fhir/v3/ActReason 2016-11-11 FRAUD fraud To perform one or more operations on information used for fraud detection and prevention processes. http://hl7.org/fhir/v3/ActReason 2016-11-11 GOV government To perform one or more operations on information used within government processes. http://hl7.org/fhir/v3/ActReason 2016-11-11 HACCRED health accreditation To perform one or more operations on information for conducting activities related to meeting accreditation criteria. http://hl7.org/fhir/v3/ActReason 2016-11-11 HCOMPL health compliance To perform one or more operations on information used for conducting activities required to meet a mandate. http://hl7.org/fhir/v3/ActReason 2016-11-11 HDECD decedent To perform one or more operations on information used for handling deceased patient matters. http://hl7.org/fhir/v3/ActReason 2016-11-11 HDIRECT directory To perform one or more operation operations on information used to manage a patient directory. Examples: facility enterprise payer health information exchange patient directory http://hl7.org/fhir/v3/ActReason 2016-11-11 HLEGAL legal To perform one or more operations on information for conducting activities required by legal proceeding. http://hl7.org/fhir/v3/ActReason 2016-11-11 HMARKT healthcare marketing To perform one or more operations on information for marketing services and products related to health care. http://hl7.org/fhir/v3/ActReason 2016-11-11 HOPERAT healthcare operations To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. http://hl7.org/fhir/v3/ActReason 2016-11-11 HOUTCOMS health outcome measure To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions. http://hl7.org/fhir/v3/ActReason 2016-11-11 HPAYMT healthcare payment To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. http://hl7.org/fhir/v3/ActReason 2016-11-11 HPRGRP health program reporting To perform one or more operations on information used for conducting activities to meet program accounting requirements. http://hl7.org/fhir/v3/ActReason 2016-11-11 HQUALIMP health quality improvement To perform one or more operations on information used for conducting administrative activities to improve health care quality. http://hl7.org/fhir/v3/ActReason 2016-11-11 HRESCH healthcare research To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. http://hl7.org/fhir/v3/ActReason 2016-11-11 HSYSADMIN health system administration To perform one or more operations on information to administer the electronic systems used for the delivery of health care. http://hl7.org/fhir/v3/ActReason 2016-11-11 MEMADMIN member administration To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program. http://hl7.org/fhir/v3/ActReason 2016-11-11 PATADMIN patient administration To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient. http://hl7.org/fhir/v3/ActReason 2016-11-11 PATRQT patient requested To perform one or more operations on information in response to a patient's request. http://hl7.org/fhir/v3/ActReason 2016-11-11 PATSFTY patient safety To perform one or more operations on information in processes related to ensuring the safety of health care. http://hl7.org/fhir/v3/ActReason 2016-11-11 PERFMSR performance measure To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions. http://hl7.org/fhir/v3/ActReason 2016-11-11 POPHLTH population health To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program. http://hl7.org/fhir/v3/ActReason 2016-11-11 PUBHLTH public health To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. http://hl7.org/fhir/v3/ActReason 2016-11-11 PWATRNY power of attorney To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative. http://hl7.org/fhir/v3/ActReason 2016-11-11 PurposeOfUse purpose of use Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes. http://hl7.org/fhir/v3/ActReason 2016-11-11 RECORDMGT records management To perform one or more operations on information used within the health records management process. http://hl7.org/fhir/v3/ActReason 2016-11-11 REMITADV remittance advice To perform one or more operations on information about the amount remitted for a health care claim. http://hl7.org/fhir/v3/ActReason 2016-11-11 SUPNWK support network To perform one or more operations on information in response to a request by a person authorized by the patient. http://hl7.org/fhir/v3/ActReason 2016-11-11 THREAT threat To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. http://hl7.org/fhir/v3/ActReason 2016-11-11 TRAIN training To perform one or more operations on information used in training and education. http://hl7.org/fhir/v3/ActReason 2016-11-11 TREAT treatment To perform one or more operations on information for provision of health care.
Cross-version ValueSet STU3.SecurityControlObservationValue for use in FHIR R4B
This cross-version ValueSet represents content from `http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26` for use in FHIR R4B.
This value set is part of the cross-version definitions generated to enable use of the value set `http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26` as defined in FHIR STU3 in FHIR R4B. The source value set is bound to the following FHIR STU3 elements: * Across FHIR versions, the value set has been mapped as: * `http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26` * `http://terminology.hl7.org/ValueSet/v3-SecurityControlObservationValue|2014-03-26` Note that all concepts are included in this cross-version definition because no concepts have compatible representations Following are the generation technical comments: All concepts in the comparison are have code literals listed as identical. The source value set has fewer active concepts (91) than the target (111), so the source is narrower than the target. FHIR ValueSet `http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26`, defined in FHIR STU3 does not have any mapping to FHIR R4B
comply with jurisdictional privacy policy
comply with organizational privacy policy
comply with organizational security policy
no disclosure without subject authorization
no disclosure without information subject's consent directive
no disclosure without organizational authorization
no disclosure to patient, family or caregivers without attending provider's authorization
no redisclosure without consent directive
no redisclosure without information subject's consent directive
no disclosure without jurisdictional authorization
no disclosure without originator authorization