...
| Code Block |
|---|
<openmrs:htmlInclude file="/dwr/interface/DWREncounterService.js"/>
<openmrs:htmlInclude file="/scripts/jquery/dataTables/css/dataTables_jui.css"/>
<openmrs:htmlInclude file="/scripts/jquery/dataTables/js/jquery.dataTables.min.js"/>
<openmrs:htmlInclude file="/scripts/jquery-ui/js/openmrsSearch.js" />
<script type="text/javascript">
var lastSearch;
$j(document).ready(function() {
new OpenmrsSearch("findEncounter", true, doEncounterSearch, doSelectionHandler,
[ {fieldName:"personName", header:"Patient Name"},
{fieldName:"encounterType", header:"Encounter Type"},
{fieldName:"formName", header:"Encounter Form"},
{fieldName:"providerName", header:"Encounter Provider"},
{fieldName:"location", header:"Encounter Location"},
{fieldName:"encounterDateString", header:"Encounter Date"}
],
{
searchLabel: '<spring:message code="Encounter.search" javaScriptEscape="true"/>',
searchPlaceholder:'<spring:message code="Encounter.search.placeholder" javaScriptEscape="true"/>'
});
});
//The action to take when the user selects an item from the hits in the widget
function doSelectionHandler(index, data) {
document.location = "encounter.form?encounterId=" + data.encounterId + "&phrase=" + lastSearch;
}
//Contains the logic that fetches the results from the server,, should return a map of the form <String, Object>
function doEncounterSearch(text, resultHandler, getMatchCount, opts) {
lastSearch = text;
DWREncounterService.findCountAndEncounters(text, opts.includeVoided, opts.start, opts.length, getMatchCount, resultHandler);
}
</script>
|
The first four html includes are required because they contain the necessary scripts used by the widgets and the css file for improved styling via datatables' support for jquery-ui themes so that the widgets match the active theme on the page.
You call to the server needs to return a map of the results with the following key names:
count: Maps to the count of the total expected number of hits, this is only required for the first call, therefore in your code on the server, it is recommended to check when the start index is 0, you include the count
objectList: Maps to the actual list of hits
notification: Maps to an form of informative or error message you wish to display for the user about the results
searchAgain: Maps to the phrase to search against, when this key is included with a value, the search widget machinery will discard the current results and re run the search against the new specified phrase, a use case for this is if there are no matches to what the user originally entered and you wish to send them back results based on a shorter phrase
Next thing is to initialize the widget and there are 2 ways to do it, the one used above is the one which delegates to a helper function that takes in 4 arguments. Below is the other way:
...