# 90-590 Ch. 243: Ch. 243: Uniform Reporting System for Health Care Claims Data Sets

> Maine · Regulations · In force

URL: https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_243

## Section

- **Citation:** 90-590 Ch. 243
- **Heading:** Ch. 243: Uniform Reporting System for Health Care Claims Data Sets
- **Jurisdiction:** Maine
- **Kind:** Regulations
- **Status:** In force
- **Text as of:** August 14, 2026
- **Source:** Compiled text
- **Location:** Code of Maine Rules / 90-590 Maine Health Data Organization / Ch. 243

## Text

SUMMARY: This Chapter contains the provisions for filing health care claims data sets from all third-party payors, third-party administrators, Medicare health plan sponsors and pharmacy benefits managers.
The provisions include:
Identification of the organizations required to report;
Establishment of requirements for the content, format, method, and time frame for filing health care claims data;
Establishment of standards for the data reported; and
Compliance provisions.
1.	Definitions
Unless the context indicates otherwise, the following words and phrases shall have the following meanings:
Billing Provider. “Billing provider” means a provider or other entity that submits claims to health care claims processors for health care services directly performed or provided to a subscriber or member by a service provider.
Capitated Services. “Capitated services” means services rendered by a provider through a contract where payments are based upon a fixed dollar amount for each member monthly.
Carrier. "Carrier" means an insurance company licensed in accordance with 24-A M.R.S., including a health maintenance organization, a multiple employer welfare arrangement licensed pursuant to Title 24-A, Chapter 81, a preferred provider organization, a fraternal benefit society, or a nonprofit hospital or medical service organization or health plan licensed pursuant to 24 M.R.S. An employer exempted from the applicability of 24-A M.R.S., Chapter 56-A under the federal Employee Retirement Income Security Act of 1974, 29 United States Code, Sections 1001 to 1461 (1988) (“ERISA”) is not considered a carrier.
Co-Insurance. “Co-insurance” means the dollar amount a member pays as a pre-determined percentage of the cost of a covered service after the deductible has been paid.
Co-Payment. “Co-payment” means the fixed dollar amount a member pays to a health care provider at the time a covered service is provided or the full cost of a service when that is less than the fixed dollar amount.
Deductible
arrier.
Co-Insurance. “Co-insurance” means the dollar amount a member pays as a pre-determined percentage of the cost of a covered service after the deductible has been paid.
Co-Payment. “Co-payment” means the fixed dollar amount a member pays to a health care provider at the time a covered service is provided or the full cost of a service when that is less than the fixed dollar amount.
Deductible. "Deductible" means the total dollar amount a member pays towards the cost of covered services over an established period before any payments are made by the contracted third-party payor.
Dental Claims File. “Dental claims file” means a data file composed of service level remittance information including, but not limited to, member demographics, provider information, charge/payment information, and current dental terminology codes from all non-denied adjudicated claims for each billed service.
Designee. "Designee" means an entity with which the MHDO has entered into an arrangement under which the entity performs data collection, validation and management functions for the MHDO and is strictly prohibited from releasing information obtained in such a capacity.
Health Care Claims Processor. “Health care claims processor” means a third-party payor, third-party administrator, Medicare health plan sponsor, or pharmacy benefits manager.
Hospital. "Hospital" means any acute care institution required to be licensed pursuant to 22 M.R.S., Chapter 405.
MBI. “MBI” means the Center for Medicare and Medicaid Services Medicare Beneficiary Identifier.
Medical Claims File. “Medical claims file” means a data file composed of service level remittance information including, but not limited to, member demographics, provider information, charge/payment information, and clinical diagnosis/procedure codes from all non-denied adjudicated claims for each billed service.
Medicare Health Plan Sponsor
e and Medicaid Services Medicare Beneficiary Identifier.
Medical Claims File. “Medical claims file” means a data file composed of service level remittance information including, but not limited to, member demographics, provider information, charge/payment information, and clinical diagnosis/procedure codes from all non-denied adjudicated claims for each billed service.
Medicare Health Plan Sponsor. “Medicare health plan sponsor” means a health insurance carrier or other private company authorized by the United States Department of Health and Human Services, Centers for Medicare and Medicaid Services to administer Medicare Part C and Part D benefits under a health plan or prescription drug plan.
Member. “Member” includes the subscriber and any spouse or dependent who is covered by the subscriber’s policy.
Member Eligibility File. “Member eligibility file” means a data file composed of demographic information for each individual member eligible for medical, pharmacy, or dental insurance benefits for one or more days of coverage any time during the reporting month.
MHDO. "MHDO" means the Maine Health Data Organization.
M.R.S. “M.R.S.” means Maine Revised Statutes.
Non-hospital Provider. "Non-hospital provider" means any provider of health care services other than a hospital.
Pharmacy. “Pharmacy” means a drug outlet licensed under 32 M.R.S., Chapter 117.
Pharmacy Benefits Manager. "Pharmacy benefits manager" means an entity that performs pharmacy benefits management as defined in 24-A M.R.S. §4347, sub-section 17.
Pharmacy Benefits Manager Compensation. “Pharmacy benefits manager compensation” means the difference between:
the value of payments made by a carrier to its pharmacy benefits manager; and
the value of payments made by the pharmacy benefits manager to dispensing pharmacies for the provision of prescription drugs or pharmacy services with regard to pharmacy benefits covered by the carrier.
Pharmacy Claims File
efits Manager Compensation. “Pharmacy benefits manager compensation” means the difference between:
the value of payments made by a carrier to its pharmacy benefits manager; and
the value of payments made by the pharmacy benefits manager to dispensing pharmacies for the provision of prescription drugs or pharmacy services with regard to pharmacy benefits covered by the carrier.
Pharmacy Claims File. “Pharmacy claims file” means a data file composed of service level remittance information including, but not limited to, member demographics, provider information, charge/payment information, and national drug codes from all non-denied adjudicated claims for each prescription filled.
Plan Sponsor. “Plan sponsor” means any person, other than an insurer, who establishes or maintains a plan covering residents of the State of Maine, including, but not limited to, plans established or maintained by two or more employers or jointly by one or more employers and one or more employee organizations, or the association, committee, joint board of trustees or other similar group of representatives of the parties that establish or maintain the plan.
POS. “POS” means point of sale.
Provider. "Provider" means a health care facility, health care practitioner, health product manufacturer, health product vendor or pharmacy.
Rebate. “Rebate” means a discount, chargeback, or other price concession that affects the price of a prescription drug product, regardless of whether conferred through regular aggregate payments, on a claim-by-claim basis at the point-of-sale, as part of retrospective financial reconciliations (including reconciliations that also reflect other contractual arrangements), or by any other method. “Rebate” does not mean a “bona fide service fee”, as such term is defined in Section 447.502 of Title 42 of the Code of Federal Regulations, published October 1, 2019.
Service Provider. “Service provider” means the provider who directly performed or provided a health care service to a subscriber or member.
Subscriber
ations that also reflect other contractual arrangements), or by any other method. “Rebate” does not mean a “bona fide service fee”, as such term is defined in Section 447.502 of Title 42 of the Code of Federal Regulations, published October 1, 2019.
Service Provider. “Service provider” means the provider who directly performed or provided a health care service to a subscriber or member.
Subscriber. “Subscriber” is the insured individual.
Substance Use Disorder (SUD). “SUD” means a cluster of cognitive, behavioral, and physiological symptoms indicating that the individual continues using the substance despite significant substance-related problems such as impaired control, social impairment, risky use, and pharmacological tolerance and withdrawal, excluding tobacco/nicotine or caffeine use.
SUD Claims File: “SUD Claims File” means a data file composed of service level remittance information, de-identified in accordance with HIPPA regulations, including member demographics, provider information, charge/payment information, and clinical diagnosis/procedure codes from all non-denied, adjudicated claims and claim lines for each billed service for SUD or SUD related parts of medical and pharmacy claims.
Third-party Administrator. “Third-party administrator” means any person licensed by the Maine Bureau of Insurance under 24-A M.R.S., Chapter 18 who, on behalf of a plan sponsor, health care service plan, nonprofit hospital or medical service organization, health maintenance organization or insurer, receives or collects charges, contributions or premiums for, or adjusts or settles claims on residents of this State.
Third-party Payor. "Third-party payor" means a state agency that pays for health care services or a health insurer, carrier, including a carrier that provides only administrative services for plan sponsors, nonprofit hospital, medical services organization, or managed care organization licensed in the State.
2
contributions or premiums for, or adjusts or settles claims on residents of this State.
Third-party Payor. "Third-party payor" means a state agency that pays for health care services or a health insurer, carrier, including a carrier that provides only administrative services for plan sponsors, nonprofit hospital, medical services organization, or managed care organization licensed in the State.
2.	Health Care Claims Data Set Filing Description
Health care claims processors shall submit to the MHDO or its designee a completed health care claims data set for all members who are Maine residents in accordance with the requirements of this section. Each health care claims processor is also responsible for the submission of all health care claims processed by any sub-contractor on its behalf. The health care claims data set shall include, where applicable, a member eligibility file containing records associated with each of the claims files reported: a medical claims file, a pharmacy claims file, and/or a dental claims file. The data set shall also include supporting definition files for payor specific provider specialty codes. Third-party administrators and carriers acting as third-party administrators for self-funded employee benefit plans regulated by ERISA are not required to submit data for members in such plans.
A.	General Requirements
(1)	Adjustment Records. Adjustment records shall be reported with the appropriate positive or negative fields with the medical, pharmacy, and dental claims file submissions. Negative values shall contain the negative sign before the value. No sign shall appear before a positive value.
enefit plans regulated by ERISA are not required to submit data for members in such plans.
A.	General Requirements
(1)	Adjustment Records. Adjustment records shall be reported with the appropriate positive or negative fields with the medical, pharmacy, and dental claims file submissions. Negative values shall contain the negative sign before the value. No sign shall appear before a positive value.
(2)	Capitated Payment Arrangements. A capitated payment record shall be reported for every month that a member is covered under a particular payment arrangement. In addition, capitated service records shall be included in the medical claims file, if any services were provided to the member in a given month. Specific instructions for reporting capitated payments and services are provided below. For capitated payment arrangements that a payor indicates are 42 CFR Part 2 SUD-related, the payor shall provide a de-identified payment record in the capitated payments file and a de-identified capitated service record in the medical claims file for every SUD-related service provided. Associated 42 CFR Part 2 SUD-related payment and service records shall contain the same CSUM IDs. Follow the additional instructions in Appendices D-1 and G-1.
Payment Record. The purpose of a capitation payment summary record is to indicate the payment made to a provider each month for a member covered by a capitated service contract, regardless of whether any services were provided to the member in a given month. Only one summary claim record or line per member per month on a capitated service contract is reported in the capitated payments file, as specified in Appendix G-1.
Service Record. Separate service lines for each service provided under a capitated service contract shall be reported in the medical claims file, Appendix D-1, and flagged as capitated services. If no services were provided to a member on a capitated service contract in a given month, then no service lines are reported
tract is reported in the capitated payments file, as specified in Appendix G-1.
Service Record. Separate service lines for each service provided under a capitated service contract shall be reported in the medical claims file, Appendix D-1, and flagged as capitated services. If no services were provided to a member on a capitated service contract in a given month, then no service lines are reported. All data fields should be treated as on any other claim, except for the following ones, which are populated or left blank as specified: Paid Amount (MC063) is ‘0’; Payment Arrangement Type Indicator field (MC331) is ‘09’; the Procedure Code (MC055) for the specific procedure or service; Service Line Dates (MC334 and MC335) for the specific procedure or service; and the appropriate Quantity (MC061) greater than or equal to ‘1’.
(3)	Claims Records. Records for the medical, pharmacy, and dental claims file submissions shall be reported at the visit, service, or prescription level. The submission of the medical, pharmacy, and dental claims is based upon the paid dates and not upon the dates of service associated with the claims.
(4)	Codes
(a)	Code Sources. Unless otherwise specified, the code sources listed and described in Appendix A are to be utilized in association with the member eligibility file and medical, pharmacy, and dental claims file submissions.
(b)	Specific/Unique Coding. Except for provider, provider specialty, and individual, non-bundled procedure/diagnosis codes, specific or unique coding systems shall not be permitted as part of the health care claims data set submission.
(5)	Co-Insurance/Co-Payment. Co-insurance and co-payment are to be reported in two separate fields in the medical, pharmacy, and dental claims file submissions.
(6)	Coordination of Benefits Claims. Claims where multiple parties have financial responsibility shall be included with all medical, pharmacy, and dental claims file submissions.
itted as part of the health care claims data set submission.
(5)	Co-Insurance/Co-Payment. Co-insurance and co-payment are to be reported in two separate fields in the medical, pharmacy, and dental claims file submissions.
(6)	Coordination of Benefits Claims. Claims where multiple parties have financial responsibility shall be included with all medical, pharmacy, and dental claims file submissions.
(7)	Denied Claims. Denied claims shall be excluded from all medical, pharmacy, and dental claims file submissions. When a claim contains both approved and denied service lines, only the approved service lines shall be included as part of the health care claims data set submittal.
(8)	Eligibility Records. Records for the member eligibility file submission shall be reported at the individual member level with one record submitted for each claim type if the product codes are different. If a member is covered as both a subscriber and a dependent on two different policies during the same month, two records must be submitted.
(9)	Exclusions
(a)	Filing. Health care claims processors that have less than $2,000,000 per calendar year of adjusted premiums or claims processed, for premiums or claims subject to required reporting, are excluded from filing health care claim data sets and from the annual registration requirements of Section 3(A).
(b)	Medical Claims File Exclusions. All claims related to health care policies issued for specific disease, accident, injury, hospital indemnity, disability, long-term care, student comprehensive health, or vision coverage of durable medical equipment are to be excluded from the medical claims file submission. Claims related to Medicare supplemental, Tricare supplemental, or other supplemental health insurance policies are to be excluded if the claims are not considered to be primary. If the policies cover health care services entirely excluded by the Medicare, Tricare, or other program, the claims must be submitted
of durable medical equipment are to be excluded from the medical claims file submission. Claims related to Medicare supplemental, Tricare supplemental, or other supplemental health insurance policies are to be excluded if the claims are not considered to be primary. If the policies cover health care services entirely excluded by the Medicare, Tricare, or other program, the claims must be submitted. Claims for dental services containing current dental terminology codes are to be excluded from the medical claims file.
(c)	Member Eligibility File Exclusions. Members without medical, pharmacy, and/or dental coverage during the month reported shall be excluded.
(d)	Pharmacy Claims File Exclusions. Pharmacy services claims generated from non-retail pharmacies that do not contain national drug codes are part of the medical claims file and not the pharmacy claims file.
(10)	File Format. Each data file submission shall be an encrypted (AES-256) ASCII file, variable field length, and asterisk delimited.
(11)	Header and Trailer Records. Each member eligibility file and each medical, pharmacy, and dental claims file submission shall contain a header record and a trailer record. The header record is the first record of each separate file submission, and the trailer record is the last. The header and trailer record formats are described in Appendices B-1 and B-2.
(12)	Non-Duplicated Claims. A carrier or health care claims processor and any contracted entity acting on its behalf shall use best efforts to ensure that duplicate claims are not submitted to the MHDO or its designee.
(13)	Subscriber or Member Identification
eparate file submission, and the trailer record is the last. The header and trailer record formats are described in Appendices B-1 and B-2.
(12)	Non-Duplicated Claims. A carrier or health care claims processor and any contracted entity acting on its behalf shall use best efforts to ensure that duplicate claims are not submitted to the MHDO or its designee.
(13)	Subscriber or Member Identification
(a)	Social Security Numbers. Health care claims processors shall assign to each of their members a unique identification code that is the member’s social security number. If a health care claims processor does not collect the social security numbers for all members, the health care claims processor shall use the number of the subscriber and then assign a discrete two-digit suffix for each member under the subscriber’s contract.
(b)	Contract Numbers. If the subscriber’s social security number is not collected by the health care claims processor, the subscriber’s certificate or contract number shall be used in its place. The discrete two-digit suffix shall also be used with the certificate or contract number.
The unique member identification code assigned by each health care claims processor shall remain with each subscriber or member for the entire period of coverage for that individual.
(c)	Names. Health care claims processors shall submit the complete names of all subscribers and members.
(d)	Consistent, Inter-file Identifiers. A carrier or health care claims processor and any contracted entity acting on its behalf shall ensure that member and subscriber identifiers for the same individuals are unique and consistent across all eligibility and claims files.
l.
(c)	Names. Health care claims processors shall submit the complete names of all subscribers and members.
(d)	Consistent, Inter-file Identifiers. A carrier or health care claims processor and any contracted entity acting on its behalf shall ensure that member and subscriber identifiers for the same individuals are unique and consistent across all eligibility and claims files.
(e)	Carrier Specific Unique Member (CSUM) ID. As an inter-file identifier, the CSUM ID should uniquely and consistently identify a member in both the medical claims and the capitated payments files. The CSUM ID shall be used when the payor indicates that related records in the medical and capitation files contain 42 CFR Part 2 SUD-related data, and other inter-file identifiers shall be left blank. For fully identifiable data records that do not contain 42 CFR Part 2-related data, the CSUM ID shall be left blank, and all other inter-file identifiers shall be populated, when available. This ID must differ from any of the other identifiers on the record and may not be derived from any of these in a manner that the original values could be determined.
B.	Detailed File Specifications
(1)	Filled Fields. All required fields shall be filled where applicable. Non-required text and number fields shall be left blank when unavailable.
(2)	Position. All text fields are to be left justified. All numeric fields are to be right justified.
(3)	Signs. Positive values are assumed and need not be indicated as such. Negative values must be indicated with a minus sign and must appear in the left-most position of all numeric fields. Signed over punch characters are not to be utilized.
(4)	Individual Elements and Mapping. Individual data elements, data types, field lengths, field description/code assignments, and mapping locators (UB-04, CMS 1500, ANSI X12N 270/271, 835, 837) for each file type are presented in the following appendices:
ndicated with a minus sign and must appear in the left-most position of all numeric fields. Signed over punch characters are not to be utilized.
(4)	Individual Elements and Mapping. Individual data elements, data types, field lengths, field description/code assignments, and mapping locators (UB-04, CMS 1500, ANSI X12N 270/271, 835, 837) for each file type are presented in the following appendices:
(a)	(i)	Member Eligibility File Specifications – Appendix C-1
(ii)	Member Eligibility File Mapping to National Standard Formats – Appendix C-2
(b)	(i)	Medical Claims File Specifications – Appendix D-1
(ii)	Medical Claims File Mapping to National Standard Formats – Appendix D-2
(c)	(i)	Pharmacy Claims File Specifications – Appendix E-1
(ii)	Pharmacy Claims File Mapping to National Standard Formats – Appendix E-2
(d)	(i)	Dental Claims File Specifications – Appendix F-1
(ii)	Dental Claims File Mapping to National Standard Formats – Appendix F-2
(e)	(i)	Capitated Payments File Specifications – Appendix G-1
(ii)	Capitated Payments File Mapping to National Standard Formats – Appendix G-2
3.	Submission Requirements
A.	Registration/Contact and Enrollment Update. Each health care claims processor not excluded from submitting claims data under Section 2(A)(9)(a) shall complete a registration survey or update an existing one at https://mhdo.maine.gov/portal by February 28th of each year. It is the responsibility of the health care claims processor to amend, as needed, all company, contact and enrollment information.
B.	File Organization. The member eligibility file, medical claims file, pharmacy claims file, and the dental claims file are to be submitted to the MHDO or its designee as separate ASCII files. Each record shall be terminated with a carriage return (ASCII 13) or a carriage return line feed (ASCII 13, ASCII 10).
C.	Filing Method. Data files must be submitted to the MHDO’s Data Warehouse Portal via secure FTP or secure web upload interface. E-mail attachments shall not be accepted.
D.	Testing of Files
ntal claims file are to be submitted to the MHDO or its designee as separate ASCII files. Each record shall be terminated with a carriage return (ASCII 13) or a carriage return line feed (ASCII 13, ASCII 10).
C.	Filing Method. Data files must be submitted to the MHDO’s Data Warehouse Portal via secure FTP or secure web upload interface. E-mail attachments shall not be accepted.
D.	Testing of Files. Within one hundred and eighty days of the adoption of any changes to the data element content of the files as described in Section 2 and at least sixty days prior to the initial submission of the files or whenever the data element content of the files as described in Section 2 is subsequently altered, each health care claims processor shall submit to the MHDO or its designee a data set for comparison to the standards listed in Section 4. Based upon a calendar period of one month or one quarter, the size of the data files submitted shall correspond to the filing period established for each health care claims processor under subsection F of this Section.
E.	Rejection of Files. Failure to conform to the requirements subsections
A, B, or C of this Section shall result in the rejection of the applicable data file(s). All rejected files must be resubmitted in the appropriate, corrected form to the MHDO or its designee within 15 days.
F.	Filing Periods. The filing period for each applicable claims data file listed in Section 2 shall be determined by the minimum monthly total of Maine-resident members for whom claims are being paid by each health care claims processor. The data files are to be submitted in accordance with the following schedule:
If the data files submitted by an individual health care claims processor support or are related to the files submitted by another health care claims processor, the MHDO shall determine a filing period that is consistent for all parties involved.
G.	Replacement of Data Files
ing paid by each health care claims processor. The data files are to be submitted in accordance with the following schedule:
If the data files submitted by an individual health care claims processor support or are related to the files submitted by another health care claims processor, the MHDO shall determine a filing period that is consistent for all parties involved.
G.	Replacement of Data Files. No health care claims processor may replace a complete data file submission more than one year after the end of the month in which the file was submitted unless it can establish exceptional circumstances for the replacement. Any replacements after this period must be approved by the MHDO. Individual adjustment records may be submitted with any monthly data file submission.
H.	Run-Out Period. Health care claims processors shall submit medical, pharmacy, and/or dental claims files for a six-month period following the termination of coverage date for all members who are Maine residents.
4.	Standards for Data; Notification; Response
A.	Standards. The MHDO or its designee shall evaluate each member eligibility file, medical claims file, pharmacy claims file, and dental claims file submission in accordance with the following standards:
(1)	The applicable code for each data element identified in Appendices C-1, D-1, E-1, and F-1 shall be included within eligible values for the element;
(2)	Coding values indicating “data not available”, “data unknown”, or the equivalent shall not be used for individual data elements unless specified as an eligible value for the element;
(3)	Member sex, diagnosis and procedure codes, and date of birth and all other date fields shall be consistent within an individual record; and
-1, and F-1 shall be included within eligible values for the element;
(2)	Coding values indicating “data not available”, “data unknown”, or the equivalent shall not be used for individual data elements unless specified as an eligible value for the element;
(3)	Member sex, diagnosis and procedure codes, and date of birth and all other date fields shall be consistent within an individual record; and
(4)	Member identifiers shall be consistent across files.
B.	Notification. Upon completion of this evaluation, the MHDO or its designee will promptly notify each health care claims processor whose data submissions do not satisfy the standards for any filing period. This notification will identify the specific file and the data elements within them that do not satisfy the standards.
C.	Response. Each health care claims processor notified under subsection 4(B) will respond within 60 days of the notification by making the changes necessary in order to satisfy the standards.
5. Voluntary File Submissions
Any self-funded employee benefit plan regulated by ERISA may voluntarily submit completed healthcare data sets for Maine residents. The MHDO shall collect such data sets in accordance with the provisions of this chapter for uniform reporting system for health care claims data sets. Any such data shall be subject to the same laws and regulations as other MHDO data.
6.	Public Access
Information collected, processed and/or analyzed under this rule shall be subject to release to the public or retained as confidential information in accordance with 22 M.R.S. Chapter 1683 and Code of Maine Rules 90-590, Chapter 120, unless prohibited by state or federal law.
7
re claims data sets. Any such data shall be subject to the same laws and regulations as other MHDO data.
6.	Public Access
Information collected, processed and/or analyzed under this rule shall be subject to release to the public or retained as confidential information in accordance with 22 M.R.S. Chapter 1683 and Code of Maine Rules 90-590, Chapter 120, unless prohibited by state or federal law.
7.	Extensions or Waivers to Data Submission Requirements
If a health care claims processor due to circumstances beyond its control is temporarily unable to meet the terms and conditions of this rule, a written request must be made to the Compliance Officer of the MHDO as soon as it is practicable after the health care claims processor has determined that an extension or waiver is required. The written request shall include: the specific requirement to be extended or waived; an explanation of the cause; the methodology proposed to eliminate the necessity of the extension or waiver; and the time frame required to come into compliance. If the Compliance Officer does not approve the requested extension or waiver, the health claims processor making the request may submit a written request appealing the decision to the MHDO Board. The appeal shall be heard by the MHDO Board at the next regularly scheduled meeting following receipt of the request at the MHDO.
8.	Compliance
The failure to file, report, or correct health care claims data sets when required in accordance with the provisions of this rule may be considered a violation under 22 M.R.S. Sec. 8705-A and Code of Maine Rules 90-590, Chapter 100: Enforcement Procedures.

