ASPEN Data Monitoring System (ADM) ASPEN Training 101/102.
-
Upload
joel-wells -
Category
Documents
-
view
229 -
download
3
Transcript of ASPEN Data Monitoring System (ADM) ASPEN Training 101/102.
ASPEASPENNData Monitoring Data Monitoring System (ADM)System (ADM)ASPEN Training 101/102ASPEN Training 101/102
ADM is also referred to as “ACTS ADM is also referred to as “ACTS Download” because:Download” because:
• ADM’s initial release focuses on ADM’s initial release focuses on “ACTS” complaint data, and“ACTS” complaint data, and
• ADM supports states ability to ADM supports states ability to “download” information from ASPEN “download” information from ASPEN to state databases in a time-to state databases in a time-sensitive mannersensitive manner
Introducing ADM (101/102)Introducing ADM (101/102)
ADM allows states to use ACTS as their primary ADM allows states to use ACTS as their primary complaints management system while complaints management system while minimizing double data entry needed to minimizing double data entry needed to maintain related state complaint systems and maintain related state complaint systems and functionsfunctions
Since ASPEN has no way to directly Since ASPEN has no way to directly communicate with a state’s internal systems, communicate with a state’s internal systems, ADM was created to bridge this gap: ADM was created to bridge this gap: ADM is a ADM is a toolkit that allows state developers to create an toolkit that allows state developers to create an interface between the ASPEN database and their interface between the ASPEN database and their internal state systems and functionsinternal state systems and functions
While the initial ADM release focuses on While the initial ADM release focuses on monitoring ACTS-related data, the design monitoring ACTS-related data, the design permits expansion to additional data categories permits expansion to additional data categories in the futurein the future
About ADM About ADM
ADM may be used to monitor more than twenty different ADM may be used to monitor more than twenty different data entities in the ASPEN database. These include: data entities in the ASPEN database. These include: • ACTS-specific entities such as complaint intake, ACTS-specific entities such as complaint intake,
allegation, complainant, citation and EMTALAallegation, complainant, citation and EMTALA• Selected ASPEN entities such as facility, survey, and Selected ASPEN entities such as facility, survey, and
administrator may also be monitored.administrator may also be monitored. ADM sends electronic alerts to state systems when ADM sends electronic alerts to state systems when
changes occur to monitored ASPEN tables. For example, changes occur to monitored ASPEN tables. For example, ADM can notify state systems whenever a complaint is ADM can notify state systems whenever a complaint is added, updated or removed by ACTS users.added, updated or removed by ACTS users.
ADM does not allow states to change data in the ASPEN ADM does not allow states to change data in the ASPEN database.database.
What ADM DoesWhat ADM Does
ADM: Five Functional Components (See following ADM: Five Functional Components (See following slides)slides)
5)5) Test Tool: Test Tool: An ADM test tool is An ADM test tool is provided. States may use this provided. States may use this tool to connect to the ADM API tool to connect to the ADM API to determine that activated ADM to determine that activated ADM messages are delivered properly messages are delivered properly through the API.through the API.
ADM Component SummaryADM Component Summary
Configuring ADMConfiguring ADM
Once your state determines database events to be monitored and prepares a state application to respond to related ADM messages, you will proceed as follows to configure ADM:
Configuring ADM AlertsConfiguring ADM Alerts
1. From the System menu in ACO, select System Configuration, then ASPEN Data Alert Configuration
Configuring ADM AlertsConfiguring ADM Alerts
This opens ADM’s ACTS Download Table Candidates window.
Configuring ADM AlertsConfiguring ADM Alerts
Note that for each entity, three ADM alert types may be configured:
• Insert – alerts when a new record is added to a monitored entity table
• Update – alerts when a change is made to an existing record in a monitored entity table
• Delete – alerts when a record is removed from a monitored entity table
ADM ScenarioADM Scenario
Problem:
A state’s internal complaint system automatically notifies local law enforcement via fax whenever a complaint with an abuse allegation (Allegation type 01 – Resident/Patient/Client Abuse) is received.
ACTS does not provide fax services, but the state wishes to use ACTS for complaint tracking and avoid double entry into both systems
ADM ScenarioADM Scenario
Solution:
Use ADM to provide an interface between ACTS and automated state fax services as follows:
ADM ScenarioADM Scenario
1. Create state software application interface to ADM API.
2. Activate ADM monitoring for complaint allegations: Open ACO.
Select System Configuration, then ASPEN Data Alert Configuration.
Locate the Complaint Allegation Entity (COMP_ALG) and select the options to monitor Inserts and Update events on this table.
ADM ScenarioADM Scenario
2. Confirm allegation monitoring:
Create a test intake in ACTS, and assign an abuse allegation. Note the intake and allegation IDs.
Activate the ADM test application, and request next message. Confirm correct allegation ID is referenced.
State ComplaintStaff Input Complaint
ACTS
ADM Scenario: Implement ADM Scenario: Implement SolutionSolution
ASPEN Database Generates
ADMMessage
ADM ListenerReceives message
and passes toState application
State ApplicationRetrieves Data and
Sends Fax
FaxServer
Using the ADM Application Using the ADM Application Programming Interface DLL Programming Interface DLL (Training session 102 only)(Training session 102 only)
ADM API name: AspenDataExchange.DLL
This is a standard Windows DLL
The DLL can be called by languages using both ‘unmanaged’ memory as well as the new ‘managed’ .NET memory models:
• Unmanaged languages: Visual Basic, Visual C++, PowerBuilder
• Managed examples: C#.NET
Using the ADM Application Using the ADM Application Programming Interface DLLProgramming Interface DLL
ADM API Functions “callable” by state applications:
• OpenOracleDatabase(): Opens a connection to the CMS QIES database containing ASPEN. This is called once whenever the state application starts-up. Other functions are not available until this function is called and returns a success.
• CloseOracleDatabase(): Closes the Oracle database connection. Called whenever the state application is shutting down.
• GetQueueMessage(): Retrieve the next ASPEN event message from ADM queue.
• CountWaitingMessages(): Counts the number of messages pending in the ADM queue without de-queuing any messages.
• AspenGetLastErrorNumber(): Returns number of last error, if any.
• AspenGetLastErrorMessage(): Returns text of last error, if any.
Understanding ADM MessagesUnderstanding ADM Messages
ADM Messages are delivered to state applications via the ADM DLL
ADM Messages ‘alert’ the state system about a specific change to the ASPEN database
Messages are in XML format
Understanding ADM MessagesUnderstanding ADM Messages
Messages provide the following information about monitored events:
• The name of the monitored entity which triggered the message
• The type of action which triggered the message (Insert, Update or Delete)
• Key field/value pairs defining the unique data row in the entity table which triggered the message.
Understanding ADM MessagesUnderstanding ADM Messages
Example Message: Alert message triggered by change to Complaint Intake entity that is being monitored for UPDATE actions (e.g., modifying an existing intake):
<Message><Table>CINTAKE</Table><Time>11/24/04 04:47:06 P.M.</time><Msg_ID>32012<Msg_ID><Action>UPDATE</Action><Keys>
<Key><Keyname>INTAKEID</Keyname><Keyvalue>CA00014138</Keyvalue>
</Key></Keys>
</Message>
ADM Test ApplicationADM Test Application ADM provides a test application
ADM_Test.EXE
Allows states to . . .
• Determine that ADM is properly configured
• Test that the ADM message queue is active
• Ensure the ADM API is properly delivering messages from the ADM queue
• View both unparsed and parsed (using DOM) XML message structure