Assessment (technical) on the use cases work out on Stork and Trillium Bridge
Issue to be assessed
STORK
- JavaScript integration into default OpenNCP portal portlet successfully demonstrated
- form auto filling (epSOS International Search Mask) as a convenience tool for the HP up and running -> patient identifiers are extracted from card and automatically filled in the search mask
- Clarification: the OpenNCP team mentioned operational issues by PN using many different portals; thus constraining the adequateness of one generalized portlet, to be discussed with group
- OpenSTORK Home (OpenNCP documentation);
- Isabel Cruz, can provide more input (informally);
Trillium Bridge
- Ask Alexander Berler (Unlicensed) and Kostas Karkaletsis...
Preliminary technical assessment of OpenNCP branches created for Trillium Bridge and STORK use cases: the branches are confined to the OpenNCP Portal and CDA Display Tool. These are closely connected to OpenNCP, but are not part of the main functionality related to message passing and other backbone technical infrastructure. Kostas Karkaletsis has more knowledge about the technical implementation of the OpenNCP Portal and perhaps could assess the possibility of merging the Trillium Bridge branch to the master branch.
Isabel Cruz confirms that for STORK use cases the changes were confined to OpenNCP Portal. Plugin for loging in (for Patient and HealthProfessional) on the OpenNCP Portal; Isabel Cruz will check if is a Liferay plugin or there are any other changes.
- Stéphane Spahni is using and testing the implementation of the plugin, but seems that some documentation is missing on the Stork DEMO.
- No need to merge.
Alexander Berler (Unlicensed) confirms that Trillium Bridge changes are confined to "OpenNCP Portal and CDA Display Tool"
- No need to merge.
Recommendation
- TODO (4): TelCo with OpenNCP team on February, 2nd to consolidate integration approach and technology into “official” e-SENS/OpenNCP fork
Related references