Who can use this how-to
- You must have populated your Redox data on demand repository with your existing patients. Learn how to populate your patient repository.
- (Optional) Test sending these requests with our TEFCA-CommonWell sandbox. Learn about our TEFCA-CommonWell sandbox.Use curl for technical validation
- Be familiar with the following terms and concepts to send your queries to TEFCA-CommonWell:
Searching TEFCA-CommonWell for patient records is an optional step if you want to:
- Confirm that you’ve already added a patient record in your repository for TEFCA-CommonWell. If the patient isn’t found with the steps in this how-to guide, you should add it. Learn how to populate your patient repository.
- Locate specific sites to directly query. After locating a site, use the organization OID in the location query response to request patient records.
First, using Postman or curl, send a PatientSearch.LocationQuery request with either the network patient ID or patient demographics to the CommonWell EMPI destination.
- The Meta.Destination.ID changes based on environment type:
- Development destination ID: adf917b5-1496-4241-87e2-ed20434b1fdb
- Production destination ID: 97f2dc1d-c71b-43a7-a436-9b789d44c804
- For production queries, set the Test value to false.
- The network patient ID is the patient identifier from TEFCA-CommonWell. If you don’t have it, you can leave the Identifiers array empty and rely on demographic matching.
- For patient demographics, review the LocationQuery schema for full requirements.
What demographic information to include
Example: Search for locations in TEFCA-CommonWell
bash
The response returns identifiers, including both ID and IDType (i.e., PIAA) and demographic information about the patient, including Organization.Identifiers[].ID. Review the LocationQueryResponse schema for full context and technical details.
CommonWell EMPI results
Example: Successful response for location search in TEFCA-CommonWell
json
Onramp to TEFCA resources