Testimonial: Supporting Rural Community Health Through Specialized Care

 

An exceptional care experience can happen in most any setting, no matter how remote. Aspen Mountain Medical Center evinces that with the right commitment and support, many of the challenges facing rural healthcare providers can be overcome.

To help achieve their mission, Aspen Mountain partnered with MEDHOST. Through collaboration, the two partners provide the hardworking community of Rock Springs and its surrounding area with a sturdy foundation for specialized care that surpasses all standards.

 

See More MEDHOST Partnerships

Testimonial: Implementing and Optimizing for Continued Success

Testimonial: Maintaining Growth in Rural Healthcare Through a Strong HIT Partnership

A Family Affair: A MEDHOST EDIS Implementation Story

Transcript

Show Full Transcript

1
00:00:05,210 –> 00:00:08,410
The whole thought process behind
the actual build out of Aspen

2
00:00:08,410 –> 00:00:10,850
Mountain Medical Center was to
bring value the healthcare

3
00:00:10,850 –> 00:00:13,900
system to not pass along
needless cost to the patient

4
00:00:13,900 –> 00:00:15,650
but to give them that
top of the line care

5
00:00:15,650 –> 00:00:17,840
that this community deserves.

6
00:00:17,840 –> 00:00:20,600
We’re able to collaborate a
lot with our local hospital

7
00:00:20,600 –> 00:00:23,210
and add extra services
that necessarily

8
00:00:23,210 –> 00:00:26,990
wouldn’t be available in
a rural area in Wyoming.

9
00:00:26,990 –> 00:00:29,900
Initially as a new facility
we had a lot of growing pains.

10
00:00:29,900 –> 00:00:32,900
We were doing all of the IBM
and servers and everything

11
00:00:32,900 –> 00:00:36,200
on site which was a lot of
maintenance and updates.

12
00:00:36,200 –> 00:00:37,940
It was at that
point that we really

13
00:00:37,940 –> 00:00:40,370
decided that a best
solution for us

14
00:00:40,370 –> 00:00:44,060
was to go to a
hosted solution.

15
00:00:44,060 –> 00:00:47,290
MEDHOST is able to integrate
the services that we already

16
00:00:47,290 –> 00:00:51,070
have here in Aspen we’re able
to have a vitals flow so that

17
00:00:51,070 –> 00:00:54,300
allows for the nurses to be
more at the patient’s bedside

18
00:00:54,300 –> 00:00:57,400
and it helps us grow to give
the nurse more availability

19
00:00:57,400 –> 00:01:01,210
and malleability to do other
services for our patients.

20
00:01:01,210 –> 00:01:03,550
If we can pick up the phone
and we can call somebody

21
00:01:03,550 –> 00:01:08,440
at our EMR or EHR provider
and get an Active Response

22
00:01:08,440 –> 00:01:10,180
we make change happen faster.

23
00:01:10,180 –> 00:01:11,720
We protect the patients

24
00:01:11,720 –> 00:01:14,700
and that’s the ultimate goal.
Some of the templates that we

25
00:01:14,700 –> 00:01:20,070
use some of the built in easy
to access parts of the EMR

26
00:01:20,070 –> 00:01:22,350
allow us to focus more
on our patient experience

27
00:01:22,350 –> 00:01:26,390
and be nurse to patient
rather than nurse to computer.

28
00:01:26,390 –> 00:01:29,510
It’s nice that MEDHOST
is able to interface

29
00:01:29,510 –> 00:01:32,930
with the other products that
we have in the system already.

30
00:01:32,930 –> 00:01:36,230
We use Mindray which is the
vitals machines and answering

31
00:01:36,230 –> 00:01:39,950
machines – those seamlessly
flow vitals and anesthesia

32
00:01:39,950 –> 00:01:42,560
data into the medical
records so they’re not having

33
00:01:42,560 –> 00:01:44,370
to sit and chart all of that.

34
00:01:44,370 –> 00:01:46,730
It’s flowing in, we can
see what’s happening,

35
00:01:46,730 –> 00:01:48,620
and we can tweak it
the way we want it

36
00:01:48,620 –> 00:01:52,010
and use the product to
the best of its ability.

37
00:01:52,010 –> 00:01:54,140
The ultimate goal is
taking care of the patient.

38
00:01:54,140 –> 00:01:56,720
We cannot create the change
that we want to create unless we

39
00:01:56,720 –> 00:02:00,447
have a solid EHR partner.
MEDHOST takes a lot

40
00:02:00,447 –> 00:02:02,780
of stress off of us because
we know that the updates are

41
00:02:02,780 –> 00:02:03,980
getting done all the time.

42
00:02:03,980 –> 00:02:06,170
It’s much better faster.

43
00:02:06,170 –> 00:02:08,500
It’s been a really
good solution.