HI530 Unit 7 Standards Evaluation Example

Five Specialty Practices, Four Record Systems, One Question About What Each Can Receive: A Unit 7 Standards Evaluation for Sending Referrals From a Primary Care Network

[Student Name]

Purdue University Global

HI530: Clinical Terminologies, Vocabularies, and Information Standards

Unit 7 Standards Evaluation

[Instructor Name]

[Date]

Tolland Ridge Health, the five practices and every score are composite; the standards, regulation and studies cited are real.

The Problem

Tolland Ridge Health's twelve primary care clinics send about 1,900 referrals a month to five outside specialty practices: cardiology, orthopedics, gastroenterology, dermatology and behavioral health. Today the referral travels by fax, the specialist's office retypes it, and the consult note returns by fax days or weeks later, if it returns at all. The network wants an electronic path that delivers a usable referral and brings a usable consult note back.

What a Referral Must Carry

Before comparing standards, the team agreed on what a referral must deliver to be useful on arrival. It must identify the patient well enough for the specialist's office to match or register them without a phone call. It must state the clinical question in the referring clinician's words, because a referral without a question is the most common reason specialists send patients back. It must carry the active problem list, current medications, allergies and recent relevant results in coded form, so the specialist's staff can import them rather than retype them. It must include insurance and authorization details, since a missing authorization delays the first visit more often than any clinical gap. And it must name the referring clinician and a return address for the consult note. A standard that carries some of these but not others leaves the specialist's staff on the phone, which is the fax era with better formatting.

Receiver Inventory

1. Cardiology, record system A: Direct address, yes; can import a structured referral document, yes; FHIR endpoint available, yes; accepts inbound version 2 referral messages, no; returns consult notes as structured documents over Direct.

2. Orthopedics, record system B: Direct, yes; imports structured referral, yes; FHIR, no; version 2, no; returns consult notes by Direct.

3. Gastroenterology, record system A: Direct, yes; imports, yes; FHIR, yes; version 2, yes, through an existing laboratory interface engine; returns consult notes by Direct.

4. Dermatology, record system C: Direct, yes; imports, yes; FHIR, no; version 2, no; returns by Direct.

5. Behavioral health, record system D: Direct, yes; imports, no, can only display documents; FHIR, no; version 2, no; returns notes by fax.

Totals: five of five hold Direct addresses; four of five can import structured referral documents; two expose FHIR endpoints; one accepts version 2 messages.

Weights

Weights were set by the network's referral management team before scoring and are defended on their own terms, so a reader can dispute a weight without disputing a score.

1. Receiver acceptance today: 40. A standard the specialist cannot accept delivers nothing.

2. Consult note return path: 20. A referral loop that does not close is only half solved.

3. Content structure: 15. Coded content can be imported rather than retyped.

4. Cost and effort to implement: 15.

5. Readiness for future needs: 10.

Scores

Each option is scored from 0 to 3 on each criterion.

1. HL7 version 2 referral messages. Acceptance 1, since only gastroenterology can receive them. Return path 0, since none of the practices sends consult notes back this way. Structure 2, with coded segments. Cost 1, since each practice would need its own point-to-point interface. Readiness 0. Weighted total: 85 of 300, or 28.3 percent.

2. Structured referral documents over Direct. Acceptance 3, since four practices can import and the fifth can at least display them. Return path 3, since four practices already return consult notes as structured documents by Direct. Structure 2, with coded sections inside a document. Cost 3, since every practice already holds a Direct address. Readiness 2. Weighted total: 275 of 300, or 91.7 percent.

3. FHIR through an application programming interface. Acceptance 1, since two practices expose endpoints. Return path 1. Structure 3, with individually addressable coded resources. Cost 1, since referral workflows over the interface would need custom development on both ends. Readiness 3, consistent with federal certification criteria for standardized interfaces (45 C.F.R. § 170.215). Weighted total: 150 of 300, or 50.0 percent.

The most modern standard scores lower than the document standard today, not because it is worse but because three of the five receivers cannot yet accept it.

Discussion

FHIR is the stronger standard on structure and future readiness, and apps built on it can plug into record systems in a consistent way (Mandel et al., 2016). But the evaluation's question is what works for these five practices now, and the answer is the structured document over Direct. Every practice can receive it, most can import it, and most already send consult notes back the same way, which closes the loop the network cares about most. The document option also needs the least change in each practice's daily work, since staff already open Direct messages for other purposes and would see referrals arrive in the same inbox. Version 2 messaging, the oldest of the three, fails on reach: building and maintaining five point-to-point interfaces for one practice's worth of acceptance is poor value. The one weak point is behavioral health, whose record system can display but not import documents. Its staff would read the referral rather than retype it, which is still better than fax, but its consult notes would continue to return by fax. Health information exchange research has long found that the slowest receiver sets the limits of any exchange (Vest & Gamm, 2010), and this practice is that receiver.

Recommendation

1. Adopt structured referral documents over Direct secure messaging for all five practices within six months.

2. Pilot FHIR-based referrals with cardiology and gastroenterology, the two practices with endpoints, in the following year, and re-run this evaluation then.

3. Work with the behavioral health practice and its vendor toward document import, and in the meantime track its consult note return rate separately.

4. Measure the share of referrals that receive a consult note back within 30 days, from a fax-era baseline of about 45 percent, with a target of 80 percent.

Limits

The inventory reflects each practice's current version and contracts, which may change. Scores were assigned by one team, and a different team might weight cost or readiness differently. Interoperability texts caution that every standard choice is a compromise between what is possible now and what is best later (Benson & Grieve, 2021), and this recommendation is designed to be revisited.

References

Benson, T., & Grieve, G. (2021). Principles of health interoperability: FHIR, HL7 and SNOMED CT (4th ed.). Springer.

45 C.F.R. § 170.215 (2024). https://www.ecfr.gov/current/title-45/section-170.215

Mandel, J. C., Kreda, D. A., Mandl, K. D., Kohane, I. S., & Ramoni, R. B. (2016). SMART on FHIR: A standards-based, interoperable apps platform for electronic health records. Journal of the American Medical Informatics Association, 23(5), 899-908. https://doi.org/10.1093/jamia/ocv189

Vest, J. R., & Gamm, L. D. (2010). Health information exchange: Persistent challenges and new strategies. Journal of the American Medical Informatics Association, 17(3), 288-294. https://doi.org/10.1136/jamia.2010.003673