Jul 04

Among other activities, I design and implement RESTful APIs. I use the VSCode, the Swagger Editor, the Swagger UI and the Swagger Codegen, or a combination, as needed. I also use Docker for containerisation as much as possible because I dislike burdening my host machine with all manner of software and the resulting need to manage versions, version conflicts, etc..

To help myself, and others, I documented the steps necessary to create a Docker Image to host the Swagger Editor so that Docker container using that Image can be spun up as needed in seconds and destroyed as quickly when no longer required. The intent of the document is to provide a set of steps that a reader can use to create a self-contained Docker container for API-First development using latest Swagger Editor (3.x) and OpenAPI (2 or 3).

The Image is the basis for a container that will have the means to:

  • Run the Swagger Editor Server
  • Convert YAML specification documents to JSON and the vice versa

The container is based on the latest Docker node image with extras.

The container uses:

  • Swagger Editor Distributable (swagger-editor-dist)
  • swagger-codegen-cli/3.0.20 to support YAML to JSON conversion and generation of client and server stubs based on the OpenAPI Specification / Swagger file for supported languages. swagger-codegen-cli requires Java 8, which is installed during container setup.
  • nodemon server
  • http-server server

Please see  https://github.com/mwczapski/Swagger_Editor_3_Docker_Container for package artefacts.

May 05

The package named in this article provides detailed steps for creating a Docker Container that runs a private git server.

Scripts in the package facilitate creation of a Docker Image and a Docker Container with a private GIT Server. The image uses the most recent GIT distribution (2.26 at the time of this writing). The container can be used to provide docker-network-wide Git repository for small to medium size teams working on projects whose sources cannot or should not be stored in cloud-hosted Git repositories. Small to medium start-ups or small companies might be examples.

The image is based on bitnami/minideb:jessie image as at early May 2020.

Installing latest Git from sources, and pre-requisites for building Git from sources, blows the image up from about 51MB (bitnami/minideb:jessie) to about 778MB during the build process, and then shrinks it back to 238MB once the build is finished and build tools are removed.

The image is saved as the `gitserver:1.0.0` Docker Image and, if the user invokes the script with the correct argument, also uploaded to a remote docker repository, which must be defined (see later). Please see https://github.com/mwczapski/private_gitserver_docker_container for RAEADME and package artifacts.

Feb 12

Introduction

In this article detailed steps for creating a Docker image containing the IPF Open eHealth Platform environment based the IPF 3.7-SNAPSHOT are provided. This image can be used for exploration of the IPF platform and its healthcare integration capabilities, as well as generic Apache Camel integration platform features and capabilities that complement the healthcare capabilities of the IPF.

This article could be of interest to these who are aware of healthcare integration standards, health information exchange standards and requirements of healthcare integration. Specifically these who would like to explore the IPF, a FOSS platform (Free, Open Source Software), to determine whether to deploy it in a healthcare environment as a healthcare integration platform that supports common healthcare interoperability standards.

Please see the full article at:
IPF Open eHealth Integration Platform – Build IPF Docker Image

The Docker Container Image is now available for pull in the Docker Hub – IPF Open eHealth Integration Platform Docker Container Image

Dec 29

New release, v0.7, is available – see link below for downloadable archive. Throughput masurements were added. Manpages were updated.

I spend considerable time working with HL7. In the past I used SeeBeyond ICAN and Sun Java CAPS products, and OpenESB with HL7 Binding Component,  to rapidly create MLLP senders and receivers for the HL7 solutions I was building and testing. I also tried, at various times, 7 Scan, Interface Explorer and more recently HL7 Browser. For the blog articles I am writing on HL7 I need simple tooling that allows me to send HL7 v2 delimited messages from a file to a MLLP listener and receive acknowledgements, receive HL7 messages from a sender and retrun acknowledgements, and recently to combine multiple sender message streams into a single stream, with correct acknowledgement handling. The tooling has to be free for me to distribute with the projects and the articles and to use in my day job as well.

Not finding anything that would fit the bill, and that would work reliably enough, I developed my own tools.

