Sound Principles Sound Principles properly applied really do bring project success Presentation by Alec Fearon CEng FIEE Presentation by Alec Fearon CEng FIEE to to The Second International The Second International Performance Management Performance Management Symposium Symposium 7 – 10 October 2003 at RUSI London 7 – 10 October 2003 at RUSI London
60
Embed
Sound Principles properly applied really do bring project success Presentation by Alec Fearon CEng FIEE to The Second International Performance Management.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Sound PrinciplesSound Principles
properly applied really do bring project success
Presentation by Alec Fearon CEng FIEE Presentation by Alec Fearon CEng FIEE toto
The Second International The Second International Performance Management Performance Management
SymposiumSymposium 7 – 10 October 2003 at RUSI London7 – 10 October 2003 at RUSI London
The CollaboratorsThe CollaboratorsCore project teamled by Dr Nick Gaunt
Health Record expertsled by Dr Dipak Kalra
Domain specialistsled by Dr Stan Shepherd
Enabling technologies
gatekeepergatekeeper into lifelong record
ProtectProtect the data in its care
ControlControl role-based access
to single, unified recordsingle, unified record
though content content may bemay be federatedfederated
guardianguardian of care pathway
Custody of rulesrules
Co-ordinateCo-ordinate workflowworkflow of organisations
Generate alertsalerts in response to health events
Evaluate quality of individual carequality of individual care
Report against NSF standardsNSF standards
Concept of OperationConcept of Operation
primary purposeprimary purpose
prototypingprototyping
involving involving local local stakeholdersstakeholders
scenario-driven scenario-driven role play role play
user requirements user requirements
for an for an
Electronic Health RecordElectronic Health Record
proof of conceptproof of concept
How to synthesise an EHR How to synthesise an EHR
Patient consentPatient consent
Role-based accessRole-based access
Patient interactionPatient interaction
Workflow co-ordinationWorkflow co-ordination
Stevens, Brook, Jackson, ArnoldSystems Engineering: coping with complexity
The CollaboratorsThe CollaboratorsCore project teamled by Dr Nick Gaunt
Enabling technologies
Health Record expertsled by Dr Dipak Kalra
System Integrators
Financial ControlFinancial ControlTo this end, I have imposed a To this end, I have imposed a moratorium on all expenditure that moratorium on all expenditure that does not have my express does not have my express authorisation. authorisation. This authorisation will normally be This authorisation will normally be given against costed Statements of given against costed Statements of Work Work and will also require compliance with and will also require compliance with the procurement policy described in the procurement policy described in the Project Management Plan v2.1.the Project Management Plan v2.1.
System connectivity over System connectivity over the Internetthe Internet
Issue ManagementIssue Management
AchievementAchievementS Devon built a demonstrator populated with real though pseudonymised patient data which proves the design concepts.
They are the only ERDIP site to have applied informatics theory best practice in what appears to be an operable systems design.
They have created a series of care pathway scenarios …
Source: ERDIP National Evaluation by PA Consulting Group
1 of 21 of 2
AchievementAchievement
• capable of being used operationally
• that can be tailored to operate either under the toughest consent management rules, or under more easily operable but less granular levels of control over consent.
In respect of patient consent, they have …. designed and built a system:
Given the complexity of the issue, this is a remarkable achievement.
Source: ERDIP National Evaluation by PA Consulting Group2 of 22 of 2
Concept Assessment Demonstration Manufacture In ServiceAccept Disposal
Userrequirements
definition
Componentdesign, build & test
Installation &validation
Systemsrequirements
definition
Architecturaldesign Integration &
verification
Relativeeffort
Scalability & TailoringScalability & Tailoring
Use Case Use Case TemplateTemplate
Use Case Use Case DiagramDiagram
ArchitectingArchitectingMust start with Operational ConceptMust start with Operational Concept
abstractabstractthenthenspecificspecific
based on a based on a simple idea of simple idea of how the how the overriding goal overriding goal is to be metis to be met
drives the Functional and Physical Architecturesdrives the Functional and Physical Architectures
Dr. Alexander H. Levis, Chief Scientist of the US Air Force
[1] Eberhardt Rechtin Systems Architecting: Creating and Building Complex Systems[2] IEEE STD 610.12[3] Dr. Alexander H. Levis, Chief Scientist of the US Air Force