Stream: implementers
Topic: atom on fhir
Eric Haas (Dec 20 2016 at 01:14):
has anybody created any fhir tools on atom like grahame's notepad++ stuff?
Abbie Watson (Dec 20 2016 at 02:42):
Not yet, but I know how to. I created the meteor-api package back in the day that had the Meteor API (with the Blaze/Backbone UI layer), so I know how to make code-snippets, syntax highlighting, context menus, launch external commands, etc. What kind of utilities are you thinking of?
Eric Haas (Dec 20 2016 at 04:16):
Oh the usual, validate instances, convert between json and xml, narrative generator with built in support for the markdown elements....
James Agnew (Dec 20 2016 at 14:34):
Took me a few re-reads to realise you were talking about Atom the text editor and not Atom the DSTU1 bundle format... and I use Atom the text editor every day. Sheesh. :)
This would be sweet if someone had the capacity, that's for sure.
Grahame Grieve (Dec 20 2016 at 20:12):
my experience with notepad++ tells me that it's a lot of work; you need an especially strong meta layer in the object implementation you're using
Abbie Watson (Dec 20 2016 at 21:06):
I'm not sure if that meta layer entirely exists yet; but the good news is that Atom is built on Chrome and is isomorphic to the rest of the Meteor stack. Javascript on the server, client, database, testing, and... development environment.
Unfortunately, Atom has traditionally been written in Coffeescript, and Meteor has already moved to ES6 and React, which has made sharing libraries between the two difficult. But it appears that there have been some successful attempts to write Atom packages in ES6. If that becomes standard, it will become a lot easier to import/export modules; and we should be able to merge Meteor on FHIR and Atom into a complete FHIR based IDE.
Right now, the best way I can think of doing schema validations would be to use one of the Atom DDP plugins to query the Meteor on FHIR interface engine; and have Meteor on FHIR do the validation.
Converting between JSON and XML isn't fundamentally difficult; but how useful is the XML support, really? An Atom based IDE would necessarily be isomorphic across the V8 engine, meaning Atom/Chrome/Mongo, meaning a JSON infrastructure.
What do you mean by narrative generator?
Patrick Werner (Dec 22 2016 at 12:34):
XML suppor is fundamental. As many people (including myself) prefer to read/write XML instad of json.
Abbie Watson (Dec 27 2016 at 05:06):
Well.... how about this... I will be happy to create some Atom plugins for FHIR, but am only going to commit to doing the JSON portion; and will accept pull-requests from anybody who wants to do the XML portion. ;)
Last updated: Apr 12 2022 at 19:14 UTC
