I think there are still some details to be worked out with the MFE work regarding how things are loaded, etc., but in principle there’s no reason that the MFE work stops us from launching SoF apps. It’s just a matter of ensuring that there are appropriate extension slots in the patient chart or elsewhere in the application.
I love the idea of support SoF in OpenMRS and if someone has the time and inclination, it shouldn’t be a huge lift to get the GSoC project into a working state. I know @sidvaish97 has expressed interest in continuing to work on it, but he’s still in school. Basically, if there’s some momentum and someone can commit a couple of months of developer time to it, there’s no reason we shouldn’t be able to get SoF fully working in OpenMRS.
CDS Hooks is also a bit orthogonal to the work to support CDS being done in the analytics engine. With the analytics engine, we want to leverage it’s streaming capabilities to enable real-time calculation of data that can be used for CDS. With CDS Hooks, we’d be sending a request to an external CDS system that does the calculation. Of course, one way we could get CDS integration with the analytics engine is to make the analytics engine one of those external systems .
CDS Hooks is definitely on the list of things I’d like to see supported in OpenMRS. We do need to have some discussions around how we properly trigger CDS Hooks and what infrastructure we need in place for that. This might be an appropriate topic for a design forum at some point?