Community Connect/New Practice Team Model

Community Connect/New Practice Team Model
One effect of the new and upcoming Affordable Care Act laws, is that healthcare organizations are acquiring smaller private practices and able to grow their organizations. Another is for smaller practices to contract with larger organizations to utilize their Electronic Medical Records (EMRs). EMRs can be prohibitively expensive for smaller practices, as can the penalties for not using them, so contracting with larger organizations allows them to keep autonomy and use of and EMR with a large network.
The benefits to the large organizations in both cases are clear with the increase in patient base and potential revenue. However this growth, often rapid, can present significant and numerous challenges to the administration.
EMR Project Teams
One area where challenges is realized is with the EMR Project Teams. The teams are often ‘bare-bones’ so an aggressive timeline can stretch teams too far and existing projects (upgrade, optimization, maintenance, etc) are often be neglected by necessity.
One method to help alleviate this strain is to bring in a team dedicated to the build and roll out of the newly acquired and community connect clinics. This allows the organization analysts to focus on the existing projects, and the dedicated team to build and roll out the clinics quickly and consistently.
Success Story
Utilizing this ‘team’ approach has been shown to be successful at a recent site which uses the Epic EMR. Creating a team with 1 Project Manager, 1 Ambulatory Analyst, and 1 Cadence Analyst was shown to be an ideal team structure. The addition of a second ‘team’ of 1 Ambulatory and 1 Cadence Analyst when the timeline was very tight proved to be beneficial.
The first clinic to go up was a collaborative approach between the added team and the existing staff. Embedding the team allowed them to learn the build conventions, documentation, change management, and various organization experts for different build aspects. The go-live was also collaborative to ensure the proper processes were being used.
The second clinic was more autonomous for the team, but a point-person was used from the staff for questions and the build was reviewed for accuracy.
The following clinics were autonomous which allowed the staff to work on a major upgrade. The team was able to ask questions as needed, but were able to build and roll-out clinics with limited time required from the staff.
If you would like any more information on this community connect model and how it could work for your organization, then please contact for more information.

Open Sourcing S2C Tool

This is a follow up post to our previous article ‘Migrating Solr to Amazon CloudSearch using the S2C tool’. Last month, we released an open source tool ‘S2C’, a Linux console based utility that helps developers to migrate search index from Apache Solr to Amazon CloudSearch.

In this article, we share the source code of the S2C tool which will allow developers to customize and extend the S2C tool to suit their requirements. The source code can be downloaded in the below link.

Further, we discuss step-by-step instructions on how to build the source code of S2C tool.


In this section, we detail the pre-requisites for building S2C tool process.
1. The application is developed using Java. Download and Install Java 8 .Validate the JDK path and ensure the environment variables like JAVA_HOME, classpath, path is set correctly.

2. We will use Gradle to build the S2C tool. Download and Install Gradle.
Please read getting-started.html (inside Gradle base folder) in setting up Gradle. Gradle is an open source build tool which does not require any pre-requisites like Maven or Ant.

3. Download the source code directly from the link
or alternatively
Download and install Git – and then use the following command to clone the source from Git

git clone (requires Git installation)

Note: The source code is available in public and does not require any credentials to access the source.

Build process

We will use Gradle, an open source build tool to build the S2C migration utility.
1. Verify the path, classpath, environment variables of Java, Gradle. Example: JAVA_HOME, GRADLE_HOME

2. Unzip the downloaded S2C source code and run the following command from the main directory. Example: E:/s2ctool/s2c-master or /opt/s2ctool/s2c-master

 ./gradlew -PexportPath=/tmp :s2c-cli:exportTarGz

The above command will create .tgz (zip file) at ‘/tmp’ directory. The directory path can be changed if required

gradle exportTarGz

The above command will create .tgz at ‘s2c-master/s2c-cli/tmp’ directory.


gradle exportZip

The above command will create .zip at ‘s2c-master/s2c-cli/tmp’ directory.

Build output or s2c-cli-1.0.tgz

3.The build output is the final product that is deployed to do migration from Solr to Amazon CloudSearch. The deployment steps are discussed in detail in the original blog ‘Migrating Solr to Amazon CloudSearch using the S2C tool’.

Please do write your feedback and suggestions in the below comments section to improve this tool. We also intend to write a follow-up post sharing the original source code of this tool.

About the Authors

 Dhamodharan P is a Senior Cloud Architect at 8KMiles.




 Dwarakanath R is a Principal Architect at 8KMiles.