201709 GraphQL

GraphQL Track

Submitting WG/Project/Implementer Group

Grahame Grieve on behalf of FHIR-I/AID

Justification

There has been ongoing implementer interest in a more agile way to fetch data from a FHIR server, and some implementers have told me that they won't use FHIR because of this.

Proposed Track Lead

Grahame Grieve (looking for handover)

Expected participants

• test.fhir.org
• hapi server

Roles

Server

Makes data available through a graphQL interface:

1. support query a patient resource using graphQL (or Observation)
2. support forward reference - follow Patient.generalPractitioner (or Observation.subject)
3. support search - allow search on patients
4. support publish metadata describing 1-3

Servers should list which steps they implement on the tracking spreadsheets

Client

1. query a patient resource using graphQL (or Observation)
2. forward reference - follow Patient.generalPractitioner (or Observation.subject)
3. search on patients
4. (advanced) Metadata driven interface (picklist?)

Scenarios

as implied by roles

TestScript(s)

Test scripts don't support graphQL yet. Should they?

Security and Privacy Considerations

No implications not already obvious on the RESTful interface.