Call Girls Ludhiana Just Call 9907093804 Top Class Call Girl Service Available
Interpretation and Adoption of the Concept of Enterprise-wide and Best of Breed Health IT within the New Zealand eHealth Community
1. UU/IT
Interpretation and Adoption of the
Concept of Enterprise-wide and Best
of Breed Health IT within the New
Zealand eHealth Community
Rebecka Janols1, Karen Day2 and
Martin Orr2
1Uppsala University 2Universityof Auckland
Department of National Institute for Health
Information Technology Innovation
@ UU/IT 2012-11-15 | #‹#›
3. UU/IT
eHealth in New Zeeland
Implemented in most areas
Complex puzzle of IT systems and applications
Same IT systems differently configured
Changes are required:
Hard to maintain
Expensive
To enable future developments
@ UU/IT 2012-11-15 | #‹#›
4. UU/IT
The NZ Health IT plan (2010)
“set priorities for regional and national IT
investments over a five-year period”
Shared care record that focuses on the patient and
is shared between the patient and involved care
providers.
DHBs in the same region need to come together
and agree on a common platform (i.e. a standard
set of software that is used within the region).
@ UU/IT 2012-11-15 | #‹#›
5. UU/IT
“The aim of this paper is to unbundle what
Enterprise-wide and Best of Breed IT means in
the New Zealand health context.”
@ UU/IT 2012-11-15 | #‹#›
6. UU/IT
Methods
Review of key documents and relevant research
14 participants from different organisations with
different roles
Clinical Hospital manager/ Service
education IT manager Research Organisation Vendor
1 x x
2 x
3 x
4 (x) x
5 x
6 x x
7 (x) x
8 (x) x
9 (x) x
10 (x) x
11 x
12 x x
13 x x
14 x x
@ UU/IT 2012-11-15 | #‹#›
7. UU/IT
The participants‟ interpretation
“Enterprise sounds like you have one
significant and large all-encompassing
process, program, software. Best of Breed
you are going to have different parts of
different programs attached to maybe a
central source…”
@ UU/IT 2012-11-15 | #‹#›
8. UU/IT
Enterprise-wide is based on
“best practice”
“They have actually looked at: ‘what is
health care? What are we trying to do?
What are the basic sets? How does
medicine really work?’…”
@ UU/IT 2012-11-15 | #‹#›
9. UU/IT
Research definition: Enterprise systems
Health care Enterprise
system system
“Enterprise systems are
commercial software Reality
packages that enable the Enterprise
integration of transactions- system
oriented data and business
processes throughout an
organisation.”
Marcus and Tanis (2000)
@ UU/IT 2012-11-15 | #‹#›
10. UU/IT
Research definition: 'Best of Breed‟
Health care
system
“In the „best of breed‟
approach, the organization
picks and chooses ERP
modules which best support
its business processes from
various vendors.”
Sumner and Bradley (2007)
@ UU/IT 2012-11-15 | #‹#›
11. UU/IT
Best of Breed systems
Benefits Disadvantages
Customised to a particular Hard to integrate
purpose Hard to share data
Easier to implement change A complex network of
Flexibility system
A degree of individualisation Problems with upgrading to
newer versions
To many vendors
Cost – too expensive to
maintain.
Innovations stops
Security holes between the
system
@ UU/IT 2012-11-15 | #‹#›
12. UU/IT
Enterprise-wide systems
Benefits Disadvantages
Built on "best practice” „Best practice‟ is defined by
Easy to share and access the vendor not the users
detailed data Need to compromise – “one
One patient – one record size fits all”
Easier to manage Flexibility – hard to change
Standardisation of the data Users need to adapt to the
Centrally held data base system
Ability to interface Harder to innovate
The same “Look and feel” Monopoly – little power over
the supplier
Security is integrated- not
adhoc Expensive
Less duplication
@ UU/IT 2012-11-15 | #‹#›
13. UU/IT
Enterprise-wide vs. Best of Breed
The disadvantages with the BoB are often
mitigated by an Enterprise-wide system.
The disadvantages with the enterprise
systems are often mitigated by the BoB.
What is the future solution?
Is the answer one or the other?
@ UU/IT 2012-11-15 | #‹#›
14. UU/IT
CONCLUSION 1
‘Best practice’ can be differently interpreted.
@ UU/IT 2012-11-15 | #‹#›
15. UU/IT
Research definition: 'Best practice‟
‘‘The better or best ways of performing a
particular process’’
O‟Leary (2000)*
* O‟Leary DE. Enterprise resource planning systems: systems, life cycle, elecronic commerce
and risk. (Cambridge)
@ UU/IT 2012-11-15 | #‹#›
16. UU/IT
1. „Best practice‟ defined by the users
Health care
system
@ UU/IT 2012-11-15 | #‹#›
17. UU/IT
1. „Best practice‟ defined by the users
Health care “Vision”
system
“Reality”
@ UU/IT 2012-11-15 | #‹#›
18. UU/IT
2. „Best practice‟ for a process
Process X
(Org 1)
Process X IT-system
(Org 2)
process X
(Org 3)
‘‘One process – one system’’
@ UU/IT 2012-11-15 | #‹#›
19. UU/IT
3. Evaluated “best practice”
“.. it has gone through some form of
evaluations and inspections as being the
preferred option”
@ UU/IT 2012-11-15 | #‹#›
20. UU/IT
Does ‘best practice’ exist?
“The idea of best practice builds on the
assumption that there are certain solutions
that are superior compared to others when
solving problems in a certain context. “
Axelsson et al. (2012)*
* Axelsson K., Melin U. and Söderström F. (2012) Analyzing best practice and critical
success factors in a health information system case - are there any shortcuts to
successful IT implementation? In. 19th European Conference on Information
Systems.
@ UU/IT 2012-11-15 | #‹#›
21. UU/IT
Don‟t forget
“Since every organization is unique and has its
certain conditions there are obvious risks that
some of the built-in (best practice) actions and
processes in an IT system do not suit the
organization.“
Axelsson et al. (2012)*
* Axelsson K., Melin U. and Söderström F. (2012) Analyzing best practice and critical
success factors in a health information system case - are there any shortcuts to
successful IT implementation? In. 19th European Conference on Information
Systems.
@ UU/IT 2012-11-15 | #‹#›
22. UU/IT
CONCLUSION 2
All user groups have different
responsibilities, requirements and needs. A
enterprise-wide system is too generic to
adequately meet all users needs.
@ UU/IT 2012-11-15 | #‹#›
23. UU/IT
Findings: Enterprise-wide
systems
can be “too generic”
“The risk is that you develop something that is
so generic that it isn’t particularly useful to
the people who need to use it in a day-to-day
basis. That it collects data at a population
level, a district level…”
@ UU/IT 2012-11-15 | #‹#›
24. UU/IT
Who are the users?
“Everybody!”
@ UU/IT 2012-11-15 | #‹#›
25. UU/IT
Who are the users?
Administrative GPs
staff Physiotherapists
Managers PMOs
Government
DHBs Nurses
“Everybody!”
Physiologists
Hospital physicians
Assistant nurses
Researchers
Patients
@ UU/IT 2012-11-15 | #‹#›
26. UU/IT
What are data used for?
Administrative GPs
staff Physiotherapists
Research
Managers Clinical practice
PMOs
Government
DHBs Nurses
Measure quality “Everybody!”
Physiologists Inform founding
Statistics Hospital physicians
Planning Long term disease register
Assistant nurses
Measure outcome Researchers
Patients
Measure progress
@ UU/IT 2012-11-15 | #‹#›
27. UU/IT
Can all users‟ requirements be
supported by the same system?
Or does
responsibilities, roles, contextual
settings and traditions matter?
@ UU/IT 2012-11-15 | #‹#›
28. UU/IT
CONCLUSION 3
Enterprise-wide vs. BoB is a false dichotomy.
Need to identify what must be customised
and what can be centralised.
@ UU/IT 2012-11-15 | #‹#›
30. UU/IT
Future solution 1
“…maybe an enterprise-wide solution but it
allows local adaptation for those users in
different areas/…/I think that they both [ERP
and BoB] have risks and they both have
potentials in them. The devil is in the detail.”
@ UU/IT 2012-11-15 | #‹#›
31. UU/IT
Future solution 2
“…the core aspects of data and functionalities
are placed in an accessible location and they
then feed some of those systems. Then, if it
suits me to have an enterprise
system, absolutely fine, go for it/…/I think
that gives freedom to innovate around the
edge.”
@ UU/IT 2012-11-15 | #‹#›
32. UU/IT
3 conclusions
1. There is not a shared understanding of what
„Best practice‟ means.
2. A enterprise-wide system is too generic to
adequately meet all users needs.
3. Enterprise-wide vs. Best of Breed is a false
dichotomy. The challenge is to identify what
must be customised and what can be
centralised.
@ UU/IT 2012-11-15 | #‹#›
33. UU/IT
Thanks for your attention!
Questions?
Please contact me for future cooperation!
Rebecka.Janols@it.uu.se
@ UU/IT 2012-11-15 | #‹#›
Editor's Notes
Research interests: Human Computer Interaction, usability, user centeredness, change management and health informatics.Interviews, observations, evaluations and surveys at several Swedish county councils.Gain knowledge of user adoption when deploying and using enterprise-wide health IT systems.
Towards consistency, patient centeredness and a shared care record.
Questions:Their background and experiences related to this subjectInterpretation of the terms "enterprise-wide" and best of breed ITBenefits and risksReasons for choosing/not choosing the different solutionsIdentify user groups, their needs and requirements
Not all participantshadheard the two terms. Butwhen I askedthemtodefinethem, almost all gave the same definition.“Enterprise sounds like you have one significant and large all-encompassing process program, software. Best of Breed you are going to have different parts of different programs attached to maybe a central source. So you actually attach a skeleton, framework, as suppose to ‘one of everything’ is done by this particular program or software.”
Some said that it is based on a deeper thinking – not just modules interlinked by the vendor. You can almost say that the vendor have identified a best practice for delivering health care.“They have actually looked at: ‘what is health care? What are we trying to do? What are the basic sets? How does medicine really work?’That to me is an ‘enterprise-wide thing’. Not a whole lot of different modules were the vendor is just interlinking them, because we could have done that as well.”
*Marcus L. and Tanis C. (2000) The Enterprise System Experience - From Adoption to Success in Framing the Domains of IT Management: Projecting the Future Through the Past
Traditionally: BoB have been selected by the users – the clinicians
Research definition.In the research we found Findings: Three ways of defining ‘Best Practice’
“… each person responsible for that particular function chooses the computer software that best meets their needs to deliver to their function.”
“… each person responsible for that particular function chooses the computer software that best meets their needs to deliver to their function.”
All said that they had a BoB tradition – that the clinicians had been powerful in the decision. Discussion about Best practice, what is Best practice.“It was always ‘my opinion’- rules/…/ that is really silly, we don’t have the money to do that/…/ there must be some logic why that one is better than that one/…/ you need to agree what the best of breed is.”
*Marcus L. and Tanis C. (2000) The Enterprise System Experience - From Adoption to Success in Framing the Domains of IT Management: Projecting the Future Through the Past
When you are talking about best practice you talk about that there is one way that is better than another. The question is according to who? Who decides what is the best way??
“the pre-packaged solutions to reach success might turn out to be shortcuts that do not work in a situated practice.“ Axelsson (2012)
This quote is from a researcher - The answer lies in the middleClinicians have been to dominantThe clinicians needs have not been listen to.
Shared repository
I’m submitting my PhD early next year and are loocking for oppertunites to be a part of the future ehealth development in NZ.What should we do in NZ?I’m not saying that it is bad that you are cooperating between the DHBs. However it is important to realise that it can be a reason that they have selected different systems, not just because they want to be uniqe. And there is an advantage that they are used to the system. Changing system takes time, money and energy. be aware of the risks – not just buy the solutions on the benefits. I want in this presentation highlight that there is a debate, and that it is more complex than people think. And there is no consensus. false dichotomy.3Ccore (backbone) common (lab portal) customized (particular services have special needs).every strategy have pros and cons - you pick if for the pros - some other needs to take care of the cons. need to think about the cons. pros cons and compromises. space - I have not been involved in that. The procurement are important and I agree with what I know about active procurements. Important to have a broad picture – but it is also important that you are aware of that there is different users and they have different needs. And compromising their needs might be a short cuts that doesn’t work!I understand the question like that. Refraze the question. from what i have learned in this research. Is it good that the DHBs are working together? Or are they loosing their individuallity?