FHIR Developer Skill
Quick Reference
HTTP Status Codes
Code
When to Use
200 OKSuccessful read, update, or search
201 CreatedSuccessful create (include Location header)
204 No ContentSuccessful delete
400 Bad RequestMalformed JSON, wrong resourceType
401 UnauthorizedMissing, expired, revoked, or malformed token (RFC 6750)
403 ForbiddenValid token but insufficient scopes
404 Not FoundResource doesn't exist
412 Precondition FailedIf-Match ETag mismatch (NOT 400!)
422 Unprocessable EntityMissing required fields, invalid enum values, business rule violations
Required Fields by Resource (FHIR R4)
Resource
Required Fields
Everything Else
Patient
(none) All optional
Observation
status, codeOptional
Encounter
status, classOptional (including subject, period)
Condition
subjectOptional (including code, clinicalStatus)
MedicationRequest
status, intent, medication[x], subjectOptional
Medication
(none) All optional
Bundle
typeOptional
Required vs Optional Fields (CRITICAL)
Only validate fields with cardinality starting with "1" as required.
Cardinality
Required?
0..1, 0..*NO
1..1, 1..*YES
Common mistake : Making subject or period required on Encounter. They are 0..1 (optional).
Value Sets (Enum Values)
Invalid enum values must return 422 Unprocessable Entity.
Patient.gender
male | female | other | unknown
Observation.status
registered | preliminary | final | amended | corrected | cancelled | entered-in-error | unknown
Encounter.status
planned | arrived | triaged | in-progress | onleave | finished | cancelled | entered-in-error | unknown
Encounter.class (Common Codes)
Code
Display
Use
AMBambulatory
Outpatient visits
IMPinpatient encounter
Hospital admissions
EMERemergency
Emergency department
VRvirtual
Telehealth
Condition.clinicalStatus
active | recurrence | relapse | inactive | remission | resolved
Condition.verificationStatus
unconfirmed | provisional | differential | confirmed | refuted | entered-in-error
MedicationRequest.status
active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
MedicationRequest.intent
proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Bundle.type
document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection
Validation Pattern
Python/FastAPI:
from fastapi import FastAPI
from fastapi. responses import JSONResponse
app = FastAPI( )
def operation_outcome ( severity: str , code: str , diagnostics: str ) :
return {
"resourceType" : "OperationOutcome" ,
"issue" : [ { "severity" : severity, "code" : code, "diagnostics" : diagnostics} ]
}
VALID_OBS_STATUS = { "registered" , "preliminary" , "final" , "amended" ,
"corrected" , "cancelled" , "entered-in-error" , "unknown" }
@app. post ( "/Observation" , status_code= 201 )
async def create_observation ( data: dict ) :
if not data. get( "status" ) :
return JSONResponse( status_code= 422 , content= operation_outcome(
"error" , "required" , "Observation.status is required"
) , media_type= "application/fhir+json" )
if data[ "status" ] not in VALID_OBS_STATUS:
return JSONResponse( status_code= 422 , content= operation_outcome(
"error" , "value" , f"Invalid status ' { data[ 'status' ] } '" ) , media_type= "application/fhir+json" )
TypeScript/Express:
const VALID_OBS_STATUS = new Set ( [ 'registered' , 'preliminary' , 'final' , 'amended' ,
'corrected' , 'cancelled' , 'entered-in-error' , 'unknown' ] ) ;
app. post ( '/Observation' , ( req, res) => {
if ( ! req. body. status) {
return res. status ( 422 ) . contentType ( 'application/fhir+json' )
. json ( operationOutcome ( 'error' , 'required' , 'Observation.status is required' ) ) ;
}
if ( ! VALID_OBS_STATUS . has ( req. body. status) ) {
return res. status ( 422 ) . contentType ( 'application/fhir+json' )
. json ( operationOutcome ( 'error' , 'value' , ` Invalid status ' ${ req. body. status} ' ` ) ) ;
}
} ) ;
Pydantic v2 Models (use Literal, not const=True):
from typing import Literal
from pydantic import BaseModel
class Patient ( BaseModel) :
resourceType: Literal[ "Patient" ] = "Patient"
id : str | None = None
gender: Literal[ "male" , "female" , "other" , "unknown" ] | None = None
Coding Systems (URLs)
System
URL
LOINC
http://loinc.org
SNOMED CT
http://snomed.info/sct
RxNorm
http://www.nlm.nih.gov/research/umls/rxnorm
ICD-10
http://hl7.org/fhir/sid/icd-10
v3-ActCode
http://terminology.hl7.org/CodeSystem/v3-ActCode
Observation Category
http://terminology.hl7.org/CodeSystem/observation-category
Condition Clinical
http://terminology.hl7.org/CodeSystem/condition-clinical
Condition Ver Status
http://terminology.hl7.org/CodeSystem/condition-ver-status
Common LOINC Codes (Vital Signs)
Code
Description
8867-4Heart rate
8480-6Systolic blood pressure
8462-4Diastolic blood pressure
8310-5Body temperature
2708-6Oxygen saturation (SpO2)
Data Type Patterns
Coding (direct) vs CodeableConcept (wrapped)
Coding - Used by Encounter.class:
{ "system" : "http://terminology.hl7.org/CodeSystem/v3-ActCode" , "code" : "AMB" }
CodeableConcept - Used by Observation.code, Condition.code:
{ "coding" : [ { "system" : "http://loinc.org" , "code" : "8480-6" } ] , "text" : "Systolic BP" }
Reference
{ "reference" : "Patient/123" , "display" : "John Smith" }
Identifier
{ "system" : "http://hospital.example.org/mrn" , "value" : "12345" }
Common Mistakes
Mistake
Correct Approach
Making subject or period required on Encounter
Both are 0..1 (optional). Only status and class are required
Using CodeableConcept for Encounter.class
class uses Coding directly: {"system": "...", "code": "AMB"}
Returning 400 for ETag mismatch
Use 412 Precondition Failed for If-Match failures
Returning 400 for invalid enum values
Use 422 Unprocessable Entity for validation errors
Forgetting Content-Type header
Always set Content-Type: application/fhir+json
Missing Location header on create
Return Location: /Patient/{id} with 201 Created
Resource Structures
For complete JSON examples of all resources, see ✓
Make data-driven prioritization decisions faster
Stakeholder Communication Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓ Save 3-5 hours/week on communication overhead
Implementation Guide Prerequisites
› Claude Desktop or compatible AI client › Access to product documentation and roadmap tools (Jira, Notion, etc.) › Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.) › Stakeholder contact information and communication channels Time Estimate
30-60 minutes to see productivity improvements
Steps
1 Install product management skill 2 Start with user story generation for known feature 3 Progress to competitive analysis: research 2-3 competitors 4 Use for roadmap prioritization: apply RICE/ICE scoring 5 Draft stakeholder communications and refine based on feedback 6 Build template library for recurring PM tasks 7 Share effective prompts with product team Common Pitfalls
⚠ Not validating competitive research—verify facts before sharing ⚠ Accepting user stories without involving engineering team ⚠ Over-relying on frameworks without qualitative judgment ⚠ Not customizing outputs to company culture and communication style ⚠ Skipping stakeholder validation of generated requirements Best Practices ✓ Do
+ Validate research and competitive analysis with real data + Collaborate with engineering when generating technical requirements + Customize frameworks and templates to your company context + Use skill for first drafts, refine with stakeholder input + Document successful prompt patterns for PM tasks + Combine AI efficiency with human judgment and intuition ✗ Don't
− Don't publish competitive analysis without fact-checking − Don't finalize user stories without engineering review − Don't make prioritization decisions solely on AI scoring − Don't skip customer validation of generated requirements − Don't ignore company-specific context and culture 💡 Pro Tips
★ Provide context: company goals, constraints, customer feedback ★ Ask for alternatives: 'Show 3 ways to prioritize this roadmap' ★ Request stakeholder-specific formatting: 'Executive summary vs. engineering spec' ★ Use skill for 70% generation + 30% customization to company needs When to Use This ✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path 1 Basic: user stories, feature specs, status updates 2 Intermediate: competitive analysis, prioritization frameworks, PRDs 3 Advanced: product strategy, go-to-market planning, OKR setting 4 Expert: product vision, market positioning, business model innovation Reviews 4.5 ★ ★ ★ ★ ★ 69 reviews
N
Naina Verma ★ ★ ★ ★ ★ Dec 28, 2024
I recommend fhir-developer-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
M
Maya Lopez ★ ★ ★ ★ ★ Dec 28, 2024
We added fhir-developer-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
K
Kofi Taylor ★ ★ ★ ★ ★ Dec 12, 2024
fhir-developer-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
O
Omar Sharma ★ ★ ★ ★ ★ Dec 12, 2024
Useful defaults in fhir-developer-skill — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
D
Dhruvi Jain ★ ★ ★ ★ ★ Dec 8, 2024
fhir-developer-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
M
Maya White ★ ★ ★ ★ ★ Dec 8, 2024
fhir-developer-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
O
Oshnikdeep ★ ★ ★ ★ ★ Nov 27, 2024
Registry listing for fhir-developer-skill matched our evaluation — installs cleanly and behaves as described in the markdown.
O
Omar Mehta ★ ★ ★ ★ ★ Nov 19, 2024
Keeps context tight: fhir-developer-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
K
Kofi Lopez ★ ★ ★ ★ ★ Nov 19, 2024
fhir-developer-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.
L
Layla Patel ★ ★ ★ ★ ★ Nov 3, 2024
Registry listing for fhir-developer-skill matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 69
prev 1 / 7 next
Discussion Comments — not star reviews No comments yet — start the thread.
