1 / 13

CDS Field Attributes

CDS Field Attributes. CDS provides users the mean to collect additional patient information that are not available through standard screens. Field attributes provide users the mean to validate and control these data. There are four basic types of field attributes :

hoang
Download Presentation

CDS Field Attributes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CDS Field Attributes

  2. CDS provides users the mean to collect additional patient information that are not available through standard screens. Field attributes provide users the mean to validate and control these data

  3. There are four basic types of field attributes : 1. DFT : Default Attribute 2. REQ/REQI : Required Attribute 3. IFE : Conditional Attribute 4. FCLn/FCLnA : Field Check Attribute

  4. 1. DFT : Default Attribute Provide default value for the query Syntax : DFT = [value]

  5. 1. DFT : Default Attribute 2. REQ/REQI : Required Attribute Determine if the response to a query is required. REQ (Required) is checked when the user files the data REQI (Required Immediately) is checked when the user moves to the next field Syntax : REQ = [expression] or REQI = [expression]

  6. 1. DFT : Default Attribute 2. REQ/REQI : Required Attribute 3. IFE : Conditional Attribute Defines a requirement that must be satisfied by previously-entered data in another response field. If the previous response DOES NOT satisfy the condition, the cursor skips the response field. Syntax : IFE = [expression]

  7. 1. DFT : Default Attribute 2. REQ/REQI : Required Attribute 3. IFE : Conditional Attribute 4. FCLn/FCLnA : Field Check Attribute Evaluates a response (FCLn) and initiates an action (FCLnA) (n is an integer, represents the number of field check) Syntax : FCLn = [expression] FCLnA = [expression]

  8. Example : We have two queries : Query Mnemonic : QRY_1 Question : Do you take vitamin ? Response : [Y/N] Query Mnemonic : QRY_2 Question : What type ? Response : [TEXT]

  9. QRY_1 : Do you take vitamin ? [Y/N] QRY_2 : What type ? [TEXT] We want : 1. Default answer for QRY_1 is “Y” 2. Make QRY_1 a required field 3. Make QRY_2 a required field ONLY if the answer to QRY_1 is “Y” 4. Skip QRY_2 if the answer to QRY_1 is “N” 5. Valid responses to QRY_1 are “n”, “N”, “y”, “Y”. Anything else should result in an error message.

  10. QRY_1 : Do you take vitamin ? [Y/N] QRY_2 : What type ? [TEXT] Solution : Q1 : Default answer to QRY_1 is “Y” A1 : Place DFT = “Y” on QRY_1 Q2 : Make QRY_1 required field A2 : Place REQ = “Y” (or REQI = “Y”) on QRY_1

  11. QRY_1 : Do you take vitamin ? [Y/N] QRY_2 : What type ? [TEXT] Solution : Q3 : Make QRY_2 a required field ONLY if the answer to QRY_1 is “Y” A3 : Place REQ/REQI = [ANS,QRY_1]|0 = “Y” on QRY_2 Q4 : Skip QRY_2 if the answer to QRY_1 is “N” A4 : Place IFE = [ANS,QRY_1]|0 = “Y” on QRY_2

  12. QRY_1 : Do you take vitamin ? [Y/N] QRY_2 : What type ? [TEXT] Solution : Q5 : Valid responses for QRY_1 are “n”, “N”, “y”, “Y”. Anything else should result in an error A5 : Place FCL1 = (@.response’=“n”)&(@.response’= “N”) &(@.response’=“y”)&(@.response’=“Y”) FCL1A = @W.err(“Invalid response. Y/N only”)

  13. The End Thank you

More Related