Please use this identifier to cite or link to this item: http://hdl.handle.net/20.500.11889/4152
DC FieldValueLanguage
dc.contributor.authorde Lusignan, Simon-
dc.contributor.authorKrause, Paul John-
dc.contributor.authorMichalakidis, Georgios-
dc.contributor.authorVicente, M. Tristan-
dc.contributor.authorThompson, S.-
dc.contributor.authorMcGilchrist, Mark-
dc.contributor.authorSullivan, Frank (Frank M.)-
dc.contributor.authorRoyen, P. van-
dc.contributor.authorAgreus, L.-
dc.contributor.authorDesombre, T.-
dc.contributor.authorTaweel, Adel-
dc.contributor.authorDelaney, B.-
dc.date.accessioned2017-01-17T11:14:27Z-
dc.date.available2017-01-17T11:14:27Z-
dc.date.issued2012-
dc.identifier.urihttp://hdl.handle.net/20.500.11889/4152-
dc.description.abstractObjectives: To perform a requirements analysis of the barriers to conducting research linking of primary care, genetic and cancer data. Methods: We extended our initial data-centric approach to include socio-cultural and business requirements. We created reference models of core data requirements common to most studies using unified modelling language (UML), dataflow diagrams (DFD) and business process modelling notation (BPMN). We conducted a stakeholder analysis and constructed DFD and UML diagrams for use cases based on simulated research studies. We used research output as a sensitivity analysis. Results: Differences between the reference model and use cases identified study specific data requirements. The stakeholder analysis identified: tensions, changes in specification, some indifference from data providers and enthusiastic informaticians urging inclusion of socio-cultural context. We identified requirements to collect information at three levels: micro- data items, which need to be semantically interoperable, meso- the medical record and data extraction, and macro- the health system and socio-cultural issues. BPMN clarified complex business requirements among data providers and vendors; and additional geographical requirements for patients to be represented in both linked datasets. High quality research output was the norm for most repositories. Conclusions: Reference models provide high-level schemata of the core data requirements. However, business requirements’ modelling identifies stakeholder issues and identifies what needs to be addressed to enable participation.en_US
dc.language.isoen_USen_US
dc.subjectMedical informaticsen_US
dc.subjectMedical records - Data processingen_US
dc.subjectPrimary care (Medicine)en_US
dc.subjectPhysicians (General practice)en_US
dc.subject.lcshPublic health records-
dc.subject.lcshInformation storage and retrieval systems - Research-
dc.titleBusiness process modelling is an essential part of a requirements analysis. Contribution of EFMI primary care workingen_US
dc.typeArticleen_US
newfileds.departmentEngineering and TechnologyEngineering and Technologyen_US
newfileds.item-access-typeopen_accessen_US
newfileds.thesis-prognoneen_US
newfileds.general-subjectnoneen_US
item.languageiso639-1other-
item.fulltextWith Fulltext-
item.grantfulltextopen-
Appears in Collections:Fulltext Publications
Files in This Item:
File Description SizeFormat
De Lusignanimia_2012-7-1_17940.pdf899.79 kBAdobe PDFView/Open
Show simple item record

Page view(s)

125
Last Week
0
Last month
2
checked on Mar 25, 2024

Download(s)

37
checked on Mar 25, 2024

Google ScholarTM

Check


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.