
 
information covering all other recording, including 
those ones originated outside the organization (e.g. 
letters, emails or notes of meetings).  
Since the service models employed by health 
care providers and social care providers are different 
there are important differences between EHR and 
ESR: healthcare records are focused on a single 
patient, often with considerable details and depth, 
and the confidentiality of the individual is strongly 
protected, while social care records, on the other 
end, place the individual in their daily living context 
of family and other informal carers, including the 
attitudes and effects on each, so as to ensure mental 
support and understanding (Rigby, 2012). 
Since the empowerment of each citizen also 
means that he or she should be able to contribute 
with documentation, namely observations of his or 
her daily living (Bos, 2012), PHR have, nowadays, 
an increasing importance. They include data and 
information related with the individuals’ lifetime 
and individuals’ care maintain by each individual. 
Furthermore, PHR can represent more than a 
repository for the individual data, because they are 
able to combine data, information, knowledge and 
tools to help any individual to be proactive in their 
own care (Schloeffel, 2003). This stands in contrast 
with EHR, which are operated by organizations and 
contains data entered by professionals.  
The information on a PHR might include patient-
reported outcome data, laboratory results, and data 
from a broad range of devices. For instance, 
important data sources are wearable remote 
monitoring systems with sensors to capture 
physiological parameters such as electrocardiogram 
(ECG), blood pressure, body temperature or heart 
rate. These devices are particularly important for 
home care and are one of the research investments of 
the promising AAL developments (Queirós et al., 
2012). 
4 CONCEPT 
The AAL environments can increase or maintain the 
individuals’ performance in a broad spectrum of 
activities and participation. Furthermore, AAL 
systems should acquire context information and 
combine multiple sources of information and make 
pattern-based predictions to be able to track the 
individuals (e.g. localization, activities or 
behaviours). 
Another range of AAL services are related with 
biomedical devices that can be implemented and 
used both in clinical settings and in persons’ home, 
smoothing the transition between both environments 
(Blobel, 2010). 
Since information is a requisite for high quality 
care services and also for the empowerment of the 
citizens’, the potential of AAL services can be 
increased, if there is the possibility to create the 
conditions to integrate both user-generated data and 
AAL services-generated data with institutional EHR 
and ESR, so that care can be more integrated, 
personalized and useful for citizens. Consequently, 
there is the need that AAL infrastructures should 
support information architectures that enable the 
creation and maintenance of information objects, 
according to the requirements and needs of a wide 
range of users and care providers. 
Due to the difficult to accommodate the 
development of new applications in poor structured 
contexts (Heeks, 2006), open management 
information paradigms (Yli-Hietanen and Niiranen, 
2008) are required with robust and stable domain 
models separated from the implementations and able 
to specific adaptation. In this respect, we argue that 
AAL information architectures should follow an 
open management information paradigm, with two 
modelling levels for the information structure: the 
information model and the knowledge model. 
The first level, the information model, embraces 
all data types that are required to record the pertinent 
information. It is the fundamental model required for 
the technical implementation and, therefore, must be 
stable over time in order to be maintainable. On the 
other end, in the second level, the knowledge model, 
domain and application specific concepts are 
modelled (archetypes) with constraint rules to 
specialize the underlying information model. 
According to this approach, archetypes are instances 
of an object oriented system implementation, which 
means they can be created and manipulated by 
adequate tools and alter as desired, without changing 
the underlying information technical specifications.  
The concept was validated by defining a data 
repository (i.e. the information model), accordingly 
to HL7 RIM and a set of functions for the 
management of the archetypes, in order to shape the 
HL7 RIM to specific application domains (i.e. the 
knowledge model).  
For the specification of the data repository we 
select the HL7 RIM. Thus, data repository is 
characterized by being a generic container and it is 
necessary to evaluate whether this container is 
adequate to accommodate all information objects 
that can be associated with AAL services. 
The followed validation procedure consisted in 
the creation of scenarios, emphasizing not only the 
AALInformationbasedServicesandCareIntegration
405