The Line Type defines the exact data to be recorded in the eCHR and how the data is displayed. 

Supported Line Types

Most eCHR Line Types can be configured entirely in the eCHR Profiles page, although some require further configuration within their environments in the UI.

The following Line Types can be configured:

• Action Completion
• BOM-Related Line Types
  • As Built
  • BoM Definition (not supported for no-code configuration)
  • Build Record
  • Use / Remove Transactions
• Case Data
• Check Result Set
• Documents (configured entirely within the eCHR Profiles)
  • Checklist Document
  • Check Result Set Document
  • Checklist Step Document
  • Issue Document
  • Item Document
  • Job Document
  • Operation Document
  • Product Document
  • Recipe Document
• eCHR-Related Line Types - note that these line types do not currently support eCHR end-user no-code configuration as they are used for a wide range of purposes / data capture requirements. For changes to these line types, contact Eyelit Support.
  • eCHR On Closure
  • eCHR On Creation
  • eCHR Transfer
  • Generic eCHR Data WF Action
• Issue (configured entirely within the eCHR Profiles)
• Item-Related Line Types
  • Item Adjust Qty Actual
  • Item Adjust Qty WIP
  • Item Note
  • Item Serial Number Change
  • Item Split
  • Item Summary Data
• Label Print
• Operation Quantity Completion
• Scrap-Related Line Types
  • Scrap Available Quantity
  • Scrap WIP (configured entirely within the eCHR Profiles)
• Tool Use (configured entirely within the eCHR Profiles)

Line Type Configuration Overview

Most eCHR data is collected during the execution of a workflow. Here is an example of a workflow and the Line Types that were configured to record relevant data in the eCHR:

The eCHRs build out as you progress through the workflow. There are a few things worth noting:

• BOM Definition, Product Document, and Job Document eCHR Line Types are created when you start the job. They are not operation dependent. These eCHRs are updated as new versions of the documents are created or as new documents are added (e.g. adding job documents).
• The As Built eCHR Line Type will be created at the point at which the eCHR is finalised and fixed (when moved to status Pending Approval).

eCHR Section

After defining the eCHR profile, you can define what data will be collected (lines), which are grouped into sections. The data gets put into sections and, within a section, you have section configs. The configs define what sort of data is going to be collected and how it will be displayed.

Having collected all this data, there are three places you can view that data:

1.  eCHR headers in the listing page.
2.  Line summary and line details.
3. HTML report.

New eCHR Section

To create an eCHR section:

1. Select the version of the eCHR profile that is in draft status and click the New Section button.
2. Provide a name and set the Active field to Yes or No. If you select No, content will not be saved for this section.

New eCHR Section Config

1. Select the section you created and click the New eCHR Section Config button.
2. Complete the New / Edit eCHR Section Config input screen.

Blue fields in the form are required and are flagged with an asterisk (*) in this document. 

• eCHR Line Type*: See Supported Line Types for the list of line types.
• Configure the line type to specify what data is stored in the eCHR. Two options:
  
  • No-Code eCHR Section Advanced Configuration: Low level of technical skills required.
  • Advanced section configuration: A level of technical skill is required.

New eCHR Section Configuration

To access the New eCHR Section Config screen:

1. Navigate to eCHR Profiles, select an eCHR Profile version and select a section (see previous section on how to create an eCHR section).
2. Click the New Config button.

New / Edit eCHR Config

• eSignatures: eSignatures add administrative burden so use it where it is essential to have. For example, you may have an issue that is updated regularly. You might choose not to eSign their updates in the eCHR.
  • Insert eSign Profile: Signature required for a new record. Not required for the As Built line type.
  • Update eSign Profile: Signature required for an updated record. Not required for the As Built line type.
  • Delete eSign Profile: Signature required for a deleted record. Note that this does not permanently delete the information from blockchain - it marks the record as deleted only, which maintains the audit record. Not required for the As Built line type.
• Line Type-specific 
  • Checklist Type: Select a Checklist Type. Only displays for the Checklist Result Set line type.
  • Checklist: Select a Checklist. Only displays for the Checklist Result Set line type.
  • Document Type: Only required for the Checklist Document, Checklist Step Document, Issue Document, Item Document, Job Document, Operation Document, Product Document, and Recipe Document line types.
  • Reference Key: Only displays for the Generic eCHR data WF action line type.
  • Issue Type: Select an Issue Type. Only displays for the Issue line type.
  • Tool Type: Select a Tool Type. Only displays for the Tool Use line type.
  • Tool Group: Select a Tool Group. Only displays for the Tool Use line type.

eCHR Line Configuration

eCHR lines no-code framework reduces the need for technical skills to implement. You can configure eCHR content in terms of what data is stored and how it is visualised through guided configuration tools. This provides you with the flexibility to configure regulatory data capture that matches your processes without customisation or complex technical configuration. This covers configuration of standard comprehensive data sets for each line type but not additional / changed information in the datasets. For that, see advanced configuration.

eCHR Line Type Data Point Configure Data 

The data fields to be stored and visualised for each eCHR section lines can be configured through a graphical UI. The Configure Data screen lists the data points that belong to a profile. Each row represents one data field.

