MHS logo

The Gateway

Tech Blog
Blog Image

Resources

Tools

  • Email this article to a friendEmail Page
  • Printer-friendly versionPrint

Larger Text

  • Text  A  A  A  A

The Gist of MEDLOG Updates

March 12, 2012 posted by Tracy Ellis

Tracy Ellis, director of MC4’s Logistics Management Division since 2009, oversees MC4’s field operations. He’s a retired colonel having served 26 years in the Army and was the former commander of Tobyhanna Army Depot.

MC4 users aren’t strangers to software updates. In order to keep up with the latest and greatest of technology, patches are fielded periodically. Upgrades to the Defense Medical Logistics Standard Support (DMLSS) system will be occurring within six months including a new DMLSS Customer Assistance Module (DCAM) software release. These upgrades will require preparation on the part of the units receiving these upgrades.

There is currently a DMLSS hardware refresh and upgrade underway with the combat support hospital at Dwyer that involves moving from the Unix to a Windows/Oracle operating system. A few new units in theater will also receive DMLSS in the next few months. We are trying to get them up and running before the next DMLSS and DCAM upgrades coming down the pike.

In mid-April, DMLSS 3.1.2 Generation IV will be provided to CONUS-based hospitals. It’s our plan that by the end of June, all the servers worldwide will be up-to-date so everyone is running on the same version of DMLSS. The DMLSS Gen IV includes a PKI certificate validation process that will have no impact for field users. When the upgrades are pushed, users will simply log on to the system, accept to download the current version and continue using the system like they normally would.

There is also a new version of DCAM that is being released in conjunction with the DMLSS Gen IV upgrade. This new DCAM version 1.4.4 is not backward compatible with DCAM 35.2.5 so MC4 is producing a post-deployment systems support (PDSS) release on disk that will be distributed in the June/July timeframe for the information management office, unit level system administrator or sustainment automation support management office (SASMO) personnel to run.

DCAM 1.4.4 will have significant changes to the look and feel of DCAM that will take users some time to get adjusted to. MC4 training materials are being updated to help customers acclimate to these changes. Training is being offered to MC4 support personnel and then to DCAM users to help everyone get up to speed on these changes. DCAM 1.4.4 will also be incorporated into the next MC4 EMR 2.1.4.0 release to reduce the number of times a unit has to manage MC4 updates in theater.

The DMLSS Gen IV and DCAM 1.4.4 updates are occurring at the same time because both will require all systems that connect to it to have .x509 certificate authentication. The challenge for DCAM users is the .x509 certification, which is tied to each computer running the app, so the new DCAM will require all DCAM level II and level I instances to have certificates as well. Each unit is responsible for going through their system administrators/S6 and requesting unique certificates for each computer that will run DCAM 1.4.4.

After the DMLSS Gen IV update is complete, any DCAM customer that connects to a DMLSS server who has not updated to DMLSS 1.4.4 will lose the ability to connect and transfer order files. These DCAM users may have to export and email orders until they receive their DCAM upgrade. Fortunately, anyone who is already setup to export and email orders won’t experience disruption in service.

To help units prepare for these upgrades, we are working with those that actively connect to a DMLSS server first and then will help the remaining units. We will also have our MC4 region support teams and MC4 medical logistics operations team available to help with training and upgrades once the PDSS software is approved and released.

thumbs up iconRecommend (0)

0 comments Comments (0)  Category: Medical Logisticians

Training Exercise uses Notional and Real Patients

March 8, 2012 posted by Dr. Ken Meade

Dr. Ken Meade, MC4's chief of clinical operations in Europe and the Far East, was the deputy commander for clinical services for the 212th Combat Support Hospital, Miesau, Germany, and medical director for the Landstuhl Army Medical Clinics in Belgium, Italy, Kosovo, Kuwait and Qatar.

Last fall, the 212th Combat Support Hospital (CSH) and the 30th Medical Command (MEDCOM) conducted a unique training exercise at the Joint Multinational Training Center (JMTC) training area in Grafenwoehr, Germany. During this field training exercise (FTX), more than 240 actual sick-call patient encounters were documented into the live AHLTA-T application on MC4 computers, and more than 350 notional patient encounters were also documented.

The exercise included an abundant variety of trauma and medical encounters, and it included two epidemic events. The success of the exercise depended on minimizing any confusion between the notional and real sick call patients that were included in the exercise.

Patient encounters were documented in AHLTA-T. MC4 staff, including myself, were onsite to help ensure that the patient data was properly moving forward to the Theater Medical Data Store (TMDS), the Medical Situational Awareness in the Theater (MSAT) application, to the training servers and to legacy AHLTA.

From my account, this training exercise was a success and serves as an excellent model for future training exercises; it stands as a benchmark for future medical brigade and CSH certifying exercises.

Notable accomplishments
The 212th CSH entered a substantial number of well-documented notional encounters. This is impressive because nearly all the encounters had detailed provider notes as well as satisfactory nursing documentation. Kudos to the CSH's hard working staff!

The abundance of both notional and actual encounter information gave the 30th MEDCOM an opportunity to analyze the exercise events with much greater detail than a typical training event.

Challenges
Both the CSH and the MEDCOM had several challenges that needed to be overcome in order to make this exercise a reality. Initially, there were multiple challenges regarding the initial setup of the training server; challenges that could have threatened the conduct of this training event. But once we made it past these hurdles, MC4 staffers were in full swing recommending best clinical business practices and consulting commanders with questions about individual unit needs and requirements.

The greatest risk associated with the exercise was the possible inadvertent entry of a patient into the wrong system. Real patients and real social security numbers cannot be entered into a training system; the consequences of this are serious. Also, it was important not to enter notional patients into the real electronic medical record system.

To ensure that no errors were made, the CSH paid strict attention to the separation of notional and live data, and the physical location of notional and live computers. Equally important was labeling the computers, properly training users (including patient administrators, the sick-call facility members, the providers, the medical screeners and the nurses), and continually emphasizing to the CSH staff the importance of not mixing the live and notional patients.

I strongly advise using these same proven methods during any future exercises that try to work with notional and live patients during the same event. The complexity of such an exercise required a lot of preparation, but in the end we demonstrated that the MC4 EMR system could successfully and concurrently document a large number live patient encounters and simulated patient encounters during a training exercise.

Learn More
The large numbers of both real and notional documentation was unique during this large scale exercise. The work that was done by the 212th CSH is available for review today; I recommend reviewing the documentation of this exercise to see exactly how the patient encounter data is displayed in the real system and to learn how to use these tools while exercising the mission command of level II and III medical facilities in a deployed environment.

  • View the entire live encounter information that was done during the FTX by logging into TMDS.
  • Review the notional information on the AKIMEDA TMDS training server.
  • The exercise training encounter data can be viewed on the AKIMEKA MSAT Training Server.

thumbs up iconRecommend (0)

0 comments Comments (0)  Category: Medical Staff

Add new comment

Your name [optional]

Email someone the link to this page. Please fill out the fields below.

A copy of the message will be sent to your email address.

RECIPIENT NAME :

RECIPIENT EMAIL :

SENDER NAME :

SENDER EMAIL :

SUBJECT :

MESSAGE :

 


 

Privacy Policy

Subscribe to The Gateway Monthly, an MC4 wrap-up including news, tips, blogs and photos on military health information systems supporting the warfighters.

Delivered straight to your inbox, see what's new in the world of tactical electronic medical recording, medical logistics, and medical command and control missions.

RECIPIENT NAME :

RECIPIENT EMAIL :
 


Privacy Policy