Skip to content
Skills Library
Programming · Tool integration

meddev-interoperability

/meddev-interoperability

Enable safe and standards-aligned interoperability: HL7 FHIR/IHE profiles, data formats, terminology mapping, and API design for medical data exchange. Use when working on interoperability in medical device software.

Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Enable safe and standards-aligned interoperability: HL7 FHIR/IHE profiles, data formats, terminology mapping, and API design for medical data exchange. Use when working on interoperability in medical device software.

Original author description

Enable safe and standards-aligned interoperability: HL7 FHIR/IHE profiles, data formats, terminology mapping, and API design for medical data exchange. Use when working on interoperability in medical device software.

How it works

  1. Purpose
  2. When to Apply
  3. Requirements (testable)
  4. Recommended Practices
  5. Patterns
  6. Anti-Patterns (risks)
  7. Verification Checklist
  8. Traceability
  9. References
  10. Changelog
Original SKILL.md headings · 84 lines, 514 words
SKILL.md preview
---
name: meddev-interoperability
description: 'Enable safe and standards-aligned interoperability: HL7 FHIR/IHE profiles, data formats, terminology mapping, and API design for medical data exchange. Use when working on interoperability in medical device software.'
license: MIT
metadata:
  skill_id: CONN-INTEROP
  version: 1.0.0
  last_updated: '2026-01-04'
  applies_to: Class A, Class B, Class C
  jurisdiction: FDA, EU MDR, Global
  prerequisites: REG-ISO14971, REG-FDA-PREMARKET
  category: connectivity
---

# Medical Device Interoperability

## Purpose
Enable safe and standards-aligned interoperability: HL7 FHIR/IHE profiles, data formats, terminology mapping, and API design for medical data exchange.

## When to Apply
- Designing or updating device APIs, data exchange, or integrations with HIS/EMR/cloud.
- Handling PHI or clinical decisions based on exchanged data.

## Requirements (testable)
1. Standards Use: Prefer established standards (HL7 FHIR, HL7 v2 where applicable, IHE profiles) for relevant data flows; document conformance. Rationale: interoperability and clarity.
2. Terminology: Use standard vocabularies (SNOMED CT, LOINC) for clinical concepts; map device codes to standard codes. Rationale: semantic consistency.
3. Data Integrity: Validate messages (schema/length/range); apply checksums/hashes over payloads where appropriate; reject/flag invalid data. Rationale: correctness.
4. Security & Privacy: Protect PHI with TLS 1.3+; enforce authz (scopes/roles); log access; minimize data shared. Rationale: confidentiality/integrity.
5. Error Handling: Provide clear, standard error responses; fail safe; no silent truncation. Rationale: predictable integration.
6. Traceability: Log message IDs, timestamps, and correlation IDs; link to requirements/tests; keep audit for safety-relevant exchanges. Rationale: accountability.
7. Interop Risks: Document interop-related hazards (misinterpretation, time sync, version mismatch) and mitigations. Rationale: safety.

## Recommended Practices
- Provide versioned APIs and explicit capability statements (e.g., FHIR CapabilityStatement).
- Time-sync devices (NTP/PTP) to avoid timestamp drift in clinical workflows.
- Use contract tests against partner systems; include negative cases.
- Avoid custom extensions unless necessary; document them clearly.

## Patterns
FHIR-like JSON validation (pseudo):
```python
# REQ-INTOP-VALID-01; TEST-INTOP-04
def validate_observation(obs: dict) -> bool:
    required = ["resourceType", "status", "code", "subject", "effectiveDateTime"]
    if obs.get("resourceType") != "Observation":
        return False
    return all(k in obs for k in required)
```

Terminology mapping table (YAML):
```yaml
# REQ-INTOP-TERM-02
device_code: FLOW_RATE
loinc: 8310-5
display: Infusion flow rate
```

Error response:
```json
// REQ-INTOP-ERR-03; TEST-INTOP-07
{ "error": "invalid-parameter", "detail": "missing code" }
```

## Anti-Patterns (risks)
- Custom proprietary formats without mapping -> risk: misinterpretation by HIS/EMR.
- Sending PHI over plaintext or weak TLS -> risk: data breach.
- Silent acceptance of invalid messages -> risk: wrong clinical decisions.
- No time sync -> risk: misleading timestamps in therapy/diagnostics.

## Verification Checklist
- [ ] Standards selected and documented; conformance statements present.
- [ ] Terminology mapped to SNOMED/LOINC (or applicable); mappings versioned.
- [ ] Message validation implemented; invalid data rejected/logged.
- [ ] TLS 1.3+ and authz enforced; PHI minimized; access logged.
- [ ] Error responses clear and standard; no silent truncation.
- [ ] Interop hazards documented with mitigations/tests.
- [ ] Time synchronization implemented and monitored.

## Traceability
- Requirements `REQ-INTOP-###` linked to contract/interop tests `TEST-INTOP-###`; logs maintain correlation IDs for message tracing.

## References
- HL7 FHIR R4/R5; HL7 v2 where applicable.
- IHE profiles relevant to devices (e.g., PCD-01, DEC).
- FDA interoperability guidance (2017).
- IEC 62304/ISO 14971 for risk integration.

## Changelog
- 1.0.0 (2026-01-04): Initial interoperability skill with standards use, validation, terminology, and security guidance.

## Audit History
- **2026-01-04**: Audit performed. Verified:
  - HL7 FHIR R4/R5 references accurate
  - IHE profiles (PCD-01, DEC) correctly mentioned
  - FDA interoperability guidance (2017) reference verified
  - SNOMED CT and LOINC terminology references appropriate

Versions

The database has no other skills named meddev-interoperability.

Database snapshot: 13.11.2026 · package version 802b2aacdd95 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100meddev-usb-medical
    Implement safe USB device connectivity: class selection, enumeration handling, data validation, electrical and safety considerations. Use when working on usb medical in medical device software.
  • 100meddev-wifi-medical
    Secure and robust WiFi connectivity for medical devices: WPA3/enterprise auth, certificate management, coexistence, resilience, and hospital network integration. Use when working on wifi medical in medical device software.
  • 85interoperability-qualification
    Qualify Open Agentic Catalog with independent local clients, resource consumers or Catalog peers using maintained interoperability harnesses. Use for HF, AGNTCY, MCP, A2A, Skill or Plugin compatibility and exact governed handoffs; normative profile interpretation uses standards-conformance.
  • 90esp32-protocol-version-interoperability
    Use when designing, reviewing, debugging or validating protocol version interoperability for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release.
  • 100reviewing-interoperability
    Reviews a change for interoperability — whether the code correctly speaks the external standards and protocols it claims to (ISO/IEC 25010:2023). Consolidates conformance checks scattered across other lenses: HTTP semantics (safe/idempotent methods, status codes, conditional…
  • 90esp32-ble-mobile-interoperability
    Use when designing, reviewing, debugging or validating ble mobile interoperability for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.