My team uses GitHub Actions 18 in total jobs across about 12 workflows. When we get multiple pull requests we end up driving contention on the workflows and resources we use. I ran across concurrency control for the workflows. To take advantage of concurrency control add this snippet to the bottom of your pull request workflow: When you stack the commits you end up with this warning, and the prior job is stopped:
Tracing the IBM FHIR Server file access on MacOSX
Thie attached GIST is a package of Kubernetes yaml files and Java code to test locally with Docker/Kubernetes with the IBM FHIR Server. You’ll want to kubectl apply -f <filename> for each of the files. Then apply the fhir-server-config-snippet.json to your fhir-server-config.json And run kubectl config use-context docker-desktopkubectl -n fhir-cicd-ns port-forward kafka-0 9092 Thanks to https://github.com/d1egoaz/minikube-kafka-cluster for the inspiration.
HL7 FHIR® Da Vinci Health Record Exchange (HREX) is an FHIR Implementation Guide at version 0.2.0 – STU R1 – 2nd ballot. The HREX Implementation Guide is a foundational guide for all of the Da Vinci guides which support US payer, provider, member and HIPAA covered entity data exchange. The guide defines “FHIR profiles, operations” and depends on HL7 FHIR® US Core Implementation Guide STU3 Release 3.1.0. In an issue, I implemented this profile and operation.
If you want to check your fillfactor settings, you can can check the `pg_class` admin table to see your settings using this article.
I went through a Knowledge Transfer to a teammate who is implementing GitHub Actions and workflows in their repository. My team has been working with GitHub actions since they became available to developers. You can see my team’s workflows at https://github.com/IBM/FHIR/tree/main/.github/workflows and our automation scripts at https://github.com/IBM/FHIR/tree/main/build Here are my tips: Pushing Changes to GH Pages If you need to push changes back to GitHub, I recommend you checkout your code to a working sub folder and build in that subfolder, and copy the artifacts back to another subfolder and then push those changes (after a git add and commit…
The team I am on just release an OpenShift operator to install and setup the IBM FHIR Server. The CASE is published to GitHub and the container images (built on the OpenSource version 4.9.1) are in the IBM Entitled Registry. If you have any questions about the release, I’m happy to answer. IBM FHIR Server is capable of processing, validating, and storing healthcare data in an industry-standard format that can be used for running search and other reporting capabilities. Built for the enterprise and offering cloud portability, it’s an integral component of a data integration pipeline. IBM FHIR Server WEBSITE
Here are some short cut APIs for Open Liberty API and IBM FHIR Server’s batch feature.
My lab is now live and available on the IBM Digital Developer Conference. In my session, developers integrate a healthcare data application using IBM FHIR Server with OpenShift serverless, to create and respond to actual healthcare scenarios. The lab materials Link to the lab material https://prb112.github.io/healthcare-serverless/ and you need to sign up for the lab using the following instructions. Signing up for the Lab To get access to the lab environment, follow the following instructions:1. Get added to the IBM Cloud account “DEGCLOUD” using the following app: – https://account-invite.mybluemix.net/ – Enter Lab key: welcome – Enter IBM ID: the email…