Stream: javascript
Topic: Language User Group
Joshua Kelly (Jun 10 2021 at 20:54):
Hello all, great to virtually meet many of you at DevDays this week. There seems to be growing interest in JS/TS tooling (myself included), from implementers who are new to FHIR but experienced in other ways. Especially with the TypeScript definitions work @Brian Kaney released into DefinitelyTyped, I think there's a big opportunity for us to improve what's offered to developers in this space
Being new, I'm not sure what the etiquette is here, but I'd like to propose the creation of a JS Language User Group. I'm not sure if the FHIR community has a format for such things, but I think there's a need to:
- Co-ordinating JS resources for the "new to FHIR" audience
- Collaborating on JS/TS infrastructure we need as a community
- Generally build bridges between JS users in FHIR
So, who's interested? Is there a group already? If not, is there a format for them generally or if it's a choose your own adventure I could propose some parameters.
Ilya Beda (Jun 11 2021 at 19:14):
Hi @Joshua Kelly
Let's just use this stream in the zulip. All coordination around FHIR happens here in chat.fhir.org.
I don't think we need something external.
Joshua Kelly (Jun 11 2021 at 19:25):
Hello @Ilya Beda , thanks for replying and great to meet you this week.
Yes I agree. To be clear, I am not proposing any communication technology change. I am hoping to collaborate on JS/TS FHIR tool projects and to talk more about how we can improve the implementer experience together.
Some communities have working groups that are formal co-ordination points for "language/user group" activity - if that's what this stream already is, I'm happy to say just be saying hello and continuing the conversation started at DevDays :)
Ilya Beda (Jun 11 2021 at 20:51):
Yes, the stream is the kind of working group you mentioned. We can continue our conversation here.
Ilya Beda (Jun 11 2021 at 21:00):
As the following step, we can review all existing JavaScript/TypeScript
compare it with this list https://confluence.hl7.org/display/FHIR/Open+Source+Implementations and update it.
Also, we need to check what critical tools are missing or become obsolete.
Abbie Watson (Jun 14 2021 at 17:29):
Ilya Beda said:
As the following step, we can review all existing JavaScript/TypeScript
compare it with this list https://confluence.hl7.org/display/FHIR/Open+Source+Implementations and update it.
Also, we need to check what critical tools are missing or become obsolete.
Hello,
So.... I've been tracking JavaScript/TypeScript FHIR libraries for 4 or 5 years now, and have some of the info that you're looking for. Just updated the Open Source Implementations page with links for the NodeOnFHIR project.
https://github.com/symptomatic/node-on-fhir
You may find the package.json file to be of particular interest.
https://github.com/symptomatic/node-on-fhir/blob/development/package.json
Brian Kaney (Jun 15 2021 at 02:25):
Hi @Abbie Watson - FYI we just pushed out DT types for fhir - @types/fhir with r2, r3, and r4 (from the MS codegen project). I think Ahryman40k types library is only r4.
Abbie Watson (Jun 15 2021 at 02:37):
Brian Kaney said:
Cool. The Meteor build pipeline supports TypeScript, so we should be able to add a reference and pull the type definitions in without much difficulty. It will be another few years yet before the core boilerplate migrates away from ECMAScript, but package authors should be able to have a relatively TypeScript centric experience as soon as those definitions are pulled in. Either through NPM or Atmosphere.
Last updated: Apr 12 2022 at 19:14 UTC
