Stream: uk
Topic: Medication Issues - GP Connect
Kevin Mayfield (Sep 05 2019 at 05:35):
Gp connect spec has a model of medication issues where every issue (medicationrequest - order) has a basedon (parent) plan (another medication request plan). The supplier I'm working with and at least two versions from another supplier (I used to work for) doesn't follow this model (a gp issues a drug, they may plan an issue but normally they dont).
The only way of following the spec is to create synthetic issues with a status of plan (but note I will have real planned issues).
As a consumer I will also need to filter out the synthetic planned issues (wouldn't want to display/have duplicate/synthetic issues), however I only need to do that if I'm not using MedicationStatement.
I believe the spec is wrong in enforcing this model and interested in views?
Kevin Mayfield (Sep 05 2019 at 05:35):
Last updated: Apr 12 2022 at 19:14 UTC