You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases when addresses, locations (and contact details?) should not be disclosed to protect a service or service users.
Whilst this information may exist within a source providers database, they would not want to publish it as part of open data.
Including a field to indicate where data should be, or has been, redacted, could be useful to:
(a) Indicate to data users the reason for any missing data;
(b) Support validation before data publication, but ensuring that all records with a 'confidential/redacted' flag have had the information removed;
(c) Enable use of HSDS to exchange data between trusted organisations (i.e. not via open publication) without losing important information about security controls that should be applied before data is released;
(d) Support those using HSDS as a model for designing schema to consider the importance of recording when information should be protected.
The text was updated successfully, but these errors were encountered:
From the API thread at openreferral/api-specification#21
There are cases when addresses, locations (and contact details?) should not be disclosed to protect a service or service users.
Whilst this information may exist within a source providers database, they would not want to publish it as part of open data.
Including a field to indicate where data should be, or has been, redacted, could be useful to:
(a) Indicate to data users the reason for any missing data;
(b) Support validation before data publication, but ensuring that all records with a 'confidential/redacted' flag have had the information removed;
(c) Enable use of HSDS to exchange data between trusted organisations (i.e. not via open publication) without losing important information about security controls that should be applied before data is released;
(d) Support those using HSDS as a model for designing schema to consider the importance of recording when information should be protected.
The text was updated successfully, but these errors were encountered: