Doug Ritchie
COEMR
EBO – THE CURRENT STATUS
DISCLOSURE
What follows will be some incomplete
information but it is the best we currently
have.
This is an evolving situation and not a lot of
answers to tough questions are yet available
to COEMR
We will tell you all that we know.
PAST HISTORY
Clients were encouraged to sign up for EBO in
the Jan-Mar 2008 timeframe knowing that
the actual release of EBO would be sometime
later (indefinite knowledge as to when)
Significant cost savings at $250 per provider
This offer has been extended through 7/31/2008
COEMR was able to convince over 100
providers to sign up
PAST HISTORY
The eCW plan for EBO has been as follows:
First release (first half of 2008) will allow an EBO
user to run any/all current reports that are in eCW
or APL reports but under EBO
Second release (second half of 2008) will allow an
EBO user to run new reports that are being
developed by eCW for clinical data reporting
EVENTS
COEMR has had an early version of EBO to
test but this was not able to be put on an ASP
COEMR has used this version on a local dedicated
computer that was “connected” to a clinical
database
None of this has ever been released to COEMR
clinics to date
eCW has stated that while EBO is designed to
be introduced with v8 of eCW that it will work
with version 7.6.X also.
CURRENT STATUS
EBO is a highly dynamic situation at eCW
today due to a myriad of reasons
Learning from COGNOS how to implement and
optimize EBO
Learning how EBO will work in a clinic from a
hardware point of view
Learning how EBO will work will take time
between clinics (those in early releases), COEMR,
and eCW as we are entering new territory here.
CURRENT STATUS (continued)
We have also just learned 7/8/2008 that:
This will require another upgrade of eCW to a
version yet to be numbered (perhaps 7.6.56) in
order to run EBO in the clinic
COEMR must upgrade the report server at the
ASP with additional hardware (not yet on order)
as we have learned that the existing report server
is not strong enough to run EBO
However, the release of EBO that we will get will
have authentication built in and that it will run
inside of the new version to be released.
CURRENT STATUS (continued)
We have also just learned 7/8/2008 that:
eCW will provide documentation to COEMR by 7/9
as to how to set up EBO in an ASP environment.
This has so far been unavailable to COEMR.
CURRENT STATUS (continued)
We have also just learned 7/8/2008 that:
Documentation on using EBO is due to us OR it
will come in the form of one on one training (for
COEMR staff members) to be done on or before
7/18/2008
We can allow two clinics initially access to EBO
given the hardware shortcomings that we
currently have with the likely candidates being
One in Bend/Redmond/Prineville
One in Eugene
CURRENT STATUS (continued)
We have also just learned 7/8/2008 that:
Version 7.6.56 (or equivalent) will also include
other changes and/or bug fixes from all prior
releases that we have deployed.
eCW will provide a list of these changes very soon
Once we determine the early adopters for EBO we
will have to use the data of how many users
running reports using EBO will be on the server in
order to best understand our hardware needs for
adding other clinics later.
FINAL COMMENT
Changes to this will be expected over time
How to run EBO in an ASP environment
How many users per report server can be
accommodated
This will dramatically increase demand on the report
server later in the year when clinical reports are added to
EBO (providers, mid-levels and others will be accessing
EBO)
The formal release of v8.0 of eCW is coming soon and
once this gets into production widely it is surely true
that EBO software will continue to change
EBO SERVER SPECS
We have learned that EBO essentially
requires us to purchase new servers for both
ASP’s with the following requirements:
Quad core processors at 64 bit
2 GB of RAM for operating system and EBO
1 GB per practice depending upon the number of
users
Maximum of 8 users concurrently per dual core
processor (16 users per quad core?)
Need to add one CPU per each additional 8 users
SOME SIMPLE COMPUTATIONS
In 2H2008 EBO will include clinical data
This means that reports will not only be run
by financial staff but by many on clinical staff
Clinics Concurrent users No. of processors No. of EBO servers at
ASP
1 8 1 1
2 16 2 1
3 24 3 1
4 32 4 1
5 40 5 2
20 160 20 5
THE BOTTOM LINE
We cannot predict today exactly how many
servers will be required in ASP-East
(Redmond), ASP-West (Eugene)
We should begin the testing phase before the
end of July
doug@coemr.com (541) 585-2588
rochelle@coemr.com (541) 585-2586
This presentation will be placed on the COEMR website in the customer
area that requires a login.
QUESTIONS?