Before querying TEFCA-CommonWell for data, you must load your existing patient data into your Redox data on demand repository. Learn more about data on demand.
After first populating your patient repository, you must keep your patient demographics and records up-to-date as you continue patient care.
- You must have qualified for TEFCA and set up your credentials and OIDs. Learn more about setting up your onramp to TEFCA.
- You must have created your TEFCA-Commonwell organization record. Learn more about creating an organization record.
- Be familiar with the following terms and concepts to send requests to TEFCA-CommonWell:
The extensions in the code examples are all required for any PatientAdmin messages. Learn more about extensions.
This is a critical first step in your TEFCA-CommonWell workflow. It must be done before querying TEFCA-CommonWell or maintaining your patient records.
Send a PatientAdmin.NewPatient request for each of your patients to create their patient record in TEFCA-CommonWell to associate your patient with the same patient in external organizations. You must use at least one patient identifier with the ID Type of the patient OID assigned to you.
- The Meta.Destination.ID changes based on environment type:
- Development destination ID: 3122bfff-f1fb-4fdf-97de-294f24338229
- Production destination ID: 7fd005ac-d788-40c5-b4e8-b57bb8e310a9
- For production queries, set the Test value to false.
- The patient identifier and demographics below are example values only. Replace them with the relevant patient information.
- The patient identifier should be the MRN or primary ID of the patient in your system.
- The ID type should map to the value Redox provides. Typically, this means mapping a value like MR to this OID. This OID is linked to the repository and required to associate the patient.
- For demographics, review the PatientAdmin data model schema for full requirements.
Repeat this step every time you add a new patient to your patient care.
Complete this step every time demographics or contact information changes for existing patients.
Send a PatientAdmin.PatientUpdate request with the updated details. Patient demographics must be updated before you can query for their data again.
- The destination ID changes based on environment type:
- Development destination ID: 3122bfff-f1fb-4fdf-97de-294f24338229
- Production destination ID: 7fd005ac-d788-40c5-b4e8-b57bb8e310a9
- For production queries, set the Test value to false.
- The patient identifier and demographics below are example values only. Replace them with the relevant patient information.
- The patient identifier should be the MRN or primary ID of the patient in your system.
- The ID type should map to the value Redox provides. Typically, this means mapping a value like MR to this OID. This OID is linked to the repository and required to associate the patient.
- For demographics, review the PatientAdmin data model schema for full requirements.
Complete this step every time you identify duplicate records for the same patient.
Send a PatientAdmin.PatientMerge request to merge the patient records and replace the previous identifiers with the new one. Patient records must be merged appropriately before you can query for their data again.
- The destination ID changes based on environment type:
- Development destination ID: 3122bfff-f1fb-4fdf-97de-294f24338229
- Production destination ID: 7fd005ac-d788-40c5-b4e8-b57bb8e310a9
- For production queries, set the Test value to false.
- The patient identifier and demographics below are example values only. Replace them with the relevant patient information.
- The patient identifier should be the MRN or primary ID of the patient in your system.
- The ID type should map to the value Redox provides. Typically, this means mapping a value like MR to this OID. This OID is linked to the repository and required to associate the patient.
- For demographics, review the PatientAdmin data model schema for full requirements.