Will look at them , but the resources (man power) to implement would be the main bottle neck. Remember there are 3 who contribute on a full time basics and they will be mentoring the students, who I hope will double our manpower resource pool in the future.
I have no issues either, but we should have better documentation. Along with that, we should also see which project it fits best with, and if it doesn’t fit at the moment, we need to think which project it fits with. Or else it won’t be maintained and won’t make much sense to put it under the banner.
While I am still not very enamored of Gitlab, there is no reason why repos for these (at least until they are salvaged, adapted, used, integrated, whatever) should not be on GitLab as cannon. That said, I think that the first item listed is one of those web app thingies that very much sound like something that should touch the toolkit. The second one seems to be something everyone needs (there any telehealth stuff in the toolkit?). The third also sounds like a web UI piece that the toolkit should at least look at.
Without documentation, it is really hard to review. Some screenshots of each would help evaluate too.
Agree with @aethelwulffe here. None of these were developed specifically for integration with OpenEMR or LibreHealth EHR. All of them have the potential of integration with our “stuff” but mostly presented as material for ideas and salvage.
The Volunteer Portal is entirely stand alone. It needs to be backed off of it’s intended use, but is a good example of a Responsive website using React and PHP/Laravel
The WebRTC is just a block of stand alone code. It could be integrated into anything.
MEDIC was written (originally) to import/export to OpenEMR, but I have used it for standalone Health Data as well as just creating an data collection tool for field use unrelated to health care. It runs on a thumb drive comfortably.