HL7-UK / UK-Core-Access

Apache License 2.0
3 stars 2 forks source link

IHE QEDm as model for interaction #4

Closed Dunmail closed 1 year ago

Dunmail commented 1 year ago

IHE have drafted a QEDm standard: https://wiki.ihe.net/index.php/Query_for_Existing_Data_for_Mobile_(QEDm) that defines a FHIR API for retrieval of patient information very similar to those that were identified during the discovery phase. Should we reference or align to this standard?

In addition, NHS Digital have a Clinical Data Sharing API under active development as part of UK Core [ https://simplifier.net/guide/uk-qepd?version=current] that was last updated in November 2022. @KevinMayfield: Is there a spec for international QEPD? Is this an 'official' NHS Digital project? How does it fit in with the prioritisation of work by the UK FHIR Board?

clarotech commented 1 year ago

I think we should assess QEDm to see whether there is anything overtly problematic with it. If not, then absolutely.

clarotech commented 1 year ago

Also might be an idea to look at PDQm as well. I recall reviewing this for IHE a few years back and it was a little US in focus, but I think that has been rectified now.

KevinMayfield commented 1 year ago

The NHS Digital spec is not official, it is more research looking at what is available (to support clinical process / FHIR Workflow)

We also had https://profiles.ihe.net/ITI/MHD/index.html (FHIR XDS) and https://wiki.ihe.net/index.php/Mobile_Retrieve_Form_for_Data_Capture to cover sharing data in other information models.

Dunmail commented 1 year ago

QEDm draft: https://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_QEDm.pdf

Dunmail commented 1 year ago

QEDm-compatibility looks reasonable - review in more detail.

Also consider MHD, PDQm for future development.

clarotech commented 1 year ago

Having looked more closely at QEDm then I think the UK-Core-Access can probably support it (for the resources that are in the scope of UK-Core-Access).

QEDm by itself will not be sufficient by itself however, although not explicit it makes assumptions on the profiles that are used for the resources (think US Core !). These do not equally apply to UK Core, so additional searches will be required.