If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

IRIS Interoperability formerly known as Ensemble comes with many built in adapters. It does not have a service or adapter to receive mail. I have written email service to receive mail messages via SMTP which can be passed to email operation.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
Reviews by other members of the community are marked by * in the last column.

1. Fhir-client-java

This is a simple fhir client in java to practice with fhir resources and CRUD requests to a fhir server.

Note that for the most part auto-completion is activated.

GitHub

1. Fhir-client-python

This is a simple fhir client in python to practice with fhir resources and CRUD requests to a fhir server.

Note that for the most part auto-completion is activated, that's the main reason to use fhir.resources.

GitHub

Motivation

This project was thought of when I was thinking of how to let Python code deal naturally with the scalable storage and efficient retrieving mechanism given by IRIS globals, through Embedded Python.

My initial idea was to create a kind of Python dictionary implementation using globals, but soon I realized that I should deal with object abstraction first.

So, I started creating some Python classes that could wrap Python objects, storing and retrieving their data in globals, i.e., serializing and deserializing Python objects in IRIS globals.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.
The rating reflects the experience of the reviewer with the status found at the time of review.
It is kind of a snapshot and might have changed meanwhile.
So if you did a major change and expect a changed review just let me know.
Reviews by other members of the community are marked by * in the last column

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package. The rating reflects the experience of the reviewer with the status found at the time of review. It is kind of a snapshot and might have changed meanwhile.
New with this edition:
Reviews by other members of the community are marked by * in the last column.

It is becoming more and more common to see beautiful badges in the README.MD file with useful information about the current project in the repositories of GitHub, GitLab and others.
For instance:

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov suggested publishing my monthly summary of my reviews here in DC.
It reflects my experience with the status I found at the time of my review.

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov suggested publishing my monthly summary of my reviews here in DC.
It reflects my experience with the status I found at the time of my review.

I work as an Integration Engineer for United States Department of Veterans Affairs (VA). I work on a Health Connect production which processes many RecordMap files. I do not fully understand RecordMaps and I wanted to develop an application for the Interoperability contest where I could learn more about working with RecordMaps. I browsed InterSystems documentation for inspiration on how to start. I was happy to find CSV Record Wizard.