Avoid multiple links to same target

jmandel · jmandel · commit ceae94ac5314 · 2024-10-22T16:18:43.000-05:00
diff --git a/add_links.ts b/add_links.ts
@@ -57,19 +57,26 @@ async function addLinks() {
       content = content.replace(/\[([^\]]+)\]\(https:\/\/build\.fhir\.org\/ig\/HL7\/[^)]+\)/g, '$1');
 
       let linkCount = 0;
+      const insertedUrls = new Set<string>();
+
       for (const linkifier of linkifiers) {
         if (linkifier.packageId !== currentIGName) {
-          const regex = new RegExp(`\\b${escapeRegExp(linkifier.term)}\\b(?![^\\[]*\\])`, 'g');
-          let hasReplaced = false;
-          content = content.replace(regex, (match) => {
-            if (!hasReplaced) {
-              hasReplaced = true;
-              linkCount++;
-              const repoName = packageToRepo[linkifier.packageId] || linkifier.packageId;
-              return `[${match}](https://build.fhir.org/ig/HL7/${repoName})`;
-            }
-            return match;
-          });
+          const repoName = packageToRepo[linkifier.packageId] || linkifier.packageId;
+          const targetUrl = `https://build.fhir.org/ig/HL7/${repoName}`;
+
+          if (!insertedUrls.has(targetUrl)) {
+            const regex = new RegExp(`\\b${escapeRegExp(linkifier.term)}\\b(?![^\\[]*\\])`, 'g');
+            let hasReplaced = false;
+            content = content.replace(regex, (match) => {
+              if (!hasReplaced) {
+                hasReplaced = true;
+                linkCount++;
+                insertedUrls.add(targetUrl);
+                return `[${match}](${targetUrl})`;
+              }
+              return match;
+            });
+          }
         }
       }
 
diff --git a/summaries/hl7.cda.us.ccdar2dot2.md b/summaries/hl7.cda.us.ccdar2dot2.md
@@ -1,4 +1,4 @@
-This standard, known as Consolidated [CDA](https://build.fhir.org/ig/HL7/hl7.cda.us.ccda) ([C-CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd)) 3.0, aims to improve the exchange of patient information between healthcare systems in the United States. It provides detailed templates for creating various types of clinical documents, such as discharge summaries and referral notes, ensuring consistent formatting and data representation.
+This standard, known as [Consolidated CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd) (C-CDA-ccda-2.1-sd)) 3.0, aims to improve the exchange of patient information between healthcare systems in the United States. It provides detailed templates for creating various types of clinical documents, such as discharge summaries and referral notes, ensuring consistent formatting and data representation.
 
 C-CDA 3.0 consolidates previous versions, removes outdated elements, and adds new templates to align with current data requirements. It uses a library of modular templates for document headers, sections, and entries, allowing for reuse across different document types. The standard also establishes a contextual framework in the document header that applies throughout, with the ability to override at lower levels when needed.
 
diff --git a/summaries/hl7.cda.us.eyecare.md b/summaries/hl7.cda.us.eyecare.md
@@ -1,6 +1,6 @@
 This standard aims to improve how eyecare data is shared electronically between healthcare systems. It focuses on capturing key information from eye exams, such as visual acuity, refraction, diagnostic tests, and posterior segment observations, in a consistent format.
 
