Update repository URLs in docs and cloud workflow to use new reposito…

…ry name, add trademark used with permission notice.

PiperOrigin-RevId: 579012251

README.md

@@ -1,9 +1,9 @@
-# Medical Claims Tools
-<a href="https://github.com/google/medical_claims_tools/actions">
-  <img src="https://github.com/google/medical_claims_tools/workflows/go_test/badge.svg" alt="GitHub Actions Build Status" />
+# Bulk FHIR Tools
+<a href="https://github.com/google/bulk_fhir_tools/actions">
+  <img src="https://github.com/google/bulk_fhir_tools/workflows/go_test/badge.svg" alt="GitHub Actions Build Status" />
 </a>
-<a href="https://godoc.org/github.com/google/medical_claims_tools">
-  <img src="https://godoc.org/github.com/google/medical_claims_tools?status.svg" alt="Go Documentation" />
+<a href="https://godoc.org/github.com/google/bulk_fhir_tools">
+  <img src="https://godoc.org/github.com/google/bulk_fhir_tools?status.svg" alt="Go Documentation" />
 </a>
 
 👀 _Please tell us more about your interest in or usage of these tools at our [survey here](https://docs.google.com/forms/d/e/1FAIpQLSdmWHaGc41gWiobMT6kNd0PGPPeWGeS-LyG6CrGZ79moaUIEQ/viewform)!_
@@ -138,11 +138,11 @@ To set up the `bulk_fhir_fetch` program to run periodically on a GCP VM, take a
 
 If cloning the repo for production use, we recommend cloning the repository at
 the latest released version, which can be found in the
-[releases](https://github.com/google/medical_claims_tools/releases)
+[releases](https://github.com/google/bulk_fhir_tools/releases)
 tab. For example for version `v0.1.5`:
 
 ```sh
-git clone --branch v0.1.5 https://github.com/google/medical_claims_tools.git
+git clone --branch v0.1.5 https://github.com/google/bulk_fhir_tools.git
 ```
 
 ## Build
@@ -161,3 +161,6 @@ directory.
 This repository also contains example [analysis notebooks](analytics)
 using synthetic data that showcase query patterns once the data is in FHIR Store
 and BigQuery.
+
+## Trademark
+FHIR® is the registered trademark of HL7 and is used with the permission of HL7.

docs/gcp_vm_setup.md

@@ -1,4 +1,4 @@
-# GCP VM Setup for medical_claims_tools
+# GCP VM Setup
 
 This documentation details how to setup a standard GCP Debian VM to build and
 run `bulk_fhir_fetch` from source. It also details how to configure the VM service
@@ -36,14 +36,15 @@ account to have the ability to upload to FHIR store.
         command will look something like `rm -rf /usr/local/go && tar -C
         /usr/local -xzf <installer name>`
 
-4.  Clone the medical_claims_tools repository
+4.  Clone the repository
 
     ```sh
-    git clone https://github.com/google/medical_claims_tools
+    git clone https://github.com/google/bulk_fhir_tools
     ```
 
 5.  Build `bulk_fhir_fetch`:
 
     ```sh
+    cd bulk_fhir_tools
     go build cmd/bulk_fhir_fetch/bulk_fhir_fetch.go
     ```

orchestration/bulk_fetch_workflow.yaml

@@ -89,9 +89,9 @@ main:
                         echo Sending results to bucket: ${BUCKET} && \n
                         echo $(apt-get -y update) && \n
                         echo $(apt-get -y install git-all) && \n
-                        echo $(git clone https://github.com/google/medical_claims_tools.git) && \n
-                        cd medical_claims_tools/ && \n
-                        go version && \n
+                        echo $(git clone https://github.com/google/bulk_fhir_tools.git) && \n
+                        cd bulk_fhir_tools/ && \n
+                        echo $(ls) && \n
                         echo building go file && \n
                         go build cmd/bulk_fhir_fetch/bulk_fhir_fetch.go && \n
                         echo $( ls .) && \n