FRIENDLY/IMPORTANT REMINDER: Do not post PII/PHI in this group

30 views
Skip to first unread message

VA Lighthouse API Support for Developers

unread,
Nov 14, 2019, 1:46:40 PM11/14/19
to VA Lighthouse API Support for Developers

FRIENDLY/IMPORTANT REMINDER: Do not post PII/PHI in this group


Please be very careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when posting to this Google Group or in emails sent to VA Lighthouse.


In certain circumstances, VA Lighthouse may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. It is your responsibility to remove all PII and PHI from any file that you share with us on this website or via email.


Examples of PII, PHI and other sensitive information include:

  • VA API OAuth Client ID
  • VA API OAuth Client Secret
  • VA API key
  • GUIDs/UUIDs
  • Name, Address, Phone Number
  • Social Security Number (SSN)
  • Medical Record Number

Common places where you might include this information include:

  • API request or response payloads, in the text of your post
  • API request or response payloads, in files attached to your post (e.g. .xml, .json)
  • API request or response payloads, in screenshots attached to your post **If you are sharing API request or response payloads, please redact PII and other sensitive information by replacing the information with the word 'REDACTED'. For example:
--REDACTED
Content-Disposition: form-data; name="metadata"
Content-Type: application/json

{"veteranFirstName": "REDACTED",
"veteranLastName": "REDACTED",
"fileNumber": "REDACTED",
"zipCode": "REDACTED",
"source": "MyVSO",
"docType": "21-22"}
--REDACTED
Content-Disposition: form-data; name="content"
Content-Type: application/pdf

<Binary PDF contents>
--REDACTED
Content-Disposition: form-data; name="attachment1"
Content-Type: application/pdf
<Binary PDF attachment contents>
--REDACTED--

When in doubt, leave it out.


-The VA Lighthouse Team

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages