New feature / Change #6753
Updated by Olivier Bitsch about 2 months ago
So endpoint should looks like:
- Appointments: connected on invites - https://build.fhir.org/appointment.html
- Encounters: connected on consultations. It seems feasible to fetch Encounters from Appointment (under class?) https://build.fhir.org/encounter.html
Check this project as base https://www.npmjs.com/package/fhir
Edit:
# HCW <> FHIR
## To be implemented
### Appointment (FHIR) <> Invite (HCW)
mapping: publicInvite
> https://build.fhir.org/appointment.html
POST
- **start** (when consultation start - optionnal): check date is in future.
- **participant** (list of participant - mandatory), we must meet:
- 0 or 1 patient (code: PAT)
- must have telecom > ContactPoint with at least email or sms.
- must have name (HumanName):
- must have family (lastName)
- must have given (firstName)
- must have gender
- 1 practitioner (code: PPRF)
- must have telecom > ContactPoint with at least email.
- **recurrenceTemplate**: must return error if defined.
- **occurrenceChanged**: must return error if defined.
- **basedOn**: must return error if defined.
- **patientInstruction**: must return error if defined.
- **note**: put in metadata (only 1 supported)
- **cancellationDate**: must return error if defined.
- **minutesDuration**: put in metadata
- **end**: put in metadata
- **description**: put in metadata
- **reason**: put in metadata
- **identifier**: put in metadata
note :
- some field can be accepted, but will be ignored (e.g end).
- queue will not be supported later.
GET
In addition of POST item, we can return:
- **status**:
## To be implemented later
## Practitioner
mapping: User (role: doctor)
> https://build.fhir.org/practitioner.html
## Group
mapping: Queue
> https://build.fhir.org/group.html