I embellished the basic sender a bit so I could send multiple messages, one after the other, from a file, delay between successive sends, generate MSH-10, replace MSH-3-1, MSH-4-1, MSH-5-1 and MSH-6-1, and increase timeout for acknowledgements.

The tools are all old fashioned command line tools – no graphical user interface.

CMDHL7Listener – man page: https://blogs.czapski.id.au/wp-content/uploads/2010/12/CMDHL7Listener.pdf

CMDHL7Sender – man page: https://blogs.czapski.id.au/wp-content/uploads/2010/12/CMDHL7Sender.pdf

CMDHL7Proxy – man page: https://blogs.czapski.id.au/wp-content/uploads/2010/12/CMDHL7Proxy.pdf

Deprecated Distribution: https://blogs.czapski.id.au/wp-content/uploads/2010/12/CMDHL7_v0.5.zip

Current Distribution: https://blogs.czapski.id.au/wp-content/uploads/2010/12/CMDHL7_v0.7.zip

Release 0.5 and 0.7 are free to use by anyone for any purpose and will stay that way. There may not be future releases 🙂
I used HAPI 1.0.1 libraries for HL7 processing – http://hl7api.sourceforge.net/

Apr 03

For these who have an interst, here is my January 2011 CV / Resume:

https://blogs.czapski.id.au/wp-content/uploads/2011/01/Michael_Czapski_January_2011_resume_cv1.2.pdf

Apr 03

As I was going through the past entries, fixing links and uploading articles, to make sure that past posts in the new blog are working, I came across articles related to my trip for the Java One 2008 and the “launch” of the Java CAPS book. Since it is not likely that I will be getting another book in a great hurry I thought I will post some of the picures I took with my crummy phone camera 🙂

Michael Czapski with a copy oof the Java CAPS Book in the Java One 2008 bookstore

Brendan Marry, one of the co-authors, with the Java CAPS Book, in front of a shelf with a bunch of Java CAPS books

Java One 2008 feeding place - sone of the over 15 thousand people queuing to get lunch

Java One 2008 - plenary session venue

Brendan Mary with Myrna Rivera (right) in the Prentice Hall boot on teh Java One 2008 Exhibition floor. Myrna, who worked for SUn Publishing at the time, helped us a great deal in getting the book published - thanks Myrna 🙂

Java One 2008 - a walking, talking Duke mascot

Frank Kieviet (not that one could tell) delivering his part of our Java One session on implementing EAI patterns with OpenESB

Prentice Hall booth at Java One 2008 exhibition floor, featuring the Java CAPS book, amongst others 🙂

Mar 12

With the future uncertain, and things changing around me, I feel it inappropriate to have my own articles associated with the employer of the moment, whomever that may be from time to time.  As a consequence I transferred all the articles I posted from http://blogs.sun.com/javacapsfieldtech/ to my own blog site, https://blogs.czapski.id.au.

blogs.czapski.id.au is the site where I will be posting all future articles.

I declare https://blogs.czapski.id.au officially open 🙂

While I am migrating my blog to blogs.czapski.id.au some links in older posts may be broken. For as long as it works, go to the http://blogs.sun.com/javacapsfieldtech/ find the post with the identical title.
Mar 06

 

I am sorry to say that as at September 2010 all these links are no longer valid – seems like somebody has been going around closing sites to make sure that HL7 standards do not get used too widely 🙁

For these who have a need, the HL7 v 2.3.1 standard document is available online at http://www.medclinic.net/HL7Specs/ as at February 24, 2010. The site does not seems to have been updated for a long time so the standard document may well be available for a while longer.

HL7 v 2.3 document is available at http://www.uhc.com.pl/teksty/HL7/, again, as at February 24, 2010.

IHE Europe has an interesting “interactive” site where HL7 can be “explored” at http://ihe.univ-rennes1.fr/HL7/.

Tagged with:
Jan 07

Java CAPS Basics Book: http://safari.oreilly.com/9780137146130

Michael’s Java CAPS Field Technical Tips Blog: http://blogs.sun.com/javacapsfieldtech/

Java CAPS Basics Book review: http://www.javaranch.com/bunkhouse/bookSearch.jsp?category=Web Services and SOAP

