Nice! Is there any video recording, Dan?
- Log in to post comments
Nice! Is there any video recording, Dan?
Thanks, Renato!
You introduced the graph! Nice work!
Update: iris4health-fhir-analytics uses FHIR REST API too.
And ZPM supports dashboards and pivots resources now.
Oh, yes sure! Public ZPM registry pm.community.intersystme.com is open for everything which is approved in OEX.
Just make sure you have valid module.xml in the root of the repo and turn on the checkbox "Package Manager" in the Open Exchange app - and it will be published as module to the public ZPM registry.
We analyzed the projects submitted for the contest and here is the matrix, which project gets what bonus:
|
Name |
FHIR Server REST API usage |
FHIR SQL Schema usage |
Healthcare standards transformations |
Docker container usage |
|
x |
x |
x |
||
| x |
x |
x |
x |
|
|
x |
x |
|||
|
x |
x |
|||
| x |
x |
Hi Jose!
Thank you much for the feedback! What I also like about your app that you used ZPM and managed to use the DeepSeeWeb community project to visualize FHIR data.
Nicely done!
Hi Anssi! Interesting case! It'd be great to publish the example of code in Github and Open Exchange!
Thank you, Tim! We are actively improving Open Exchange, and your feedback is very important!
Looks like a great idea, please go ahead, @Rehman Masood!
Wow! So fast! Thank you, Yuri!
Another idea for the contest: use your iPhone's health app data to transform into FHIR data and submit to the FHIR server. See the details
Here is the new topic for the FHIR contest:
CDA to FHIR data transformation
iPhone can export health data to CDA, see the details. Transform this data into FHIR format using IRIS for Health and submit to the FHIR server.
Here is an example of how you can transform CDA to FHIR data using IRIS for HEalth. Tagging @Guillaume Rongier for more details.
The main announcement is updated too.
Yuri!
What a beautiful idea! Thank you!
If these boxes could be clickable and point to documentation/tag would be a nice features table!
Thanks, Robert! Will add a few corrections:
COS stands for Caché ObjectScript. Now the name of language is InterSystems ObjectScript, so Obs is OK
There is no BASIC anymore in IRIS (I think).
Globals! This is a must.
A current set of proposed topics could be found here.
Developers!
You are welcome to use iris-fhir-template to build your InterSystems IRIS for Health solutions for the contest.
The template uses the preview release 2020.3 of InterSystems IRIS for Health
A very helpful repository to generate synthetic FHIR compatible data shared by @Phillip Booth
E.g. to generate data for 5 patients in an /output subfolder of a current folder call:
docker run --rm -v $PWD/output:/output --name synthea-docker intersystemsdc/irisdemo-base-synthea:version-1.3.4 -p 5Which you can load then into IRIS for Health with:
zw ##class(HS.FHIRServer.Tools.DataLoader).SubmitResourceFiles("path/output", "FHIRNamespace", "/restapi/endpoint/fhir/r4")Hi All!
Update the article to introduce iris.script approach - dockerfile is smaller, objectscirpt is clearer.
You probably right for a majority of tasks. But how do you manage with AI tasks which NEED to manage thousands of features of entities? And features are properties/fields from data storage perspective.
Anyway, I'm really curious how do you deal with AI/ML tasks in IRIS or Caché.
Thanks, Ed!
Could you make a PR?
Could you provide an example? and what do you mean by origin?
Hi Lucas!
With
zpm "install objectscript-errors-analytics"
you can also see examine these errors in the IRIS Analytics dashboard. Check for more.
Our community works) And collaboration ;) And the curiosity too )
And this was a perfect case to test the new ZPM feature ;)
Bravo, Robert!!!
A lot of developers who never saw globals now can see it and I see how they are saying you "Thank you!"
Yes!
This is better! But still 2 lines per error. Is it possible to have one per error?
Turned out we'll not fix this soon. module.xml stats RULES for gathering the package and for a clean up too.
So if you delete the package with rcc.PCG in module.xml will delete literally the package rcc from the system with all the child classes.
This is how it works now.
So for now please describe the exact feature package in the module.xml.
I have 75 rows per error in this table.
Is it possible to have one line per error - like a summary table ERRORS_SUMMARY, link to this details table? And the summary will have only:
reference, date,type(SYNTAX, UNDEFINED,etc),line of code,$ZV
Yes, thank you Robert!
Did the same but with
catch e {
Do e.Log()
}Which is more "stylish" if you may.
Example of the usage in a freshly baked objectscript-errors package.