Application programming interfaces — Establishment and maintenance — Interface requirements

Tenn. Code Ann. § 56-7-128, under General Provisions.

Tenn. Code Ann. § 56-7-128

(a) As used in this section, “health insurance entity” has the same meaning as defined in § 56-7-109.

(b) To facilitate patient and provider access to health information, a health insurance entity shall establish and maintain the following application programming interfaces (API) for the benefit of all insureds and contracted providers:(1) Patient access API, as described in 42 CFR 422.119 (a)-(e);(2) Provider directory API, as described in 42 CFR 422.120;(3) Payer-to-payer exchange API, as described in 42 CFR 422.121(b);(4) Provider access API, as described in 42 CFR 422.121(a); and(5) Prior authorization API, as described in 42 CFR 422.122.

(1) Patient access API, as described in 42 CFR 422.119 (a)-(e);

(2) Provider directory API, as described in 42 CFR 422.120;

(3) Payer-to-payer exchange API, as described in 42 CFR 422.121(b);

(4) Provider access API, as described in 42 CFR 422.121(a); and

(5) Prior authorization API, as described in 42 CFR 422.122.

(c) [Deleted by 2025 amendment.]

(d) For the API required by this section, a health insurance entity shall establish and maintain each API for its insured and providers at the earliest date CMS requires any of its regulated plan or product types to establish and maintain the same API.

(e) This section does not limit existing requirements under this chapter.

(f) The commissioner of commerce and insurance may promulgate rules to effectuate this section. The rules must be promulgated in accordance with the Uniform Administrative Procedures Act, compiled in title 4, chapter 5.