You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
44 lines
1.8 KiB
YAML
44 lines
1.8 KiB
YAML
type: object
|
|
required:
|
|
- vektis
|
|
- when
|
|
properties:
|
|
code:
|
|
description: |-
|
|
If present, the source uses a short code (a 'memocode') to represent feats, and this is the code associated with it.
|
|
type: string
|
|
example: ECG
|
|
vektis:
|
|
description: |-
|
|
The vektis code from list 8 (the list for feats GPs can declare) representing this feat.
|
|
|
|
For custom feats that therefore cannot actually be declared with any insurance company, this value is 0.
|
|
type: number
|
|
example: 13005
|
|
when:
|
|
description: |-
|
|
The stated feat was performed on this date. subscription style feats by convention always on the first day of a quarter.
|
|
$ref: ../date.yaml
|
|
invoice:
|
|
description: |-
|
|
If this feat has been declared, the invoice id that declared it. Not all source systems track this, and generally
|
|
invoices aren't instantly sent as feats are registered. Thus, if this field isn't provided, either the feat hasn't been invoiced yet,
|
|
or the source system doesn't track invoicing, or the GP office doesn't use the source system for invoicing.
|
|
type: string
|
|
example: A00001234
|
|
gp:
|
|
description: |-
|
|
The GP responsible for this patient at the time of the feat. If income is redistributed to each GP participating in this practice,
|
|
this should be used to know where to send received funds to.
|
|
|
|
Contents are free-form as it depends on the source system.
|
|
type: string
|
|
example: AA
|
|
practitioner:
|
|
$ref: 'Practitioner.yaml'
|
|
description:
|
|
description: |-
|
|
Some source systems allow adding a comment or description when registering a feat; often simply a copy of the description of
|
|
what `vektis` represents, but can be explicitly typed in by the practitioner registering this feat.
|
|
type: string
|
|
example: "12001: Dubbel consult huisarts" |