PARTICIPATION | |
Q: | IN ARRANGEMENTS WHERE A SERVICE PROVIDER IS REIMBURSED BY THE TPA, AND THEN THE CARRIER REIMBURSES THE TPA, WILL THE TPA NEED TO PASS THE SERVICE PROVIDER DETAIL TO THE CARRIER FOR REPORTING? |
A: | Yes, Medical Data Call requires that all service provider data be reported at a line item detail level. The Provider ID Number should reflect the service provider’s ID, and the Provider Taxonomy Code and the Place of Service should reflect that of the service provider. |
DATA TRANSMISSION | |
Q: | HOW ARE DATA SUBMITTERS NOTIFIED THAT A FILE WAS ACCEPTED OR REJECTED? |
A: | Data submitters are notified via system-generated email, which is addressed to the email address reported in the Electronic Transmittal Record on the file. |
Q: | HOW ARE REJECTED RECORDS RETURNED? |
A: | The record return file is returned via text file (.TXT) attachment included in a system-generated email. |
Q: | WILL DATA SUBMITTERS BE REQUIRED TO INCLUDE A TRANSMITTAL RECORD IN THE MEDICAL DATA CALL FILE? |
A: | Yes. The product type is reported as WCM for Medical Data Call. |
Q: | IS THERE A SPECIFIC FILE NAMING CONVENTION REQUIRED FOR THE MEDICAL DATA CALL? |
A: | Yes. The Medical Data Call files require the standard CDX naming convention. The first two positions will be MC for Medical Data Call and all other parts of the CDX file naming convention follow. We have the ability to accept a limited amount of additional file identification content on the far right of the file name, after the end of the standard CDX naming convention. |
Q: | WHERE SHOULD THE SUBMISSION CONTROL RECORD BE PLACED WITHIN THE DATA SUBMISSION? |
A: | Display the Submission Control Record at the end of the file. The file should be structured with E.T.R. transmittal record at the top of the file, then the medical data transactions, then the Submission Control Record at the end of the file. |
Q: | IF THE CARRIER IS ALREADY SUBMITTING WCPOLS AND WCSTAT FILES THROUGH CDX, IS THERE ANYTHING ELSE CARRIERS NEED TO DO TO SUBMIT MEDICAL DATA CALL FILES ELECTRONICALLY? |
A: | Carriers must set up the WCMED product within CDX and establish reporting permissions for this product. |
Q: | CAN CARRIERS WITH A LARGE VOLUME OF DATA SUBMIT MONTHLY INSTEAD OF QUARTERLY? |
A: | Yes. Monthly submissions are encouraged so that large volumes of data can be successfully transmitted and received. |
DATA REPORTING | |
Q: | WHY DO THE CARRIER CODE, POLICY NUMBER IDENTIFIER, POLICY EFFECTIVE DATE AND CLAIM NUMBER IDENTIFIER HAVE TO MATCH THOSE VALUES AS REPORTED ON THE UNIT STATISTICAL DATA? |
A: | The ability to match the Carrier Code, Policy Number Identifier, Policy Effective Date and Claim Number Identifier with the Unit Statistical data values allows our organization to use the statistical claim information along with the medical data in our actuarial analysis. |
Q: | WHAT IF THE CLAIM NUMBER IDENTIFIER SUPPLIED BY OUR VENDOR DOES NOT EXIST OR DOES NOT MATCH THE UNIT STATISTICAL CLAIM NUMBER IDENTIFIER? |
A: | The Claim Number Identifier is a linking field and must match the unit statistical claim number. Since each carrier's systems and business partner arrangements are different, each carrier will have to make a business decision to either require it from the vendor, supply it to the vendor, or populate it in their own system prior to submission. |
Q: | IF WE NEED TO REPORT THE POLICY NUMBER AND CLAIM NUMBER THAT WERE REPORTED FOR UNITS, WHAT WOULD WE REPORT IF THIS INFORMATION IS NOT AVAILABLE FOR OLDER CLAIMS? |
A: | We recognize that the difference in duration of reporting from 11 report levels (unit data) to 30 years (medical data) may pose a problem with this requirement when reporting older claims. In these cases, we would accept the policy number and claim number that identify the claim in your system today. This policy number and claim number must be consistently used for all future reporting of claim transactions. |
Q: | HOW SHOULD PAYMENT TRANSACTIONS THAT ARE VOIDED OR STOP PAID BE HANDLED? |
A: | If a payment transaction is reported to prior to the void or stop pay, the transaction must be cancelled in order to remove it from the database. If the void or stop pay occurs before a transaction is reported, then the void or stop pay transaction will not need to be reported. |
Q: | HOW WILL DATA SUBMITTERS REPORT CHANGES TO A PREVIOUSLY REPORTED CLAIM? |
A: |
Key fields that change require a cancellation record to first remove the record from the database. After cancelling the previously reported record, submit a new record with all key fields including those that did not change. Include Transaction Code 01 (original), with Transaction Date reported as the date the key field change was made in the source system and all other data elements must be reported according to the specific data element reporting rule. Key fields are defined as: Carrier Code, Policy Number, Policy Effective Date, Claim Number Identifier, Bill ID Number, Line ID Number, Transaction Code, and Transaction Date. Because the Medical Data Call is transactional, “non-key” field changes would be corrected through the reporting of future replacement transactions. |
Q: | THE CLAIM NUMBER IDENTIFIER DATA ELEMENT IS LIMITED TO 12 BYTES. SOME CLAIM NUMBERS CAN BE UP TO 18 BYTES. HOW SHOULD CARRIERS HANDLE THIS? |
A: | Use the same 12-digit Claim Number this is reported on the Unit Statistical Report for the same claim. Claim number is required for file acceptance. |
Q: | FOR RECORD REPLACEMENTS AND CANCELLATIONS, SHOULD CARRIERS REPORT THE ENTIRE BILL ON RESUBMISSIONS, UNLESS AN ERROR IS RECEIVED? |
A: | The reporting rules for record replacements and cancellations are found in the Medical Data Call Manual. If the records are true replacements, then the entire bill should be reported, otherwise the new record would overlay the previously reported record with missing data. On a cancellation record, only data required for linkage (key identifying fields) would be required to cancel a record. |
Q: | WHEN ARE MEDICAL TRANSACTIONS REQUIRED TO BE REPORTED? |
A: | The Medical Call Data is based on transaction date. The transaction date is the date the information was processed by the original source of the data. Do not use submitted or received date. Some carriers choose to report on the date of actual payment, which is permitted. |
Q: | WHEN DOES A TRANSACTION RECORD NEED TO BE UPDATED? IS IT WHEN ANY FIELD VALUE CHANGES? |
A: |
When key fields change, carriers should cancel a record (transaction code = 02) and then submit a new record (transaction code = 01.) When non-key fields change, carriers should replace the original record with a new record (transaction code = 03) and include the new values. The key fields cannot be changed during the replacement transaction so that our data processing system is able to match up the records. For non-key field changes, if there is a change being made for the same Bill ID and Line ID, then the carrier must replace the record. The incremental amount/change is NOT submitted as a separate transaction. The transactions are essentially reported “summarized” at the Bill ID and Line ID level. When replacing any data element, all the fields in the transaction must be reported regardless of whether the fields are changing. Key fields are defined as: Carrier Code, Policy Number, Policy Effective Date, Claim Number Identifier, Bill ID Number, Line ID Number, Transaction Code, and Transaction Date. |
Q: | WHEN A CARRIER BEGINS REPORTING, WHICH TRANSACTIONS WOULD BE IN THE INITIAL REPORT – BILLS WHICH HAVE A SERVICE REPORTING DATE ON OR AFTER THE CARRIER BEGAN REPORTING OR BILLS WHICH ARE RECEIVED AFTER THE CARRIER BEGAN REPORTING? |
A: |
Reporting requirements are related to transaction dates. Do not use service date as a method of determining what transactions go into the file. The only other date that matters for purposes of inclusion in the data file is Accident Date. Accident Date is important because of the duration of the reporting requirement which states that transactions must be reported until medical transactions no longer occur for the claim or 30 years from the Accident Date, whichever comes first. |
Q: | PAYMENTS SUCH AS MILEAGE CHARGES, TRANSPORTATION CHARGES, HOTEL EXPENSES, AND NURSE CASE MANAGEMENT EXPENSES ARE CODED AS MEDICAL PAYMENTS IN OUR SYSTEM. ARE THESE TYPES OF PAYMENTS TO BE REPORTED ON THE MEDICAL DATA CALL? |
A: | If the items in question are services for which your company pays medical benefits, and they can be captured at the detail level, they should be reported for the Medical Data Call. However, medical expenses incurred for the benefit of the carrier, and thus reported under allocated expenses for Unit Statistical Reporting, should not be reported for the Medical Data Call. |
Q: | WILL REIMBURSEMENTS TO THE CLAIMANT OR EMPLOYER FOR A BILL THAT THEY HAVE PAID BE EXCLUDED FROM THE MEDICAL DATA CALL? |
A: | No, if a service was provided by a medical service provider and a bill was submitted, whether paid by the claimant or insurer, the line item for the service should be reported. |
Q: | IF PAID AMOUNT = 0 AND CHARGED AMOUNT > 0, DO YOU REPORT TO MEDICAL DATA CALL? |
A: |
Yes, transactions where the paid amount is zero should be reported as long as a paid amount of zero is deemed to be the final payment amount after the transaction has been processed (e.g., denying a payment because the service wasn't medically necessary), and the reason for a zero paid amount is not due to a duplicated billing or because the claim is denied. However, if a claim is denied prior to reporting any transactions, (e.g., denying a payment because it is a non-workers compensation injury), no transactions should be sent for that claim. If medical transactions were reported to Medical Data Call prior to the claim being denied, those transactions should be cancelled. |
Q: | IF AMOUNT CHARGED IS = 0, DO YOU REPORT TO MEDICAL DATA CALL? |
A: | If original record reports charged $0, we would not normally receive a transaction for a service that did not contain a charge. However, if the insurer makes a payment even though charges are zero, that transaction should be sent. |
Q: | DO YOU REPORT DENIED BILLS TO MEDICAL DATA CALL? |
A: | Since Medical Data Call is medical transactional data, and not a claim data call, if medical transactions were reported and then the claim was subsequently denied (e.g. non-workers compensation injury) those reported transactions should be cancelled. If a claim is denied prior to reporting any transactions, then no transactions should be reported for that claim. Also, if the claim is a workers compensation claim and all services on a bill were denied, for example, the services were not related to the specific workers compensation injury and therefore will be paid by the claimant's group health policy, those services (transactions) should be not reported. |
Q: | FOR CANCELLATION TRANSACTIONS, DO CARRIERS ONLY REPORT KEY FIELDS OR ALL FIELDS? |
A: | It is not necessary to submit all fields in this case. When submitting a cancellation record, submit the following:
|
Q: | IF THE ORIGINAL BILL LINE ITEM WAS NOT REPORTED BECAUSE PAID WAS $0, THEN LATER ON THE BILL LINE ITEM WAS PAID, WOULD THE UPDATED TRANSACTION BE REPORTED AS AN ORIGINAL RECORD OR A REPLACEMENT RECORD? |
A: | If you choose to not report an original record because paid was $0 for valid reasons, and then later there was a paid amount >0 for that record, report the data as an original record. If you send a replacement record that does not match back to an original record, the replacement record will be rejected. |
Q: | SHOULD BILL LINE ITEMS AGAINST COAL CLASSES (WHERE THE POLICY IS COAL) BE REPORTED TO MEDICAL DATA CALL? |
A: | No, those bill line items to not have to be reported to Medical Data Call. |
Q: | SHOULD BILL LINE ITEMS ON CLAIMS AGAINST COMMERCIAL CLASSES (WHERE THE POLICY IS COAL) BE REPORTED TO THE MEDICAL DATA CALL? |
A: | Yes, those bill line items should be reported to Medical Data Call. |
Q: | SHOULD SUBROGATION TRANSACTIONS BE REPORTED TO MEDICAL DATA CALL? |
A: | Do not report original or replacement subrogation-related records or medical bill line adjustments related to subrogation in your data submissions to Medical Data Call. |
Q: | SOME CARRIERS MAY NOT CAPTURE THE POLICY EFFECTIVE DATE DATA ELEMENT IN THEIR SYSTEMS. CAN CARRIERS DEFAULT TO ACCIDENT DATE INSTEAD? |
A: | No, the carrier must report the Policy Effective Date in effect at the time of the accident. Do not report the policy inception date. Policy Effective Date is a critical field and must be populated. |
Q: | SOME CARRIERS MAY NOT CAPTURE THE POLICY NUMBER IDENTIFIER DATA ELEMENT IN THEIR SYSTEMS. WHAT SHOULD BE REPORTED IN THIS CASE? |
A: | Policy Number Identifier is a critical field and must be populated. |
Q: | SOME CARRIERS MAY NOT CAPTURE REGULATORY (REQUIRED) DATA ELEMENTS IN THEIR SYSTEMS. WHAT SHOULD BE REPORTED IN THIS CASE? |
A: | We recognize that data elements such as Carrier Code, Policy Number, Policy Effective Date and Claim Number may only reside in the carrier system. Since the data reporting is ultimately the carrier’s responsibility, carriers need to ensure this data is provided to any entity, such as medical bill review vendor, that will be reporting the data on behalf of the carrier. The Carrier Code, Policy Number Policy Effective Date and Claim Number must be the same as reported on the Unit Statistical data. |
Q: | SHOULD THE INTEREST PENALTY FOR LATE MEDICAL BILL PAYMENT BE INCLUDED AS A SEPARATE LINE ITEM WHEN APPLICABLE? |
A: | The interest penalty for late medical bill payment should not be reported to the Medical Data Call. |
Q: | SHOULD THE INITIAL REPORT OF MEDICAL DATA CALL INCLUDE EXISTING CLAIMS WITH MEDICAL EXPENSE INCURRED IN THAT QUARTER OR NEW CLAIMS ONLY? |
A: | All transactions that occurred in the quarter based on transaction date, whether for existing claims (up to 30 years old) or new claims, should be reported. We do not expect prior history to be reported for any existing claims that are reported. |
INDUSTRY CODE SETS | |
Q: | DOES MEDICAL DATA CALL REQUIRE THE USE OF INDUSTRY STANDARD CODES FOR DATA ELEMENTS SUCH AS PROVIDER TAXONOMY CODE, PLACE OF SERVICE CODE, PAID PROCEDURE CODE, PAID PROCEDURE MODIFIER CODE, AND ICD DIAGNOSTIC CODE, OR WILL THE CARRIER BE ALLOWED TO USE INTERNAL CODES FROM THEIR SYSTEM OR VENDOR’S SYSTEM? |
A: | Data validation edits will compare the codes reported by the data provider against the standard codes defined and maintained by the various industry organizations. Although we will not reject individual records for invalid or missing codes, we will consider the correct reporting of the field an overall factor in the quality and acceptance of the data. |
Q: | WHY IS THERE A SECONDARY PROCEDURE CODE FIELD WHEN EACH RECORD IS BASED ON A TRANSACTION AT THE LINE LEVEL OF A BILL AND THEREFORE THERE WOULD ONLY BE ONE PAID PROCEDURE CODE? |
A: | Although generally only one Paid Procedure Code is listed on each line on the medical form, multiple codes may apply. The Secondary Procedure Code should be reported when it is identified and will be reported primarily in facility billing. Report the primary code in the Paid Procedure Code field, and the Secondary Procedure Code in the Secondary Procedure Code field. |
Q: | WHAT IS MEANT BY PAID PROCEDURE CODE MODIFIER? |
A: | The Paid Procedure Code Modifier represents a service or procedure that has been altered by a specific circumstance without changing the definition of the service or procedure. The modifiers provide more details related to the Paid Procedure Code. |
Q: | IS THERE A PREFERRED HIERARCHY FOR REPORTING PAID PROCEDURE CODES WHEN MORE THAN ONE MAY BE APPLICABLE? |
A: | The preferred hierarchy for reporting Paid Procedure Codes is as follows:
|
Q: | IS THERE A DEFAULT DIAGNOSIS CODE WE SHOULD USE FOR REPORTING TRANSACTIONS FOR WHICH WE HAVE NOT RECEIVED A DIAGNOSIS CODE FROM THE PHARMACY VENDOR? |
A: | When a diagnosis code is not present, it is acceptable to leave the field blank. We recognize that prescription drug transactions will not typically include a diagnosis code. |
Q: | FOR THE DATA ELEMENT PRIMARY ICD DIAGNOSTIC CODE, THIS IS ONLY VALID FOR PHYSICIAN AND HOSPITAL. IS THERE A DEFAULT OR SHOULD WE SEND A BLANK FOR PHARMACY? |
A: | When a diagnosis code is not present, it is acceptable to leave the field blank. If possible, the pharmacy should obtain the ICD code from the prescribing physician. Note the default code 999.9 is not a valid code for the Medical Data Call. |
Q: | WHAT TYPES OF DIAGNOSTIC CODES WILL BE ACCEPTED FOR MEDICAL DATA CALL? |
A: | Default codes and generic “home grown” codes are not considered valid. Data edits will validate all ICD codes submitted against the standard industry diagnostic codes. Although we will not reject individual records for invalid or missing codes, we will consider the correct reporting of the field an overall factoring the quality and acceptance of the quarterly data. |
Q: | THERE ARE INSTANCES WHERE A HOSPITAL BILL MAY HAVE SUMMARY AND DETAIL LINES, WHERE THE SUMMARY LINE CONTAINS THE REVENUE CODE AND THE DETAIL LINE CONTAINS THE CPT®/HCPCS CODE. IN THAT INSTANCE, WOULD IT BE SUFFICIENT TO REPORT ONLY THE REVENUE CODE OR ARE CARRIERS REQUIRED TO REPORT THE CPT®/HCPCS CODE AS WELL? |
A: | Since Revenue Codes provide only broad classifications, they should only be reported as a Paid Procedure Code when no other code was used to determine the reimbursement. In other words, if the CPT®/HCPCS code was used to determine the reimbursement amount, report the CPT®/HCPCS code associated with the reimbursement in the Paid Procedure Code field (Positions 153-177) and the Revenue Code in the Secondary Procedure Code field (Positions 290-314). |
Q: | HOW DO I KNOW WHICH NETWORK SERVICE CODE TO REPORT? |
A: | If the claimant received a medical service from an HMO, PPO, or other network provider, then report the code that appropriately reflects the network association for the provider. There does not need to be a network reduction or discount applied. For example, if the provider is an “in network” PPO provider but there is no PPO discount or other reduction, it is still a PPO record because the provider was part of a PPO network. |
Q: | REGARDING THE NETWORK SERVICE CODE FIELD, WHAT IS THE DIFFERENCE BETWEEN A PPO AND A PARTICIPATION AGREEMENT? |
A: | A Preferred Provider Organization (PPO) is a network of medical care providers contracted by the insurer to provide various medical care services to covered employees for specified fees. A participation agreement could be a specific arrangement with the medical provider outside of a PPO arrangement. If there are medical providers with whom that the payer has multiple network arrangements, then the Network Service Code reporting hierarchy would be PPO (Y), HMO (H), and then Participation Agreement (P.) |
Q: | IS THERE A PREFERRED HIERARCHY FOR REPORTING NETWORK SERVICE CODE (POSITION 274)? |
A: | The preferred hierarchy for reporting Network Service Code is as follows:
|
Q: | IF ICD PROCEDURE CODE IS THE BASIS FOR REIMBURSEMENT, HOW DO WE REPORT IT? |
A: | Medical Data Call will not accept ICD procedure codes on medical claims. Instead, carriers should submit the CPT®/HCPCS code as the Paid Procedure Code and the Revenue Code as the Secondary Procedure Code (if available.) |
Q: | IS IT ACCEPTABLE TO USE DEFAULT VALUES FOR THE PLACE OF SERVICE OR PROVIDER TAXONOMY FIELDS WHEN REPORTING PHARMACY BILLS THAT DO NOT PROVIDE THESE CODES? |
A: | Carriers may report the following default values for pharmacy bills:
|
Q: | THE INSTRUCTIONS FOR THE CMS-1500 HEALTH INSURANCE CLAIM FORM INDICATE THAT THE PROVIDER TAXONOMY NUMBER IS OPTIONAL FOR COMPLETING THE PROVIDER OF SERVICE OR SUPPLIER INFORMATION FIELDS. IS THE PROVIDER TAXONOMY CODE ONLY TO BE REPORTED TO MEDICAL DATA CALL IF IT IS INCLUDED WITH THE CLAIM FORM? |
A: | Provider Taxonomy Code is a required field for the Medical Data Call. As noted in the source column of the Record Layout, this information may be obtained from either the provider or payer. Since the CMS-1500 form does not require the Provider Taxonomy, it may be necessary for the data reporting entity to “build” a provider file. Many commercial bill review software packages include a provider file that “links” the provider name, address, ID (NPI, Tax ID, or FEIN) and provider type/taxonomy. |
Q: | HOW SHOULD CARRIERS POPULATE THE PROVIDER TAXONOMY CODE FIELD? |
A: | Many carriers have purchased software from their billing vendor which allows them to assign the provider taxonomy code. Medical Data Call has not identified, promoted or recommended any specific stand-alone software product that will associate NPI’s or FEIN’s with a provider taxonomy code. |
Q: | SOME CARRIERS MAY NOT CAPTURE THE PROVIDER TAXONOMY CODE DATA ELEMENT IN THEIR SYSTEMS. WHAT SHOULD BE REPORTED IN THIS CASE? |
A: | Provider Taxonomy Code is a priority field. We understand that this field may not be readily available to all data reporters but it is very important that data reporters work to get this field properly populated. |
Q: | IS THERE A WAY FOR MEDICAL DATA CALL TO POPULATE THE PROVIDER TAXONOMY CODE IF THE CARRIER PROVIDES THE PROVIDER NAME, PROVIDER ADDRESS AND FEIN (AS PROVIDER NUMBER)? |
A: | Medical Data Call cannot provide this service to carriers. |
Q: | FOR THE PLACE OF SERVICE CODE DATA ELEMENT, DOES THIS APPLY ONLY TO PHYSICIANS? |
A: | No, the Place of Service code applies to all settings where healthcare is delivered, including pharmacies. The Place of Service code also applies to any health care professional (physician, nurse, etc.) |
Q: | THE PLACE OF SERVICE CODE (POSITIONS 282-289) IS INTENDED FOR PHYSICIAN-RELATED SERVICES (CMS FORM) ONLY. SINCE THE UB FORM FOR FACILITIES DOES NOT HAVE THE PLACE OF SERVICE, HOW IS THIS FIELD TO BE REPORTED FOR A FACILITY BILL? |
A: | Place of Service must be reported whenever possible. Since the UB form does not have Place of Service, data providers have developed crosswalks based on Type of Bill from the UB form. For example, if Type of Bill is = 11X, then Place of Service = 21 (Inpatient Hospital) and if Type of Bill = 13X, then Place of Service = 22 (Outpatient Hospital.) This crosswalk in included in the Medical Data Call Manual. |
Q: | IF PLACE OF SERVICE IS NOT AVAILABLE, HOW DO CARRIERS POPULATE THE FIELD? |
A: | We recognize that Place of Service may not readily be available, but it is a priority field so it is important that carriers work to get the field properly populated. Since it is an alpha-numeric field, carriers would blank-fill until they are able to obtain the information. |
EDITING | |
Q: | WILL A VENDOR REPORTING ON BEHALF OF A CARRIER BE REQUIRED TO REPORT ALL OF THE DATA ELEMENTS IN THE RECORD LAYOUT? |
A: | Yes. Although we will validate each data element, we will not reject a record based on a single error on a single data element, nor will we request that a correction be made to a single data element in order to load the record into production. The exception to this will be the data elements required on the Submission Control record. Without these elements, we cannot process the file and the submission will be rejected. We perform Quality Tracking on each data submission, which is a process that uses tolerance levels based on the criticality of the data element. |
RESOURCES | |
Q: | WILL AN ONLINE TRACKING TOOL BE AVAILABLE FOR TRACKING THE STATUS OF DATA SUBMITTED? |
A: | Yes, the file tracking application is called Medical Data Manager. This web-based application provides detailed information related to data submission file tracking and data quality tracking. |
TESTING | |
Q: | THE MEDICAL DATA CALL ELECTRONIC SUBMISSION GUIDELINE FOR TESTING ADVISES CARRIERS TO SUBMIT A TEST FILE WITH TRANSACTION VOLUME BETWEEN 5,000 AND 50,000 RECORDS. IS IT ACCEPTABLE FOR CARRIES TO SUBMIT A TEST FILE WITH LESS THAN 5,000 RECORDS? |
A: | Yes, carriers may submit test files with less than 5,000 records. We recommend that the test file contain enough records to make it a worthwhile test that incorporates various data scenarios. Some carriers can accomplish this with only a few hundred records. |
MISCELLANEOUS / OTHER | |
Q: | WILL THE MEDICAL DATA CALL DATA BE SHARED WITH OTHER RESEARCH ORGANIZATIONS? |
A: | No, Medical Data Call will not share the medical data we collect with other research organizations. |