{'fraction_non_alphanumeric': 0.016333938294010888, 'fraction_numerical': 0.0, 'mean_word_length': 5.093922651933702, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Resilient Software Architecture Platform for the Individual Care Plan

The individual care plan (ICP) is a metamorphic being. The only steady reality that it maintains is its final objective, stated and explained in the previous chapter where the ICP is thoroughly introduced and debated. It is a fantastic beast, better described as a system of systems that is severely polymorphic due to its coverage both in level of care as well as sources of data to handle. Patient monitoring generates large volumes of data. There is the evident need of an advanced approach that can deal with these huge amounts of healthcare data extracted from various sources such as the wearable sensors, medical, and nursing records that are currently called big data. The purpose of this chapter is to introduce and discuss the software platform that is adequate to develop and deploy the system paying attention to the needs of high-availability, sensitive information security; service-level agreements for multiple healthcare interoperability; law and ruling conformance; as well as other technical and ethical aspects.