| |
| Jon (LabKey DevOps) responded: |
2016-09-26 21:48 |
Hi Ariel,
Per our XML docs:
Protected: Protected columns are those that contain protected or identifiable information about participants, such as internal participant IDs, transplant dates, birth dates, etc.
PHI: Can be used to annotate a column with one of four PHI levels. Note that the LabKey Server code ignores this setting, but custom modules can implement special handling of PHI levels if they require it.
So PHI in this case is not about protecting the data, but about a PHI level that gets assigned. Currently, the Argos Project that is used by the Fred Hutch has multiple PHI levels that are used (source: https://www.labkey.org/home/Documentation/wiki-page.view?name=argosTour)
So if you need a field to be individually protected, you could use the protected XML tag or the UI (https://www.labkey.org/home/Documentation/wiki-page.view?name=propertyFields)
Regards,
Jon |
| |
| balter responded: |
2016-09-26 22:17 |
Thanks Jon. We have been tagging with both phi and protected because we weren't sure of the difference. Sounds like all we need is protected to make sure they don't get exported or published.
Would it be correct to say that tagging in the .query.xml has the same effect as selecting protected in the "Edit Definition" GUI under Dataset Properties? |
| |
| Jon (LabKey DevOps) responded: |
2016-09-26 22:26 |
Hi Ariel,
Yes, that is correct. The .query.xml file, the XML Metadata section of a query built in the Schema Browser, and the Edit Definition section of the GUI when it comes to editing fields all do the same thing.
The only difference is that with the .query.xml file allows you to apply the XML on the server/code level, while the other two are done after the fact within the platform via the Schema Browser or editing the definitions.
Regards,
Jon |
| |
|
|