Stream: implementers
Topic: Tooling
Grahame Grieve (Sep 17 2016 at 14:11):
I am thinking of starting a new project after the WGM: an electron based editor for resources. I'll be doing some conformance resources - e.g. ValueSet, CodeSystem, ConceptMap, Questionnaire (not StructureDefinition). Would anyone else be interested in contributing? (where electron = http://electron.atom.io/)
Lloyd McKenzie (Sep 17 2016 at 14:40):
Editor for resources or for profiles?
Grahame Grieve (Sep 17 2016 at 14:43):
resources
Lloyd McKenzie (Sep 17 2016 at 14:45):
As an alternative to the spreadsheets because we're now looking at opening up resource creation plus doing logical models?
Grahame Grieve (Sep 17 2016 at 14:45):
nothing to do with spreadsheets or logical models. That's for Forge. This is for editing other kinds of resoruces
Lloyd McKenzie (Sep 17 2016 at 15:04):
Is Forge going to do logical models?
Lloyd McKenzie (Sep 17 2016 at 15:04):
But would this be an alternative to using spreadsheets for core resources too?
Grahame Grieve (Sep 17 2016 at 15:25):
Forge already does logical models
Lloyd McKenzie (Sep 17 2016 at 15:27):
Ok. And would this be an alternative to spreadsheets for core resources?
Patrick Werner (Sep 19 2016 at 08:38):
Hi @Grahame Grieve we are currently playing around with rendering FHIR Questionaires for mobile devices. A resource editor would has been one of our next steps. Would you use Electron with Angular2? We are currently switching from JQuery/JS to Angular2/TypeScript in our projects.
Grahame Grieve (Sep 19 2016 at 09:52):
I hadn't got that far yet. My own question is whether it's possible to write the code in such a way that the core editors could be used outside electron. Does the Angular question relate to that? btw, a Questionnaire editor would be in the works
Patrick Werner (Sep 19 2016 at 09:54):
It should be possible to write the Code in a way to reuse most of the angular2 code. This leads to a shared codebase for: Electron, Angular2 Webapp, Ionic2 Hybrid apps.
Patrick Werner (Sep 19 2016 at 09:55):
i'm not the angular2 expert, i'll discuss this with my colleagues..
Ewout Kramer (Sep 19 2016 at 12:04):
We are looking at Microsoft's Monaco editor (https://github.com/Microsoft/monaco-editor), which is not only cross-platform and TypeScript based, it is actually the code behing Microsoft Code, and it looks pretty extensible. Might be a better base to start off writing an editor than doing everything from scratch.
Grahame Grieve (Sep 19 2016 at 12:05):
what does it run on?
Grahame Grieve (Sep 19 2016 at 12:06):
but we're not talking about code editors
Ewout Kramer (Sep 19 2016 at 12:11):
It supports IE 9/10/11, Edge, Chrome, Firefox, Safari and Opera.
Ewout Kramer (Sep 19 2016 at 12:12):
Well VS Code is really a competitor to Atom and the like. And I think it supports configurable "intellisense", so we can help the author writing xml or json by suggesting valueset values etc.
Grahame Grieve (Sep 19 2016 at 12:39):
well, there's certainly a place for a intellisense editor - though this is more in the sense of notepad++ alternative
Brian Postlethwaite (Sep 19 2016 at 13:43):
Correct on that one.
Brian Postlethwaite (Sep 19 2016 at 13:44):
I'm investigating doing that for the fluentpath
Nate Walker (Sep 19 2016 at 21:11):
@Patrick Werner I would also like to do FHIR consumption with Angular2 - we might be doing questionnaires and also allowing a patient to review their own data, so could have a fair bit of different interactions going on. Can you let me know how you guys get on? :)
David Taylor (Sep 20 2016 at 19:31):
Hi, I'm implementing a project that integrates with RedCap API for questionnaires - has anyone else done that to your knowledge? They have support for CDISC ODM but I haven't found any other references to FHIR support.
Patrick Werner (Sep 20 2016 at 20:12):
haven't done anything with redcap, but the medical data models project of the Münster University has a collection of many Questionaires: https://medical-data-models.org/
This collection started as a CDISC ODM only and is now able to export to FHIR Questionnaire Ressources.
Michael Lawley (Sep 20 2016 at 20:26):
@David Taylor we're also have an interest in the relationship between RedCap & FHIR and are currently looking in to modifying RedCap to support talking to FHIR terminology services as an alternative to the NCBO integration. Can you tell us more about what you're doing as there could be useful overlap?
David Taylor (Sep 21 2016 at 00:50):
At this point the intent is to work with standard RedHat services as we are using our application as an integration service. We are handling RedCap Surveys by Reference and using mappings to take the responses and store as QuestionnaireResponses. Modification of RedCap isn't an option for us at this point.
Michael Lawley (Sep 21 2016 at 00:53):
ah, interesting. Are you using structure map to do the mapping?
David Taylor (Sep 21 2016 at 01:01):
I see it under STU3 - we are currently based on DSTU2. Haven't started that part yet so I'll have to look at it. For now I was just planning on mapping question xpaths with redcap field names. That way the responses can be stored referencing nested questions.
Brian Postlethwaite (Sep 23 2016 at 20:02):
I tested one of the export of the Munster Univerity questionnaires with our renderer and it looked ok.
Florian Seidel (Oct 24 2019 at 08:52):
Hi, as we have REDCap as a topic here. Has anyone tried to get the Clinical Data Pull functionality to work with a headless server like Vonk?
Michael Lawley (Oct 24 2019 at 11:53):
@Alejandro Metke ?
Alejandro Metke (Oct 24 2019 at 23:18):
No, all the work we've done is going from REDCap to FHIR, not the other way around.
Florian Seidel (Oct 31 2019 at 08:03):
I'm assuming you are talking about FHIRCap? Is there any plans to opensource the project? (Cause I've found an empty Github Repo) That would be pretty exciting!!!
Esteban Hebel (Nov 16 2020 at 21:53):
Alejandro Metke said:
No, all the work we've done is going from REDCap to FHIR, not the other way around.
Are there any news on this front?
Last updated: Apr 12 2022 at 19:14 UTC
