DOD CHCS / AHLTA Sources

[Charlie V]

 

Hello All,

 

Where can I obtain documentation, source code (FOIA?) and maybe even technical help on the DOD's version of VistA viz. CHCS / AHLTA?

And how about even TC2?

 

Charlie

[Seth Rylan Gainey]

Charlie,

The OpenAHLTA source code is available at https://github.com/OSEHRA/OpenAHLTA with instructions for setup at http://openahlta.org/. I've never used it, but Sid Tarason of Astute Semantics has a demo with it running at http://astutesemantics.com/jlv-evolution/

   - Seth

[Charlie V]

I hereby bequeath unto you my first born.

[Charlie V]

Gr8 - thanks!  Is OpenAHLTA different from AHLTA?  What is AHLTA - a GUI for CHCS?  Where is CHCS?  Is CHCS all MUMPS?  I program in MUMPS only.

Charlie

On Monday, November 9, 2015 at 4:33:52 PM UTC-5, Seth Rylan Gainey wrote:

[Charlie V]

From what I see, OpenAHLTA is all Visual Basic.  Where is the MUMPS?

Charlie

On Monday, November 9, 2015 at 4:33:52 PM UTC-5, Seth Rylan Gainey wrote:

[Faisal Sami]

Open AHLTA is the open source version of AHLTA-Theater which is developed by MHS (US military health system). The software code is in VB and the database is mysql. No mumps.

Regards,

Faisal

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Whitten]

CHCS, although based on VA's DHCP, was altered by SAIC, which claimed a copyright on the entire code base, and thus did not share it using FoIA.

CHCS, renamed CHCS I, is written totally in MUMPS. It does NOT have the RPC Broker as a method of calling code as remote procedures, and thus does not have that method of returning results.

After CHCS I was deployed, A new code base, named CHCS II was created based on many different code bases, which communicated over the TCP/IP stack. I have heard various comments, but nothing definitive about what the communication format is. I have heard ODBC, XML, HL7 and CORBA. It is unclear which of these is actually used between the various companies, and components.

 Since CHCS II was intended to be a "Best of Breed" approach, sharing data and interoperating to produce a integrated solution was not their highest priority.. The process and cost in time and space of doing this has been ascribed as a major performance hit. In a MUMPS system based on FileMan, this issue doesn't occur because integration is a facet that naturally occurs with that approach.

The slowness of CHCS II caused the DoD to put a great effort into speeding things up, which I have been told resulted in the decision to rename CHCS II to AHLTA.  I have also been told that renaming the system has not resulted in as much of a performance boost as originally expected.

So TLDR, CHCS I is written in MUMPS and no one other than DoD or their contractors have a copy. CHCS II/AHLTA is written in many languages all of which have produced proprietary non-shared-source codebases.

Hope this helped,

David Whitten
713-870-3834

[George Timson]

"....renaming the system has not resulted in as much of a performance boost as originally expected..."


Thanks for my morning laugh, David.    Worthy of Dilbert.    Your post was not "Too Long" at all!

--George

[Rafael Richards]

I have downloaded and run the OpenAHLTA listed on OSEHRA.  It is a very large virtual machine running windows.

The contents of this virtual machine is consistent with what  David W describes above:

- AHLTA is an amalgam of  closed,  proprietary components. 

- The Virtual Machine contains zero source code.  

- Even the windows license to run this virtual machine is only six months, then expires. 

So even access to *run* the binaries of  'OpenAHLTA' died a long time ago.

My advice:  Don't waste your time downloading it the openAHLTA VM.  

Rafael