wellcare-health-plans · API Governance Rules
wellcare-health-plans API Rules
Spectral linting rules defining API design standards and conventions for wellcare-health-plans.
9 Rules
error 3
warn 5
Rule Categories
fhir
operation
response
Rules
error
fhir-r4-path-prefix
All FHIR endpoints must use /fhir/r4/ path prefix.
$.paths[*]~
warn
fhir-resource-title-case
FHIR resource segments must use UpperCamelCase (e.g., Patient, ExplanationOfBenefit).
$.paths[*]~
error
fhir-operation-security
All FHIR operations must define security scopes.
$.paths[*][get,post,put,delete]
warn
fhir-accept-header
FHIR responses should return application/fhir+json content type.
$.paths[*][get].responses[200].content
warn
operation-id-camel-case
Operation IDs must use lowerCamelCase.
$.paths[*][*].operationId
error
operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
hint
fhir-search-patient-param
FHIR search operations on clinical resources must support the patient parameter.
$.paths[/fhir/r4/Coverage,/fhir/r4/ExplanationOfBenefit,/fhir/r4/Condition,/fhir/r4/Observation,/fhir/r4/MedicationRequest,/fhir/r4/Immunization,/fhir/r4/Encounter].get.parameters[*]
warn
response-401-required
Secured operations must define a 401 response.
$.paths[*][get,post,put,patch,delete].responses