hl7-be / data-access

Data Access Guidance

This Implementation Guide identifies the common technical aspects that are used for data access control, subordinate to the legal framework and functional rules.

Publication

This Implementation Guide is published in the following locations:

Continuous Build: http://hl7-be.github.io/data-access/branches/roles-and-rules/index.html
Canonical / permanent URL:

Issues

Issues and change requests are managed here:

Issues: https://github.com/hl7-be/data-access/issues
Kanban board: https://github.com/hl7-be/data-access/projects/1

---

data-access's Issues

Create IG

Add Access Matrix as reference

Create initial valueset for Security labels

Proposal:

• Security labels represent the most atomic set of data that is subject to access control rules
• Security labels will be used in rules (e.g. with Permission)
• Permission may also use other elements later, if needed

How will the security labels be handled when there's a change to the policy and rules

While the security labels do not contain the rules exactly to allow some decoupling, in the future the security labels may themselves be redefined or reclassified - for example splitting etc.
What would need to happen at the implementation side to support this? What are the requirements, and what is the impact of this on the decision to use a specific set of labels?