ETQ Reliance configuration evaluation is not a single test but a boundary review across four documented surfaces: out-of-the-box applications, drag-and-drop Designer changes, ETQScript business logic, and release-managed deployment records. ETQ describes Reliance as a cloud-native QMS with more than 40 ready-to-use applications adaptable through configuration [2][3]. The evaluation question for a healthcare quality team is therefore not whether the platform can be configured, but which configuration layer owns a given record, what inputs and outputs each layer produces, and where version or deployment boundaries require separate evidence. This article organizes those distinctions around the documentation ETQ publishes, attributes vendor claims by name, and proposes a hypothetical validation scenario that a team could adapt without implying independent testing or regulatory approval.

Configuration Surfaces and Record Ownership

ETQ Reliance documentation separates configuration into interfaces that do not require programming and interfaces that do. The vendor lists External Link, Keyword Lookup, Connection Profiles for web services, SharePoint, and Google, plus web services and Java APIs as configurable integration options [1]. ETQ states that Java APIs require Java programming, which creates a practical ownership distinction: a business analyst may own External Link or Keyword Lookup records, while a developer or integration specialist owns Java API work [1]. The documentation does not state which roles may create or modify each interface; a healthcare evaluation should record who can create, modify, and retire each configuration type, because ownership affects change control evidence. A healthcare evaluation should record who can create, modify, and retire each configuration type, because ownership affects change control evidence.

The Designer and ETQScript materials add a second ownership layer. ETQ describes Designer as a drag-and-drop process design tool for non-IT business users to modify user access settings, workflows, forms, escalation paths, and notifications [4]. ETQScript is described as a simple Python-based scripting language for advanced business logic and process automation [4]. The optional Developer License is documented as unlocking a blank canvas to build new applications beyond the standard Reliance apps [4]. These are distinct configuration surfaces with different skill requirements, and an evaluation should not treat a Designer form change and an ETQScript rule as equivalent evidence.

Inputs, Outputs, and Deployment Boundaries

The Release Management for ETQ documentation provides the clearest input and output model for configuration evaluation. An Application Profile record includes an Environments section where each environment receives a unique name and address in the format server-name:port/context/path [6]. Requirements are created as documents, structured as parent and child records, and approved before use [6]. Test Scripts attach files and select complete requirements plus applicable settings such as application names [6]. These records form a chain: requirement, test script, test plan, validation project, and configuration change request [6].

The deployment boundary appears in the configuration change management process. A Configuration Change Request is created, sent for review, and may be moved to an On-Hold phase until approved; the reviewer can update Target Date and Target Release fields [6]. This suggests that configuration changes are intended to be associated with a target release, but the documentation does not state whether the platform enforces a deployment gate or merely records the intended release. A healthcare evaluation should therefore verify whether the release field is informational or controlling, because that distinction changes the evidence required for a validated environment.

Configuration Evaluation Checklist

Create an inventory that separates out-of-the-box application settings, Designer changes, ETQScript rules, and Developer License applications. For each item, record the owner, the input that triggers the change, the output record produced, and the release or environment where the change is deployed. Use the Release Management Application Profile to document environment names and addresses [6]. Then verify whether each configuration change is linked to a Configuration Change Request with a Target Release field [6]. Finally, confirm whether the validation workflow automatically captures test evidence or requires manual compilation, and ask ETQ to clarify the NXG and CG deployment boundary for your environment [8].

Document Control as a Configuration Reference Case

The Document Control application overview offers a concrete example of how configuration surfaces interact with record linking. Controlled documents can be created using Reliance Microsoft Office integration templates or attached through the file attachment interface [5]. Forms and workflows are described as provided out-of-the-box and ready to deploy, but also configurable without programming [5]. The Document Identification Section holds general information, while the Document Body Section supports external files such as Word documents, Excel sheets, images, Visio drawings, and MS Project plans [5].

Record linking shows how configuration choices propagate across applications. The Other Links field receives a link when the Dual Linking feature creates a target document from another application within a Document Control document [5]. Related Documents can be added based on document scope and business rules, with the system adding links for selected documents [5]. For a healthcare evaluation, this means a configuration review should trace whether a linked record is owned by Document Control or by the source application, because ownership determines which workflow controls the record's lifecycle.

Validation Workflow Limits and Unresolved Questions

ETQ's Release Management documentation describes a validation process that includes creating an Application Profile, managing requirements, creating and approving test scripts, assigning test plans, and approving validation projects [6]. The process also includes obsoleting requirements and creating requirement revisions through change requests [6]. However, the documentation does not state whether this workflow automatically generates validation evidence or simply organizes records that a team must compile. A third-party vendor profile notes that ETQ's approach to validation is more traditional, with the customer performing more of the load for validation testing and report compilation [8].

Several unresolved questions remain for a healthcare configuration evaluation. The documentation does not specify whether Designer changes are automatically captured in a configuration change request or must be manually recorded. It also does not state whether ETQScript changes require a separate code review step before deployment. The relationship between Reliance NXG and Reliance CG is documented as essentially the same product, with NXG leading on new features and CG continuing in support with no determined end date [8]. A team evaluating configuration should ask ETQ which product line applies to their deployment and whether configuration evidence transfers between them.

A Hypothetical Validation Scenario for Configuration Evidence

A healthcare quality team could design a hypothetical scenario to test whether configuration evidence is traceable across the documented surfaces. The scenario would begin with a Designer change to a Document Control form field, followed by an ETQScript rule that routes a document for additional review when a specific field value is selected. The team would then create a Configuration Change Request, associate it with a target release, and attempt to trace the change through a requirement, test script, and validation project [6].

This scenario is a suggestion for planning purposes, not a claim that ETQ Reliance has been independently tested or that the workflow will behave as described in any specific deployment. The value of the scenario is that it forces the team to identify which records the platform creates automatically and which records require manual entry. If the Designer change does not appear in the configuration change request without manual action, the team would need a compensating control. If the ETQScript rule cannot be linked to a test script, the team would need a separate code review procedure. These are the questions a configuration evaluation should answer before relying on the platform's validation records.