## Nearby sections

- [90-590 Ch. 10 Ch. 10: Determination of Assessments](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_10.md)
- [90-590 Ch. 50 Ch. 50: Prices for Data Sets, Fees for Programming and Report Generation, Duplication Rates](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_50.md)
- [90-590 Ch. 100 Ch. 100: Enforcement Procedures](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_100.md)
- [90-590 Ch. 120 Ch. 120: Release of Data to the Public](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_120.md)
- [90-590 Ch. 125 Ch. 125: Health Care Information that Directly Identifies an Individual](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_125.md)
- [90-590 Ch. 241 Ch. 241: Uniform Reporting System for Hospital Inpatient Data Sets and Hospital Outpatient Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_241.md)
- [90-590 Ch. 243 Ch. 243: Uniform Reporting System for Health Care Claims Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_243.md)
- [90-590 Ch. 247 Ch. 247: Uniform Reporting System for Non-Claims-Based Payments and Other Supplemental Health Care Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_247.md)
- [90-590 Ch. 270 Ch. 270: Uniform Reporting System for Quality Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_270.md)
- [90-590 Ch. 300 Ch. 300: Uniform Reporting System for Hospital Financial Data](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_300.md)
- [90-590 Ch. 340 Ch. 340: Uniform Reporting System for Reporting 340B Drug Program Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_340.md)
- [90-590 Ch. 570 Ch. 570: Uniform Reporting System for Prescription Drug Price Data Sets](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_570.md)
- [90-590 Ch. 630 Ch. 630: Uniform System for Reporting Baseline Information and Restructuring Occurrences for Maine Hospitals and Parent Entities](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_630.md)
- [90-590 Ch. 730 Ch. 730: Interagency Reporting of Cancer Registry and Vital Statistics Data](https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_730.md)

---

Source: Frix Law Library, https://www.frixlaw.com/law-library/statutes/STATE_ME_CMR_90_590_243. Check the current official text before relying on it. Not legal advice.