Section 1e: Version 3 (V3)
Section 4: Rules and References
HL7 Version 3 Standard: Security and Privacy Ontology, Release 1
DESCRIPTION
The HL7 Security and Privacy Ontology serves to name, define, formally describe, and interrelate key security and privacy concepts within the scope of Healthcare Information Technology, including security policies, privacy policies, consent directives, resulting access control, and related ideas.
ALTERNATIVE NAMES
HL7 Version 3 Standard: Security and Privacy Ontology, Release 1 may also go by the following names or acronyms:
"HL7 V3 Security and Privacy Ontology, R1", Security and Privacy Ontology, SPO, V3
TARGETS
- Clinical and Public Health Laboratories
- Immunization Registries
- Quality Reporting Agencies
- Standards Development Organizations (SDOs)
- Regulatory Agency
- Payors
- Pharmaceutical Vendors
- EHR, PHR Vendors
- Equipment Vendors
- Health Care IT Vendors
- Clinical Decision Support Systems Vendors
- Lab Vendors
- HIS Vendors
- Emergency Services Providers
- Local and State Departments of Health
- Medical Imaging Service Providers
- Healthcare Institutions (hospitals, long term care, home care, mental health)
BENEFITS
The HL7 Security and Privacy Ontology addresses several key objectives:
- Identify important concepts in the area of Healthcare IT security and privacy.
- Establish standardized names for concepts in the area of Healthcare IT security and privacy.
- Give clear, precise textual definitions to concepts in the area of Healthcare IT security and privacy.
-
Constitute an authoritative ontology, with concepts that are:
- Formally and unambiguously defined (to the extent practical) using OWL.
- Classified in a well-organized taxonomy (class hierarchy).
- Otherwise connected in meaningful and useful ways.
- Mutually consistent.
-
Support consistent and effective Healthcare IT software implementations, especially by enabling security/privacy systems, thus:
-
Providing a sound basis for convenient, interoperable specification of e-Policies and e-Directives, which:
- Are expressed at suitable levels of abstraction (thus appropriate and stable over time).
- Can be rigorously checked for coherence, compared, and combined if possible.
- Achieving sound access control decisions.
-
Providing a sound basis for convenient, interoperable specification of e-Policies and e-Directives, which:
- Inform other work of the HL7 Security and CBCC Work Groups, such as the Composite Security and Privacy Domain Analysis Model.
-
Align with:
- The HL7 Service-Aware Interoperability Framework (SAIF).
- The HL7 RBAC Healthcare Permission Catalog.
- The HL7 Healthcare Privacy and Security Classification System (HCS).
- Other Healthcare IT terminologies such as SNOMED CT and the HL7 vocabularies, as appropriate.
IMPLEMENTATIONS/CASE STUDIES
- US Department of Veterans Affairs (VA)
RELATED DOCUMENTS
HL7 Version 3 Standard: Security and Privacy Ontology, Release 1 |
(Download) (1.31 MB) |
TOPIC
- Security and Privacy
BALLOT TYPE
- Normative
STATUS DATE
2014-05-30RESPONSIBLE WORK GROUP
STAKEHOLDERS
- Clinical and Public Health Laboratories
- Clinical Decision Support Systems Vendors
- EHR, PHR Vendors
- Emergency Services Providers
- Equipment Vendors
- Health Care IT Vendors
- Healthcare Institutions
- HIS Vendors
- Immunization Registries
- Lab Vendors
- Local and State Departments of Health
- Medical Imaging Service Providers
- Payors
- Pharmaceutical Vendors
- Quality Reporting Agencies
- Regulatory Agency
- Standards Development Organizations (SDOs)
FAMILY
- V3
CURRENT STATE
- Stable
REALM
- Universal