Skip to content

Commit

Permalink
Update access-production-claims-data.md
Browse files Browse the repository at this point in the history
  • Loading branch information
phamjennifer authored Feb 18, 2025
1 parent 815d0d8 commit ac03bbf
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions _pages/access-production-claims-data.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,15 @@ You’ll still need [a bearer token]({{ '/get-a-bearer-token' | relative_url }})
- Check the job status: `GET /api/v2/fhir/Job/{job_uuid}/$status`
- Download files: `GET/api/v2/fhir/Job/{job_uuid}/file/{file_name}`

### File expiration
### Job expiration

If it takes more than 30 hours to retrieve and download the data, the request will time out and fail. Try using [parameters]({{ '/query-parameters-V2' | relative_url }}) when running a job to filter the claims data returned and reduce file size.
Job IDs and file URLs expire after 72 hours or 6 downloads. If it takes more than 30 hours for a job to complete, the request will time out and fail. Reduce file sizes and download times by using [parameters]({{ '/query-parameters-V2' | relative_url }}) to filter the claims data returned or download compressed data files in gzip format.

### Format

Files are in NDJSON format, where each line is a Medicare claim written in JSON. The file naming standard uses a contract identifier and number to indicate sequence (e.g., Z123456_0001.ndjson). Large data files require adequate storage and a database to process the claims received.
Files are in NDJSON format, where each line is a Medicare claim written in JSON. The file naming standard uses a contract identifier and number to indicate sequence (e.g., Z123456_0001.ndjson).

You can optionally download files in gzip format and decompress (unzip) them afterward into NDJSON. Large data files require adequate storage and a database to process the claims received.

## Sample client scripts

Expand Down

0 comments on commit ac03bbf

Please sign in to comment.