-
Je něco špatně v tomto záznamu ?
Why do we need an architectural approach to interoperability?
Bernd Blobel, Frank Oemig
Jazyk angličtina Země Česko
- MeSH
- lékařská informatika MeSH
- mezioborová komunikace MeSH
- počítačové systémy * normy MeSH
- systémová integrace MeSH
- zdravotnické informační systémy * normy MeSH
Objectives: Health systems are on the move to increasing complexity, distribution, autonomy, number of domains or disciplines involved, thereby requesting evolution of interoperability to support required communication and cooperation among those systems for meeting intended business objectives. Methods: Information cycle model with its phases and phase transitions as well as systems theory are used to describe structure and processes of healthcare business cases and the interoperability levels for enabling the communication and cooperation between the principals involved. Results: When focusing on interoperability between health information systems acting as principals in an ICT business case, different levels of contribution to the common business case, i.e. phases to the completion of the information cycle, provided by the principals can be distinguished. While the first two levels, sharing data related to the business case, and sharing information derived from those data to define the required business process actions, deal with the communication challenge of interoperability, just the third level of providing the required action according to the business case concerns its operational part. Such service delivery requires appropriate system architecture for meeting the service functional cooperation challenge. When extending the consideration beyond ICT systems towards real world business systems, the architecture of non-ICT systems regarding their structure and behavior must be represented to be shared as required in the business case as well. This system extension requires domain knowledge based interoperability for covering the domain-specific concepts and relations including the constraints to be applied. When not just considering the domain-specific context, but also the context of the individual user, personalized business systems are managed. Conclusions: Advanced healthcare systems require not just communication standards for enabling interoperability, but also multi-domain, ontology-driven interoperability standards based on a generic reference architecture, that is also shortly presented in this paper.
Citace poskytuje Crossref.org
Literatura
- 000
- 00000naa a2200000 a 4500
- 001
- bmc16029738
- 003
- CZ-PrNML
- 005
- 20170406135834.0
- 007
- cr|cn|
- 008
- 161018s2016 xr ad fs 000 0|eng||
- 009
- eAR
- 024 7_
- $a 10.24105/ejbi.2016.12.1.2 $2 doi
- 040 __
- $a ABA008 $d ABA008 $e AACR2 $b cze
- 041 0_
- $a eng
- 044 __
- $a xr
- 100 1_
- $a Bernd, Blobel $u Medical Faculty, University of Regensburg, Germany; eHealth Competence Center Bavaria, Deggendorf Institute of Technology, Germany; HL7 Germany, Cologne, Germany
- 245 10
- $a Why do we need an architectural approach to interoperability? / $c Bernd Blobel, Frank Oemig
- 504 __
- $a Literatura
- 520 9_
- $a Objectives: Health systems are on the move to increasing complexity, distribution, autonomy, number of domains or disciplines involved, thereby requesting evolution of interoperability to support required communication and cooperation among those systems for meeting intended business objectives. Methods: Information cycle model with its phases and phase transitions as well as systems theory are used to describe structure and processes of healthcare business cases and the interoperability levels for enabling the communication and cooperation between the principals involved. Results: When focusing on interoperability between health information systems acting as principals in an ICT business case, different levels of contribution to the common business case, i.e. phases to the completion of the information cycle, provided by the principals can be distinguished. While the first two levels, sharing data related to the business case, and sharing information derived from those data to define the required business process actions, deal with the communication challenge of interoperability, just the third level of providing the required action according to the business case concerns its operational part. Such service delivery requires appropriate system architecture for meeting the service functional cooperation challenge. When extending the consideration beyond ICT systems towards real world business systems, the architecture of non-ICT systems regarding their structure and behavior must be represented to be shared as required in the business case as well. This system extension requires domain knowledge based interoperability for covering the domain-specific concepts and relations including the constraints to be applied. When not just considering the domain-specific context, but also the context of the individual user, personalized business systems are managed. Conclusions: Advanced healthcare systems require not just communication standards for enabling interoperability, but also multi-domain, ontology-driven interoperability standards based on a generic reference architecture, that is also shortly presented in this paper.
- 650 _2
- $a lékařská informatika $7 D008490
- 650 12
- $a zdravotnické informační systémy $x normy $7 D063005
- 650 _2
- $a mezioborová komunikace $7 D033183
- 650 12
- $a počítačové systémy $x normy $7 D003199
- 650 _2
- $a systémová integrace $7 D018511
- 700 1_
- $a Oemig, Frank $u HL7 Germany, Cologne, Germany
- 773 0_
- $t European journal for biomedical informatics $x 1801-5603 $g Roč. 12, č. 1 (2016), s. en3-en9 $w MED00173462
- 856 41
- $u http://www.ejbi.org/img/ejbi/ejbi2016-1.pdf $y domovská stránka časopisu - plný text volně přístupný
- 910 __
- $a ABA008 $b online $y 4 $z 0
- 990 __
- $a 20161018063931 $b ABA008
- 991 __
- $a 20170406140124 $b ABA008
- 999 __
- $a ok $b bmc $g 1168690 $s 954376
- BAS __
- $a 3 $a 4
- BMC __
- $a 2016 $b 12 $c 1 $d en3-en9 $i 1801-5603 $m European Journal for Biomedical Informatics $n Eur. J. Biomed. Inform. (Praha) $x MED00173462
- LZP __
- $c NLK188 $d 20170406 $a NLK 2016-36/vt