{"text_format":"1","workbook":"xlsx","n_sheets":18,"sheets":["CHANGES","Example","message_validation_service_type","proxy.tm_testinstance","proxy_type","tm_step_instance_exec_status","tm_step_instance_message","tm_step_instance_msg_validation","tm_test","tm_test_instance","tm_test_instance_exec_status","tm_test_steps","tm_test_step_instance","tm_test_step_message_type","tm_testing_session","tm_testing_session_type","validation_service_type","validation_status"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"CHANGES","index":0,"n_rows":16,"n_cols":4,"rows_kept":16,"cut":false,"hidden":false,"merged":[[15,0,15,1]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:","2013-11-04"]
[]
[]
["Version","Description","Changed By","Date"]
[1,"First draft","Tareq Nabeel","2013-07-05"]
[2,"Gazelle-based","Tareq Nabeel","2013-10-21"]
[3,"Corrected tm_test_instance_exec_status and tm_step_instance_exec_status enums.","Tareq Nabeel","2013-10-24"]
[4,"Created testing_session_type entity","Rizwan Tanoli","2013-11-04"]
[]
[]
[]
[]
[]
[]
["The worksheets are ordered alphabetically.  New columns and tables are highlighted by the color:"]

{"sheet":"Example","index":1,"n_rows":8,"n_cols":7,"rows_kept":8,"cut":false,"hidden":true,"merged":[[3,1,3,6]]}
["Hurrys - Store System - Data Dictionary",null,null,null,"Copyright (C) CRaG Systems 2006"]
["Printed On:",{"$f":"NOW()","v":""}]
[]
["Product","An item in the cataloque of products that are available for purchase by a customer"]
["Data Member Name","Description","Type","Additional Type Information","Defult Value","Mandatory?","Unique?"]
["Product Number","The unique identifier of the item in the catalogue","Integer","00000000 to 99999999, always 8 digits including leading zeroes",0,"Yes","Yes"]
["Description","Short description of the product for customer consumption","Character","min:1, max:256","null","No","No"]
["Unit Cost","The current list price of the product","Currency","GBP min £0.00 max £1000000.00","null","Yes","No"]

{"sheet":"message_validation_service_type","index":2,"n_rows":9,"n_cols":8,"rows_kept":9,"cut":false,"hidden":false,"merged":[[3,1,3,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["message_validation_service_type","New intermediate table (link table) for many-to-many relationship between tf_hl7_message_profile and validation_serivce_type tables.   A given tf_hl7_message_profile can have multiple validation service types (Gazelle EVS, NIST HL7) offered to test editor to choose from."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["tf_hl7_message_profile_id","The tf_hl7_message_profile","int","Yes","No","evs, nisthl7",null,"Foreign-key to tf_hl7_message_profile"]
["validation_service_type_id","The validation service type","int","Yes","No",null,null,"Foreign-key to validation_service_type"]
["validation_service_url","The path to the validation service","varchar(1024)","Yes","No",null,null,"The web-service URL path that's specific for this message type and validation service type.  It will not include the host name or IP address of the server hosting the validation service tool."]

{"sheet":"proxy.tm_testinstance","index":3,"n_rows":9,"n_cols":9,"rows_kept":9,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["proxy.tm_testinstance","Existing table in proxy DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["date","The time the record was created","No","int","Yes","No","evs, nisthl7",null,"Foreign-key to tf_hl7_message_profile"]
["tmid","The tm_test_instance id in the gazelle database","No","int","Yes","No",null,null,"Foreign-key to validation_service_type"]
["status","Inactive(0) or Active(1).","Yes","int","Yes","No","0,1",null,"Used to filter out old test instances that are no longer in Running/Waiting state.  When test instances are make inactive (paused, interrupted, aborted) by TEE or by user, then this column value will be updated to 0 for that test instance."]

{"sheet":"proxy_type","index":4,"n_rows":17,"n_cols":8,"rows_kept":17,"cut":false,"hidden":false,"merged":[[3,1,3,7],[14,1,14,7],[15,1,15,7],[16,1,16,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["proxy_type","New look-up table for all possible proxy types that can be used to intercept messages from initiators and responders.  Gazelle might be switched to use a different Proxy type in the future."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","varchar(45)","Yes","Yes","gazelle, nist"]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","varchar(45)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["gazelle","Gazelle Proxy (what is currently being used)."]
["nist","NIST Proxy"]

{"sheet":"tm_step_instance_exec_status","index":5,"n_rows":24,"n_cols":8,"rows_kept":24,"cut":false,"hidden":false,"merged":[[3,1,3,7],[14,1,14,7],[15,1,15,7],[16,1,16,7],[17,1,17,7],[18,1,18,7],[19,1,19,7],[20,1,20,7],[21,1,21,7],[22,1,22,7],[23,1,23,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_step_instance_exec_status","New look-up table for all possible execution statuses that a tm_test_step_instance could go through."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","varchar(45)","Yes","Yes","inactive, waiting, interrupted, skipped, paused, aborted, initiated, responded, completed",null,"Waiting is supposed to replace Running.  \n\nRunning implies that the message is being processed.  Waiting implies that the system is waiting for exchanges to occur and is a more accurate indication of what’s going on.\n\nSo the correct keys are:\ninactive, waiting, interrupted, skipped, paused, aborted, initiated, responded, and completed.\n\nThe happy path would be inactive --> waiting --> initiated --> responded --> completed."]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","varchar(45)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["inactive","Not active yet."]
["waiting","Active but no messages have been intercepted yet from sender and receiver."]
["interrupted","The test step instance was stopped by the system after it had become active at one point."]
["skipped","The test step has been skipped by the participant."]
["paused","The test step has been paused by the participant after it had become active."]
["aborted","The test step has been aborted by the participant after it had become active."]
["initiated","A request message has been intercepted."]
["responded","A response message has been intercepted."]
["completed","The test step instance is complete."]

{"sheet":"tm_step_instance_message","index":6,"n_rows":18,"n_cols":8,"rows_kept":18,"cut":false,"hidden":false,"merged":[[3,1,3,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_step_instance_message","New table that maps the intercepted Proxy message with a tm_test_step_instance row.  It also keeps track of message validation results via its relationship to tm_step_instance_msg_validation table."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["proxy_msg_id","Value of the pxy_abstract_message Id in the Proxy database.","int","Yes","Yes",null,null,"Cannot create foreign key constraint to another database"]
["proxy_type_id","The type of Proxy we're using.","varchar(255)","Yes","Yes",null,null,"Foreign key to proxy_type e.g. Gazelle Proxy, NIST Proxy, etc."]
["direction","Request(0) or Response(1)","int","Yes","No","0,1",null,"This will give context to sender_tm_config_id and receiver_tm_config_id and thereby help in determining whether or not the system has received all expected exchanges."]
["tm_test_step_instance_id","The resolved step_instance","int","No","No",null,null,"Foreign key to tm_test_step_instance table"]
["tm_test_step_message_type_id","The resolved message type","int","No","No",null,null,"Foreign key to tm_test_step_instance_message table.  We could derive it from direction and tm_test_step_instance but storing the key here for better performannce.  Needed for message validation.  Message Type and the type of Validation Service and the URL to the service are all stored in tm_test_step_message_type."]
["sender_tm_configuration_id","The sender's tm_configuration","int","No","No",null,null,"Foreign key to tm_configuration table.  The gazelle DB tm_configuration row that corresponds to the sender of the message e.g. The sender for PIX Feed would be initiator tm_configuration.  From tm_configuration, we can find the Actor, Host, Syste in Session, and System.\nIt is important to track the sender and receiver tm_configs in order to determine when a test_step_instance can be marked COMPLETED."]
["receiver_tm_configuration_id","The receiver's tm_configuration","int","No","No",null,null,"Foreign key to tm_configuration table.  The gazelle DB tm_configuration row that corresponds to the receiver of the message e.g. The receiver for PIX Feed would be responder tm_configuration."]
["last_changed","The time the record was created/updated.","datetime","No","No",null,null,"The date and time at which this record was last modified.  Note that this record will be updated at various times during TEE processing (creation, message type resolution, tm_test_step_instance resolution, validation etc.)"]
[]
[]
["Notes:"]
["We might need to store Proxy DB Host Name as well as the proxy_msg_id will have context/meaning only within a certain proxy database."]

{"sheet":"tm_step_instance_msg_validation","index":7,"n_rows":11,"n_cols":8,"rows_kept":11,"cut":false,"hidden":false,"merged":[[3,1,3,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_step_instance_msg_validation","New intermediate table (link table) for many-to-many relationship between tm_step_instance_message and message_validation_service_type tables.   Each message (request and response) for a given test step instance can go through validations with different validation services (NIST HL7, EVS, etc.)"]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["tm_step_instance_message_id","The tm_step_instance_message","int","Yes","Yes",null,null,"Foreign key to tm_step_instance_message"]
["message_validation_service_type_id","The message_validation_service_type","int","Yes","Yes",null,null,"Foreign key to message_validation_service_type"]
["validation_report","The full validation report","blob","No","No",null,null,"This would be the output of the web service call to the validation service."]
["validation_status_id","The validation status","int","No","No",null,null,"Foreign key to validation_status table."]
["last_changed","The time the record was created/updated.","datetime","No","No",null,null,"The date and time at which this record was last modified."]

{"sheet":"tm_test","index":8,"n_rows":7,"n_cols":9,"rows_kept":7,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test","Existing table in gazelle DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["auto_complete","Whether or not the TEE will mark the test instances as Complete when they complete.","Yes","boolean","Yes","No","TRUE, FALSE",{"$f":"TRUE()","v":true},"When all of the test step instances in a test instance have reached final status (aborted, skipped, complete, etc.), the TEE can mark the Test Instance as complete.  This flag will control whether TEE should do that or not."]

{"sheet":"tm_test_instance","index":9,"n_rows":9,"n_cols":9,"rows_kept":9,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test_instance","Existing table in gazelle DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["tm_test_id","Test Definition","No","int","Yes","No"]
["last_status_id","The test instance status","No","int","Yes","No",null,null,"Foreign-key to tm_status table.  Can take on the values: started, completed (To be Verified), paused, verified, aborted, partially verified, failed, critical.  These statuses should be changed only by the verifier."]
["execution_status_id","Execution status","Yes","int","Yes","No",null,null,"Foreign-key to tm_test_instance_exec_status.  The execution status of the test instance.  Values would be changed by TEE automatically and by participant."]

{"sheet":"tm_test_instance_exec_status","index":10,"n_rows":22,"n_cols":8,"rows_kept":22,"cut":false,"hidden":false,"merged":[[3,1,3,7],[14,1,14,7],[15,1,15,7],[16,1,16,7],[17,1,17,7],[18,1,18,7],[19,1,19,7],[20,1,20,7],[21,1,21,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test_instance_exec_status","New look-up table for all possible execution statuses that a tm_test_instance could go through."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","varchar(45)","Yes","Yes","inactive, active, interrupted, skipped, paused, aborted, completed"]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","varchar(45)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["inactive","Not active yet."]
["active","One or more test step instances are in active status (waiting, initiated, responded)."]
["interrupted","The test instance was stopped by the system after it had become active at one point."]
["skipped","The test instance has been skipped by the participant."]
["paused","The test instance has been paused by the participant after it had become active."]
["aborted","The test instance has been aborted by the participant after it had become active."]
["completed","The test instance is complete."]

{"sheet":"tm_test_steps","index":11,"n_rows":17,"n_cols":9,"rows_kept":17,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test_steps","Existing table in gazelle DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["message_type","The message type","No","varchar(45)","Yes","No",null,null,"ADT_A01 or ADT_A08 or ADT_A40 for PIX Feed.\nUnforunately, this column is free form.  It should have been a foreign key to tf_hl7_message_profile table."]
["transaction_id","The transaction","No","int","Yes","No",null,null,"Foreign-key to tf_transaction table which would have ITI-8 for PIX Feed."]
["test_roles_initiator_id","The initiator role for the test","No","int","Yes","No",null,null,"Would ultimately resolve (via the link table tm_test_roles and ultimately tm_role_in_test) to PAT_IDENTITY_SRC-PIX or PIX_MGR-PIX."]
["test_roles_responder_id","The responder role for the test","No","int","Yes","No"]
["auto_triggered","Whether or not to start the step instance automatically","Yes","boolean","Yes","No","TRUE, FALSE",{"$f":"TRUE()","v":true},"If the step instance corresponding to previous step has reached final status (aborted, skipped, completed, etc.), then TEE can mark the step instance corresponding to this test step in Running/Waiting status thereby eliminating the need for participant to do it manually on the UI.  This makes the UI easier to use.  There will be times that end-users would not want this to be done automatically e.g. for manual test steps or if some end-users just don't like step instances to be marked in Running status automatically."]
["auto_complete","Whether or not to mark the step instance as complete automatically.","Yes","boolean","Yes","No","TRUE, FALSE",{"$f":"TRUE()","v":true},"If the step instance corresponding to the current step has gone through all of the expected exchanges (controlled by expected_message_count), then TEE can mark the step instance as COMPLETE.  This flag controls whether or not TEE should do that automatically."]
["expected_message_count","The expected number of messages to be exchanged by the corresponding step instance.","Yes","int","Yes","No",null,2,"The number of expected proxy interceptions.  This would be more than two if more than one exchange is expected between intiator and responder ... or if there is a three-way communication for example.  \n\nThe number would be computed based on tm_test_roles card_max/card_min of the test_roles_initiator and test_roles_responder.  It can be overwritten by test_definition editor.  \n\nWe do need to know when the Test Execution Engine can mark the test step as completed."]
[]
["Notes:"]
["We could remove message_type column.  The message_type is captured by the new tm_test_step_message_type table."]
["We could remove transaction_id column.  The transaction_id is captured by the new tm_test_step_message_type table."]

{"sheet":"tm_test_step_instance","index":12,"n_rows":15,"n_cols":9,"rows_kept":15,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test_step_instance","Existing table in gazelle DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["tm_test_steps_id","Test Step","No","int","Yes","No","evs, nisthl7",null,"Foreign-key to tf_hl7_message_profile"]
["tm_test_instance_id","Test Instance","No","int","Yes","No",null,null,"Foreign-key to validation_service_type"]
["test_steps_instance_status_id","Verification status","No","int",null,null,null,null,"Foreign-key to tm_test_step_instance_status table.  Possible values are (Done, Failed, Activated, Deactivated, Skipped, Verified).  Values should be changed by verifier only."]
["status_id","Not used","No","int"]
["execution_status_id","Execution status","Yes","int","Yes","No",null,null,"Foreign-key to tm_step_instance_exec_status.  The execution status of the test step instance.  Values would be changed by TEE automatically and by participant."]
[]
["Notes:"]
["We should change test_steps_instance_status_id to verification_status_id to make its intent clear.   \"Activated\" should be removed from list of enums."]
["We should eliminate status_id column"]

{"sheet":"tm_test_step_message_type","index":13,"n_rows":11,"n_cols":8,"rows_kept":11,"cut":false,"hidden":false,"merged":[[3,1,3,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_test_step_message_type","New intermediate table (link table) for many-to-many relationship between tf_hl7_message_profile and tm_test_steps tables.   Test steps can involve multple messages (requests and responses) and each can have a different message type.  We need to keep track of each as the validation services will be different for each message type profile."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["direction","The direction of the message","int","Yes","No","0,1",null,"Request(0) or Response(0)"]
["tm_test_steps_id",null,"int",null,null,null,null,"Foreign-key to tm_test_steps table."]
["tf_hl7_message_profile_id","The validation service type","int","Yes","No",null,null,"Foreign-key to tf_hl7_message_profile table.  This will be selected by test editor."]
["message_validation_service_type_id","The validation service type","int",null,null,null,null,"Foreign-key to message_validation_service_type table.  This will be selected by test editor.  The selection offerings will change based on what tf_hl7_message_profile was selected. The test editor can choose from a list of validation services available for this tf_hl7_message_profile."]
["auto_validate","The path to the validation service","boolean","Yes","No","TRUE, FALSE",{"$f":"TRUE()","v":true},"Whether or not the TEE should invoke the validation services configured for this message in the test step."]

{"sheet":"tm_testing_session","index":14,"n_rows":9,"n_cols":9,"rows_kept":9,"cut":false,"hidden":false,"merged":[[3,1,3,8]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_testing_session","Existing table in gazelle DB."]
["Data Member Name","Description","New column","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","No","int","Yes","Yes"]
["type","Testing Session Type","No","varchar","Yes","No",null,null,"The value populated here would come from the key column in testing_session_type when \nA new record is created. This is a diversion from current design where admin is responsible for\nSpecifying this value."]
["status_id","Not used","No","int"]
["testing_session_type_id","Testing Session Type","Yes","int","Yes","No",null,null,"Foreign-key to tm_testing_session_type.  The testing session type of the testing session instance.  Value would be defined by Gazelle admin through UI."]

{"sheet":"tm_testing_session_type","index":15,"n_rows":20,"n_cols":8,"rows_kept":20,"cut":false,"hidden":false,"merged":[[3,1,3,7],[14,1,14,7],[15,1,15,7],[16,1,16,7],[17,1,17,7],[18,1,18,7],[19,1,19,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["tm_testing_session_type","New look-up table for all possible execution statuses that a tm_test_instance could go through."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","Varchar(100)","Yes","Yes","Connectathon,\nPre-Connectathon,\nInteroperability,\nShowcase,\nOther"]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","Varchar(100)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["connectathon","connectathon testing session."]
["Pre-connectathon","Pre-connectathon testing session."]
["Interoperability","Interoperability testing session."]
["showcase","Showcase testing session."]
["other","Generic Testing session."]

{"sheet":"validation_service_type","index":16,"n_rows":18,"n_cols":8,"rows_kept":18,"cut":false,"hidden":false,"merged":[[3,1,3,7],[15,1,15,7],[16,1,16,7],[17,1,17,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["validation_service_type","New look-up table for all possible validation-service tools that intercepted messages can be validated with.   Messages could be validated using different tools depending on capability of the tool."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","varchar(45)","Yes","Yes","evs, nisthl7"]
["base_url","Will include server host name (or IP address)","varchar(1024)","Yes","No",null,null,"If NIST HL7 Validation Tools becomes hosted on a different server, we only need to change this value.  The value can also include path that's common to all web service urls hosted by the tool."]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","varchar(45)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["evs","Gazelle EVS"]
["nisthl7","NIST HL7 Validation"]

{"sheet":"validation_status","index":17,"n_rows":19,"n_cols":8,"rows_kept":19,"cut":false,"hidden":false,"merged":[[3,1,3,7],[14,1,14,7],[15,1,15,7],[16,1,16,7],[17,1,17,7],[18,1,18,7]]}
["NIST - InteropTestbed - Data Dictionary"]
["Last Edited On:",{"$f":"CHANGES!B2","v":""}]
[]
["validation_status","New look-up table for all possible validation-statuses from message validation performed by validation services invoked by TEE."]
["Data Member Name","Description","Type","Mandatory?","Unique?","Possible Values","Default Value","Details"]
["id","Primary key","int","Yes","Yes"]
["key","Unique name","varchar(45)","Yes","Yes","pass, fail, warning, error"]
["description","The description for the enum value","varchar(1024)","Yes","No"]
["label_key_for_display","The key to be used to extract the label for the UI from resource bundles.","varchar(45)","Yes","Yes"]
[]
[]
[]
[]
["Enum values"]
["Key value","Description"]
["error","An error was encountered during validation service call i.e. We could not invoke the service properly so no determination can be made."]
["fail","There were validation errors."]
["warning","There were no validation errors but there were validation wanrings."]
["pass","No validation warnings or errors were encountered."]