5 ways to utilize Camunda more efficiently in your microservice architecture
Use cases for workflow engines
When talking about workflow automation, companies and business people usually think about human task management and task lists. And that makes sense since workflow engines are a great tool for that. However, workflow automation is actually much more. Modern workflow engines are lightweight and can operate high volumes at low latency. This makes them applicable for every problem that requires a state machine, whether the main driver of the requirement at hand is business or IT. Other motivating factors for using workflow engines also include graphical visibility which is important in case of long-running workflows and them being persistent state machines that help with tasks of versioning process models, scheduling or operation control.
Continue reading “Microservices in Healthcare”
Edition: Real-world problems and solutions
For an intro we suggest to brush up on some reading from our part 1: READ HERE
Creating a puzzle
Tuning our thinking to the granularity of resources defined in FHIR wasn’t enough. Very soon we encountered our first challenge – making them work together. This is a very important notion in FHIR since the standard considers resource combination as an integral tool in representing healthcare use-cases.
Searching through extensive documentation we identified mechanisms in place providing this function:
Continue reading “# Hands on experience with interoperability | Redox to FHIR – Vicert follows through”
Vicert Takes on a Challenge
When a client asked for a Redox Data Chateau service adapter, a lot of new keywords were thrown my way.
We had to look into every detail of “Redox”, “FHIR format”, “Data Models”, “resources” and “Clinical Summary” concepts in order to quickly create a bigger picture where everything needed for our project made sense.
Continue reading “Developers Hands-On Experience with Interoperability: Redox to FHIR Vicert Takes on a Challenge”
In the healthcare space, there are companies that function as intermediaries that forward claims information from healthcare providers to insurance payers, also known as clearinghouses.
Likewise, if we want to exchange messages between two distributed software components, we need a mediator. This mediator is known as the message broker. It receives incoming messages from a sender and sends them to a receiver. This way the sender and receiver can be totally decoupled.
A message broker acts as an intermediary platform in communication between two applications.
Continue reading “What is a message broker? And how could it be leveraged more in Healthcare”
Continue reading “Getting started – Learn the basic React Native”
If you’ve ever worked on an android project you must have had the chance to fight the libraries version. Android tried to split the support libraries into smaller pieces, and we got some modularisation, (com.android.support:cardview-v7, com.android.support:recyclerview-v7), but this approach has made things more complicated because of the versions. We are well aware of the mess with the backwards-compatibility-libraries v4, v7, v13, v8, v?.Android decided to make androidx to stop this version confusion so every support library like android.support.v7.recyclerview.extensions.AsyncDifferConfig is now androidx.recyclerview.widget.AsyncDifferConfig.
Continue reading “Migration to androidX”
FHIR (pronounced “Fire”) is a standard for interoperable exchange of healthcare data developed under the HL7 organization. FHIR includes all features present in HL7 V2, HL7 V3, and CDA.
For more information on FHIR and benefits for providers, payers, clinicians, etc. – check out the latest white paper!
Continue reading “How to use a HAPI-FHIR library and SMART Health IT #FirstEncounter”