[XL] Pipeline lenses: transform lenses to fsh and send encoded to FHIR

[gmej]

Lenses build/push will be automated. The new process deprecates this lens-selector service.

[gmej]

@joofio do you have any github workflow that executes sushi that we can reuse for this task?

[gmej]

I would use this repo owned by @joofio as an example of a fsh/sushi project to use the same structure: https://github.com/joofio/test-epi-composition

[gmej]

This task is related and developel along with #16

[joofio]

why sushi? i dont quite understand this issue?

[gmej]

The idea is to develop lenses with a .fsh file and a .js file (the lens itself). a workflow would base64 the lens in the fsh encode and then build the JSON with sushi. Maybe we misunderstood the process of transforming sushi to HAPI FHIR

[joofio]

why the overhead of sushi and not plain json?

[gmej]

we thought that potential lens developers (and us) might prefer writing fsh than json. That's the reason, but we are open for suggestions. How would you proceed with this?

[joofio]

no. fsh is niche. I would go with json which everybody knows

[aalonsolopez]

we have now the first version of our new CLI tool (which can be implemented on Actions) to bundle normal lenses to a FHIR compliant JSON file. it also have a command to upload the file to a given domain including a FHIR IPS server

https://www.npmjs.com/package/@gravitate-health/fhir-lens-bundler

CC/ @joofio @jkiddo

[joofio]

what this mean in fact? what are "normal lenses"? what does the " it also have a command to upload the file to a given domain including a FHIR IPS server" mean?

[aalonsolopez]

Let me show you a demo video here, I'll see if I can

[aalonsolopez]

A normal lens is a Lens in its source code version, e.g. JavaScript

[joofio]

done