Stream: OpenHIE
Topic: IGs
Carl Leitner (Jan 27 2021 at 16:42):
continuing thread with @Jose Costa Teixeira and @Ally Shaban on IGs here. We will include IG documentation of the resources and workflow on the HAPI to ElasticSearch adapter in the general case reporting IG. see https://github.com/intrahealth/fhir2es
Carl Leitner (Jan 27 2021 at 16:44):
@Ryan Crichton @Daniel Futerman @Richard Stanley it would be good to align IGs to Instant OpenHIE packages as well. Is there an easy place to see what those packages currently are (core, health worker, etc.)? I don't know if we want a separate 'data analytics' package and IG that builds of core and include the HAPI, ES connector. I know that HAPI+ES is already in HW, so ideally that would depend on a 'data analytics' package. we could then have the case report IG depend on data analytics
Carl Leitner (Jan 27 2021 at 16:45):
thinking aloud, so any feedback would be appreciated here
Richard Stanley (Jan 27 2021 at 17:15):
It was recently discussed. iHRIS (+mHero) and OpenCR all use ES/Kibana. So, there will be a separate analytics package. But, to implement this safely requires adding a dependency tree for packages. That's being worked on here: https://github.com/openhie/instant/pull/63
Richard Stanley (Jan 27 2021 at 17:18):
All packages are at the root of the repo: https://github.com/openhie/instant But, going forward I wonder if we'll need to be more explicit in the directory structure about which are infrastructure versus workflow packages.
@Ryan Crichton @Daniel Futerman for their thoughts.
Ryan Crichton (Jan 28 2021 at 06:57):
I think separate packages for anything common makes sense. The dependency ordering stuff is still new but we are almost done with it so packages depending on packages will be supported properly.
@Richard Stanley we could definitely split packages out into folders that make sense. Also, not all packages need to be in this single repository. We can include packages by mounting them into the instant OpenHIE docker image. This means that we could have groups of packages that exist outside of the main repository. Is it worth discussing what packages should actually be in the main repo or should be just put stuff there until it becomes an issue?
Richard Stanley (Jan 28 2021 at 14:46):
@Ryan Crichton I hadn't thought of that as an option, but it's very interesting. So, for example, the main iHRIS repo would have a /instant folder with the same content like instant/docker and instant/k8s? It makes sense. I'm happy to help prototype it.
Richard Stanley (Jan 28 2021 at 14:54):
On common dependencies, postgres and mysql would also be useful.
Ryan Crichton (Jan 28 2021 at 14:59):
@Richard Stanley ya, that's definitely possible. It might be worth keeping key packages in the repo for easy of use. We could even use Instant OpenHIE for private project specific packages in this way. Or, for example, if their was a particular group of packages that we want to keep separate as they work together.
Richard Stanley (Jan 28 2021 at 15:41):
That's great, thanks.
Carl Leitner (Jan 31 2021 at 17:18):
hey all, updates the case-reporting IG to reflect the L1-L4 levels of knowledge representation and started pulling together a google doc qith some questions/suggestions/open-issues to resolve. would appreciate any feedback.
- https://docs.google.com/document/d/1aumqL0vinwAHyTc9GPi4jUEqdadYjtkDdICikEQcCxE/edit
- https://openhie.github.io/case-reporting/
Last updated: Apr 12 2022 at 19:14 UTC
