DO NOT SHARE PII, PHI, or API TOKENS when posting to the Google Group

140 views
Skip to first unread message

Developer Group for QPP APIs

unread,
Nov 21, 2018, 11:05:45 AM11/21/18
to Developer Group for QPP APIs
Please do not 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 CMS.

To troubleshoot issues in this forum, we do not need TINs, NPIs, or JWTs (API tokens). Should any of that information be necessary, we will direct you to the QPP Help Desk.

In certain circumstances, CMS 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:
  • TIN (Taxpayer Identification Number)
  • NPI
  • API keys for any environment you have access to
  • Social security numbers
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 words 'REDACTED'. For example:

{
  "entityType": "individual",
  "taxpayerIdentificationNumber": "REDACTED",
  "nationalProviderIdentifier": "REDACTED",
  "performanceYear": 2017,
  "measurementSets": [
    {
      "measurements": [
        ....
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages