# Maintain your Redox repository for TEFCA-CommonWell
> **Who can use this how-to**
>
> - Existing customers using Network Onramps
All TEFCA-CommonWell participants must respond to requests they receive from other network participants. In some cases, you may receive a high volume of requests per day.
With Redox as your responder, we respond to incoming patient requests on your behalf. However, you must push patient records and documents to your Redox data on demand repository so that we have an accurate representation of each of your patients.
## Prerequisites
- You must have [created a TEFCA-CommonWell organization record](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/create-a-tefca-commonwell-organization-record) and [populated your Redox data on demand repository with your existing patients](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/populate-your-patient-repository-for-tefca-commonwell). Patient demographic data must be up-to-date in your repository.
- (_Optional_) Test sending these requests with our TEFCA-CommonWell sandbox.
> **Use curl for technical validation**
>
> You can copy our code examples and send the test requests with `curl` ([learn more about curl](https://curl.haxx.se/docs/manpage.html)) instead of Postman. If you do, remember to:
>
> - Remove any comments from the code examples (starting with `//`).
> - Replace any variables (e.g., `{{YOUR-VARIABLE}}`).
> - Add the `source-id` if you have multiple sources. We don’t include `{{source-id}}` in the code examples, so you’ll have to add them yourself. [Learn about including source details](/basics/data-exchange-with-redox/Managing-source-details-in-outgoing-requests).
> - Make sure you have a full request for your own use since some of the code examples are abbreviated.
>
> Check out these troubleshooting guides if you run into errors:
>
> - [Troubleshoot TEFCA-CommonWell errors](/troubleshooting/troubleshoot-tefca-commonwell-errors)
> - [Troubleshoot OAuth API key errors](/troubleshooting/troubleshoot-oauth-api-key-errors)
- Be familiar with the following terms and concepts to send your queries to TEFCA-CommonWell:
TEFCA-CommonWell terms to know
| **Term** | **Description** |
| --- | --- |
| Organization or object ID (OID) | Identifies a particular healthcare organization within the TEFCA-CommonWell network. When you create a new organization record within TEFCA, the returned OID becomes the sender organization ID for your later queries. |
| Patient Identity Assigning Authority (PIAA) | The entity that assigns patient identifiers in the healthcare system. This value becomes the ID type in the metadata of TEFCA-CommonWell queries for documents. |
Metadata for TEFCA-CommonWell requests
This table contains the metadata fields for Redox data models if you’re querying or sending requests to TEFCA-CommonWell via the Redox Data Model API.
| **Field** | **Description** | **Notes** |
| --- | --- | --- |
| `Meta.Destinations.ID` | A universally unique identifier (UUID) for the destination you wish to search. This ID is different for staging and production environments. Check out the destination ID table for specifics. | For patient searches, this is a CommonWell EMPI destination. For document searches, this is a CommonWell XCA destination. For responding with information about your patients, this is your own document repository. |
| `Meta.FacilityCode` | Set to your organization OID or `null`. | This is required for document searches. A less common workflow might include directly querying to an external organization within the network. In that case, use their organization OID. |
| `Meta.Extensions.organization-name` | The name of the organization running the query. | Generally, this is the name of your organization or the covered entity that you’re providing services for. |
| `Meta.Extensions.sender-organization-id` | The organizational OID to identify your organization as the one sending the request. | This field is used for audit purposes and for search logic. To generate your organization OID for the `sender-organization-id` extension, [refer to TEFCA identity and organization structure](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/tefca-identity-and-organization-structure). |
| `Meta.Extensions.user-id` | Either the name of the user sending the request or the relevant provider. This should be a human-readable identifier and is required for audit purposes. | The provider’s name should still be populated when an automated process runs the query. For example, a provider may have an automated process triggered after completing a patient visit. In that case, the query runs in the background on the provider’s behalf. |
| `Meta.Extensions.user-role` | The role of the user sending the request. | You must use a SNOMED value for this field. [See SNOMED codes](https://www.hl7.org/fhir/valueset-practitioner-role.html). |
| `Meta.Extensions.purpose-of-use` | The purpose of use for this request (e.g., Treatment). | You must qualify for a "Treatment" purpose of use when using Network Onramps. |
Destination IDs for TEFCA-CommonWell
You must populate any test requests with the appropriate destination ID in the `Meta.Destinations` array based on the environment and type of requests:
| **Query purpose** | **Development ID** | **Production ID** |
| --- | --- | --- |
| Perform a patient search (`PatientSearch.LocationQuery`) | `3122bfff-f1fb-4fdf-97de-294f24338229` | `7fd005ac-d788-40c5-b4e8-b57bb8e310a9` |
| Create or update an organization (`Organization.New`, `Organization.Update`) | `3122bfff-f1fb-4fdf-97de-294f24338229` | `7fd005ac-d788-40c5-b4e8-b57bb8e310a9` |
| Search for a clinical summary/document (`ClinicalSummary.DocumentQuery`, `ClinicalSummary.DocumentGet`) | `cf1dca0e-98de-432b-8c9a-dd039816df0e` | `79981c00-b9c4-40a9-9844-01980e6e524e` |
| Save patient details to your repository (`PatientAdmin.NewPatient`, `PatientAdmin.PatientUpdate`, `PatientAdmin.PatientMerge`) | `3122bfff-f1fb-4fdf-97de-294f24338229` | `7fd005ac-d788-40c5-b4e8-b57bb8e310a9` |
| Save documents to your repository (`ClinicalSummary.VisitQuery`, `ClinicalSummary.VisitPush`) | This is specific to your organization. Redox provides the correct ID. | This is specific to your organization. Redox provides the correct ID. |
##
## Manage patient consent
By default, we treat each patient as “consented” if their data is saved into your Redox data on demand repository. This means we can return the patient’s data if requested by another network participant.
### Patient declines to share data
If a patient declines consent, however, you can send a `PatientAdmin.PatientUpdate` with the `Consent` extension ([learn about extensions](https://docs.redoxengine.com/permalink/309bUsOmy4QGEjAGqMB2vK)). You can toggle the patient’s consent status to declined by sending an empty `codeableConcept` with the Consent extension. When a patient’s consent status changes, any of their existing data will no longer be returned to network participants.
**Example: Declined patient consent in Consent extension **
```json
curl \
-X POST https://api.redoxengine.com/endpoint \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_TOKEN" \
-d '{
"Meta": {
"Extensions": {
"sender-organization-id": {
"url": "https://api.redoxengine.com/extensions/sender-organization-id",
"string": "{{ORGANIZATION-OID}}"
},
"user-id": {
"url": "https://api.redoxengine.com/extensions/user-id",
"string": "{{SENDING-USER-NAME}}"
},
"user-role": {
"url": "https://api.redoxengine.com/extensions/user-role",
"coding": {
"code": "112247003",
"display": "Medical Doctor"
}
},
"purpose-of-use": {
"url": "https://api.redoxengine.com/extensions/purpose-of-use",
"coding": {
"code": "TREATMENT",
"display": "Treatment"
}
}
},
"DataModel": "PatientAdmin",
"EventType": "PatientUpdate",
"Test": true,
"Destinations": [
{
"ID": "{{DATA-ON-DEMAND-REPOSITORY-ID}}"
}
]
},
"Patient": {
"Identifiers": [
{
"ID": "1234",
"IDType": "MR"
}
],
"Demographics": {
{
...
}
},
"Notes": [],
"Contacts": [
{
...
}
],
"Diagnoses": [
{
...
}
],
"Allergies": [
{
...
}
],
"PCP": {
{
...
}
},
"Insurances": [
{
...
}
],
"Guarantor": {
...
},
"Extensions": {
"consent-type": {
"url": "https://api.redoxengine.com/extensions/consent-type",
"codeableConcept": []
},
}
}
}
```
> **API reference**
>
> [Review the PatientAdmin data model](https://docs.redoxengine.com/permalink/patient-admin-patient-update) schema for full requirements.
### Patient consents to share data after declining
If a patient consents to share their data initially, nothing needs to be done. However, if a patient has declined consent previously and chooses to consent later, follow these instructions.
Send a `PatientAdmin.PatientUpdate` with `codeableConcept` populated as it is in the example below. This text toggles a patient’s consent status again so their data can be shared with network participants.
**Example: Toggle a patient’s consent with the Consent extension **
```json
{
"url": "https://api.redoxengine.com/extensions/consent-type",
"codeableConcept": [
{
"text": "Treatment",
"coding": [
{
"system": "2.16.840.1.113883.3.18.7.1",
"code": "TREATMENT",
"display": "Treatment"
}
]
},
{
"text": "Request of the Individual",
"coding": [
{
"system": "2.16.840.1.113883.3.18.7.1",
"code": "REQUEST",
"display": "Request of the Individual"
}
]
},
]
}
```
## Save patient documents
After providing care for a patient, save the patient summary documents to your **data on demand repository** so Redox can respond to requests for documents from other network participants. You must include certain data when you're returning data to the network. [Check out the rules for returned data](https://docs.redoxengine.com/permalink/1ldmpAmaxAriJ7Ei0zYn3Q/#what-data-is-exchanged).
Send a `ClinicalSummary.VisitPush` request with all the available unique clinical information that you produce. Be mindful of these requirements and best practices:
| **Field** | **Notes** |
| --- | --- |
| `Meta.Test` | Set this value to `False` for production requests. |
| `Meta.Destinations.ID` | This value changes based on environment type. For `VisitPush`, this is the data on demand repository ID that your Technical Account Manager gives to you. |
| `Header.Patient.Identifiers[].IDType` | At least one patient identifier should include an ID Type that matches the patient identification OID used in the `PatientAdmin` messages. Typically, this is `MR`. |
| `Header.Document.ID` | This ID must be globally unique across TEFCA-CommonWell as either a GUID or an internally unique ID prefixed with your organizational OID. Our examples use the OID prefix. |
| `Header.Document.Type` `Header.Document.TypeCode` | These values should be a LOINC code. Typically, you should use the code for a Continuity of Care Document (i.e., `34133-9`). When sending a document related to a single patient visit, you should use these codes: Use Progress Notes (i.e., `11506-3`) for outpatient/ambulatory visits. Use discharge summary (i.e., `18842-5`) for inpatient/hospital visits. |
| `Header.Document.Custodian.Name` | We recommend populating this value since it tells other clinical network participants where the data came from. If this field isn’t populated, the value defaults to the `Meta.Source.Name`, which is set based on the source you’re sending the request from. We encourage you to populate as much of the `Header.Document.Custodian.Name` object as possible. Most entries use the same data as their directory, but you may want more or less granularity. |
| `Documents[].Author.Location` | Some external systems use this to display the location the document originated from when viewing a list documents. When looking at an individual document, `Custodian.Name` is typically used instead. Typically, the `Author` and `Custodian` values are the same, but they may differ. If not supplied, Redox sets this to the directory entry name you’ve saved to TEFCA-CommonWell. See the difference between [Author](https://build.fhir.org/ig/HL7/CDA-core-2.0/StructureDefinition-Author.html) and [Custodian](https://build.fhir.org/ig/HL7/CDA-core-2.0/StructureDefinition-Custodian.html). |
Since `ClinicalSummary.VisitPush` is lengthy, we include an abbreviated example below. [Check out a full example](https://docs.redoxengine.com/permalink/clinical-summary-visit-push) or view the Postman package.
**Example: Save a patient document (abbreviated)**
```bash
curl \
-X POST https://api.redoxengine.com/endpoint \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_TOKEN" \
-d '{
"Meta": {
"DataModel": "Clinical Summary",
"EventType": "VisitPush",
"Test": true,
"Destinations": [
{
"ID": "{{DATA-ON-DEMAND-REPOSITORY-ID}}"
}
]
},
"Header": {
"DirectAddressFrom": null,
"DirectAddressTo": null,
"Document": {
"Author": {
"ID": "4356789876",
"IDType": "NPI",
"Type": null,
"FirstName": "Pat",
"LastName": "Granite",
"Credentials": [
"MD"
],
"Address": {
"StreetAddress": "123 Main St.",
"City": "Madison",
"State": "WI",
"ZIP": "53703",
"County": "Dane",
"Country": "USA"
},
"EmailAddresses": [],
"PhoneNumber": {
"Office": "+16085551234"
},
"Location": { ...
}
},
"ID": "{{REDOX-PARENT-OID}}^67890",
"Locale": "US",
"Title": "Community Health and Hospitals: Annual Physical",
"DateTime": "2012-09-12T00:00:00.000Z",
"Type": "Progress Note",
"TypeCode": {
"Code": "11506-3",
"CodeSystem": "2.16.840.1.113883.6.1",
"CodeSystemName": "LOINC",
"Name": "Progress Note"
},
"Visit": {
"Location": {
"Type": "Outpatient Clinic",
"Facility": "RHS Vista Oaks Clinic",
"Department": "Vista Oaks Clinic",
"Room": null
},
"StartDateTime": "2020-11-12T00:18:30.592Z",
"EndDateTime": "2020-11-12T00:18:30.592Z",
"Reason": "Annual Physical",
"VisitNumber": "30311442"
}
},
"Patient": {
"Identifiers": [
{
"ID": "1234",
"IDType": "MR"
}
],
"FirstName": "Timothy",
"MiddleName": "Paul",
"LastName": "Bixby",
"DOB": "2008-01-06",
"SSN": "101-01-0001",
"Sex": "Male",
"Race": "White",
"IsHispanic": null,
"MaritalStatus": "Married",
"IsDeceased": null,
"DeathDateTime": null,
"PhoneNumber": {
"Home": "+18088675301",
},
"EmailAddresses": [],
"Language": "en",
"Citizenship": [],
"Address": {
"StreetAddress": "4762 Hickory Street",
"City": "Monroe",
"State": "WI",
"ZIP": "53566",
"County": "Green",
"Country": "US"
}
},
"PCP": { ...
}
},
"AdvanceDirectivesText": "
Directive Description Verification Supporting Document(s)
Resuscitation status Do not resuscitate Dr. Robert Dolin, Nov 07, 1999 Advance directive
",
"AdvanceDirectives": [
{
"Type": {
"Code": "304251008",
"CodeSystem": "2.16.840.1.113883.6.96",
"CodeSystemName": "SNOMED CT",
"Name": "Resuscitation",
"AltCodes": []
},
"Code": "304253006",
"CodeSystem": "2.16.840.1.113883.6.96",
"CodeSystemName": "SNOMED CT",
"Name": "Do not resuscitate",
"AltCodes": [],
"StartDate": "2011-02-13T05:00:00.000Z",
"EndDate": null,
"ExternalReference": "AdvanceDirective.b50b7910-7ffb-4f4c-bbe4-177ed68cbbf3.pdf",
"VerifiedBy": [
{
"FirstName": "Robert",
"LastName": "Dolin",
"Credentials": "Dr.",
"DateTime": null
}
],
"Custodians": [
{
"FirstName": "Robert",
"LastName": "Dolin",
"Credentials": "Dr.",
"Address": { ...
}
}
]
}
],
"AllergyText": "
Substance Reaction Severity Status
Penicillin G benzathine Hives Moderate to severe Inactive
Codeine Shortness of Breath Moderate Active
Aspirin Hives Mild to moderate Active
",
"Allergies": [ ...
] ...
}
],
"AssessmentText": "Recurrent GI bleed of unknown etiology; hypotension perhaps secondary to this but as likely secondary to polypharmacy.Acute on chronic anemia secondary to #1.Azotemia, acute renal failure with volume loss secondary to #1.Hyperkalemia secondary to #3 and on ACE and K+ supplement.Other chronic diagnoses as noted above, currently stable.Also, this person has back problems.",
"Assessment": {
"Diagnoses": [
{
"Value": "Displacement of lumbar intervertebral disc without myelopathy",
"DateTime": "2009-11-01T05:00:00.000Z",
"IsNegativeIndicator": false,
"Codes": [
{
"Code": "202708005",
"CodeSystem": "2.16.840.1.113883.6.96",
"CodeSystemName": "SNOMED-CT",
"Name": "Herniated lumbar intervertebral disc"
},
{ ...
}
]
},
{
"Value": "Thoracic or lumbosacral neuritis or radiculitis, unspecified",
"DateTime": "2009-11-01T05:00:00.000Z",
"IsNegativeIndicator": false,
"Codes": [
{
"Code": "M54.16",
"CodeSystem": "2.16.840.1.113883.6.90",
"CodeSystemName": "ICD-10",
"Name": "Right lumbar radiculopathy"
}
]
}
]
},
"ChiefComplaintText": "Dark stools.",
"EncountersText": "
Encounter Performer Location Date
Pnuemonia Dr Henry Seven Community Health and Hospitals 20120806
",
"Encounters": [
{
"Identifiers": [
{
"ID": "2376492",
"IDType": "URMC Epic CSN"
}, ...
],
"Type": {
"Code": "99222",
"CodeSystem": "2.16.840.1.113883.6.12",
"CodeSystemName": "CPT",
"Name": "InPatient Admission",
"AltCodes": []
},
"DateTime": "2012-08-06T04:00:00.000Z",
"EndDateTime": null,
"Providers": [ ...
],
"Diagnosis": [
{
"Code": "233604007",
"CodeSystem": "2.16.840.1.113883.6.96",
"CodeSystemName": "SNOMED CT",
"Name": "Pneumonia",
"AltCodes": []
}
],
"ReasonForVisit": [
{
"Code": "233604007",
"CodeSystem": "2.16.840.1.113883.6.96",
"CodeSystemName": "SNOMED CT",
"Name": "Pneumonia",
"AltCodes": []
}
]
}
],
"FamilyHistoryText": "Father (deceased)
Diagnosis Age At Onset
Myocardial Infarction (cause of death) 57
Diabetes 40
",
"FamilyHistory": [ ...
],
"HistoryOfPresentIllnessText": "Kelp, Lonnie Ray Sr., MD PHD - 10/21/2014 8:07 PM PSTDate: 10/21/2014
Pre-procedure diagnosis: L5 S1 Acute Lumbar Radiculopathy (Right)
Post-procedure diagnosis: Same
Procedure: 1) L5S1 Transforaminal Epidural Steroid injection(Right)
2) Fluoroscopic Guidance for needle placement
Complications: None
CONSENT: Today's procedure, its potential benefits as well as its risks and potential side effects were reviewed. Discussed risks of the procedure include bleeding, infection, nerve irritation or damage, reactions to the medications, headache, failure of the pain to improve, and exacerbation of the pain were explained to the patient, who verbalized understanding and who wished to proceed. Informed consent was signed.
DESCRIPTION OF PROCEDURES: After written informed consent was obtained, the patient was taken to the fluoroscopy suite. Anatomical landmarks were identified by way of fluoroscopy in multiple views. Strict aseptic technique was utilized.
A 22-gauge 3-1/2-inch needle was then incrementally advanced using multiple fluoroscopic views from an oblique approach into the Right L5S1 lumbar intervertebral space. Both AP and lateral views were used to confirm final needle placement. After negative aspiration, Omniopaque 240 contrast was injected which delineated epidural without vascular flow and a normal epidurogram under fluoroscopy in the lateral and AP view. After negative aspiration was reconfirmed, a 1.0 mL of 0.25% Bupivicaine and 1mL of 40 mg/mL of Kenalog was slowly injected into the epidural space.
All needles were removed intact. Hemostasis was maintained. There were no complications. The area was cleaned and a Band-Aid placed as necessary. The patient tolerated the procedure well and all needles were removed intact. After a period of observation, the patient was noted to be hemodynamically stable and neurovascularly intact following the procedure as prior to the procedure, and was ultimately discharged to home with supervision in good condition. The patient was instructed to schedule an appointment in the office within 2 weeks.
Lonnie Ray Kelp Sr., MD PHD
",
"ImmunizationText": "
Vaccine Date Status
Influenza virus vaccine, IM May 2012 Completed
Tetanus and diphtheria toxoids, IM Apr 2012 Completed
",
"Immunizations": [ ...
],
"InstructionsText": "Please carefully follow the subsequent instructions and patient education:
FlossBrush teeth twice daily
Scarf tying instructions may be found online.",
"InsurancesText": null,
"Insurances": [
{
"Plan": { ...
}
}
],
"InterventionsText": "Patient practiced use of novel prosthesis including movements formerly neglected including distal extension and retroflexive hyperextension.",
"MedicalEquipmentText": "
Supply/Device Date Supplied
Automatic implantable cardioverter/defibrillator Nov 1999
Total hip replacement prosthesis 1998
Wheelchair 1999
",
"MedicalEquipment": [ ...
],
"MedicationsText": "
Medication Directions Start Date Status Indications Fill Instructions
Albuterol 0.09 MG/ACTUAT inhalant solution 0.09 MG/ACTUAT inhalant solution, 2 puffs once 20120806 Active Pneumonia (233604007 SNOMED CT) Generic Substitition Allowed
",
"Medications": [ ...
],
"MedicationsAdministeredText": "
Medication Start Date Status
Albuterol 0.09 MG/ACTUAT inhalant solution 0.09 MG/ACTUAT inhalant solution, 2 puffs once 20120806 Active
",
"MedicationsAdministered": [ ...
],
"ObjectiveText": "Chest: clear to ausc. No rales, normal breath soundsHeart: RR, PMI in normal location and no heave or evidence ofcardiomegaly,normal heart sounds, no murm or gallop",
"PhysicalExamText": "All examinations performed within normal limits.
WNL
Nothing to report here.",
"PlanOfCareText": "
Planned Activity Planned Date
Consultation with Dr George Potomac for Asthma 20120820
Chest X-ray 20120826
Sputum Culture 20120820
",
"PlanOfCare": { ...
},
"ProblemsText": "Pneumonia : Status - ResolvedAsthma : Status - Active",
"Problems": [ ...
],
"ProceduresText": "
Procedure Date
Chest X-Ray 8/7/2012
",
"Procedures": { ...
},
"ReasonForReferralText": "
Incoming Referral Reason Specialty Diagnoses / Procedures Referred By Contact Referred To Contact
Consult, Test & Treat (Routine) BA-Physical Medicine / Physical Medicine and Rehab DiagnosesRadiculopathy, lumbar regionL5S1 TTRANSFORMINAL ESIL5S1 TTRANSFORMINAL ESIProceduresPR INJECT ANES/STEROID FORAMEN LUMBAR/SACRAL W IMG GUIDE ,1 LEVELINJECTION Kelp, Lonnie Ray Sr., MD PHD Kelp, Lonnie Ray Sr., MD PHD
",
"ReasonForVisitText": "Light stools.",
"ResultText": "
LABORATORY INFORMATION
Chemistries and drug levels
HGB (M 13-18 g/dl; F 12-16 g/dl) 13.2
WBC (4.3-10.8 10+3/ul) 6.7
PLT (135-145 meq/l) 123 (L)
",
"Results": [ ...
],
"ReviewOfSystemsText": "Patient denies recent history of fever or malaise. Positive for weakness and shortness of breath. One episode of melena. No recent headaches. Positive for osteoarthritis in hips, knees and hands.",
"SocialHistoryText": "
Social History Element Description Effective Dates
smoking Former Smoker (1 pack per day 20050501 to 20110227
smoking Current Everyday Smoker 2 packs per day 20110227 - today
",
"SocialHistory": { ...
},
"SubjectiveText": " Complaints of rectal bleeding, fatigue and a change in bowel patterns. Has several days of constipation alternating with diarrhea. ",
"VitalSignsText": "
Date / Time: Nov 1, 2011 August 6, 2012
Height 69 inches 69 inches
Weight 189 lbs 194 lbs
Blood Pressure 132/86 mmHg 145/88 mmHg
",
"VitalSigns": [ ...
]
}
```
> **Onramp to TEFCA resources**
>
> **Basic information**
>
> - [Interact with clinical networks](/how-to-use-redox/interact-with-clinical-networks)
> - [TEFCA identity and organization structure](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/tefca-identity-and-organization-structure)
>
> **How-to**
>
> - [Set up your onramp to TEFCA-CommonWell](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/set-up-your-onramp-to-tefca-commonwell)
> - [Test sandbox for onramp to TEFCA-CommonWell](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/test-sandbox-for-onramp-to-tefca-commonwell)
> - [Populate your patient repository for TEFCA-CommonWell](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/populate-your-patient-repository-for-tefca-commonwell)
> - [Create a TEFCA-CommonWell organization record](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/create-a-tefca-commonwell-organization-record)
> - [Search TEFCA-CommonWell for patient records](/how-to-use-redox/interact-with-clinical-networks/onramp-to-carequality/search-for-patient-records)
> - [Request patient documents from TEFCA-CommonWell](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/request-patient-documents-from-tefca-commonwell)
> - [Maintain your Redox repository](/how-to-use-redox/interact-with-clinical-networks/onramp-to-tefca-commonwell/maintain-your-redox-repository-for-tefca-commonwell)
>
> **Troubleshooting**
>
> - [Common TEFCA errors](/troubleshooting/troubleshoot-tefca-commonwell-errors)