FIELDING THE FUTURE


the HALO application compared to the legacy application has the potential to reduce hardware costs.


Clark: As an Army acquisition program, what are you doing to support the Army’s leadership priorities and support multido- main operations? In other words, how does MC4 remain relevant?


Ellis: Te deployment and further devel- opment of HALO supports the Army’s priorities—people, readiness, modern- ization and reform. Improving the ability to document care for Soldiers supports health care delivery, which is all about taking care of people. Advances in opera- tional health information systems, such as HALO, provide real-time data in support of medical mission command. Tis helps maintain readiness through the ability to rapidly shift resources in support of the fight. While the focus of this interview is on HALO and electronic health care documentation, MC4 deploys operational health IT solutions that support all 10


health care functions, including medical logistics, preventive medicine and medi- cal mission command. In each of these areas, we see the value of lightweight, scalable, cost-effective solutions that incorporate commercial off-the-shelf hard- ware and software solutions that can be rapidly modified and deployed in support of multidomain operations ranging from early-entry operations through large-scale combat operations. And the rapid, incre- mental delivery of capability is consistent with modernization and reform efforts by leveraging the power of operational health information systems to help maintain the Army’s competitive edge.


Clark: Isn’t the DOD already moving out with modernizing its EHR? Why not just use that solution in the deployed environ- ment rather than develop an application like HALO?


EASY DOCUMENTATION


Ellis: Military Health System Genesis is military medicine’s modernized, enter- prise-level EHR that has also been adopted


Providers can co-sign patient encounters and health documentation. (Photo by the author)


by the VA. But it is not ready to field to operational forces. Until it is ready, being satisfied with the legacy operational health care applications is not the answer, espe- cially when there are opportunities to rapidly deliver enhancements and addi- tional capability in the interim to our deployed Soldiers. HALO is an example— a cost-effective improvement over the legacy EHR that will serve as a bridging solution until the modernized solution is ready to deploy to operational forces.


Clark: How many encounters can be pushed at the same time? Where does the data go?


STANDARD PRACTICE


The HALO software application is essentially an electronic Standard Form 600. (Photo by the author)


Jay Patnaude: Te transfer of the medi- cal encounters is seamless. Regardless


https://asc.ar my.mil


67


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172