openui5-fhir
Advanced tools
🔥
The OpenUI5-FHIR project connects the worlds of UI5 and FHIR®. Build beautiful and enterprise-ready web applications based on the FHIR® specification.
The world of healthcare is in change. Though being a highly regulated industry, more and more solutions move from on-premise into the cloud due to increasing costs. With this, there is a need to standardize communication between all players in the healthcare ecosystem (hospital, insurances, etc.). The FHIR® protocol, developed by HL7, has the goal to achieve that. To build UI5 applications based on a FHIR® server, there is a need to provide a UI5 library who enables FHIR® for UI5. The OpenUI5-FHIR project provides the sap.fhir UI5 library, which fills this gap. Currently, this library provides the UI5 FHIR Model which handles the communication with a FHIR® server by a central instance, like the ODataModel does it for OData services. The UI5 FHIR Model enables teams to implement fast and full scope UI5 applications based on a FHIR® server. In future, the OpenUI5-FHIR project might be enhanced by further FHIR® specific UI5 artefacts.
The complete documentation can be viewed in our Documentation.
OpenUI5 provides models out of the box, which can be fragmented in client or server-side models.
Inside the healthcare community there are a few specifications for clinical/medical data. FHIR® is one of them. Furthermore FHIR® provides a query language to access and modify the data.
To develop OpenUI5 applications based on FHIR® servers, there is a need to provide an easy to use way to bind the UI to an model which takes care of creating, reading, updating and deleting the corresponding data in the FHIR® server. This is the reason for the brand new UI5 FHIR Model, which is included in the OpenUI5-FHIR project.
The OpenUI5-FHIR project provides following UI5 artefacts:
The OpenUI5-FHIR project is completely integrated into the world of UI5. That means applications built with the OpenUI5-FHIR libary can be consumed in any modern browser.
The underlaying FHIR® server has to full following requirements:
The OpenUI5-FHIR project is published at npm on package openui5-fhir, which includes all necessary files. Add following snippet to your project package.json and update the version of openui5-fhir to the desired version.
"dependencies": {
"openui5-fhir": "X.Y.Z"
}
There is already a sample app available, which illustrates the use of OpenUI5-FHIR. Check it out and have fun!
The list of current issues is available here
Do you've any questions? Don't hesitate to raise a new issue.
The idea of the OpenUI5-FHIR project is ab initio to be driven by the community of healthcare players and enthusiastic individuals.
Please read this document to read more about your options:
The following table displays the versions of OpenUI5-FHIR and the corresponding compatible OpenUI5 versions:
| OpenUI5-FHIR | OpenUI5 |
|---|---|
| 1.X.Y | > 1.58.0 |
2.0.1 (2020-10-15)
FAQs
The OpenUI5-FHIR Library enables UI5 to the FHIR world
The npm package openui5-fhir receives a total of 17 weekly downloads. As such, openui5-fhir popularity was classified as not popular.
We found that openui5-fhir demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.