Title: Integrating MCH Data Systems Identifying User Needs
1Integrating MCH Data SystemsIdentifying User
Needs
- Sherry Spence, MCH Data Systems Coordinator
- Oregon Department of Human Services
Supported in part by funding from the Maternal
and Child Health Bureau (Title V, Social Security
Act), Health Resources and Services
Administration, and by the Centers for Disease
Control and Prevention, US Department of Health
and Human Services Opinions stated do not
represent those of CDC, HRSA, or USDHHS
2Acknowledgements
- FamilyNet Executive Sponsors
- Katherine Bradley and Lorriane Duncan
- FamilyNet Project Teams
- DHS Project Management Office
- Oregons many FamilyNet stakeholders
- Oregons Families
3Developing System Project Plans
4Developing Project Plans
- First steps
- Agree on business goal
- Describe project
- Identify stakeholders
- Define scope
- Develop requirements
- Search for resources
- Project documents
- Project description
- Executive sponsor
- Governance
- Requirements
- Project plan
- Phasing
- Time and resource needs
- Management
5Developing System Requirements
6User Needs - the Conundrums
- Developers say
- We dont speak the same language.
- Users dont need to understand system
limitations and capacities. - So users should just tell us what they need, and
well decide how to do it. - Users dont know what they need.
7Developer Needs-the Conundrums
- Users Say
- Developers should just tell us what the system
can do, and well decide if or how we can use
it. - Developers dont understand what we say we have
to keep explaining the same thing over and over.
8Collaboration Communication
- All experts speak their own language.
- We need to communicate what and why we work out
how together. - Nobody knows the detail Ive seen.
- The data system will change the process.
- Integration takes a long time.
9Exercise in Defining System Requirements
10Definitions
11Dictionary Opinion presented as truth in
alphabetical order.
- John Ralston Saul (1947- ), writer
12BUSINESS GOAL
- Strategic statement of the proposed software
systems responsibility - How will the software system support
accomplishing the business processes?
13SYSTEM PROCESS
- Sequence of events that yields an observable
result of value to a specific actor
14ACTOR
- Entity that interacts with the system to fulfill
the business goal - Person
- Group or organization
- Software system
15CONSTRAINT
- Statement or rule that is externally imposed
16ASSUMPTION
- Statement made about a process that is not based
in fact. - High probability of occurrence
- Some risk that can be assessed and mitigated
17RISK
- Discrete occurrence that can affect the system
development project for better or worse.
18When I make a worddo a lot of work like that,I
always pay it extra.
- Lewis Carroll (1832-1898), Through the Looking
Glass
19Exercise in Defining System Requirements
- Develop goal statement - 5 min.
- Post and discuss processes - 15 min.
20The Exercise Web-Enable Our Pet Grooming Service
- Define business goal in one sentence
- Group activity
- Identify system processes and actors
- Post-it notes on post-it tablet sheets
- Document constraints and assumptions
- Identify risks
- Review/revise processes and actors
21What Are Components of a Good Approach?
22Components of a Good Approach
- Highlights communication and collaboration
- Identifies what and why first, then how
- Lets the system change the process
- Provides an environment where users and
developers are comfortable - Develops interaction, communication, and trust
23Thank you.
- Contact Information
- Sherry Spence, MA
- MCH Data Systems Coordinator
- Oregon Department of Human Services
- Health Services, Office of Family Health
- 800 NE Oregon St., Suite 805
- Portland, OR 97232
- 503-731-4059
- sherry.spence_at_state.or.us
24Oregons Websites
- FamilyNet New Module Prototype
- https//dhs-sphere1d.hr.state.or.us/FCMPro/login.j
sp - DHS Project Management Tools
- http//www.dhs.state.or.us/admin/pmo/
- DHS/HS Office of Family Health http//www.dhs.stat
e.or.us/publichealth/ofhs
25Time for a