@@ -1407,8 +1410,8 @@ Removals are handled through a custom remove operation on the /Group endpoint. T
}
~~~
-### Overwrite a Group Membership
-Users can also submit a Group resource which completely overwrites the existing Group. This results in the current group membership being completely overwritten with the members listed in the given resource.
+### Overwrite a group membership
+Users can also submit a Group Resource which completely overwrites the existing group. This results in the current group membership being completely overwritten with the members listed in the given resource.
-
+
An access token as well as Accept and Prefer headers are required for the Group/{id}all/$export.
-The Prefer header is NOT required for /Patient/{id}/$everything, but it DOES require an X-Provenance header whereas the /Group/{id}/$export endpoint does not. The format is defined by the FHIR Bulk Data Export spec. Consult the [FHIR Datatypes](https://www.hl7.org/fhir/datatypes.html#instant) page for more information.
+The Prefer header is NOT required for /Patient/{id}/$everything, but it DOES require an X-Provenance header whereas the /Group/{id}/$export endpoint does not. The format is defined by the FHIR Bulk Data Export spec. Consult the FHIR Datatypes page for more information.
## Requesting data using _since with the /Group endpoint
-### Request to Start a job using the _since parameter within the /Group endpoint
+### Request to start a job using the _since parameter within the /Group endpoint
If the request was successful, a 202 Accepted response code will be returned and the response will include a Content-Location header. @@ -1701,28 +1699,28 @@ If the request was successful, a 202 Accepted response code will be returned and ## Requesting data using _since with the /Patient endpoint -### Request data synchronously for an individual Patient using the _since parameter within the /Patient/{id}/$everything endpoint +### Request data synchronously for an individual patient using the _since parameter within the /Patient/{id}/$everything endpoint
If the request was successful, a 200 Success response code will be returned and the response will not include a Content-Location header. Instead, it contains the data in the body of the response. @@ -1778,12 +1776,12 @@ Claims data can be found at the URLs within the output field. The output includes file integrity information in an extension array. It contains https://dpc.cms.gov/checksum (a checksum in the format algorithm:checksum) and https://dpc.cms.gov/file_length (the file length in bytes). -The number 42 in the example data file URLs is the same job ID from the Content-Location header URL when you initiate an export job. If some of the data cannot be exported due to errors, details of the errors can be found at the URLs in the error field. The errors are provided in [NDJSON](http://ndjson.org/) files as FHIR [OperationOutcome](http://hl7.org/fhir/STU3/operationoutcome.html) resources. +The number 42 in the example data file URLs is the same job ID from the Content-Location header URL when you initiate an export job. If some of the data cannot be exported due to errors, details of the errors can be found at the URLs in the error field. The errors are provided in NDJSON files as FHIR OperationOutcome resources. ## Retrieve the NDJSON output file(s) -To obtain the exported explanation of benefit data, a GET request is made to the output URLs in the job status response when the job reaches the Completed state. The data will be presented as an [NDJSON](http://ndjson.org/) file of ExplanationOfBenefit resources. +To obtain the exported explanation of benefit data, a GET request is made to the output URLs in the job status response when the job reaches the Completed state. The data will be presented as an NDJSON file of ExplanationOfBenefit Resources.
-
@@ -1472,15 +1475,15 @@ Users can also submit a Group resource which completely overwrites the existing
### Locate your Group.id
You may only pull data for one practitioner’s roster at a time.
-You can do this by sending a GET request to the Group endpoint to retrieve the [Attribution Group](https://hl7.org/fhir/STU3/group.html) of the Practitioner. Use the Practitioners’ [National Provider Identity (NPI)](https://www.cms.gov/Regulations-and-Guidance/Administrative-Simplification/NationalProvIdentStand/) number as a parameter in this request.
+You can do this by sending a GET request to the Group endpoint to retrieve the Attribution Group of the practitioner. Use the practitioners’ National Provider Identity (NPI) number as a parameter in this request.
-The response will return a [Bundle](https://www.hl7.org/fhir/STU3/bundle.html) resource which contains the attribution groups for the given Practitioner. **You can use the Group.id value of the returned resources to initiate an export job.** Your Group ID can be found by referencing the {id} variable in the resource object of your Group.
+The response will return a Bundle Resource which contains the Attribution Groups for the given practitioner. **You can use the Group.id value of the returned resources to initiate an export job.** Your Group ID can be found by referencing the {id} variable in the resource object of your group.
**Example:**
@@ -1553,15 +1556,10 @@ The response will return a [Bundle](https://www.hl7.org/fhir/STU3/bundle.html) r
# Export Data
------------
-The primary interaction with the DPC pilot API is via the FHIR /Group/$export operation.This allows an organization to export Patient. Coverage, and Explanation of Benefit data in an asynchronous and bulk manner. Details on the FHIR bulk data operations can be found in the [FHIR Bulk Data Specification](https://build.fhir.org/ig/HL7/bulk-data/OperationDefinition-group-export.html).
-
-**Prerequisites:**
-- Completion of the Authorization section
-- Access to the API: active Bearer {access_token}
-- Completion of the Attestation & Attribution section
+The primary interaction with the DPC pilot API is via the FHIR /Group/$export operation. This allows an organization to export Patient, Coverage, and Explanation of Benefit data in an asynchronous and bulk manner. Details on the FHIR bulk data operations can be found in the FHIR Bulk Data Specification.
## Initiate an export job
-In order to start a Patient data export job, you will need to locate your Group.id. Locate your Group.id by referencing the {id} variable in the resource object of your Group.
+In order to start a patient data export job, you will need to locate your Group.id. Locate your Group.id by referencing the {id} variable in the resource object of your group.
**Example:**
@@ -1574,7 +1572,7 @@ In order to start a Patient data export job, you will need to locate your Group.
Next, make a GET request to the /Group/$export endpoint with three required headers: an access token, an Accept header, and a Prefer header.
-The dollar sign (‘$’) before the word “export” in the URL indicates that the endpoint is an action rather than a resource. The format is defined by the [FHIR Bulk Data Specification](https://build.fhir.org/ig/HL7/bulk-data/OperationDefinition-group-export.html).
+The dollar sign (‘$’) before the word “export” in the URL indicates that the endpoint is an action rather than a resource. The format is defined by the FHIR Bulk Data Specification.
### Request:
@@ -1588,20 +1586,20 @@ The dollar sign (‘$’) before the word “export” in the URL indicates that
-H 'Prefer: respond-async'
### Response:
-If the request was successful, a 202 Accepted response code will be returned with a Content-Location header. The value of this header indicates the location to monitor your job status and outcomes. The value of the header also contains the Export Job ID of the Job. There is no BODY to the Response, only headers.
+If the request was successful, a 202 Accepted response code will be returned with a Content-Location header. The value of this header indicates the location to monitor your job status and outcomes. The value of the header also contains the Export Job ID of the Job. There is no BODY to the response, only headers.
**Example:**
Content-Location: https://sandbox.dpc.cms.gov/api/v1/Jobs/{unique ID of export job}GET /api/v1/Group/{attribution group ID}/$export?_type=Patient,CoverageGET /api/v1/Group/{attribution group ID}/$export?_type=ExplanationOfBenefitBe wary of requesting data from before 02-12-2020
- Due to limitations in the Beneficiary FHIR Data (BFD) Server, data from before 02-12-2020 is marked with the arbitrary lastUpdated date of 01-01-2020. If you input dates between 01-01-2020 and 02-11-2020 in the _since parameter, you will receive all historical data for your beneficiaries. Data loads from 02-12-2020 onwards have been marked with accurate dates. + Due to limitations in the Beneficiary FHIR Data (BFD) Server, data from before 02-12-2020 is marked with the arbitrary lastUpdated date of 01-01-2020. If you input dates between 01-01-2020 and 02-11-2020 in the _since parameter, you will receive all historical data for your beneficiaries. Data loads from 02-12-2020 onwards have been marked with accurate dates.
GET /api/v1/Group/{id}/$export?_type=Patient&_since=2020-02-13T08:00:00.000-05:00
Authorization: Bearer {access_token}
Accept: application/fhir+json
Prefer: respond-async
curl -X GET 'https://sandbox.dpc.cms.gov/api/v1/Group/{id}/$export?_since=2021-05-13T08:00:00.000-05:00' \
-H "Accept: application/fhir+json" \
-H "Prefer: respond-async" \
-H "Authorization: Bearer {access token}
202 AcceptedIf the request was successful, a 202 Accepted response code will be returned and the response will include a Content-Location header. @@ -1701,28 +1699,28 @@ If the request was successful, a 202 Accepted response code will be returned and ## Requesting data using _since with the /Patient endpoint -### Request data synchronously for an individual Patient using the _since parameter within the /Patient/{id}/$everything endpoint +### Request data synchronously for an individual patient using the _since parameter within the /Patient/{id}/$everything endpoint
GET /api/v1/Patient/{id}/$everything?_since=2020-02-13T08:00:00.000-05:00
Authorization: Bearer {access_token}
Accept: application/fhir+json
X-Provenance: {provenance header}
curl -X GET 'https://sandbox.dpc.cms.gov/api/v1/Patient/{id}/$everything?_since=2021-05-13T08:00:00.000-05:00' \
-H "Accept: application/fhir+json" \
-H "X-Provenance: {provenance header}" \
-H "Authorization: Bearer {access token}"
200 SuccessIf the request was successful, a 200 Success response code will be returned and the response will not include a Content-Location header. Instead, it contains the data in the body of the response. @@ -1778,12 +1776,12 @@ Claims data can be found at the URLs within the output field. The output includes file integrity information in an extension array. It contains https://dpc.cms.gov/checksum (a checksum in the format algorithm:checksum) and https://dpc.cms.gov/file_length (the file length in bytes). -The number 42 in the example data file URLs is the same job ID from the Content-Location header URL when you initiate an export job. If some of the data cannot be exported due to errors, details of the errors can be found at the URLs in the error field. The errors are provided in [NDJSON](http://ndjson.org/) files as FHIR [OperationOutcome](http://hl7.org/fhir/STU3/operationoutcome.html) resources. +The number 42 in the example data file URLs is the same job ID from the Content-Location header URL when you initiate an export job. If some of the data cannot be exported due to errors, details of the errors can be found at the URLs in the error field. The errors are provided in NDJSON files as FHIR OperationOutcome resources. ## Retrieve the NDJSON output file(s) -To obtain the exported explanation of benefit data, a GET request is made to the output URLs in the job status response when the job reaches the Completed state. The data will be presented as an [NDJSON](http://ndjson.org/) file of ExplanationOfBenefit resources. +To obtain the exported explanation of benefit data, a GET request is made to the output URLs in the job status response when the job reaches the Completed state. The data will be presented as an NDJSON file of ExplanationOfBenefit Resources.
@@ -2064,32 +2062,23 @@ To obtain the exported explanation of benefit data, a GET request is made to the
# Postman Collection
-This collection contains example requests to public endpoints for the DPC API. To use this collection, you must have the Postman App downloaded onto your computer. Next, please obtain the prerequisites listed below and refer to the DPC User Guide for additional instructions. You will need these to successfully update the required values in your local Postman sandbox environment to make requests.
-
-**Prerequisites:**
-- Download the [Postman App](https://www.postman.com/downloads/)
-- A registered client token
-- Your private key
-- Your public key ID
-
-1. Please download the DPC Postman collection. This will include the collection of requests, the sandbox environment, and global variables to be imported into your Postman App.
+This collection contains example requests to public endpoints for the DPC API. To use this collection, you must have the Postman App downloaded onto your computer. This will include the collection of requests, the sandbox environment, and global variables to be imported into your Postman App.
-2. Select the environment (top right): Data at the Point of Care Sandbox
-3. Please fill in the following values:
- - client_token: Your [client token](#step-two-client-tokens) is generated through the DPC portal. Be sure to save a copy of your token in a safe place.
- - PRIVATE_KEY: Paste the contents of your private key in the `PRIVATE_KEY` field of your local Postman sandbox environment. Do not share your private key otherwise. If you do not already have your public and private keys, please generate your [public/private](#step-three-public-keys) key pair through the DPC portal.
- - key-id: This is the system id of your public key, which is returned to you when the public key is uploaded to the DPC portal. You need this to generate a JWT, which will be exchanged for an access token.
-
-With these 3 values in place, the JWT and a fresh access token are automatically generated for you before each request in this Postman collection to prevent you from having to manually refresh the access token every 5 minutes while using the collection. You may occasionally receive a 401 error message regarding invalid credentials. If this happens, please try your request a second time.
+1. Select the environment (top right): Data at the Point of Care Sandbox
+2. Please fill in the following values:
+ - client_token: Your [client token](#step-two-client-tokens) is generated through the DPC Portal. Be sure to save a copy of your token in a safe place.
+ - PRIVATE_KEY: Paste the contents of your private key in the `PRIVATE_KEY` field of your local Postman sandbox environment. Do not share your private key otherwise. If you do not already have your public and private keys, please generate your [public/private](#step-three-public-keys) key pair through the DPC Portal.
+ - key-id: This is the DPC ID of your public key, which is returned to you when the public key is uploaded to the DPC Portal. You need this to generate a JWT, which will be exchanged for an access token.
+3. With these three values in place, the JWT and a fresh access token are automatically generated for you before each request in this Postman collection to prevent you from having to manually refresh the access token every five minutes while using the collection. You may occasionally receive a 401 error message regarding invalid credentials. If this happens, please try your request a second time.
Additional instructions and details can be found within the description of each request in the Postman collection. These can be viewed by clicking the drop-down arrow next to each request title.
## Patient/$everything
-Patient/{id}/$everything is an endpoint that allows users to retrieve all resources about a Patient using their DPC internal ID (UUID), represented as {id} in the request. Included in the resources will be the Patient, Coverage, and ExplanationOfBenefit resources for one patient’s historical data from the last seven years, combined into a Bundle. It is a synchronous download, so it differs from the Group $export operation in that it does not create a job that needs to be monitored or data files to download. The response body will contain the Bundle.
+Patient/{id}/$everything is an endpoint that allows users to retrieve all resources about a patient using their DPC internal ID (UUID), represented as {id} in the request. Included in the resources will be the Patient, Coverage, and ExplanationOfBenefit Resources for one patient’s historical data from the last seven years, combined into a bundle. It is a synchronous download, so it differs from the Group $export operation in that it does not create a job that needs to be monitored or data files to download. The response body will contain the bundle.
If you only have the Medicare Beneficiary Identifier (MBI) of the patient, you can retrieve the DPC internal ID by first making a GET request for that specific patient as the UUID is returned in that response. See [List a Specific Patient](#list-a-specific-patient) for details.
@@ -2099,15 +2088,15 @@ This request requires an X-Provenance header for attestation ([see example](#exa
Learn more about the HL7 FHIR Specification for:
-[Operation Patient Everything (Release v4)](http://hl7.org/fhir/R4/operation-patient-everything.html)
+Operation Patient Everything (Release v4)
-[Operation Patient Everything (Release v3)](http://hl7.org/fhir/STU3/operation-patient-everything.html)
+Operation Operation Patient Everything (Release v3)
**Request**
diff --git a/common/pilot.html b/common/pilot.html
index 57bafbdd..ab5d3363 100644
--- a/common/pilot.html
+++ b/common/pilot.html
@@ -2,7 +2,7 @@
layout: page-sidenav
title: About the Pilot
banner_title: About the Pilot
-permalink: /pilot
+permalink: /pilot.html
id: pilot
button: Email DPC to Request Production Access
button_url: mailto:DPCINFO@cms.hhs.gov
@@ -12,11 +12,11 @@
GET /api/v1/Patient/{id}/$everythingcurl -v https://sandbox.dpc.cms.gov/api/v1/Patient/{id}/$everything
-H 'Authorization: Bearer {access_token}' \
diff --git a/common/docsV2.md b/common/docsV2.md
index ccd95fd0..e0aa3431 100644
--- a/common/docsV2.md
+++ b/common/docsV2.md
@@ -2,7 +2,7 @@
layout: page-sidenav
title: DPC Documentation
banner_title: Documentation
-permalink: /docsV2
+permalink: /docsV2.html
id: docsV2
button: Sign Up for Sandbox
button_url: https://sandbox.dpc.cms.gov/users/sign_in
diff --git a/common/faq.html b/common/faq.html
index 7c860815..571d185b 100644
--- a/common/faq.html
+++ b/common/faq.html
@@ -3,7 +3,7 @@
title: Frequently asked questions
banner_title: Frequently asked questions
description: Frequently asked questions about the Data at the Point of Care pilot
-permalink: /faq
+permalink: /faq.html
id: faq
button: DPC Google Group
button_url: "https://groups.google.com/d/forum/dpc-api"
@@ -257,4 +257,18 @@
Good news: our sandbox environment matches the production environment, and we'll roll out new functionality in sandbox before sending it into production. Even if you are not able to participate in the production pilot at this juncture, please continue to test in the sandbox environment with synthetic data. Your feedback through the Google Group is invaluable to our researchers and engineers as we all work together to shape the future of DPC.
+
+
+
+
+
+ Yes, you can inherit AWS’ HITRUST certification if your DPC solution meets the following requirements:
+
+ - The DPC solution is contained entirely within AWS Services that have received a HITRUST certification. See AWS' list of HITRUST-certified services under HITRUST CSF.
+ - The DPC solution applies the controls listed on the HITRUST website. You should download the AWS Custom HITRUST Shared Responsibility Matrix to determine which HITRUST controls AWS customers can inherit as part of the Shared Responsibility Model.
+ - You submit a valid and accepted External Inheritance request through the HITRUST website. Follow the instructions in the User Guide to do so.
+
+
About the DPC Pilot
- The Centers for Medicare and Medicaid Services (CMS) Data at the Point of Care (DPC) API is currently in a pilot phase in which a limited number of users can access Medicare Fee-For-Service claims data through the API once their solution has been approved for production. This pilot program promotes the industry-standard HL7 Fast Healthcare Interoperability Resources (FHIR), specifically the Bulk FHIR specification.
+ The Centers for Medicare & Medicaid Services (CMS) Data at the Point of Care (DPC) API is currently in a pilot phase in which a limited number of customers can access Medicare Fee-For-Service claims data through the API once their solution has been approved for production. This pilot program promotes the industry-standard HL7 Fast Healthcare Interoperability Resources (FHIR), specifically the Bulk FHIR specification.
- Since the pilot is a learning experience for both CMS and users, participants in the pilot program may encounter breaking changes to code, iterations to regulations, and will be asked to participate in research sessions with CMS as the program continues to grow and evolve.
+ Since the pilot is a learning experience for both CMS and customers, participants in the pilot program may encounter breaking changes to code, iterations to regulations, and will be asked to participate in research sessions with CMS as the program continues to grow and evolve.
@@ -29,60 +29,56 @@
-About the DPC Pilot
If interested in implementing DPC on behalf of healthcare organizations, please begin by following the steps below.1. Test the API
- -
- Health IT implementers are asked to test and develop a solution in the sandbox environment using synthetic data before applying for production credentials.
-
-
-
+Test the API
- - Review and agree to the Terms of Service. + Request access to the DPC Sandbox Environment through Sandbox Sign Up / Login.
- - Upload synthetic data from DPC’s public GitHub repository. More details included in this README file. + Upload synthetic data from DPC’s public GitHub repository. More details included in this README file.
-
- Reference the following guides to get started:
-
-
-
- - DPC Documentation - -
- - HL7 FHIR Standards - -
- - BB2.0 Implementation Guide - -
+
-
+
- + DPC Documentation + +
- + HL7 FHIR Standards + +
- + BB2.0 Implementation Guide
2. Apply for Production Credentials
+Apply for Production Credentials
-After testing and developing a DPC solution in the sandbox environment: +After developing and testing a DPC solution in the sandbox environment, complete the steps below. -a. Join the Production Pilot Queue
+1. Request to Join the Production Pilot Queue
-When you're ready to request production access, please email the DPC team. You will receive a follow-up email from the DPC team when it is your turn to onboard. Depending on the backlog of organizations, this may mean that your organization will sit in the queue for a few weeks before it is your turn to onboard. +When you're ready to request production access, please email the DPC Team. You will receive a follow-up email from the DPC Team when it is your turn to onboard. -
+
-
@@ -94,7 +90,15 @@
-
+
+ Warning:
+
- Please do not plan to fill out the application unless your organization has tested your solution in sandbox and is able to share security documentation with CMS. + Please do not fill out the application unless your organization has tested your solution in sandbox and is able to share security documentation with CMS.
b. Schedule a Demonstration with the DPC team
+2. Schedule a Demonstration with the DPC Team
-In the email following up on your application to the pilot program, you will receive a link to schedule a demonstration of your DPC solution with the DPC team. +After you request production access, you will receive an email about scheduling a demonstration of your DPC solution with the DPC Team.
@@ -94,7 +90,15 @@
Please be prepared to answer the following questions:
-
- Walk us through the end-to-end workflow. How will practitioners see the data in your system?
+ Walk us through the end-to-end workflow.
+
+ -
+ How do you attribute patients to practitioners?
+
+ -
+ How will practitioners see the data in your system?
+
+
-
How frequently will your organization make requests to the API? How quickly will you need the data returned?
@@ -103,19 +107,19 @@
What is your retry logic for requests that fail?
-
- What will you do if you do not receive data back for some of the requested patients?
+ What will you do if you do not receive data back for some of the requested patients? For example, data for patients outside of the 18-month lookback period for a given provider will not be returned during early phases of the pilot.
-
- How will the data be used? For example, are you using the data for aggregate population reporting, or for insights into the needs of an individual patient? or both?
+ How will the data be used? For example, are you using the data for aggregate population reporting, or for insights into the needs of an individual patient? Or both?
-
Where does the application live?
-
- Would there be a separate instance if you bring on another practice during pilot or MVP?
+ Would there be a separate instance if you bring on another practice during the pilot?
-
- During onboarding in the early phases of the pilot program, we'll be providing keys directly to the practitioner organization to grant access to production via secure email - we will not be using the same web portal as our sandbox environment. Please consider how to best communicate with the practitioner to securely transfer secrets if necessary.
+ During onboarding, we'll be providing keys directly to the practitioner organization to grant access to production via secure email - we will not be using the same web portal as our sandbox environment. Please consider how to best communicate with the practitioner to securely transfer secrets if necessary.
-
Are you ready for breaking changes during the pilot program?
@@ -133,10 +137,10 @@
-
- Walk us through the end-to-end workflow. How will practitioners see the data in your system?
+ Walk us through the end-to-end workflow.
+
-
+
- + How do you attribute patients to practitioners? + +
- + How will practitioners see the data in your system? + +
-
How frequently will your organization make requests to the API? How quickly will you need the data returned?
@@ -103,19 +107,19 @@
What is your retry logic for requests that fail?
- - What will you do if you do not receive data back for some of the requested patients? + What will you do if you do not receive data back for some of the requested patients? For example, data for patients outside of the 18-month lookback period for a given provider will not be returned during early phases of the pilot.
- - How will the data be used? For example, are you using the data for aggregate population reporting, or for insights into the needs of an individual patient? or both? + How will the data be used? For example, are you using the data for aggregate population reporting, or for insights into the needs of an individual patient? Or both?
- Where does the application live?
- - Would there be a separate instance if you bring on another practice during pilot or MVP? + Would there be a separate instance if you bring on another practice during the pilot?
- - During onboarding in the early phases of the pilot program, we'll be providing keys directly to the practitioner organization to grant access to production via secure email - we will not be using the same web portal as our sandbox environment. Please consider how to best communicate with the practitioner to securely transfer secrets if necessary. + During onboarding, we'll be providing keys directly to the practitioner organization to grant access to production via secure email - we will not be using the same web portal as our sandbox environment. Please consider how to best communicate with the practitioner to securely transfer secrets if necessary.
-
Are you ready for breaking changes during the pilot program?
@@ -133,10 +137,10 @@
c. Provide Security Certification
+3. Provide Security Certification
- Health IT implementers preparing to onboard the production environment must provide one of the accepted security certifications below:
+ Prior to onboarding to the production environment, you must provide one of the accepted security certifications below:
@@ -226,7 +230,7 @@
3. Onboard with DPC
+Onboard with DPC
The onboarding session will test your DPC solution with production Medicare Fee-For-Service claims data.
@@ -235,34 +239,34 @@
-
diff --git a/common/tos.md b/common/tos.md
index 737c2451..28af9dcf 100644
--- a/common/tos.md
+++ b/common/tos.md
@@ -1,7 +1,7 @@
---
layout: page-tos
title: Terms of service
-permalink: /terms-of-service
+permalink: /terms-of-service.html
id: tos
---
*Last updated: 8/19/21*
diff --git a/common/update-page.md b/common/update-page.md
index 0e9df4c2..57d92686 100644
--- a/common/update-page.md
+++ b/common/update-page.md
@@ -2,7 +2,7 @@
layout: page-info
title: Updates
banner_title: Updates
-permalink: /updates
+permalink: /updates.html
id: updates
button: DPC Google Group
button_url: "https://groups.google.com/d/forum/dpc-api"
diff --git a/ops/release.sh b/ops/release.sh
index 67054516..5aa58de1 100644
--- a/ops/release.sh
+++ b/ops/release.sh
@@ -105,8 +105,6 @@ echo "" >> $TMPFILE
echo "$commits" >> $TMPFILE
echo "" >> $TMPFILE
-git tag -a -m"$PROJECT_NAME release $NEWTAG" -s "$NEWTAG"
-
RELEASE_PATH="/repos$GITHUB_REPO_PATH/releases"
python github_release.py --release $NEWTAG --release-file $TMPFILE --repo $RELEASE_PATH
diff --git a/package-lock.json b/package-lock.json
index 1ce936a7..7b6c5b3e 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,8 +1,254 @@
{
"name": "dpc-static-site",
"version": "1.0.0",
- "lockfileVersion": 1,
+ "lockfileVersion": 2,
"requires": true,
+ "packages": {
+ "": {
+ "name": "dpc-static-site",
+ "version": "1.0.0",
+ "license": "ISC",
+ "dependencies": {
+ "@cmsgov/design-system-core": "^3.7.0",
+ "@cmsgov/design-system-layout": "^3.7.0",
+ "normalize.css": "^8.0.1",
+ "svg4everybody": "^2.1.9"
+ },
+ "devDependencies": {}
+ },
+ "node_modules/@babel/runtime": {
+ "version": "7.9.2",
+ "resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.9.2.tgz",
+ "integrity": "sha512-NE2DtOdufG7R5vnfQUTehdTfNycfUANEtCa9PssN9O/xmTzP4E08UI797ixaei6hBEVL9BI/PsdJS5x7mWoB9Q==",
+ "dependencies": {
+ "regenerator-runtime": "^0.13.4"
+ }
+ },
+ "node_modules/@cmsgov/design-system-core": {
+ "version": "3.7.0",
+ "resolved": "https://registry.npmjs.org/@cmsgov/design-system-core/-/design-system-core-3.7.0.tgz",
+ "integrity": "sha512-0zenYytLfS0SKndAAiBY1h/nyx8XIShXqnhC1JEJCAIyDRfTF/M5FFOFdY5tY1jO09LukqWic/c0G7Tmib7LfQ==",
+ "deprecated": "This package has been deprecated in favor of @cmsgov/design-system. See the CMSDS docs (https://design.cms.gov/startup/migrating-v2) for more information.",
+ "dependencies": {
+ "@cmsgov/design-system-support": "^3.7.0",
+ "classnames": "^2.2.5",
+ "core-js": "^2.5.3",
+ "downshift": "^3.2.10",
+ "ev-emitter": "^1.1.1",
+ "lodash.uniqueid": "^4.0.1",
+ "react-aria-modal": "^2.11.1"
+ },
+ "peerDependencies": {
+ "prop-types": "^15.0.0 || ^16.0.0",
+ "react": "^15.0.0 || ^16.0.0",
+ "react-dom": "^15.0.0 || ^16.0.0"
+ }
+ },
+ "node_modules/@cmsgov/design-system-layout": {
+ "version": "3.7.0",
+ "resolved": "https://registry.npmjs.org/@cmsgov/design-system-layout/-/design-system-layout-3.7.0.tgz",
+ "integrity": "sha512-VYC7arPRvagEEUrNOJ/0nySpspglW/xEj6D9cyUCU+CPcxp2hSznRXfKG1qrhY6g0zOU8Y+fdLED560sb3mjLA==",
+ "deprecated": "This package has been deprecated in favor of @cmsgov/design-system. See the CMSDS docs (https://design.cms.gov/startup/migrating-v2) for more information.",
+ "dependencies": {
+ "@cmsgov/design-system-support": "^3.7.0"
+ }
+ },
+ "node_modules/@cmsgov/design-system-support": {
+ "version": "3.7.0",
+ "resolved": "https://registry.npmjs.org/@cmsgov/design-system-support/-/design-system-support-3.7.0.tgz",
+ "integrity": "sha512-Xymyo7EtHl8PsyQLVxPysh45RgnCLFIzACmU6am0laR8R+SPBHZtlDNqGJ4FziBOwoMW9m5J1jtAlN8RGkZS8Q==",
+ "deprecated": "This package has been deprecated in favor of @cmsgov/design-system. See the CMSDS docs (https://design.cms.gov/startup/migrating-v2) for more information."
+ },
+ "node_modules/classnames": {
+ "version": "2.2.6",
+ "resolved": "https://registry.npmjs.org/classnames/-/classnames-2.2.6.tgz",
+ "integrity": "sha512-JR/iSQOSt+LQIWwrwEzJ9uk0xfN3mTVYMwt1Ir5mUcSN6pU+V4zQFFaJsclJbPuAUQH+yfWef6tm7l1quW3C8Q=="
+ },
+ "node_modules/compute-scroll-into-view": {
+ "version": "1.0.13",
+ "resolved": "https://registry.npmjs.org/compute-scroll-into-view/-/compute-scroll-into-view-1.0.13.tgz",
+ "integrity": "sha512-o+w9w7A98aAFi/GjK8cxSV+CdASuPa2rR5UWs3+yHkJzWqaKoBEufFNWYaXInCSmUfDCVhesG+v9MTWqOjsxFg=="
+ },
+ "node_modules/core-js": {
+ "version": "2.6.11",
+ "resolved": "https://registry.npmjs.org/core-js/-/core-js-2.6.11.tgz",
+ "integrity": "sha512-5wjnpaT/3dV+XB4borEsnAYQchn00XSgTAWKDkEqv+K8KevjbzmofK6hfJ9TZIlpj2N0xQpazy7PiRQiWHqzWg==",
+ "deprecated": "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.",
+ "hasInstallScript": true
+ },
+ "node_modules/downshift": {
+ "version": "3.4.8",
+ "resolved": "https://registry.npmjs.org/downshift/-/downshift-3.4.8.tgz",
+ "integrity": "sha512-dZL3iNL/LbpHNzUQAaVq/eTD1ocnGKKjbAl/848Q0KEp6t81LJbS37w3f93oD6gqqAnjdgM7Use36qZSipHXBw==",
+ "dependencies": {
+ "@babel/runtime": "^7.4.5",
+ "compute-scroll-into-view": "^1.0.9",
+ "prop-types": "^15.7.2",
+ "react-is": "^16.9.0"
+ },
+ "peerDependencies": {
+ "react": ">=0.14.9"
+ }
+ },
+ "node_modules/ev-emitter": {
+ "version": "1.1.1",
+ "resolved": "https://registry.npmjs.org/ev-emitter/-/ev-emitter-1.1.1.tgz",
+ "integrity": "sha512-ipiDYhdQSCZ4hSbX4rMW+XzNKMD1prg/sTvoVmSLkuQ1MVlwjJQQA+sW8tMYR3BLUr9KjodFV4pvzunvRhd33Q=="
+ },
+ "node_modules/focus-trap": {
+ "version": "2.4.6",
+ "resolved": "https://registry.npmjs.org/focus-trap/-/focus-trap-2.4.6.tgz",
+ "integrity": "sha512-vWZTPtBU6pBoyWZDRZJHkXsyP2ZCZBHE3DRVXnSVdQKH/mcDtu9S5Kz8CUDyIqpfZfLEyI9rjKJLnc4Y40BRBg==",
+ "dependencies": {
+ "tabbable": "^1.0.3"
+ }
+ },
+ "node_modules/focus-trap-react": {
+ "version": "3.1.4",
+ "resolved": "https://registry.npmjs.org/focus-trap-react/-/focus-trap-react-3.1.4.tgz",
+ "integrity": "sha512-uqMKMg9Xlny0LKHW0HqA7ncLafW57SxgeedjE7/Xt+NB7sdOBUG4eD/9sMsq1O0+7zD3palpniTs2n0PDLc3uA==",
+ "dependencies": {
+ "focus-trap": "^2.0.1"
+ },
+ "peerDependencies": {
+ "react": "0.14.x || ^15.0.0 || ^16.0.0",
+ "react-dom": "0.14.x || ^15.0.0 || ^16.0.0"
+ }
+ },
+ "node_modules/js-tokens": {
+ "version": "4.0.0",
+ "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
+ "integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ=="
+ },
+ "node_modules/lodash.uniqueid": {
+ "version": "4.0.1",
+ "resolved": "https://registry.npmjs.org/lodash.uniqueid/-/lodash.uniqueid-4.0.1.tgz",
+ "integrity": "sha1-MmjyanyI5PSxdY1nknGBTjH6WyY="
+ },
+ "node_modules/loose-envify": {
+ "version": "1.4.0",
+ "resolved": "https://registry.npmjs.org/loose-envify/-/loose-envify-1.4.0.tgz",
+ "integrity": "sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==",
+ "dependencies": {
+ "js-tokens": "^3.0.0 || ^4.0.0"
+ },
+ "bin": {
+ "loose-envify": "cli.js"
+ }
+ },
+ "node_modules/no-scroll": {
+ "version": "2.1.1",
+ "resolved": "https://registry.npmjs.org/no-scroll/-/no-scroll-2.1.1.tgz",
+ "integrity": "sha512-YTzGAJOo/B6hkodeT5SKKHpOhAzjMfkUCCXjLJwjWk2F4/InIg+HbdH9kmT7bKpleDuqLZDTRy2OdNtAj0IVyQ=="
+ },
+ "node_modules/normalize.css": {
+ "version": "8.0.1",
+ "resolved": "https://registry.npmjs.org/normalize.css/-/normalize.css-8.0.1.tgz",
+ "integrity": "sha512-qizSNPO93t1YUuUhP22btGOo3chcvDFqFaj2TRybP0DMxkHOCTYwp3n34fel4a31ORXy4m1Xq0Gyqpb5m33qIg=="
+ },
+ "node_modules/object-assign": {
+ "version": "4.1.1",
+ "resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
+ "integrity": "sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=",
+ "engines": {
+ "node": ">=0.10.0"
+ }
+ },
+ "node_modules/prop-types": {
+ "version": "15.7.2",
+ "resolved": "https://registry.npmjs.org/prop-types/-/prop-types-15.7.2.tgz",
+ "integrity": "sha512-8QQikdH7//R2vurIJSutZ1smHYTcLpRWEOlHnzcWHmBYrOGUysKwSsrC89BCiFj3CbrfJ/nXFdJepOVrY1GCHQ==",
+ "dependencies": {
+ "loose-envify": "^1.4.0",
+ "object-assign": "^4.1.1",
+ "react-is": "^16.8.1"
+ }
+ },
+ "node_modules/react": {
+ "version": "16.14.0",
+ "resolved": "https://registry.npmjs.org/react/-/react-16.14.0.tgz",
+ "integrity": "sha512-0X2CImDkJGApiAlcf0ODKIneSwBPhqJawOa5wCtKbu7ZECrmS26NvtSILynQ66cgkT/RJ4LidJOc3bUESwmU8g==",
+ "peer": true,
+ "dependencies": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1",
+ "prop-types": "^15.6.2"
+ },
+ "engines": {
+ "node": ">=0.10.0"
+ }
+ },
+ "node_modules/react-aria-modal": {
+ "version": "2.12.3",
+ "resolved": "https://registry.npmjs.org/react-aria-modal/-/react-aria-modal-2.12.3.tgz",
+ "integrity": "sha512-XIsB9mFRJe5c4MJ/CIZPRci6ZTEEWzUSRslM63rxwCFAV0HbC8KkaSlA2CtvwYmMwVd+lAsGDN7yUtOQXOGkQQ==",
+ "dependencies": {
+ "focus-trap-react": "^3.0.4",
+ "no-scroll": "^2.0.0",
+ "react-displace": "^2.3.0"
+ },
+ "peerDependencies": {
+ "react": "0.14.x || ^15.0.0 || ^16.0.0"
+ }
+ },
+ "node_modules/react-displace": {
+ "version": "2.3.0",
+ "resolved": "https://registry.npmjs.org/react-displace/-/react-displace-2.3.0.tgz",
+ "integrity": "sha512-T8g/lyn3IX8kxLO4k4vJ/oIO9G72pRTc9GYslqKsfPcN4gY5+FYR5OHxeTH1skPjVylJrveGE3OC2qCt3BuHeA==",
+ "peerDependencies": {
+ "react": "0.14.x || ^15.0.0 || ^16.0.0",
+ "react-dom": "0.14.x || ^15.0.0 || ^16.0.0"
+ }
+ },
+ "node_modules/react-dom": {
+ "version": "16.14.0",
+ "resolved": "https://registry.npmjs.org/react-dom/-/react-dom-16.14.0.tgz",
+ "integrity": "sha512-1gCeQXDLoIqMgqD3IO2Ah9bnf0w9kzhwN5q4FGnHZ67hBm9yePzB5JJAIQCc8x3pFnNlwFq4RidZggNAAkzWWw==",
+ "peer": true,
+ "dependencies": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1",
+ "prop-types": "^15.6.2",
+ "scheduler": "^0.19.1"
+ },
+ "peerDependencies": {
+ "react": "^16.14.0"
+ }
+ },
+ "node_modules/react-is": {
+ "version": "16.13.1",
+ "resolved": "https://registry.npmjs.org/react-is/-/react-is-16.13.1.tgz",
+ "integrity": "sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ=="
+ },
+ "node_modules/regenerator-runtime": {
+ "version": "0.13.5",
+ "resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.5.tgz",
+ "integrity": "sha512-ZS5w8CpKFinUzOwW3c83oPeVXoNsrLsaCoLtJvAClH135j/R77RuymhiSErhm2lKcwSCIpmvIWSbDkIfAqKQlA=="
+ },
+ "node_modules/scheduler": {
+ "version": "0.19.1",
+ "resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.19.1.tgz",
+ "integrity": "sha512-n/zwRWRYSUj0/3g/otKDRPMh6qv2SYMWNq85IEa8iZyAv8od9zDYpGSnpBEjNgcMNq6Scbu5KfIPxNF72R/2EA==",
+ "peer": true,
+ "dependencies": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1"
+ }
+ },
+ "node_modules/svg4everybody": {
+ "version": "2.1.9",
+ "resolved": "https://registry.npmjs.org/svg4everybody/-/svg4everybody-2.1.9.tgz",
+ "integrity": "sha1-W9n23vwTOFmgRGRtR0P6vCjbfi0=",
+ "engines": {
+ "node": ">=0.8.0"
+ }
+ },
+ "node_modules/tabbable": {
+ "version": "1.1.3",
+ "resolved": "https://registry.npmjs.org/tabbable/-/tabbable-1.1.3.tgz",
+ "integrity": "sha512-nOWwx35/JuDI4ONuF0ZTo6lYvI0fY0tZCH1ErzY2EXfu4az50ZyiUX8X073FLiZtmWUVlkRnuXsehjJgCw9tYg=="
+ }
+ },
"dependencies": {
"@babel/runtime": {
"version": "7.9.2",
@@ -129,6 +375,17 @@
"react-is": "^16.8.1"
}
},
+ "react": {
+ "version": "16.14.0",
+ "resolved": "https://registry.npmjs.org/react/-/react-16.14.0.tgz",
+ "integrity": "sha512-0X2CImDkJGApiAlcf0ODKIneSwBPhqJawOa5wCtKbu7ZECrmS26NvtSILynQ66cgkT/RJ4LidJOc3bUESwmU8g==",
+ "peer": true,
+ "requires": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1",
+ "prop-types": "^15.6.2"
+ }
+ },
"react-aria-modal": {
"version": "2.12.3",
"resolved": "https://registry.npmjs.org/react-aria-modal/-/react-aria-modal-2.12.3.tgz",
@@ -142,7 +399,20 @@
"react-displace": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/react-displace/-/react-displace-2.3.0.tgz",
- "integrity": "sha512-T8g/lyn3IX8kxLO4k4vJ/oIO9G72pRTc9GYslqKsfPcN4gY5+FYR5OHxeTH1skPjVylJrveGE3OC2qCt3BuHeA=="
+ "integrity": "sha512-T8g/lyn3IX8kxLO4k4vJ/oIO9G72pRTc9GYslqKsfPcN4gY5+FYR5OHxeTH1skPjVylJrveGE3OC2qCt3BuHeA==",
+ "requires": {}
+ },
+ "react-dom": {
+ "version": "16.14.0",
+ "resolved": "https://registry.npmjs.org/react-dom/-/react-dom-16.14.0.tgz",
+ "integrity": "sha512-1gCeQXDLoIqMgqD3IO2Ah9bnf0w9kzhwN5q4FGnHZ67hBm9yePzB5JJAIQCc8x3pFnNlwFq4RidZggNAAkzWWw==",
+ "peer": true,
+ "requires": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1",
+ "prop-types": "^15.6.2",
+ "scheduler": "^0.19.1"
+ }
},
"react-is": {
"version": "16.13.1",
@@ -154,6 +424,16 @@
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.5.tgz",
"integrity": "sha512-ZS5w8CpKFinUzOwW3c83oPeVXoNsrLsaCoLtJvAClH135j/R77RuymhiSErhm2lKcwSCIpmvIWSbDkIfAqKQlA=="
},
+ "scheduler": {
+ "version": "0.19.1",
+ "resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.19.1.tgz",
+ "integrity": "sha512-n/zwRWRYSUj0/3g/otKDRPMh6qv2SYMWNq85IEa8iZyAv8od9zDYpGSnpBEjNgcMNq6Scbu5KfIPxNF72R/2EA==",
+ "peer": true,
+ "requires": {
+ "loose-envify": "^1.1.0",
+ "object-assign": "^4.1.1"
+ }
+ },
"svg4everybody": {
"version": "2.1.9",
"resolved": "https://registry.npmjs.org/svg4everybody/-/svg4everybody-2.1.9.tgz",
diff --git a/postman/CMS_DPC_API_Developer.postman_collection.json b/postman/CMS_DPC_API_Developer.postman_collection.json
index 14e5aa29..79b20d5c 100644
--- a/postman/CMS_DPC_API_Developer.postman_collection.json
+++ b/postman/CMS_DPC_API_Developer.postman_collection.json
@@ -2,7 +2,7 @@
"info": {
"_postman_id": "3aefd688-7b7d-405e-9c87-586b897bd58b",
"name": "Centers for Medicare & Medicaid Services (CMS) - Data at the Point of Care (DPC) API - App Developer",
- "description": "This collection contains example requests for the public endpoints for the Data at the Point of Care (DPC) API. In order to use it, you must first create public and private keys and update the following values in your local Postman sandbox environment:\n\n1) `client_token`: This is sometimes also referred to as a `macaroon` and can be created on the DPC portal. Be sure to save a copy of your token in a safe place.\n\n2) `PRIVATE_KEY`: Follow the steps found here to create public and private keys: https://dpc.cms.gov/docs#upload-your-first-public-key and paste the contents of your private key in the `PRIVATE_KEY` field of your local Postman sandbox environment. Do not share your private key otherwise.\n\n3) `key-id`: This is the system id of your public key, which is returned to you when the public key is uploaded to the DPC portal. You need this to generate a JWT, which you will exchange for an access token.\n\nWith these 3 values in place, the JWT and a fresh access token are automatically generated for you before each request in this Postman collection to prevent you from having to manually refresh the access token every 5 minutes while using the collection. Note that, due to the way Postman works, you may occasionally experience a race condition that results in your access token not being refreshed before the main Postman request. In this case, you would receive a 401 with a message about invalid credentials. If this happens, just try the request again, and you should have a fresh token the second time.\n\nUnder `Security/Authentication`, in the `Public Keys`, you will find a request to add a public key to DPC without using the portal. This request requires auth and is not required in order to use the other requests in this collection. If you would like to create a new public key, first generate the keys locally, then follow the directions in the `Add/Register Public Key on DPC Sandbox` description. You do not need to update the `PUBLIC_KEY`, `public-key-label`, and `public-key-signature` values in the environment otherwise.\n",
+ "description": "This collection contains example requests for the public endpoints for the Data at the Point of Care (DPC) API. In order to use it, you must first create public and private keys and update the following values in your local Postman sandbox environment:\n\n1) `client_token`: This is sometimes also referred to as a `macaroon` and can be created on the DPC portal. Be sure to save a copy of your token in a safe place.\n\n2) `PRIVATE_KEY`: Follow the steps found here to create public and private keys: https://dpc.cms.gov/docsV1#upload-your-first-public-key and paste the contents of your private key in the `PRIVATE_KEY` field of your local Postman sandbox environment. Do not share your private key otherwise.\n\n3) `key-id`: This is the system id of your public key, which is returned to you when the public key is uploaded to the DPC portal. You need this to generate a JWT, which you will exchange for an access token.\n\nWith these 3 values in place, the JWT and a fresh access token are automatically generated for you before each request in this Postman collection to prevent you from having to manually refresh the access token every 5 minutes while using the collection. Note that, due to the way Postman works, you may occasionally experience a race condition that results in your access token not being refreshed before the main Postman request. In this case, you would receive a 401 with a message about invalid credentials. If this happens, just try the request again, and you should have a fresh token the second time.\n\nUnder `Security/Authentication`, in the `Public Keys`, you will find a request to add a public key to DPC without using the portal. This request requires auth and is not required in order to use the other requests in this collection. If you would like to create a new public key, first generate the keys locally, then follow the directions in the `Add/Register Public Key on DPC Sandbox` description. You do not need to update the `PUBLIC_KEY`, `public-key-label`, and `public-key-signature` values in the environment otherwise.\n",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
},
"item": [
@@ -138,7 +138,7 @@
}
]
},
- "description": "This endpoint registers the provided public key with the organization.\n\nThe provided key MUST be PEM encoded. (See https://dpc.cms.gov/docs#upload-your-first-public-key) RSA keys of 4096-bits or greater are supported, as well as ECC keys using one of the following curves:- secp256r1- secp384r1\n\nPREREQUISITES:\n- `PUBLIC_KEY`: Before using this endpoint, you must paste your PEM encoded public key as the value for this environment variable.\n- `public_key_signature`: Before using this endpoint, you must paste your public key signature as the value for this environment variable.\n- `public-key-label`: Feel free to modify this label, which is `Test Public Key` by default."
+ "description": "This endpoint registers the provided public key with the organization.\n\nThe provided key MUST be PEM encoded. (See https://dpc.cms.gov/docsV1#upload-your-first-public-key) RSA keys of 4096-bits or greater are supported, as well as ECC keys using one of the following curves:- secp256r1- secp384r1\n\nPREREQUISITES:\n- `PUBLIC_KEY`: Before using this endpoint, you must paste your PEM encoded public key as the value for this environment variable.\n- `public_key_signature`: Before using this endpoint, you must paste your public key signature as the value for this environment variable.\n- `public-key-label`: Feel free to modify this label, which is `Test Public Key` by default."
},
"response": []
},
3. Onboard with DPC
- - Approximately 2-3 weeks after your successful DPC solution demonstration in the sandbox environment, you will receive an email with information and a link to schedule an onboarding session. In the same email, you will also receive further instructions on production requirements prior to the onboarding date. + After your successful DPC solution demonstration in the sandbox environment with the DPC Team, you will receive an email with information about the onboarding session. In the same email, you will also receive further instructions on production requirements prior to the onboarding date.
- After completing production requirements, you will receive production credentials for the healthcare organization for which you are implementing the DPC solution.
-
- During the live onboarding session, you will receive real-time support from DPC engineers as you demonstrate the following:
-
-
+ During the live onboarding session with the DPC Team, you will receive real-time support from DPC engineers as you demonstrate the following:
+
- - Submit a request for data + Submit a request for data.
- - Receive requested data from DPC + Receive requested data from DPC.
Share Your Feedback
+Share Your Feedback
- - The DPC team is always seeking feedback! Pilot partners will be requested to participate in research sessions where Health IT implementers and healthcare organizations will be asked, together or separately, to share their experiences, challenges, and recommendations regarding the design of the DPC API and its features. + The DPC Team is always seeking feedback! Pilot partners will be requested to participate in research sessions where Health IT implementers and healthcare organizations will be asked, together or separately, to share their experiences, challenges, and recommendations regarding the design of the DPC API and its features.
- - Join the DPC Google Group community to ask questions, share your thoughts, and hear about updates and upcoming events related to DPC. + Join the DPC Google Group community to ask questions, share your thoughts, and hear about updates and upcoming events related to DPC.