-The standard uses [Clinical Document Architecture](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-core-sd) (CDA) templates as a foundation, specifically adapting the Physical Exam section for eyecare. It organizes related eye exam observations into groups and uses SNOMED CT codes to ensure consistent terminology for tests, methods, and findings.
+The standard uses [Clinical Document Architecture](https://build.fhir.org/ig/HL7/CDA-core-sd)-core-sd) (CDA) templates as a foundation, specifically adapting the Physical Exam section for eyecare. It organizes related eye exam observations into groups and uses SNOMED CT codes to ensure consistent terminology for tests, methods, and findings.
 
 Specific templates and value sets are defined for various aspects of eye exams, including visual acuity, refraction, and diagnostic tests like dry eye assessments. The standard also provides examples of how to structure this information within clinical documents.
 
diff --git a/summaries/hl7.fhir.us.ccda.md b/summaries/hl7.fhir.us.ccda.md
@@ -1,6 +1,6 @@
-This standard bridges two major healthcare data formats used in the United States: C-[CDA](https://build.fhir.org/ig/HL7/hl7.cda.us.ccda) and FHIR. It provides a way to translate clinical information between these formats, allowing systems using either standard to exchange data seamlessly.
+This standard bridges two major healthcare data formats used in the United States: [C-CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd) and FHIR. It provides a way to translate clinical information between these formats, allowing systems using either standard to exchange data seamlessly.
 
-The standard focuses on representing common clinical concepts found in [C-CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd) documents using FHIR resources. It leverages [US Core](https://build.fhir.org/ig/HL7/US-Core) FHIR profiles for key data elements like problems, allergies, medications, and patient demographics. This enables consistent sharing of crucial patient information across different healthcare systems.
+The standard focuses on representing common clinical concepts found in C-CDA-ccda-2.1-sd) documents using FHIR resources. It leverages [US Core](https://build.fhir.org/ig/HL7/US-Core) FHIR profiles for key data elements like problems, allergies, medications, and patient demographics. This enables consistent sharing of crucial patient information across different healthcare systems.
 
 Key features include the use of FHIR's document approach, where a central resource acts as a container for clinical data. It also provides detailed mapping guidance between C-CDA elements and FHIR resources, ensuring accurate translation of medical concepts and terminology.
 
diff --git a/summaries/hl7.fhir.us.cqfmeasures.md b/summaries/hl7.fhir.us.cqfmeasures.md
@@ -1,6 +1,6 @@
 This standard, titled "Quality Measure Implementation Guide," aims to standardize the creation and exchange of electronic clinical quality measures (eCQMs) using FHIR. It focuses on the US healthcare system, referencing regulations from the Centers for Medicare & Medicaid Services (CMS).
 
-The standard introduces several key features to improve eCQM development and use. It incorporates [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) ([CQL](https://build.fhir.org/ig/HL7/cql)) for defining measure logic, which allows for more precise and computable measure specifications. It also outlines how to specify data requirements for measure calculation and describes the use of terminology services for standardized coding.
+The standard introduces several key features to improve eCQM development and use. It incorporates [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) (CQL) for defining measure logic, which allows for more precise and computable measure specifications. It also outlines how to specify data requirements for measure calculation and describes the use of terminology services for standardized coding.
 
 A significant component of the standard is its guidance on representing composite measures, which combine multiple quality indicators into a single score. It also details the concept of a measure repository service for managing and distributing FHIR-based measures.
 
diff --git a/summaries/hl7.fhir.us.davinci-dtr.md b/summaries/hl7.fhir.us.davinci-dtr.md
@@ -1,6 +1,6 @@
 This standard aims to streamline the process of collecting patient documentation required by health insurance payers for purposes like prior authorization and claims processing. It enables payers to express their documentation requirements in a computable format using FHIR Questionnaires, allowing providers to easily gather and submit necessary information.
 
-The standard automates data collection by leveraging [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) ([CQL](https://build.fhir.org/ig/HL7/cql)) to extract existing patient data from EHRs, reducing manual entry and errors. It supports both pre-defined questionnaires and adaptive forms that adjust based on user responses.
+The standard automates data collection by leveraging [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) (CQL) to extract existing patient data from EHRs, reducing manual entry and errors. It supports both pre-defined questionnaires and adaptive forms that adjust based on user responses.
 
 Key features include the use of FHIR Questionnaires for defining documentation requirements, CQL for data extraction and logic implementation, and [SMART on FHIR](https://build.fhir.org/ig/HL7/smart-app-launch) integration for seamless EHR compatibility.
 
diff --git a/summaries/hl7.fhir.us.hsds.md b/summaries/hl7.fhir.us.hsds.md
@@ -4,4 +4,4 @@ The standard builds upon the Human Services Data Specification (HSDS), making it
 
 Healthcare providers can use this standard to find and refer patients to appropriate social services. Insurance companies can incorporate social service referrals into care management programs. Consumers can use mobile apps to search for and access social services in their communities.
 
-This standard is designed to meet requirements outlined in the CMS Interoperability and Patient Access Rule, which mandates standardized API access to provider directories, including social service providers. It also leverages US Core profiles, which are based on the United States Core Data for Interoperability ([USCDI](https://build.fhir.org/ig/HL7/US-Core)).
+This standard is designed to meet requirements outlined in the CMS Interoperability and Patient Access Rule, which mandates standardized API access to provider directories, including social service providers. It also leverages US Core profiles, which are based on the United States Core Data for Interoperability (USCDI).
diff --git a/summaries/hl7.fhir.us.ph-library.md b/summaries/hl7.fhir.us.ph-library.md
@@ -2,6 +2,6 @@ This standard, called the US Public Health Profiles Library (USPHPL), aims to si
 
 The USPHPL addresses the issue of redundant profile definitions across different public health reporting systems. It establishes a centralized library of reusable profiles, promoting consistency in public health data exchange. The standard leverages FHIR to define profiles, value sets, and extensions specific to public health reporting needs.
 
-Key users include healthcare organizations, EHR companies, public health agencies, and researchers. Healthcare organizations use it to structure their public health data for reporting, while public health agencies use it to receive and analyze reports. The USPHPL aligns with broader healthcare standards like [US Core](https://build.fhir.org/ig/HL7/US-Core) and incorporates elements from the United States Core Data Interoperability ([USCDI](https://build.fhir.org/ig/HL7/US-Core)) standard, ensuring compliance with federal regulations.
+Key users include healthcare organizations, EHR companies, public health agencies, and researchers. Healthcare organizations use it to structure their public health data for reporting, while public health agencies use it to receive and analyze reports. The USPHPL aligns with broader healthcare standards like [US Core](https://build.fhir.org/ig/HL7/US-Core) and incorporates elements from the United States Core Data Interoperability (USCDI) standard, ensuring compliance with federal regulations.
 
 By standardizing public health data exchange, the USPHPL supports improved disease tracking and outbreak detection, contributing to better population health outcomes.
diff --git a/summaries/hl7.fhir.us.pq-cmc-fda.md b/summaries/hl7.fhir.us.pq-cmc-fda.md
@@ -1,6 +1,6 @@
-This standard aims to streamline how pharmaceutical companies submit drug information to the U.S. Food and Drug Administration (FDA) for review. It focuses on the quality, chemistry, manufacturing, and controls ([PQ/CMC](https://build.fhir.org/ig/HL7/FHIR-us-pq-cmc)) section of drug applications, making this information structured and machine-readable using FHIR.
+This standard aims to streamline how pharmaceutical companies submit drug information to the U.S. Food and Drug Administration (FDA) for review. It focuses on the quality, chemistry, manufacturing, and controls (PQ/CMC) section of drug applications, making this information structured and machine-readable using FHIR.
 
-The standard aligns with the electronic [Common Technical Document](https://build.fhir.org/ig/HL7/FHIR-us-pq-cmc) ([eCTD](https://build.fhir.org/ig/HL7/FHIR-us-pq-cmc)) format and follows a phased approach, starting with solid oral dosage forms. It uses various FHIR resources to represent PQ/CMC information while maintaining human-readable narratives within the data bundles.
+The standard aligns with the electronic [Common Technical Document](https://build.fhir.org/ig/HL7/FHIR-us-pq-cmc) (eCTD) format and follows a phased approach, starting with solid oral dosage forms. It uses various FHIR resources to represent PQ/CMC information while maintaining human-readable narratives within the data bundles.
 
 Pharmaceutical companies are the primary users, structuring PQ/CMC data according to the standard for FDA submission. FDA reviewers benefit from receiving structured data, enabling more efficient and accurate review of drug applications. Software vendors developing regulatory submission systems also need to align with this standard.
 
diff --git a/summaries/hl7.fhir.uv.bulkdata.md b/summaries/hl7.fhir.uv.bulkdata.md
@@ -6,4 +6,4 @@ Security and privacy are prioritized, with mandatory encryption and recommended
 
 Key beneficiaries include developers of backend services and FHIR servers, healthcare organizations, and researchers. It enables improved data sharing and interoperability, potentially accelerating healthcare research and supporting quality improvement initiatives.
 
-The standard aligns with the [US Core](https://build.fhir.org/ig/HL7/US-Core) Data for Interoperability ([USCDI](https://build.fhir.org/ig/HL7/US-Core)) and recommends the SMART Backend Services Authorization Profile for secure access management.
+The standard aligns with the [US Core](https://build.fhir.org/ig/HL7/US-Core) Data for Interoperability (USCDI) and recommends the SMART Backend Services Authorization Profile for secure access management.
diff --git a/summaries/hl7.fhir.uv.cpg.md b/summaries/hl7.fhir.uv.cpg.md
@@ -2,6 +2,6 @@ This standard aims to improve healthcare by making clinical practice guidelines
 
 The standard streamlines CPG development, sharing, and implementation. It reduces duplicate efforts by providing a common format, minimizing inconsistencies across healthcare organizations. This accelerates the adoption of best practices into clinical workflows and enables better measurement of guideline compliance and effectiveness.
 
-Key features include a conceptual knowledge architecture separating patient state, care plans, and workflow execution. It uses [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) ([CQL](https://build.fhir.org/ig/HL7/cql)) to express CPG logic in a computable format and defines a standardized lifecycle for guideline activities.
+Key features include a conceptual knowledge architecture separating patient state, care plans, and workflow execution. It uses [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) (CQL) to express CPG logic in a computable format and defines a standardized lifecycle for guideline activities.
 
 The standard benefits multiple stakeholders. Guideline developers gain structured tools for creating computable CPGs. Healthcare providers can more easily integrate guidelines into their systems. Clinicians receive more consistent decision support based on best practices. Ultimately, patients may experience improved quality and consistency of care based on up-to-date clinical guidelines.
diff --git a/summaries/hl7.fhir.uv.cql.md b/summaries/hl7.fhir.uv.cql.md
@@ -1,4 +1,4 @@
-This standard aims to streamline the use of [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) ([CQL](https://build.fhir.org/ig/HL7/cql)) with FHIR resources in healthcare settings. It provides a unified approach for representing and evaluating clinical logic across various scenarios, including decision support, public health reporting, and research eligibility criteria.
+This standard aims to streamline the use of [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) (CQL) with FHIR resources in healthcare settings. It provides a unified approach for representing and evaluating clinical logic across various scenarios, including decision support, public health reporting, and research eligibility criteria.
 
 The standard defines profiles for packaging CQL and its compiled form as FHIR Library resources. It also includes profiles for representing information about logic libraries and their evaluation results. A key feature is the specification of a CQL evaluation service, enabling consistent implementation across different systems.
 
diff --git a/summaries/hl7.fhir.uv.fhirpath.md b/summaries/hl7.fhir.uv.fhirpath.md
@@ -2,4 +2,4 @@ This standard defines FHIRPath, a language for navigating and extracting data fr
 
 FHIRPath is designed to work with various healthcare information models, not just FHIR. Its lightweight nature makes it easier to implement and use compared to more complex languages. The standard supports literals, operators, functions, and type checking, with its formal syntax defined using an Antlr 4.0 grammar.
 
-Developers can use FHIRPath to create interoperable healthcare applications with streamlined data navigation and manipulation. This enables the development of more powerful decision support systems, quality measures, and clinical workflows. FHIRPath aligns with the [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) ([CQL](https://build.fhir.org/ig/HL7/cql)) standard, simplifying data traversal for quality measure definitions.
+Developers can use FHIRPath to create interoperable healthcare applications with streamlined data navigation and manipulation. This enables the development of more powerful decision support systems, quality measures, and clinical workflows. FHIRPath aligns with the [Clinical Quality Language](https://build.fhir.org/ig/HL7/cql) (CQL) standard, simplifying data traversal for quality measure definitions.

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-This standard, known as Consolidated [CDA](https://build.fhir.org/ig/HL7/hl7.cda.us.ccda) ([C-CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd)) 3.0, aims to improve the exchange of patient information between healthcare systems in the United States. It provides detailed templates for creating various types of clinical documents, such as discharge summaries and referral notes, ensuring consistent formatting and data representation.`
	`1`	`+This standard, known as [Consolidated CDA](https://build.fhir.org/ig/HL7/[CDA](https://build.fhir.org/ig/HL7/CDA-core-sd)-ccda-2.1-sd) (C-CDA-ccda-2.1-sd)) 3.0, aims to improve the exchange of patient information between healthcare systems in the United States. It provides detailed templates for creating various types of clinical documents, such as discharge summaries and referral notes, ensuring consistent formatting and data representation.`
`2`	`2`
`3`	`3`	`C-CDA 3.0 consolidates previous versions, removes outdated elements, and adds new templates to align with current data requirements. It uses a library of modular templates for document headers, sections, and entries, allowing for reuse across different document types. The standard also establishes a contextual framework in the document header that applies throughout, with the ability to override at lower levels when needed.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -4,4 +4,4 @@ The standard builds upon the Human Services Data Specification (HSDS), making it`
`4`	`4`
`5`	`5`	`Healthcare providers can use this standard to find and refer patients to appropriate social services. Insurance companies can incorporate social service referrals into care management programs. Consumers can use mobile apps to search for and access social services in their communities.`
`6`	`6`
`7`		`-This standard is designed to meet requirements outlined in the CMS Interoperability and Patient Access Rule, which mandates standardized API access to provider directories, including social service providers. It also leverages US Core profiles, which are based on the United States Core Data for Interoperability ([USCDI](https://build.fhir.org/ig/HL7/US-Core)).`
	`7`	`+This standard is designed to meet requirements outlined in the CMS Interoperability and Patient Access Rule, which mandates standardized API access to provider directories, including social service providers. It also leverages US Core profiles, which are based on the United States Core Data for Interoperability (USCDI).`
Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,4 @@ Security and privacy are prioritized, with mandatory encryption and recommended`
`6`	`6`
`7`	`7`	`Key beneficiaries include developers of backend services and FHIR servers, healthcare organizations, and researchers. It enables improved data sharing and interoperability, potentially accelerating healthcare research and supporting quality improvement initiatives.`
`8`	`8`
`9`		`-The standard aligns with the [US Core](https://build.fhir.org/ig/HL7/US-Core) Data for Interoperability ([USCDI](https://build.fhir.org/ig/HL7/US-Core)) and recommends the SMART Backend Services Authorization Profile for secure access management.`
	`9`	`+The standard aligns with the [US Core](https://build.fhir.org/ig/HL7/US-Core) Data for Interoperability (USCDI) and recommends the SMART Backend Services Authorization Profile for secure access management.`