Compare commits

..

No commits in common. '1e2f02df03cc130e95167840759afc7c86a0caf4' and 'ed81f0198d3ff43f6e9f2b82ea997f3b13cf3a8b' have entirely different histories.

@ -4,7 +4,7 @@ get:
- Quality of Care - Quality of Care
summary: Call-up status summary: Call-up status
description: |- description: |-
Load call-up status for patients in a care program. Returns each patient in a care program along with the progress on required or suggested measurements indicated for this care program. Load the call-up status for patients in a care program. Returns each patient in a care program along with the progress on required or suggested measurements indicated for this care program.
parameters: parameters:
- name: setKey - name: setKey
in: path in: path
@ -49,15 +49,29 @@ get:
description: Request inclusion of email addresses description: Request inclusion of email addresses
schema: schema:
type: boolean type: boolean
- name: onlyNameAddress
in: query
required: false
description: |-
If true, only data needed for printing address labels is in the response. This output is also known as Dymo output. The format of the response depends on the HTTP Accept header. If the best match between the server en caller is:
* `text/csv`, then CSV according RFC 4180 is responded;
* `application/json`, then JSON;
* `application/vnd.ms-excel` or `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, then legacy MS Excel;
While the server is still calculating, see calculating property in the response, the output is always `application/json`.
schema:
type: boolean
- $ref: '../zoo-api.yaml#/components/parameters/Authorization' - $ref: '../zoo-api.yaml#/components/parameters/Authorization'
responses: responses:
'200': '200':
description: |- description: |-
list of patients A list of patients. The format of the response is default a comprehensive JSON, but can be limited to only data needed for printing address labels, using the `onlyNameAddress` parameter. Any non JSON response has a header row with field names.
content: content:
application/json: application/json:
schema: schema:
type: object oneOf:
- type: object
properties: properties:
gpis: gpis:
$ref: '../schemas/IndicatorSet.yaml#/properties/gpis' $ref: '../schemas/IndicatorSet.yaml#/properties/gpis'
@ -126,6 +140,8 @@ get:
An index (0-based) into the `doctors` entry: This is the GP responsible for this patient. An index (0-based) into the `doctors` entry: This is the GP responsible for this patient.
status: status:
$ref: '../schemas/callUpStatus-enum.yaml' $ref: '../schemas/callUpStatus-enum.yaml'
name:
$ref: '../schemas/pat-Name.yaml'
address1: address1:
type: string type: string
description: |- description: |-
@ -175,6 +191,16 @@ get:
- name - name
- refDate - refDate
- calculating - calculating
- $ref: '../schemas/dymo.yaml'
text/csv:
schema:
$ref: '../schemas/dymo.yaml'
'application/vnd.ms-excel':
schema:
$ref: '../schemas/dymo.yaml'
'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet':
schema:
$ref: '../schemas/dymo.yaml'
'401': '401':
$ref: '../zoo-api.yaml/#/components/responses/NoAuth' $ref: '../zoo-api.yaml/#/components/responses/NoAuth'
'403': '403':

@ -0,0 +1,22 @@
type: array
items:
type: object
properties:
patPubId:
$ref: '../schemas/PatIdentity.yaml#/patPubId'
patUnid:
$ref: '../schemas/PatIdentity.yaml#/patUnid'
displayName:
type: string
example: "Timmermans - de Vos"
addressLine1:
type: string
example: "Pieter Cordifstraat 88"
addressLine2:
type: string
example: "2552 XT HAMOR"
required:
- patUnid
- displayName
- addressLine1
- addressLine2
Loading…
Cancel
Save