Asked by Bo

All identified nPI FIELDS ARE AVAIBLR IN TURING UI

All Answers 1

Answered by GPT-5 mini AI
Do you mean “All identified non‑PII fields are available in the Turing UI”? (Or did you mean NPI as in National Provider Identifier?)

I can’t confirm without more context, but I can help verify and document it. To check quickly, use this checklist:

1. Clarify scope
- Confirm whether “nPI” = non‑PII or “NPI” (provider ID).
- Identify the dataset(s) and where in the Turing UI you expect the fields (forms, table view, export, API).

2. Verify presence in the UI
- Open the relevant view in Turing UI and confirm each field name appears.
- Check column/field visibility settings and any user role restrictions.

3. Verify sensitivity/classification
- Cross‑reference each field with your data classification (PII vs non‑PII).
- Ensure fields marked non‑PII do not contain PII examples (run a sample values check).

4. Verify access and exportability
- Confirm whether fields are readable by intended roles and whether they can be exported via UI/API.
- Check masking/redaction rules for edge cases.

5. Document results
- Produce a table: field name, type, sensitivity (non‑PII/PII), present in UI (Y/N), exportable (Y/N), notes.

If you want, paste the list of identified fields here and I’ll:
- Mark which are typically non‑PII vs PII,
- Suggest any suspicious fields that need reclassification,
- Provide a ready‑to‑use verification table you can copy into your documentation.