OC FAQs and Errors

The error states that there are specimen characters like +-/*(){}%, whitespaces (space, tab, newline, carriage return, etc.) in the CRF name. The OC connector uses the OID as the form name. These special characters are not allowed in the DE form names, hence the error.

Also, when importing the OID mapping CSV file, make sure that the column ‘OS_FORM_NAME’ does not contain any special characters.

For example, a form name can be added as ‘PATHOLOGY_DATA’ and not 'PATHOLOGY DATA.'

Fix: Clean up the CRFs to ensure they don't contain special characters mentioned in the log file in the CRF.

The error is displayed when the DE form ‘PATHOLOGY’ for the event ‘BASELINE’ is not yet created; hence the data cannot be imported. It would help if you made sure that the form error is fixed and imported.

The error is displayed when the participant was created in Open Clinica with PPID ABC01, deleted, and recreated. It would help if you cleaned up the mapping tables to remove the mapping of the deleted participants.

This error occurs when the configured server URL, Username, or Password is wrong. To fix this, check the below details and update if needed in the server configuration.

• Configured URL of OC in REST API Invoker.

• The username used in the configuration should have access to OC.

• Password used in configuration should be in a working state.

To fix these details go to REST API Invoker >> use the ‘PUT' HTTP request >> ‘Resource URL’ as 'ServerURL/rest/ng/or-server-configs/{configured server ID}’

Once you update the necessary host, username, and password, click on 'Send'. You should get 200 status as a successful result.

When forms get corrupted due to any possible reason, this error occurs. In this case, you need to delete the existing form and resync the data for that form. Run below API to delete the form in OpenSpecimen.

1. Invoke the REST API using either Postman or HTTP client.

   

   <app_url> : Server URL where the forms are available. 

   {FormId}: Form identifier for which you are getting an error. Get this from the #2 step.

   <username>: OpenSpecimen Username 

   <password>: OpenSpecimen Password

2. Form ID can be retrieved from DB using below SQL

   select identifier, name from dyextn_containers where name = '<form_OID>';

form_OID: You will get the form OID from XML of CRF from OC.

When CRF has many fields (100-200), the database doesn’t allow pulling all these fields in OS. Resulting OS throws the above error.

To resolve this error, you can either exclude the fields/CRFs you don’t want to sync in OS or include only those fields/CRFs you wish to pull from OC into OID mapping csv.

Refer to https://openspecimen.atlassian.net/wiki/spaces/CAT/pages/1919779095/OC+Study+Setup#Exclude-and-Include-CRFs for steps to import the mapping csv.

When OC doesn't have an OID for any site and patients are registered to that site. Then those patients can’t be synced into OS. In the above error, the ‘I-Spy2' is a site in OC whose siteOid is null.

To fix this client has to add the OID for the site in OC.

When you are trying to collect any primary specimen or child specimen, and their visit or primary specimen is not collected respectively due to any reason, then this error occurs.

• If you get the error for primary specimens, check if the visit is collected or not.

• If this error is for child specimens, ensure that parent is collected or not.

When you sync any specimen from OC and OS doesn’t have the same specimen with the label. Then this error occurs. To resolve this, you will need to add the specimen requirements that will match the label format.

This error is reported when the auto-generated label conflicts with an existing label.

Eg: The subject '74580' has more than one 'Baseline' event in OC. Whereas in OS, there is only one 'Baseline' event configured. 

In this case, there are two ways to resolve this error.

• Configure the multiple events with unique label formats in each.

• Fix the data in OC and sync.

When the OC field has any value that is not configured in the OS, this error occurs. E.g., In the ‘Clinical Diagnosis’ dropdown field has PV values like 10 weeks gestation, 13 weeks gestation, etc. These values are not available in OS for the mapped field, then the data for these subjects won’t sync.

To resolve this, add the same values in the OS dropdown as OC.

When you try to add a huge number of fields in the OID mapping sheet, and the max data limit exceeds, this error occurs. The max data it can store is 64 KB.

Execute below DDL. This will ensure you can store up to 16 MB.

alter table os_oc_studies change oids_mapping oids_mapping mediumtext;

Or else you can add only the required field as include in the OID mapping sheet. Refer to https://openspecimen.atlassian.net/wiki/spaces/CAT/pages/1919779095/OC+Study+Setup#Exclude-and-Include-CRFs for steps to import the mapping csv.

The ‘502 Bad Gateway Error’ occurs when the source server is down or not reachable. Please contact client to get this resolved.