...
The Content Handler module receives data from interface handlers along with the content type of that data. Using this information it is expected to forward data to the appropriate processing module that can handle that data. It is also required to have functionality to allow processing modules to be able to dynamically register and de-register their interest to data of particular content types.
Interfaces
| Code Block |
|---|
| language | java |
|---|
| title | ContentHandlerService |
|---|
|
public interface ContentHandlerService extends OpenMRSService {
/** To be called by interface modules */
ContentHandler getContentHandler(String contentType);
/** To be called by processor modules on startup */
void RegisterContentHandler(String contentType, ContentHandler handler) throws AlreadyRegisteredException;
/** To be called by processor modules on shutdown */
void DeregisterContentHandler(String contentType);
} |
| Code Block |
|---|
| language | java |
|---|
| title | ContentHandler |
|---|
|
/**
* Provided by Content Handler module for implementation by processor modules.
*/
public interface ContentHandler {
void saveContent(Patient patient, String content);
void saveContent(Patient patient, String documentId, String content);
String fetchDocument(String documentId);
String queryEncounters(Patient patient, Date from, Date to);
} |