Development of the export module Sample Clauses
Development of the export module. The development of the export module was carried out in the following stages: ▪ Restructuring and Normalisation of OpenLabyrinth Database ▪ Analysis of existing OpenLabyrinth MVP export methods ▪ Development of MVP Export Prototype ▪ Refining and finalisation of Export Requirement ▪ Object Orientated Coding with C#.NET o VirtualPatientData XML (All containing elements, subelements with attributes implemented as Serializable/Deserializable Class objects) o ImsManifest XML (All containing elements, subelements with attributes implemented as Serializable/Deserializable Class objects) o ActivityModel XML (All containing elements, subelements with attributes implemented as Serializable/Deserializable Class objects) o DataAvailabilityModel XML (All containing elements, subelements with attributes implemented as Serializable/Deserializable Class objects) o Metadata XML (All containing elements, subelements with attributes implemented as Serializable/Deserializable Class objects) ▪ Assembled MVP test Packages ▪ Unit and Integrated Testing of Export Module with the Assembled Test Package ▪ Deployment of Export Module
Development of the export module. All elements of the MedBiquitous profile are implemented as Java classes and castor mapping files. When exporting a Casus case is loaded from the database and the Casus case model is converted into the MedBiquitous model. This model is marshalled and the created xml files are zipped.
Development of the export module. The export module was a developed over a longer period of time. The first version of the MVP supported by the Web-SP import/export tool included only the virtualpatient data xml. The technical/architecture approach adopted is very similar to the way Casus is exporting their VPs (reported earlier in this document)