Java CAPS Basics Book Comment: http://camelcase.blogspot.com/2008/05/first-and-only-java-caps-book-is.html

JavaOne2008 Presentation: Sun Java Composite Application Platform Suite: Implementing Selected EAI Patterns, TS-5301, JavaOne Online Technical Sessions, JavaOne 2008

Java CAPS Basics Book and JavaOne 2008 Presentation Comment: http://radio.javaranch.com/michael/2008/05/11/1210531145299.html

IT Toolbox Member Profile: http://it.toolbox.com/people/mczapski/

Key participation in Health Interoperability Showcase at the International MedInfo 2007 Conference: http://www.hisa.org.au/system/files/u1990/Interop_Showcase_2007_-_Handbook.ppt

St.Vincent’s Hospital Sydney – WebResults Project, Proceedings of AUUG’95 and Asia-Pacific World Wide Web Conference

Healthcare Workshop Presentation: Web Services and Service Oriented Architecture – Getting to There from Here, Where-to from Here? – HL7 “Web Services in Healthcare” Workshop, Tuesday, 28 March 2006 – Sydney

Healthcare Workshop Presentation: Web Services – Providing Healthcare Solutions, Where-to from Here? – HL7 “Web Services in Healthcare” Workshop, Tuesday, 28 March 2006 – Sydney

Strengthening Privacy and Confidentiality Protection for Electronic Health Records, From Proceeding (494) Web Technologies, Applications, and Services – 2005

Secure Messaging and Information Exchange for Health, HIC 2005 and HINZ 2005: Proceedings

A Question of Confidence, not a Question of Trust. Better Data Confidentiality Protection is Necessary, HIC 2004: Proceedings

Old Problem – New Solutions: HealthConnect System Architecture for Information Delivery, HIC 2003 RACGP12CC [combined conference]: Proceedings

Sep 04

Way back, when the Web was young and the number of World Wide Web sites in the whole World was counted in thousands, I built Australia’s first Web-based Diagnostic Results Reporting application. St.Vincent’s Hospital in Sydney, where I worked then, had the benefit of it for a bunch of years after I left for greener pastures. It has long since been superseded by something better, slicker and more modern. Today’s state of the art is tomorrow’s museum piece …

While I am not usually given to bragging, I am proud of the application all the same, when I remember that it happened, which is not very often at all. It was recalled to me by a couple of people whom I met after a very long time, in the last couple of weeks, so I though I will see if the conference paper I submitted to the First Asia-Pacific World Wide Web Conference, held in Sydney in 1995, is still on line. Alas, Charles Sturt University, which, until about 6 months ago, hosted the conference papers, no longer hosts them. I am still amazed that it hosted them for so many years – more then 10 – and only now retired the site.

To preserve the paper for a bit longer, and show what the state of the art in web design looked like in 1995, I uploaded the paper to the blog site. Here it is, “St.Vincent’s Hospital Sydney – WebResults Project”: https://blogs.czapski.id.au/wp-content/uploads/2010/03/for_blog_mczapski1.html. Some pictures are irretrievably gone – I don’t have the original material so some links are broken.

For these who are too young to remember, in 1993, when I started the project

  • The only way to design web pages was using a text editor and typing HTML (which graduated to version 2.0 half way through the project)
  • There was no such thing as Internet Explorer – in fact Microsoft was in the middle of creating “The Microsoft Network” in competition to the Internet – it never went very far
  • There was no such thing a Netscape Navigator – the only graphical web browser in existence was the Mosaic Browser from the National Center for Suppercomputing Applications (NCSA). A couple of the guys who built the Mosaic browser left to start Netscape and made a mint on it
  • There were two kinds of web servers – the CERN httpd and the NCSA httpd. The NCSA httpd eventually became the Appache Web Server
  • The only way for a Windows machine to connect to the Internet was to install the Trumpet Winsock TCP/IP stack, which Peter Tattam from Tasmania released to the World
  • There was no commercial anything on the Internet, no sites, no adds, no cookies,…
  • It was in 1995 at the First Asia-Apcific World Wide Web Conference in Sydney that I first saw Java and the HotJava Browser – while Java is still with us the HotJava Browser never go very far.

These were interesting days …

preload preload preload