Stream: javascript
Topic: FHIR foundation project
nicola (RIO/SS) (Oct 10 2018 at 20:17):
As we discussed with @Sean McIlvenna there are many javascript/FHIR projects around and may be we can create umbrella project and community around it to share ideas and code. Let's list active projects in this thread.
nicola (RIO/SS) (Oct 10 2018 at 20:19):
- js client - https://github.com/FHIR/fhir.js
- fresh fhirpath implementation - https://github.com/lhncbc/fhirpath.js
more?
Sean McIlvenna (Oct 10 2018 at 20:23):
- fhir.js (serialization, validation, basic FHIRPath) - https://github.com/lantanagroup/fhir.js
nicola (RIO/SS) (Oct 10 2018 at 20:24):
The idea is to try to find commonalities, great features and move FHIR javascript eco-system one level up. We identified following modules to think about:
- compact FHIR representation of FHIR StructureDefinitions, Profiles and other metadata (as foundation for other modules) and can be distributed using npm
- FHIR validation (potentially based on official JSON-Schema )
- xml<->json converter
- FHIR client
- fhirpath
nicola (RIO/SS) (Oct 10 2018 at 20:25):
- https://github.com/niquola/2way - not directly related to FHIR but very useful for UI two way transformation engine
nicola (RIO/SS) (Oct 10 2018 at 20:27):
- https://github.com/HealthSamurai/jute-example - HL7v2 parser and to FHIR transformation code
Sean McIlvenna (Oct 10 2018 at 20:47):
- web-pack'd for use in browser-only applications
- ability to hook into key serialization and validation events to add customizations
- multi-version support (STU3, R4, R5?)
nicola (RIO/SS) (Oct 10 2018 at 20:59):
Let's start from this design document - https://docs.google.com/document/d/1pSstfLRF4x-i4TTqzgfRRTEjKUprcvy45rNaJvMMDpY/edit?usp=sharing to define shape of discussion
Sean McIlvenna (Oct 10 2018 at 22:07):
A good start to the document
Nathan Hall (Oct 18 2018 at 15:07):
A little wait to the project but i have been using https://github.com/Asymmetrik/node-fhir-server-core/ which is base on us-core implementation
Nathan Hall (Oct 18 2018 at 15:08):
i am happy to help / contribute if we are interested in standardizing a fhir server in node
Abbie Watson (Oct 18 2018 at 16:45):
There's also vermonster/fhir-kit-create-react on Express.js
https://github.com/Vermonster/fhir-kit-client
And of course the Clinical Meteor project using Meteor.js
https://github.com/clinical-meteor
I think it's sort of premature to assume an angular/webpack infrastructure. Even within Node there's a pretty huge range of implementations, depending if a team is using Fibers, Promises, or ES6 await/async.
idk... this javascript stream and FHIR foundation project very much has the problem of C/C++/C#. We're ostensibly using the same language; but we're very much using different build pipelines, tooling kits, data bus architectures, packaging systems, user interfaces, etc.
Apologies for throwing cold water on this; but with all the fhir.js PR requests going directly into the javascript stream and the default presumptions of angular/webpack/etc, we've been questioning whether it makes sense to open up a #node or #ecmascript stream
nicola (RIO/SS) (Oct 18 2018 at 19:12):
I will turn it of
nicola (RIO/SS) (Oct 18 2018 at 19:13):
Let's have a first meeting next week to discuss future of FHIR and js :)
nicola (RIO/SS) (Oct 18 2018 at 19:13):
pretty sure we can find something to share
Mikhail Poluboyarinov (Oct 19 2018 at 13:39):
Let's plan our next FHIR.js meeting. Please vote for your preferred time on Doodle. https://doodle.com/poll/vbhrhhkbt9wyyz9x
Stefan Lang (Oct 19 2018 at 14:03):
Just found this 9 days old thread - very interesting + interested!
I discussed the same with @Patrick Werner recently and we intended to have a BoF at the Amsterdam DevDays on possible improvements regarding the JS implementation.
Patrick Werner (Oct 19 2018 at 14:04):
@Daniel Zsebedits is the JS expert of our Institute, he will also be in Amsterdam
nicola (RIO/SS) (Oct 19 2018 at 15:00):
Ok let's book the room in Amsterdam! @Ewout Kramer ?
Stefan Lang (Oct 19 2018 at 15:28):
Afaik there is also an orphaned Node based implementation @Alexander Zautke might know more about
Alexander Zautke (Oct 20 2018 at 14:40):
That implementation is officially declared dead. It will not see the light of day again. Sorry, out of my control :/
Vladimir Ignatov (Oct 23 2018 at 14:03):
Perhaps this is the place to add one new project - https://github.com/smart-on-fhir/client-node/. It is more of a SMART client though, meaning that it handles the auth part for you but does not offer specific fhir API (you build your fhir requests yourself)
nicola (RIO/SS) (Nov 07 2018 at 22:23):
Hey guys, i'm booking room for us on DevDays! Will post details here.
nicola (RIO/SS) (Nov 13 2018 at 14:01):
We have a room tomorrow in Amsterdam at 11:55!
Grahame Grieve (Nov 14 2018 at 02:41):
I'll hope to be free so I can be there
nicola (RIO/SS) (Nov 14 2018 at 09:20):
Chalet 2 at 11:55 - 12:35
nicola (RIO/SS) (Nov 14 2018 at 09:43):
https://gist.github.com/niquola/cdacfafad2d82bd64a9304f53b912b2f - here i put some summary for meeting
Oliver Egger (Nov 14 2018 at 10:47):
@nicola (RIO/SS) sorry i'm not in amsterdam to join you :disappointed: i have experimented with incorporating fhir.js and fhirpath.js in angular/typescript if you want to add this to your gist, see https://github.com/ahdis/ng-fhirjs and used https://github.com/artifacthealth/fhir-dts-generator to generate R3 and R4 typescript interfaces
Last updated: Apr 12 2022 at 19:14 UTC
