Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
699 changes: 695 additions & 4 deletions package-lock.json

Large diffs are not rendered by default.

9 changes: 8 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,5 +26,12 @@
"sirv": "^3.0.2",
"taze": "^21.3.0",
"vitest": "^5.0.5"
},
"allowScripts": {
"fsevents@2.3.3": true,
"puppeteer@25.13.0": true
},
"devDependencies": {
"vite": "^8.3.7"
}
}
}
2 changes: 1 addition & 1 deletion src/_announcements/whats-new-on-dpc.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The updated site includes 4 main sections, along with links to additional resour

### About (formerly “About the pilot”)

Learn about the background and purpose of the DPC pilot program. Visit Announcements (formerly Updates) for the latest DPC news.
Learn about the background and purpose of DPC. Visit Announcements (formerly Updates) for the latest DPC news.

[Visit About]({{ '/about.html' | relative_url }})

Expand Down
2 changes: 1 addition & 1 deletion src/_config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ title: Data at the Point of Care
short_title: DPC
email: dpc-api@googlegroups.com
description: >- # this means to ignore newlines until "baseurl:"
Data at the Point of Care is a pilot CMS API program that enables
Data at the Point of Care is a CMS API that enables
healthcare providers to deliver high quality care to Medicare
beneficiaries by sharing their patients' Medicare claims data for
treatment needs.
Expand Down
3 changes: 0 additions & 3 deletions src/_data/api-docs-nav.yml
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,6 @@
- name: How to Filter Claims Data
url: /api-documentation/export-data/how-to-filter.html

- name: /Patient/$everything
url: /api-documentation/export-data/patient-everything.html

- name: Postman Collection
url: /api-documentation/postman-collection.html

Expand Down
10 changes: 3 additions & 7 deletions src/_pages/about.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: api-docs
page_title: "About DPC"
seo_title: ""
description: "Data at the Point of Care (DPC) is a CMS pilot program that shares Medicare claims data with Original Medicare providers to support coordinated care."
description: "Data at the Point of Care (DPC) is an API that shares Medicare claims data with Original Medicare providers to support coordinated care."
show-side-nav: false
---

Expand All @@ -20,23 +20,19 @@ show-side-nav: false
<div class="desktop:grid-col desktop:order-1">
<h1 class="margin-top-5 desktop:margin-top-0">{{ page.page_title }}</h1>
<h2>Creating continuity for people with Medicare</h2>
<p>People with Medicare can receive care from multiple providers and care settings. As a result, providers may not have a complete picture of a patient's care history when making clinical decisions. The Data at the Point of Care (DPC) pilot program securely shares Medicare claims data in a standardized format, the <a href="https://www.hl7.org/fhir/" target="_blank">HL7® FHIR® standard</a>. This helps providers fill information gaps, make more informed clinical decisions, and coordinate care more effectively. By giving care teams a more complete picture of their patients, DPC supports better, more connected care for people with Medicare.</p>
<p>People with Medicare can receive care from multiple providers and care settings. As a result, providers may not have a complete picture of a patient's care history when making clinical decisions. Data at the Point of Care (DPC) securely shares Medicare claims data in a standardized format, the <a href="https://www.hl7.org/fhir/" target="_blank">HL7® FHIR® standard</a>. This helps providers fill information gaps, make more informed clinical decisions, and coordinate care more effectively. By giving care teams a more complete picture of their patients, DPC supports better, more connected care for people with Medicare.</p>
</div>
</div>

## Completing the picture with Medicare claims

Medicare claims tell a continuous story about visits, admissions, screenings, services, and medications. Centers for Medicare & Medicaid Services (CMS) created the DPC pilot program to securely share this information with Original Medicare providers. DPC can:
Medicare claims tell a continuous story about visits, admissions, screenings, services, and medications. Centers for Medicare & Medicaid Services (CMS) created DPC to securely share this information with Original Medicare providers. DPC can:

- Keep providers informed about services patients receive between visits, enabling more coordinated and timely care.
- Reduce the need for patients to repeatedly share their health histories, saving time and improving the patient experience.
- Provide insights into prescription refills, medication changes, and adherence, supporting better medication management and reducing gaps in treatment.
- Highlight preventive services such as flu and shingles vaccines, helping providers close care gaps and improve patient health outcomes.

## DPC is currently a pilot program

DPC is currently available to a limited number of pilot participants. We’re finalizing a new authentication and onboarding portal created based on feedback from pilot participants. During this time, CMS won’t be onboarding new production users. We'll announce general availability of production data when the portal launches. In the meantime, developers can continue exploring DPC using realistic test data in the sandbox.

## What are the other CMS claims-based FHIR APIs?

