Lnk 3067 rc .0.1.1 patientid fix

[edward-miller-lcg]

🛠 Description of Changes

Please provide a high-level overview of the changes included in this PR.

🧪 Testing Performed

Please describe the testing that was performed on the changes included in this PR.

Summary by CodeRabbit

• New Features

  • Enhanced Azure Pipelines to support release branch triggers and improved tagging for Docker images.
  • Introduced new Postman collections for "Measure Eval (Java) Service" and "Tenant Service" with various API requests.
  • Added configuration updates for Loki logging service and authentication settings in relevant projects.

• Documentation

  • Updated README.md with a new Table of Contents and detailed sections on Link Cloud services, tools, and installation instructions.

• Data Updates

  • Introduced FHIR Bundles for patient healthcare interactions, including detailed records for services, conditions, encounters, and diagnostic reports.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces several modifications across multiple Azure Pipelines YAML configuration files to enhance the pipeline's functionality for handling release branches and tagging. Key changes include updates to branch triggers, the addition of new tasks for versioning and tagging, and modifications to Docker tasks. Additionally, various project files and configuration settings have been updated to reflect a new versioning scheme. New properties have been added to application configuration files, and two new Postman collections have been introduced, along with extensive updates to the README for improved clarity and structure.

Changes

File/Path	Change Summary
Azure_Pipelines/*.yaml	- Updated branch triggers to include release/*. - Added tasks for GetRevision@1, capturing Git commit hash, and constructing tagging variable MyTag. - Modified Docker task to use MyTag.
DotNet/Account/Account.csproj, ...	- Updated <Version> to 0.1.1 across multiple project files and appsettings.json. - Updated <VersionPrefix> in DotNet/Shared/Shared.csproj. - Updated Java pom.xml files to version 0.1.1.
Java/measureeval/src/main/resources/application.yml, ...	- Added app: link-dev under loki section. - Updated authority key in authentication section of validation project.
Postman/*.postman_collection.json	- Added new Postman collections: "Measure Eval (Java) Service" and "Tenant Service" with multiple API requests and new variables for base URLs.
README.md	- Added "Table of Contents" and several new sections detailing project structure, services, and tools. - Enhanced the "Introduction" section for clarity.
Scripts/load-sql-data.sql	- Introduced SQL script for database operations across multiple databases, including INSERT operations and transaction management.
Submission Example/Methodisthospital-ACH-20240801T000000-20240826T195759/*	- Added FHIR Bundles containing healthcare-related resources for patients, including metadata and service details.

Possibly related PRs

• LNK-2610 data acq mem issue #349: Modifications to the Data Acquisition service, potentially impacting the main PR's pipeline handling.
• LNK-2607 Facility Connection Validation Bug #350: Focus on reducing messaging and memory usage in the Data Acquisition service, suggesting a connection to the main PR's pipeline improvements.
• LNK-2769 Normalization ResourceAcquired Changes #467: Changes related to the normalization service that could relate to tagging and versioning improvements in the main PR.
• LNK-2883: Added Kafka health check to .NET services #494: Addition of Kafka health checks enhancing monitoring capabilities relevant to the main PR's updates.
• LNK-3005: app-label-configuration #496: Updates to application configuration for logging, indirectly relating to enhancements in the main PR.

Suggested reviewers

• dvargaslantana
• amphillipsLGC

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.