Framework di architettura di servizi per la sanita'

       Services framework

Generic services, that will be deployed in the HealthSOAF Framework, implement the following functions:

ücreation, search and retrieval of information resources typical of the clinical and health sectors, patient records and distributed documents (profiles, prescriptions, medical history ...); a set of B2B service interfaces - common, general and decoupled from the semantic content - for management of electronic documents, in accordance with the HSSP RLUS standard;


ü unique identification of the different types of entities (people, organizations, devices, etc.) its social health ecosystem and identifying informations (demographics) management of the various entities, under both operating systems in a single organization , both systems of different organizations that interoperate between them, in accordance with the HSSP IXS standard;

ü manipulation and mapping of terminologies and heterogeneous clinical and health coding (acts, drugs, laboratory tests, pathology, etc. ..), as well as the connections between the different terminologies and coding systems, in accordance with the HSSP CTS2 standard;

ü multi-criteria information search, in a given geographical area and in a specific time window, about organizations and operators, who provide socio-clinical health services (specialists, laboratories, hospitals ...), a sort of yellow pages aid in the management of a diagnostic / therapeutic pathway for the patient, in accordance with the HSSP HSCPD standard;

ü aid to the patient’s clinical and health information protection, in order to cover the security needs such as privacy, control and access management to clinical data, controlling access to social care information to protect the resources present in a distributed environment, where emerging issues of interoperability between the various interacting systems, in accordance with the standard AC and HSSP PASS AUDIT; permit inspection, testing, verification and tracking of privacy violations to the directives of the operations performed within the system.

ü search, query and execution of modules to assist in decisions in the field of clinical health (Clinical Decision Support System - CDSS) using a standardized approach to access to clinical health knowledge, independently from the underlying, embedded in a multitude of executable models of "intelligent" systems, expert systems, decision support systems, knowledge based systems, guidelines, in accordance with the HSSP DSS standard.


and will be



Ø  designed and engineered by performing the reverse formal modeling HSSP specification, their approach Contract-based, model-driven (CMDB) adopted, according to which the description of the services are service contracts - all the rights and duties of regulators and users - multilayer formal models, defined by the Model-Driven Architecture (MDA);

Ø  realized by creating a specific add-on, the new HSSP SOA interfaces, on platforms already in the possession of partners, or ex-novo;

Ø  verified, using the automated black-box testing environment, based on the standardized language Testing and Test Control Notation (TTCN-3), specially designed, implemented and put into operation;

Ø  validated by creating CephalAid, an integrated platform of services and a cooperation and collaboration environment for the optimal management of patients with headache and migraine, in the context of health reality in the italian region Calabria.


The modules corresponding to the services will all have the same structure as "service brick." For each service, the project will implement:

1)    Consumer proxy: the library that facilitates the implementation of the consumer role of the service on a new or pre-existing software;

2)    Provider skeleton: the library that enables the implementation of the service provider role on a new or existing software system, with of course the delivery capacity of the service functions;

3)    Provider system: the system which implements the service functions and the provider role (using the corresponding library Provider skeleton).


Depending on the case, the Provider system will be implemented by creating a specific add-on, the new SOA HSSP interfaces, on the partner’s existing platforms or from scratch.