<ul class="usa-card-group flex-justify-center padding-y-4">
Expand Down
30 changes: 15 additions & 15 deletions src/_pages/api-documentation/attribution/attestation.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,14 +32,14 @@ Log into the [DPC Sandbox](https://sandbox.dpc.cms.gov/users/sign_in) and locate
**Example request**

{% capture snippet %}
GET /api/v1/Organization
GET /api/v3/Organization
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Organization' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Organization' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand Down Expand Up @@ -78,14 +78,14 @@ Send a `GET` request to `/Practitioner` to retrieve a Bundle of Practitioner Res
**Example request**

{% capture snippet %}
GET /api/v1/Practitioner
GET /api/v3/Practitioner
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Practitioner' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Practitioner' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand Down Expand Up @@ -135,7 +135,7 @@ Combine the Organization ID from the [Organization response](#locate-your-organi
"resourceType": "Provenance",
"meta": {
"profile": [
"https://dpc.cms.gov/api/v1/StructureDefinition/dpc-profile-attestation"
"https://dpc.cms.gov/api/v3/StructureDefinition/dpc-profile-attestation"
]
},
"recorded": "{TIMESTAMP}",
Expand Down Expand Up @@ -209,7 +209,7 @@ You'll need to create a Group Resource to link a list of [registered patients]({
**Example request**

{% capture snippet %}
POST /api/v1/Group
POST /api/v3/Group
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

Expand Down Expand Up @@ -257,7 +257,7 @@ Replace the placeholders before sending:
**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down Expand Up @@ -351,14 +351,14 @@ You can use the Group ID value of the returned resources to [initiate an export
**Example request**

{% capture snippet %}
GET /api/v1/Group?characteristic-value=attributed-to%24{PRACTITIONER_NPI}
GET /api/v3/Group?characteristic-value=attributed-to%24{PRACTITIONER_NPI}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group?characteristic-value=attributed-to%24{PRACTITIONER_NPI}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group?characteristic-value=attributed-to%24{PRACTITIONER_NPI}' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand Down Expand Up @@ -426,7 +426,7 @@ Use the `$add` operation to add new patients to a group.
**Example request**

{% capture snippet %}
POST /api/v1/Group/{GROUP_ID}/$add
POST /api/v3/Group/{GROUP_ID}/$add
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

Expand Down Expand Up @@ -472,7 +472,7 @@ When adding patients to a group, the body must include the same `characteristic`
**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group/{GROUP_ID}/$add' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group/{GROUP_ID}/$add' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down Expand Up @@ -532,7 +532,7 @@ Use a custom `$remove` operation on the `/Group` endpoint to remove a patient fr
**Example request**

{% capture snippet %}
POST /api/v1/Group/{GROUP_ID}/$remove
POST /api/v3/Group/{GROUP_ID}/$remove
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

Expand Down Expand Up @@ -578,7 +578,7 @@ Like `$add`, the body must include the practitioner `characteristic`.
**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group/{GROUP_ID}/$remove' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group/{GROUP_ID}/$remove' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down Expand Up @@ -653,7 +653,7 @@ Patients in the existing group that you omit from the `PUT` body are not deleted
**Example request**

{% capture snippet %}
PUT /api/v1/Group/{GROUP_ID}
PUT /api/v3/Group/{GROUP_ID}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

Expand Down Expand Up @@ -697,7 +697,7 @@ PUT /api/v1/Group/{GROUP_ID}
**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group/{GROUP_ID}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group/{GROUP_ID}' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down
4 changes: 2 additions & 2 deletions src/_pages/api-documentation/attribution/upload-patients.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,13 +30,13 @@ The `$submit` operation lets you upload a bundle of patients for registration in

**Example request**
{% capture snippet %}
POST /api/v1/Patient/$submit
POST /api/v3/Patient/$submit
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Patient/$submit' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Patient/$submit' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@ The `GET` `/Patient` operation retrieves a single Patient Resource by supplying

**Example request**
{% capture snippet %}
GET /api/v1/Patient?identifier={PATIENT_MBI}
GET /api/v3/Patient?identifier={PATIENT_MBI}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Patient?identifier={PATIENT_MBI}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Patient?identifier={PATIENT_MBI}' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand All @@ -40,7 +40,7 @@ curl 'https://sandbox.dpc.cms.gov/api/v1/Patient?identifier={PATIENT_MBI}' \
"meta": {
"lastUpdated": "2020-06-12T15:39:42.834+00:00",
"profile": [
"https://dpc.cms.gov/api/v1/StructureDefinition/dpc-profile-patient"
"https://dpc.cms.gov/api/v3/StructureDefinition/dpc-profile-patient"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like for this we are curling https://sandbox.dpc.cms.gov/api/v3/... but the profile in the response isnt specifying sandbox. Also, I believe the team is actively looking into deploying the new portal into sandbox and replacing the old web. There was some budget concerns but we should follow up on this with Manoj and team!

]
},
"identifier": [
Expand Down Expand Up @@ -75,13 +75,13 @@ The `GET` `/Patient` operation lets you retrieve a bundle of Patient Resources.

**Example request**
{% capture snippet %}
GET /api/v1/Patient
GET /api/v3/Patient
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Patient' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Patient' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,13 +30,13 @@ The `$submit` operation lets you upload a bundle of practitioner resources in a
**Example request**

{% capture snippet %}
POST /api/v1/Practitioner/$submit
POST /api/v3/Practitioner/$submit
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Practitioner/$submit' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Practitioner/$submit' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json' \
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,13 +14,13 @@ The `GET` `/Practitioner` operation lets you retrieve a [bundle](https://www.hl7

**Example request**
{% capture snippet %}
GET /api/v1/Practitioner
GET /api/v3/Practitioner
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Practitioner' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Practitioner' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json'
{% endcapture %}
Expand All @@ -32,13 +32,13 @@ Retrieve a single practitioner by providing an NPI number.

**Example request**
{% capture snippet %}
GET /api/v1/Practitioner?identifier={PRACTITIONER_NPI}
GET /api/v3/Practitioner?identifier={PRACTITIONER_NPI}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**
{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Practitioner?identifier={PRACTITIONER_NPI}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Practitioner?identifier={PRACTITIONER_NPI}' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Content-Type: application/fhir+json'
Expand All @@ -60,7 +60,7 @@ curl 'https://sandbox.dpc.cms.gov/api/v1/Practitioner?identifier={PRACTITIONER_N
"meta": {
"lastUpdated": "2020-06-10T18:43:14.150+00:00",
"profile": [
"https://dpc.cms.gov/api/v1/StructureDefinition/dpc-profile-practitioner"
"https://dpc.cms.gov/api/v3/StructureDefinition/dpc-profile-practitioner"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above here and in a few other places.

]
},
"identifier": [
Expand Down
17 changes: 8 additions & 9 deletions src/_pages/api-documentation/export-data.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,6 @@ Use `_type` and `_since` to [filter your results]({{ "/api-documentation/export-

- `_type` restricts the export to specific FHIR Resources (e.g., `?_type=Patient,Coverage`).
- `_since` excludes data older than a given date (e.g., `?_since=2025-01-07T00:00:00Z`).
- For a single patient's full 7-year history including Patient, Coverage, and ExplanationOfBenefit, use [`/Patient/{PATIENT_ID}/$everything`]({{ "/api-documentation/export-data/patient-everything.html" | relative_url }}) instead of `$export`.

## Initiating an export job

Expand All @@ -45,14 +44,14 @@ Make a `GET` request to `/Group/{GROUP_ID}/$export` with `Authorization`, `Accep
**Example request**

{% capture snippet %}
GET /api/v1/Group/{GROUP_ID}/$export
GET /api/v3/Group/{GROUP_ID}/$export
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Group/{GROUP_ID}/$export' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Group/{GROUP_ID}/$export' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept: application/fhir+json' \
-H 'Prefer: respond-async'
Expand All @@ -64,7 +63,7 @@ The API returns `202 Accepted` for successful requests. The response body is emp
**Example response header** (`202 Accepted`)

{% capture snippet %}
Content-Location: https://sandbox.dpc.cms.gov/api/v1/Jobs/{JOB_ID}
Content-Location: https://sandbox.dpc.cms.gov/api/v3/Jobs/{JOB_ID}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

Expand All @@ -77,7 +76,7 @@ Export jobs are asynchronous. While the job is still running, the same URL retur
**Example cURL command** (use the URL directly from `Content-Location`)

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Jobs/{JOB_ID}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Jobs/{JOB_ID}' \
-H "Authorization: Bearer $BEARER_TOKEN"
{% endcapture %}
{% include copy_snippet.html code=snippet language="shell" can_copy=true %}
Expand All @@ -87,12 +86,12 @@ curl 'https://sandbox.dpc.cms.gov/api/v1/Jobs/{JOB_ID}' \
{% capture snippet %}
{
"transactionTime": "2026-04-28T21:07:46.876+00:00",
"request": "https://sandbox.dpc.cms.gov/api/v1/Group/64d0cd85-7767-425a-a3b8-dcc9bdfd5402/$export",
"request": "https://sandbox.dpc.cms.gov/api/v3/Group/64d0cd85-7767-425a-a3b8-dcc9bdfd5402/$export",
"requiresAccessToken": true,
"output": [
{
"type": "ExplanationOfBenefit",
"url": "https://sandbox.dpc.cms.gov/api/v1/Data/06abfdd3-dc05-43aa-b07a-361651576c3b-0.explanationofbenefit.ndjson",
"url": "https://sandbox.dpc.cms.gov/api/v3/Data/06abfdd3-dc05-43aa-b07a-361651576c3b-0.explanationofbenefit.ndjson",
"count": 45,
"extension": [
{
Expand Down Expand Up @@ -132,14 +131,14 @@ Fetch each URL in `output[].url` with your bearer token to download an [NDJSON](
**Example request**

{% capture snippet %}
GET https://sandbox.dpc.cms.gov/api/v1/Data/{FILE_ID}
GET https://sandbox.dpc.cms.gov/api/v3/Data/{FILE_ID}
{% endcapture %}
{% include copy_snippet.html code=snippet language="http" %}

**Example cURL command**

{% capture snippet %}
curl 'https://sandbox.dpc.cms.gov/api/v1/Data/{FILE_ID}' \
curl 'https://sandbox.dpc.cms.gov/api/v3/Data/{FILE_ID}' \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H 'Accept-Encoding: gzip' \
--compressed
Expand Down
Loading
Loading