UI settings

The following settings can be viewed and edited for each data field:

• Order of data: data points can be dragged / dropped to define the order in which they will be stored / displayed.
• Is Required: Mandatory inclusion in the eCHR. This field is read-only and indicates where a field is required for system functionality or regulatory compliance.
• Store in eCHR: Defines what data you want to be stored in the immutable eCHR record. It is usually set to ‘Yes’ by default. If any are turned off, then none of the other toggles on that record can be set to ‘Yes’. Note that required fields (see above) cannot be set to 'No'.
• In Summary: Indicates whether the field will be included in the summary sections on the eCHR listing and the printable report.
• Summary Aggregation: If you have multiple elements within the summary, then you can specify Count / List, for example ‘Count’ records the number of BOM slots, or ‘List’ which records the name of each BOM slot.
• In Listing Detail: ‘Yes’ to include in the Detail section of the website report (eCHR Listing content)
• In Printable Report Details: ‘Yes’ to include in the Detail section of the printable PDF report.

Reset Default

Select the Reset Default button to reset the default settings.

Edit Row

You can edit the contents of the line through the configuration UI or by selecting a row and pressing edit. The only setting that is only accessible via the Edit Row button is the data label in eCHR. All other settings can be configured in the data configuration UI.

The Edit Row button displays when a detail row is selected to open the Edit eCHR Header Config Data Point pop-up. Here you can:

•  Change the Data Label in eCHR name.
• Select whether to store the data field in the eCHR, whether it should appear in the summary and which reports it should be displayed (website and printable reports).
• Access the advanced configuration via the Advanced View toggle. The Advanced View lets you modify the header data point, but this should generally not be required (contact Eyelit Support to assist with this if required). 

eCHR Advanced Configuration

The standard configure options cover the visualisation of system supported data only, however sometimes there may be a need to add customer specific data to the blockchain. In this scenario, contact Eyelit Support and they can use the advanced function to add new information into the content of the blockchain record.

Note that if the content is changed, the end user configuration tools are not supported, so full configuration of the contents and appearance needs to be done in Advanced Configuration mode.

Use advanced manual eCHR configuration only if a no-code option is available, or if you want to customise the default data points provided by either the no-code or advanced configuration options. Contact Eyelit Support if you want to update anything in the Advanced View.

Advanced Section Configuration

In the advanced view, the fields that you set on the no-code configuration screen for the selected line, appear in the editable Line Summary Content field. This is where you can update the content to be stored in the blockchain.

To access the advanced configuration:

1. Navigate to the eCHR section and select a line.
2. Click the Edit Config to display the New / Edit eCHR Section Config screen, then click the Advanced Config button to display the additional fields that are configurable in the advanced settings.

• Sql Statement*: Default value based on line type selected. Each eCHR Line Type above will populate a default SQL statement that defines the data to be collected. Eyelit MES can help customise a SQL statement if you need data other than what's in the default included in the eCHR.
• Required SQL Parameters: Default value based on line type selected. Pre-populates and is displayed when selecting an eCHR Line and shows the parameter the SQL statement is based on.
• Sql Output*: Default value based on line type selected. Determine if the output of the SQL is a flat structure (table) or an hierarchical structure (tree view or JSON).
• Details Panel Menu Item: Default value based on line type selected. Defines the screen used when we view the data (i.e. how the data will be displayed in the contents screen / printable report). The default can be customised.
• Details in Printable Report: Default value based on line type selected. The query that defines the data that goes into the printable report. This is usually left blank for the Document Line Type.
• Line Summary Content: Default is based on line type selected. It allows you to customise what's displayed on each line. See an example of a line summary below.
  
  
  
  
• Sub-section Content: Defining sub-section content allows you to group the data in an eCHR by a defined field, e.g. group by operation number and name.

The layout of the advanced config page is similar to the image above for all line types although additional fields may be displayed depending on the line type selected.

View eCHR data

You can view the blockchain data for the eCHR Line Types in one of the following ways:

• Workstation: Click the eCHR button on the righthand navigation (provided it was configured in the button profile).
• Item Status: By selecting the eCHR view.
• eCHR Listing: By selecting the listing and clicking the Content button.

Review and Sign eCHR Workflow Action

It is possible to close a job before the eCHR is closed because there may be post-job actions that can still be recorded in the eCHR. You can however keep an action open until a specified eCHR review and sign mode was completed. For more information, see the Review and Sign eCHR Workflow Action documentation.

Sign an eCHR Line

Users with the required permissions can sign an eCHR line from one of the following:

• Workstation (via the eCHR button if it's configured).
• Workstation - check list - where checklists are configured with e-signature sign off the e-signature is automatically recorded as part of the action function.
• Item Status page with eCHR selected in the View field.
• Content page via the eCHR Listing screen. 

Delete an eCHR Line

Users with the required permissions can delete an eCHR line from one of the following:

• Workstation (via the eCHR button if it's configured).
• Item Status page with eCHR selected in the View field.
• Content page via the eCHR Listing screen. 

Note that this does not permanently delete the information from blockchain - it marks the record as deleted only, which maintains the audit record.