There are, however, some benefits to following the SanteDB user interface elements. The applets which are readily available for use are:
AngularJS based core UI components (provides controls listed on AngularJS page)
BI core functions for rendering reports generated by the Business Intelligence Services layer.
Core configuration screens for the key functions of the SanteDB client.
SanteDB administrative panel
Registers the English Language assets
Registers the French Language assets
Registers the Spanish Language assets
Registers the Swahili Language asset
The only required file for an applet is the Manifest.xml file. This file is used by the packager to generate a bundle manifest. The manifest file contains:
Metadata information such as applet author, version, dependencies, etc.
Translations / String definitions for any languages your applet displays
Menu registrations for extending the UI menus
Error asset registrations which are rendered in-lieu of stock error pages
View model definitions for instructing the API which attributes should be "deep loaded"
Data setup instructions which are used to insert special data elements which are (not synchronized on the server).
Note: This is a legacy function, you should instead use dataset files in the Data/ directory
Configuration settings which your applet or other plugins use to customize the core engine features.
Template registrations which indicate templates you can use for constructing / pre-populating objects.
Certain plugins built into SanteDB will look for particular files to be placed in particular paths.
Any folders beginning with a . are ignored. The .ref directory is typically used to store references for code-completion.
The bi definitions folder is scanned by the Business Intelligence service on startup, and BI assets are registered for use (for reporting, creating FHIR MeasureReports, executing ad-hoc data queries, etc.)
The data folder is scanned on startup by the dataset installer and any dataset files present in this folder are installed to the server's database.
The view models folder contains view model definitions which are used to deep-load data.
Clinical Decision Support
The protocols folder is scanned by the clinical decision support engine and provides the master list of protocols to be executed by the CDSS engine.
Business Rules Engine
The matching engine configuration directory is used to configure the SanteDB matching engine.