Skip to content

Commit

Permalink
switch application/x-www-form-urlencoded to application/json - seems …
Browse files Browse the repository at this point in the history
…bfd does not accept it
  • Loading branch information
JFU-NAVA-PBC committed Feb 25, 2025
1 parent a1d3c2b commit 4fcd1dc
Showing 1 changed file with 0 additions and 77 deletions.
77 changes: 0 additions & 77 deletions static/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -423,83 +423,6 @@ paths:
application/fhir+json:
schema: {$ref: '#/components/schemas/FHIR-JSON-RESOURCE'}
/v2/fhir/Claim/_search:
post:
tags: [v2]
summary: 'search-type: Search for Claim instances'
description: This is a search type
requestBody:
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
_lastUpdated:
type: string
description: |-
Only satisfy the Search if the Beneficiary's `last_updated` Date falls within a specified _DateRange_.
A _DateRange_ can be defined by providing less than `lt` and/or greater than `gt` values.
This parameter can be included in a request one or more times.

Inexact timestamps are accepted, but not recommended, since the input will implicitly be converted to use the server's timezone.

Examples:
- `_lastUpdated=gt2023-01-02T00:00+00:00&_lastUpdated=lt2023-05-01T00:00+00:00` defines a range between two provided dates
- `_lastUpdated=gt2023-01-02T00:00+00:00` defines a range between the provided date and today
- `_lastUpdated=lt2023-05-01T00:00+00:00` defines a range from the earliest available records until the provided date
example: gt2023-01-02
service-date:
type: string
description: "Only satisfy the search request if a claim's date\
\ falls within a specified _DateRange_.\nThe _DateRange_ is defined\
\ by the claim's billing period, specifically the \n`Claim.billablePeriod.end`.\
\ A _DateRange_ can be further refined by providing \nless than\
\ `lt` and/or greater than `gt` values. This parameter can be\
\ included \nin a request one or more times.\n\nExamples:\n -\
\ `service-date=gt2023-01-02&service-date=lt2023-05-01`\n - `service-date=gt2023-01-02`\n\
\ - `service-date=lt2023-05-01`"
example: lt2023-05-01
startIndex:
type: string
description: |-
When fetching a _Bundle Response_ using pagination, this URL parameter represents an offset
(starting point) into the list of elements for the _Request_.
It is optional and defaults to 1 if not supplied.
A value 0 is not allowed and negative indices are not currently supported.

Example:
- `startIndex=100`
example: 5
_count:
description: |-
Provides the number of records to be used for pagination.

Examples:
- `_count=10`: return 10 values.
format: int32
example: 10
type:
type: string
description: |-
A list of one or more comma-separated claim types to be included in the request;
within BFD, the claim types represent an _OR_ inclusion logic meaning any claims matching one of the specified
claim types will be checked

Supported Claim Type values:
- `fiss`
- `mcs`

Examples:
- `type=fiss,mcs`
- `type=fiss`
example: fiss,mcs
required: true
responses:
'200':
description: Success
content:
application/fhir+json:
schema: {$ref: '#/components/schemas/FHIR-JSON-RESOURCE'}
/v2/fhir/ClaimJSON/_search:
post:
tags: [v2]
summary: 'search-type: Search for Claim instances'
Expand Down

0 comments on commit 4fcd1dc

Please sign in to comment.