PranavNagrecha/AwesomeSalesforceSkills / skills/admin/clinical-data-requirements
clinical-data-requirements
VerifiedUse this skill when defining clinical data model requirements for Health Cloud: HL7/FHIR data mapping, interoperability requirements, FHIR R4-aligned object activation, CodeableConcept constraints, and middleware translation requirements. NOT for the field-level mapping work itself — use data/fhir-data-mapping. NOT for choosing legacy HC24__ EHR objects vs standard clinical objects — use data/health-cloud-data-model.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.6 KB |
| references/examples.md | markdown | 5.7 KB |
| references/gotchas.md | markdown | 7.9 KB |
| references/llm-anti-patterns.md | markdown | 5.9 KB |
| references/metadata-examples.md | markdown | 4.4 KB |
| references/well-architected.md | markdown | 4.7 KB |
| scripts/check_clinical_data_requirements.pyexecutable | script | 4.4 KB |
| templates/clinical-data-requirements-template.md | markdown | 2.3 KB |
templates/clinical-data-requirements-template.md
View on GitHub# Clinical Data Requirements — Work Template
Use this template when defining clinical data model requirements for Health Cloud.
## Scope
**Skill:** `clinical-data-requirements`
**Request summary:** (fill in what the user asked for)
## Prerequisites
- [ ] FHIR R4 Support Settings enabled in Setup (FHIR-Aligned Clinical Data Model)
- [ ] FHIR R4 for Experience Cloud Sites permission set assigned to community users (if portal access to clinical data needed)
- [ ] Org provisioning date confirmed (new = Spring '23+; legacy = pre-Spring '23)
## Source System Clinical Data Inventory
| Source System | Data Standard | FHIR Resources / HL7 Message Types | Notes |
|--------------|--------------|-----------------------------------|-------|
| | FHIR R4 / HL7 v2 | | |
## FHIR Resource to Salesforce Object Mapping
| FHIR Resource | Salesforce Object | Key Mapping Notes | Deviations from Spec |
|--------------|-------------------|------------------|---------------------|
| Patient | Person Account + PersonName + ContactPoint* | Demographics → child objects | Direct Account fields do NOT work |
| Condition | HealthCondition | Code required in SF; optional in FHIR | |
| Observation | CareObservation + CareObservationComponent | | |
| (add rows) | | | |
## CodeableConcept Constraint Assessment
| Resource | Field | Max Codings in Source | Truncation Policy |
|---------|-------|----------------------|-------------------|
| Condition | code | | ICD-10 priority 1, SNOMED priority 2 |
| Observation | code | | LOINC priority 1 |
## Legacy EHR Object Migration Assessment
| Legacy Object (HC24__) | Replacement Object | Data Volume | Migration Required? |
|-----------------------|-------------------|-------------|---------------------|
| HC24__EhrCondition__c | HealthCondition | | |
| HC24__EhrMedicationStatement__c / HC24__EhrMedicationPrescription__c | MedicationStatement / MedicationRequest | | |
## Middleware Translation Requirements
| Source Format | Target Format | Translation Tool | Responsible Team |
|--------------|--------------|-----------------|-----------------|
| FHIR R4 bundle | FHIR R4 (Salesforce-normalized) | | |
| HL7 v2 ADT/ORU | FHIR R4 | | |
## Notes
(Custom coding system priorities, org edition, specific FHIR resource deviations requiring middleware logic)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |