Find meaningful ways to contribute

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

This issue requires implementing a feature to export approved diagnosis codes in a plain, per-person format (CSV or JSON) for use by external Hierarchical Condition Category (HCC) risk-score calculators. The export should exclude sensitive personal identifiers and focus solely on opaque subject IDs, dates of service, codes, and approval digests, ensuring privacy and deterministic output.

This issue aims to improve the parsing of the ICD-10-CM alphabetic index by preserving the hierarchical structure of main terms and subterms. Currently, the system flattens this structure, losing information about combination codes and cross-references, which this change will rectify by exposing index paths for generated candidates.

This issue proposes adding two new CLI commands, `openmed code suggest` and `openmed code verify`, to the OpenMed tool. These commands will allow batch users and evaluators to programmatically suggest and verify medical codes from notes, improving automation and testing capabilities within CI environments. The implementation will focus on the CLI layer, ensuring local-first data handling and emitting results in JSON format.

The user is requesting a feature to implement smooth window maximize and minimize animations, similar to those found on macOS, specifically for the Dock component. This enhancement aims to improve the visual user experience by adding a more polished feel to window transitions.

This issue proposes adding "code first" and "use additional code" sequencing hints to ICD-10-CM candidate codes. This will help flag manifestation codes that are missing their required etiology codes and ensure reviewers check for necessary additional conditions, improving coding accuracy.

This issue proposes adding functionality to report the freshness of installed vocabulary packages based on their expiry dates. It aims to make users aware of stale data, especially for time-sensitive terminologies like ICD-10-CM. The implementation involves projecting package dates onto a freshness manifest, updating the `openmed vocab list --json` output, and allowing callers to enforce fresh package requirements.

This issue is a call for testers to verify camera functionality on various ESP32-P4 displays with the HomeTiles v0.7.0 software. Users are asked to report their display model, camera status, image quality, and stream performance to help populate a testing table.

This issue proposes adding new methods to the Python service client to interact with terminology routes. These methods will allow Python callers to perform operations like lookup, validate code, expand, and translate without manually constructing parameters. The implementation includes mapping errors to typed client exceptions and thorough testing.

This issue proposes adding new command-line interface (CLI) commands to the OpenMED tool for performing terminology operations like lookup, validation, expansion, and translation. These commands will operate offline, reading data from local files, and will emit results in a standardized JSON format. The implementation will focus on the CLI layer, with dependencies on other issues for the core terminology operations.

This issue proposes the implementation of a `$subsumes` operation for FHIR CodeSystems, specifically for ICD-10-CM and HPO hierarchies. This functionality is needed to determine if one code is a parent, child, or unrelated to another within these terminologies, which is crucial for value-set checks, coding conflict rules, and cohort criteria. The implementation will involve adding a new `subsumes` function and ensuring it correctly handles different relationships and error conditions.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue proposes implementing a reader for CMS ICD-9-CM and ICD-10-CM General Equivalence Mappings (GEMs) to be loaded as local ConceptMaps. The goal is to accurately translate GEMs flags into ConceptMap equivalences and handle combination scenarios, enabling better longitudinal record analysis.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This is a feature request to add support for Emby, a media server similar to Jellyfin. The author believes it would be a relatively simple integration due to API similarities with Jellyfin, but is unable to implement it themselves. They are looking for a community contributor to develop and submit a pull request.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

This issue proposes adding support for filtering, pagination (offset and count), and active-only status to the local ValueSet expansion engine. Currently, local expansion returns all members, while remote expansion supports these parameters. The implementation will modify the local expansion to accept and apply these parameters, returning paginated results and echoing applied parameters in the response.

This is a feature request to add support for the Deluge download client to the arr-mcp application. The request outlines the technical requirements, including using its JSON-RPC API and handling a specific failure mode where the web UI is reachable but the daemon is not. It also specifies the process for submitting a pull request, emphasizing the need for live fixtures and testing against a specific Deluge version.

This issue proposes expanding LOINC ValueSets locally by leveraging LOINC part properties, which are currently ignored by the ValueSet filters. The implementation will involve mapping LOINC property names to loader metadata and supporting various filter operators for these properties, specifically for the LOINC system. This aims to enable offline expansion of lab value sets that rely on these properties.

This issue proposes to deprecate the use of repo-relative default paths for state files in the openmed library. Currently, these defaults can lead to unintended writes into the Python environment when the library is installed as a wheel. The implementation involves emitting deprecation warnings, introducing an explicit `OPENMED_GATES_DIR` setting, and updating documentation.

The `apply_patch` tool in Copilot CLI bypasses a security guardrail that checks for modifications to sensitive paths. This occurs because the tool embeds target paths within the patch text, which the current path extraction logic fails to recognize. The issue requires updating the path parsing mechanism to correctly identify and validate all modified paths against the guardrail.

This issue addresses a discrepancy in how service rate limits are applied in multi-replica deployments. Currently, rate limits are per-process, meaning a deployment with multiple replicas effectively allows a higher rate than intended. The proposed solution introduces a `OPENMED_SERVICE_RATE_LIMIT_SCOPE` setting to explicitly define whether limits are per-process or cluster-wide, and adds warnings for multi-replica deployments without a declared scope.

This issue proposes adding built-in health check endpoints (`/health/live` and `/health/ready`) to the application. These endpoints would be opt-in and designed to be used by load balancers and Kubernetes probes, providing a standardized way to monitor application health during startup, operation, and shutdown without cluttering access logs or the OpenAPI schema.

This issue proposes enhancing Meshery.io's theme functionality by respecting the user's system theme preference when no manual choice is made, and by synchronizing theme changes across all open browser tabs. The goal is to provide a more intuitive and consistent user experience.

This issue proposes adding a deprecation warning for the relation scorecard when it's signed using the built-in development key. This is to encourage users to provide their own signing keys and to align with the behavior of federated leakage reports. The change includes marking reports signed with the built-in key as development-only in their metadata and documenting the upcoming removal of the built-in key in version 7.0.

This issue proposes to enhance the pathology parser to extract specific fields like margin status, lymph node involvement, and invasion status from synoptic sections. Currently, these crucial fields are ignored, leading to incomplete data for cancer registries and tumor boards. The implementation will involve parsing explicit 'Label: value' lines and returning verbatim values with their original spans.

This issue proposes to enhance the radiology report parsing functionality by extracting explicit follow-up recommendations. The goal is to identify and structure information such as modality, interval, and body site from these recommendations to improve patient safety by preventing missed follow-ups. The implementation should focus solely on explicitly stated recommendations and not infer any.

This is a very broad and aspirational issue requesting to make the "Space Invaders" game awesome, likely within the Phaser game framework. It's tagged for "help wanted" and "hacktoberfest," suggesting a desire for community contributions to enhance an existing or new Space Invaders implementation.

A hive instance, 'hosted-ibm-alchemy-logg-ptoo', has encountered an 'agent_login_required' runtime error, indicating that a login is necessary for its operation. This error has been detected 5 times within a 10-minute window, suggesting a recurring issue that needs investigation and resolution.

A runtime error occurred in the github-relay component of the hive, specifically within the pr-request watcher. The error indicates that the head branch of a pull request was not found on the remote repository, likely due to a push authentication failure by the agent. This has been observed 5 times in the last 10 minutes.