G6PD - FHIR approach about fhircore HOT 10 CLOSED

I think what RIM rides on is not G6PD specific. Again, RIM may just end up being a collection of CQL Libraries that run on top of the more generalized FHIRCore feature that would support evaluating CQL Libraries

from fhircore.

A request, can you link this out to the existing issues that relate to it? Also some comments

1. I don’t think RIM is G6PD specific, this will definitely overlap w/work we plan to do for mADX on FHIR using Measure and MeasureReports. We can step back even further and recognize the general use-case of displaying metrics in app, this is common to almost all apps, and RIM is the tool that we can use to serve that general purpose.
2. ServiceRequest vs CarePlan resources is something we need to figure out, from previous discussion it sounded like we can get away with only using ServieRequests, @f-odhiambo how would we use CarePlans here? If we do use CarePlans, I think we’ll want PlanDefinitions to generate CarePlans from

from fhircore.

#32 is a prereq for the IPE

from fhircore.

Not exactly FHIR-related but general G6PD requirements. Looking at the fine print, I think there are requirements around authx, data encryption (that are guaranteed by current OpenSRP) which we may also want to consider supporting. We need to understand how critical those are as part of the project deliverables.

from fhircore.

from fhircore.

Tentative architecture

from fhircore.

This is out of date, Host Application is FHIR core and the RIM module is a set of FHIR resources that get loaded into FHIR Core

from fhircore.

yea, but I guess one of the features of the IPE module is to be callable from any host application (fhircore can be one such application).

The RIM module box has a comment about it not strictly being a module per se (but I guess we can emphasize that by removing the box altogether).

from fhircore.

Yep agree, IPE stays as a separate module, we'll have to determine the exact boundary as we get further into its details

from fhircore.

This issue is linked to #108 and also G6PD/Covax alignment being tracked here

from fhircore.