1 ADVANCE for Executive Insight
1 ADVANCE for Executive Insight
1 ADVANCE for Executive Insight
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
cloud contract<br />
The Cloud<br />
Contract<br />
Key elements <strong>for</strong> executing a<br />
move to the public cloud are<br />
outlined. By Chris Witt<br />
Similarities exist in a cloud contract as with<br />
other contracts you have negotiated; if you currently<br />
employ data center co-location or managed<br />
services, you will see many parallels with<br />
cloud services, <strong>for</strong> example. What follows are<br />
observations I have assembled while working<br />
with many clients. You should engage your corporate<br />
council early in the process, as they will<br />
prove to be invaluable.<br />
Key Areas of Consideration<br />
HIPAA – This might seem like an obvious area,<br />
but it requires some specific attention. Due to<br />
the nature of cloud computing, it can be difficult<br />
to know where your data is and who has access<br />
to it. Ultimately, you are on the hook to secure<br />
the data and be able to audit access. You want to<br />
ensure your vendor will facilitate this logging.<br />
Chris Witt is president and cofounder<br />
of WAKE TSI.<br />
There are clearly pros and cons of using<br />
public cloud computing in the delivery<br />
of healthcare computing services. Somewhere<br />
in the process you will select a vendor who<br />
best aligns with your strategy. The next step in<br />
this vendor relationship is to negotiate the contract.<br />
Contract negotiation is like sausage making:<br />
You want the final product but you don’t<br />
want to see how it is made.<br />
Force Majeure – Most standard contract language<br />
makes it far too easy <strong>for</strong> a vendor to declare<br />
Force Majeure. I would not recommend that a client<br />
go into anything less than a Tier 3 data center.<br />
It should take a catastrophic local event to bring<br />
down the data center. Also, your cloud instances<br />
are portable and should be replicated. A primary<br />
reason you move to the cloud is <strong>for</strong> the inherent<br />
resiliency. If you are not leveraging this, why not?<br />
Services – Make sure the contract clearly spells<br />
out the required services provided by the vendor<br />
and pre-negotiate the optional services. The<br />
contract should also cover implementation and<br />
the roles and responsibilities of each party. Do<br />
they include backup? Archiving? What happens<br />
if you need a restore?<br />
Service Level Agreement (SLA) – This is where<br />
you document your expectations. The SLA<br />
components should directly relate to the<br />
tom whalen<br />
44 <strong>ADVANCE</strong> <strong>for</strong> <strong>Executive</strong> <strong>Insight</strong>