This branded term refers to behind-the-user-interface elements that can capture discrete data from user actions.

A key SmartData property is its context, or the level at which the system stores data to the element. Context can be at the level of the patient, a specific encounter with that patient or even a note within an encounter. Patient level data (e.g., past medical history event) should not change for that patient. Encounter level data is updated and overwritten (e.g., anticipated date of discharge) within an encounter but different from encounter to encounter. Note level data can have multiple observations within an encounter (e.g. hospital stay and tracking of pain scores).


SmartData Manager Search Syntax

There are vast numbers of SmartData elements, many with similar names. Consequently, searches using the SmartData Manager can yield large numbers of results. These can be narrowed by using special search syntax options:

  • Data Type

    • Options: string, time, image, number, category, instant, date, boolean, hierarchy, database, elementid, timewithunit

    • Structure: "category:term"

    • Example: "category:pulse" will find SmartData elements that are grouped within a particular conceptual category.

  • SWS

    • Search within search; which can be used after an initial search returns large numbers of elements

    • Structure: "sws:term"

    • Example: "sws:right dp" to seek from the pulses fetch those items related to right dorsalis pedis pulse

  • Category Value

    • Can be added to an existing search line to include a search for values as well as element names

    • Structure: "... categoryvalue: "term"

    • Example: "... categoryvalue: "detected with Doppler"

AHS SmartData Elements