header title imageheader spacer image

Inside This Issue

    VCS Practice Expertise
    Cerner

  • HNA Classic™
  • HNA Millennium
  • Project Management
  • Integration
  • Vitalize Logic Library

 

Cerner Practice Newsletter
Volume 3 Issue 2, Page 2

REQUEST & REPLY RECORD STRUCTURES
By Mark Williams


CCL programs that run within PowerChart execute from the Cerner front end servers. There are record structures in the server that send and receive data. The REQUEST record structure will store data from the active patient’s chart, and is available to the program. The REPLY is an empty record structure that accepts data from the program to create the final display.

• Programs that run from PowerChart Reports use a REQUEST that stores the necessary person_id or encntr_id for the active patient and the printer and dates entered in Prompts at runtime. The REPLY is not necessary in these examples the program creates its own display. • Programs that run from Genviews and Smart Templates use the same REQUEST and a REPLY record structure. The program populates the REPLY text field with text that includes all the formatting for the final display. The server reads the REPLY and creates the final display on the Genview or Template. • Programs that run from Rules use a different REQUEST record structure to identify person_id, encntr_id, order_id, and additional Orders info available in the server before it posts to the database. • Programs that run from Operations use a few options for a REQUEST and have a REPLY record structure. The REQUEST stores info about the program that is set up in the Ops Template. The program populates the REPLY status field with an “F” or “S” to alert the server whether the ops run was a failure or a success.

For additional info on the REQUEST available to a program:

• To obtain information about the Request, turn up logging on the appropriate server (Script Batch for PowerChart Reports/Genviews/Smart Templates/Operations and Discern Expert servers for Rules) in a test domain and echo the definition using “call echorecord(REQUEST)” and/or echo the request number stored in reqinfo->updt_req using “call echorecord(REQINFO)” in your program. Run the program. Review the rtlsrv log files for that server id in “cclsrv go”. • Another option for viewing the REQUEST definition is in DiscernVisualDeveloper (DVDev) open the Request/Reply tab in the Workspace to the left of the DVDev screen. Right click in the window and choose Add/Remove. This brings up a screen to the right for viewing the requests by number or name. If you know part of the name, enter it in the search window (dcp_* or discern_* or sys_* or ccl_*). Check the box to view that REQUEST definition. The REQUEST definition will display in the workspace to the left of the screen.

If you would like further information on this or any other Cerner solutions, please contact us at vcs@getvitalized.com.