anthropos – the social co-operating system
The pumpco citizen platform is built on a completely new type of technology, a “social co-operating system” we have called anthropos.
anthropos is a specialist platform, designed from the ground up to support a new generation of citizen-owned, personalised systems of all sorts, operating seamlessly across all sectors and settings and harnessing the most leading-edge technologies in each domain.
This entirely new type of software platform, of the scale of a distributed operating system, is specifically focused on connecting people, their devices, families, friends and communities and service providers and their systems across sectors, to enable everyone and everything to communicate and work together effectively around the individual.
technology supplier collaboration
In addition, the unique architecture of the platform enables multiple third-party suppliers, not just to rapidly produce apps and services which connect up, but which co-operate with each other and make best use of the advanced facilities of the platform and enabling each supplier to deliver their distinctive value added contribution to an integrated and coherent user experience.
cross sector & sector-specific
The raison d’etre of anthropos is to enable cross-sector, multi-professional and inter-organisational collaboration, but this does not mean it caters to the lowest common denominator, but rather provides the basis of a number of specialised plugin layers, which provide specific functionality required for particular domains.
For example, healthpump is a health and wellness-specific layer and illustration shows how the layers fit together:
generic, but personalised
On top of anthropos and the vertical plugin layers, each ecosystem has their own specific plugins, providing a user experience tailored to the needs and preferences of its community as is illustrated by “our neighbourhood” in the example above.
What is even more important however is that each user has their own system, which they and their collaborators can tailor to their unique set of needs and preferences.
There is no concept of an “one size fits all”, universal panacea, which does all things for all men, but rather a unifying principle that each user only has what they really need, with the result that each person’s system is as simple as possible and as unique as they are.
fractal patterns => rapid development & extensibility
common architectural patterns extended by plugins – at every level
The architecture was designed to be extensible from the ground up, being layered, with each layer plugging into the layer below and specialising the platform to specific uses.
The same architectural patterns are used at all levels from the micro to the macro (hence fractal) enabling maximum flexibility and extensibility, with each layer building on the layers below, minimising redundant complexity.
This is true of the plugin pattern, enabling plugin Apps, services and components, which themselves can be extended by plugins.
Apps are assembled from simple reusable building blocks, which abstract the difficulties from developers, enabling complex applications and workflows to be built very quickly.
App building blocks provide core functionality around keeping in touch (e.g. contacts, groups, universal communications), sharing information (e.g. profile, books, journal, backpack, resource centre), coordination (e.g. appointments, actions, planner, availability, self-service booking, reminders, virtual assistants), collaboration (e.g. questionnaires, assessments, plans, workflow, monitoring rules, notifications, alerts, achievements) as well as access to all the infrastructural services.
APIs at every level
Although many architectural and development patterns are entirely new, existing patterns have been employed wherever relevant, such as the enterprise integration patterns, which have also been implemented in their entirety and are embedded in the core.
The result is a platform of unparalleled flexibility, enabling extremely rapid development.
loosely-coupled, federated and event-based
The anthropos architecture is extremely loosely-coupled, federated and event-based and runs co-operatively across cloud servers, personal computers and mobile and personal devices of all sorts
This unique architecture enables each component at every level to co-operate with each other without even being aware of each others existence. This permits every component to be extended individually, or even completely substituted, without impacting any others.
open and embracing third-parties
Not only does this make it easy for pumpco developers to further develop and extend the Apps, services and components of anthropos and healthpump (and its sister vertical platforms, such as justicepump), but it extends these benefits to those built by third parties, enabling their apps and components to interoperate as first class elements of any solution.
As well as interoperability, anthropos takes care of the really difficult things (e.g. massive scaleability, heterogenous data semantics, distributed configuration management, intelligent agents) it also offers a number of immensely flexible and integrated core building blocks, which can be leveraged, rather than duplicated, to make it really easy for other developers to make use of the platform to contribute their unique pieces of the jigsaw and get their ideas into the hands of those who might benefit from it as quickly and simply as possible.
existing systems integration
As well as enabling co-operation between apps and services designed to make best use of the anthropos platforms, it is equally possible to integrate systems, which were never designed to integrate, let alone cooperate with third party systems.
To enable systems already in use to be integrated into the architecture, adapters are used as protocol converters and translators, to wring the most benefit from their interoperability.
Interoperability with professional systems
For standards-compliant clinical systems, HL7 V2 & V3 messaging may be used for bi-directional transactional communications and IHE Cross-Domain Document Sharing for bilateral sharing of document-based data (including HL7 v3 CDA documents) between the citizen platform and compliant clinical systems.
Standard clinical terminologies such as SNOMED CT, coding systems and classifications are also used where appropriate.
Interoperability with cloud services
We have linked up to a wide variety of different cloud services to pull down data, mash data together and send data back.
Secure integration with third party systems such as Facebook, Twitter or iHealth, for example, is possible through the use of the OAuth v1 & v2 standards for authentication. It is similarly possible for third-party services and devices to authenticate directly with anthropos using OAuth.
In the world of messaging, in addition to mail and SMS interoperability, we have also employed the extensible message and presence protocol standard (XMPP) to enable interoperability with popular instant messaging services (e.g. google talk, facebook chat, jabber), the many 3rd party desktop and mobile clients, as well as third party audio-visual hardware and services from Cisco and their partners.
Interoperability with devices
In the device world, anthropos integrates those which expose standard and proprietary APIs and even those which expose no interface at all, across various protocols including for example, several different bluetooth profiles, ZigBee, low-level USB and web services of various sorts.
Interoperability with the resistent
Where devices or services were never designed to interoperate and do not expose interfaces of any kind, pumpco developers have also been able to successfully reverse engineer APIs, using techniques more typically associated with digital forensics, in order to interoperate with them, making most of existing assets and unlocking possibilities, previously considered impractical.