fix: correct broken forum URLs across docs and Rmd sources (Fixes #754)

docs/cdmPrivacy.html

@@ -557,7 +557,7 @@ <h1>The Data Holder’s Responsibility</h1>
 of rule sets and exemplar IRB and local governance workflows that can be
 made available to institutions navigating these processes for the first
 time. If your organization does not have an established data governance
-process, please reach out on the <a href="forums.ohdsi.org">OHDSI
+process, please reach out on the <a href="https://forums.ohdsi.org">OHDSI
 Forums</a> under “Implementers” and the community can respond with
 shared guidance from their own deployments. As a community, we aim to
 conduct research that keeps patient-level data local and share only

docs/contribute.html

@@ -507,7 +507,7 @@ <h1 class="title toc-ignore">Ask A Question</h1>
 <div id="check-the-forum" class="section level1">
 <h1>Check the Forum</h1>
 <p>Chances are someone else has already asked your question on the <a
-href="https:\forums.ohdsi.org">forum</a> and it has been answered.</p>
+href="https://forums.ohdsi.org">forum</a> and it has been answered.</p>
 </div>
 <div id="check-the-issue-log" class="section level1">
 <h1>Check the Issue Log</h1>

docs/faq.html

@@ -529,7 +529,7 @@ <h1 class="title toc-ignore">OMOP CDM Frequently Asked Questions</h1>
 full builder freely available on <a
 href="https://github.com/OHDSI/ETL-CDMBuilder">github</a> that has been
 written for a variety of data sources.</p>
-<p>The <a href="http://forums.ohdsi.org/">community forums</a> are also
+<p>The <a href="https://forums.ohdsi.org/">community forums</a> are also
 a great place to ask questions if you are stuck or need guidance on how
 to represent your data in the common data model. Members are usually
 very responsive!</p>

extras/archive/OMOP_CDM_PDF.html

@@ -3471,7 +3471,7 @@ <h2>MEASUREMENT</h2>
 <td align="left">measurement_datetime</td>
 <td align="left">Yes</td>
 <td align="left">datetime</td>
-<td align="left">The date and time of the Measurement. Some database systems don’t have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time <a href="http://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314">forum discussion</a>)</td>
+<td align="left">The date and time of the Measurement. Some database systems don’t have a datatype of time. To accommodate all temporal analyses, datatype datetime can be used (combining measurement_date and measurement_time <a href="https://forums.ohdsi.org/t/date-time-and-datetime-problem-and-the-world-of-hours-and-1day/314">forum discussion</a>)</td>
 </tr>
 <tr class="even">
 <td align="left">measurement_time</td>

rmd/cdmPrivacy.Rmd

@@ -15,7 +15,7 @@ The OMOP CDM is a person-centric model. Being person-centric means the model can
 - The United States Department of Health & Human Services´ Office for Civil Rights has defined PHI as any Personal Identifying Information  (PII) that – individually or combined – could potentially identify a specific individual, their past, present or future healthcare, or the method of payment. There are eighteen unique identifiers considered to be PHI: 1) names, 2) geographic data, 3) all elements of dates, 4) telephone numbers, 5) FAX numbers, 6) email addresses, 7) Social Security numbers (SSN), 8) medical record numbers (MRN), 9) health plan beneficiary numbers, 10) account numbers, 11) certificate/license numbers, 12) vehicle identifiers and serial numbers including license places, 13) device identifiers and serial numbers, 14) web URLs, 15) internet protocol addresses, 16) biometric identifiers (i.e. retinal scan, fingerprints), 17) full face photos and comparable images, and 18) any unique identifying number, characteristic or code. PHI is no longer considered PHI when it de-identified of these unique attributes. PHI is commonly referred to in relation to the Health Insurance Portability and Accountability Act (HIPAA) and associated legislation such as the Health Information Technology for Economic and Clinical Health Act (HITECH) [2]. 
 
 # The Data Holder's Responsibility 
-In OHDSI, it is the responsibility of each data holder to know, understand and follow local data governance processes related to use of the OMOP CDM. In the United States, these processes will follow your organization's local interpretation for maintaining compliance to PII and PHI protection. In OMOP CDM implementations containing European Union citizen data, local governance processes will include measures to comply with General Data Protection Regulation (GDPR) [3]. As a community, the OHDSI data network covers more than 330 databases from 34 countries. There is extensive community knowledge on the interpretation of rule sets and exemplar IRB and local governance workflows that can be made available to institutions navigating these processes for the first time. If your organization does not have an established data governance process, please reach out on the [OHDSI Forums](forums.ohdsi.org) under "Implementers" and the community can respond with shared guidance from their own deployments. As a community, we aim to conduct research that keeps patient-level data local and share only aggregate results.
+In OHDSI, it is the responsibility of each data holder to know, understand and follow local data governance processes related to use of the OMOP CDM. In the United States, these processes will follow your organization's local interpretation for maintaining compliance to PII and PHI protection. In OMOP CDM implementations containing European Union citizen data, local governance processes will include measures to comply with General Data Protection Regulation (GDPR) [3]. As a community, the OHDSI data network covers more than 330 databases from 34 countries. There is extensive community knowledge on the interpretation of rule sets and exemplar IRB and local governance workflows that can be made available to institutions navigating these processes for the first time. If your organization does not have an established data governance process, please reach out on the [OHDSI Forums](https://forums.ohdsi.org) under "Implementers" and the community can respond with shared guidance from their own deployments. As a community, we aim to conduct research that keeps patient-level data local and share only aggregate results.
 
 # Complying with Privacy Preservation
 Complying with local governance processes depends on the rule set being used. There may be allowable times when data use agreements and data transfer agreements exist between collaborating institutions to facilitate sharing of PII and PHI. In this section we will discuss common rule sets that organizations adhere to.

rmd/contribute.Rmd

@@ -8,7 +8,7 @@ output:
 
 # Check the Forum
 
-Chances are someone else has already asked your question on the [forum](https:\\forums.ohdsi.org) and it has been answered. 
+Chances are someone else has already asked your question on the [forum](https://forums.ohdsi.org) and it has been answered. 
 
 # Check the Issue Log
 

rmd/faq.Rmd

@@ -15,7 +15,7 @@ During the extract, transform, load (ETL) process of converting a data source in
 
 You or someone in your organization will need to create a process to build your CDM. Don’t worry though, you are not alone! The open nature of the community means that much of the code that other participants have written to transform their own data is available for you to use. If you have a data license for a large administrative claims database like IBM MarketScan® or Optum’s Clinformatics® Extended Data Mart, chances are that someone has already done the legwork. Here is one example of a full builder freely available on [github](https://github.com/OHDSI/ETL-CDMBuilder) that has been written for a variety of data sources.
 
-The [community forums](http://forums.ohdsi.org/) are also a great place to ask questions if you are stuck or need guidance on how to represent your data in the common data model. Members are usually very responsive!
+The [community forums](https://forums.ohdsi.org/) are also a great place to ask questions if you are stuck or need guidance on how to represent your data in the common data model. Members are usually very responsive!
 
 **3. Are any tables or fields optional?**