Re: [Health-dev] Working on the documentation

[Luis Falcon]

Dear Gerald

On Wed, 9 Aug 2023 13:05:46 +0200
Gerald Wiese <wiese@gnuhealth.org> wrote:

> Dear Luis,
> 
> thanks for your replies.
> 
> Could you imagine to work on this one please? That would give a
> better base to students working on the rest and ensuring consistency.
> 
> >> GNU Health HMIS functionality:
> >>
> >> Rename to Overview, add graphics and explanation + distinction of
> >> HMIS, HIS, LIS, LIMS etc. with more details. Ensure the acronyms
> >> are used consistently with the rest of the documentation after
> >> defining them more precisely.  
> 

We will create a front cover / landing page with and introduction and
link to the main components.

We can also work in protocols for the charts / graphics formats,
sizes, etc..

Right now I'm quite busy with MyGNUHealth PHR 2.0 (due this September)
and making sure that the current tasks for the HMIS will be ready in
4.4 (due October)

> About FHIR REST: I appreciate the work the both of you put on it. 
> Nevertheless I don't see it as usable at the moment and I think we 
> should make transparent that it's still in development and actually 
> stagnated.
> 
Of course.
https://pypi.org/project/gnuhealth-fhir-server/

And we have the Beta devel status.

> If nobody fixes a version conflict within two years it seems not
> maintained.
> 
I've been working on this in the last weeks / months.

https://hg.savannah.gnu.org/hgweb/health-fhir-server/

It's just that we need to address the requests with the priority
required. There hundreds/thousands of GNU Health installations
around the world. Look at the number of requests for FHIR on them... is
quite marginal,and that is because there is not still a wide adoption
of it on the market. That said, we like the standard and we'll keep
working on the FHIR support for GH.

In the meantime, we feel quite comfortable with the way we can interact
/ interoperate using open standards with other systems.

> REST API demands not only read but also write functionality and 
> scriptable HTTP access - what I found was cookie based logins meant
> for browser access.
> 
> Not sure which other standards of those are fulfilled?
> https://hl7.org/fhir/
> 
> The current state doesn't even call it beta but gives the impression 
> that you could just install and run it like this (using Python2 by
> the way).

I disagree:

The GH FHIR package clearly states beta development status.

https://pypi.org/project/gnuhealth-fhir-server/


Again, the read functionality for FHIR many resources have been working
well, and now there is an issue with the new Werkzeug libraries that
needs to be addressed.

We'll create the proper task for it and make it beautiful. I'll review
the current status and chances are I will refactor the FHIR server to
eliminate dependencies that are problematic.

We'll talk about it at GHCon.

Enjoy the day
Luis