Aetna FHIR R4 Observation
JSON Schema for the FHIR R4 Observation resource as Aetna profiles it. Derived mechanically from the components.schemas of openapi/aetna-patient-access-api-openapi.yml, which is assembled from the Swagger 2.0 documents Aetna publishes at https://developerportal.aetna.com/managedcontent/yaml/. Not authored - every constraint here is Aetna's. $refs rewritten from #/components/schemas/ to #/$defs/.
Properties
| Name | Type | Description |
|---|---|---|
| valueBoolean | boolean | The information determined as a result of making the observation, if the information has a simple value. |
| partOf | array | A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. |
| dataAbsentReason | object | Provides a reason why the expected value in the element Observation.value[x] is missing. |
| note | array | Comments about the observation or the results. |
| valueTime | string | The information determined as a result of making the observation, if the information has a simple value. |
| extension | array | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied |
| code | object | Describes what was observed. Sometimes this is called the observation "name". |
| subject | object | The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject ( |
| valueRange | object | The information determined as a result of making the observation, if the information has a simple value. |
| modifierExtension | array | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of |
| focus | array | The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus obse |
| language | string | The base language in which the resource is written. |
| valueCodeableConcept | object | The information determined as a result of making the observation, if the information has a simple value. |
| valueRatio | object | The information determined as a result of making the observation, if the information has a simple value. |
| specimen | object | The specimen that was used when this observation was made. |
| derivedFrom | array | The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. |
| _effectiveDateTime | object | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either |
| valueDateTime | string | The information determined as a result of making the observation, if the information has a simple value. |
| text | object | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is re |
| id | string | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
| issued | string | The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. |
| valueInteger | integer | The information determined as a result of making the observation, if the information has a simple value. |
| basedOn | array | A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. |
| valueQuantity | object | The information determined as a result of making the observation, if the information has a simple value. |
| identifier | array | A unique identifier assigned to this observation. |
| performer | array | Who was responsible for asserting the observed value as "true". |
| effectivePeriod | object | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either |
| effectiveTiming | object | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either |
| method | object | Indicates the mechanism used to perform the observation. |
| hasMember | array | This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. |
| encounter | object | The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. |
| _issued | object | The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. |
| bodySite | object | Indicates the site on the subject's body where the observation was made (i.e. the target site). |
| referenceRange | array | Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR".In other words, to represent two distinct target populations |
| component | array | Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic |
| contained | array | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope |
| valueString | string | The information determined as a result of making the observation, if the information has a simple value. |
| effectiveDateTime | string | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either |
| interpretation | array | A categorical assessment of an observation value. For example, high, low, normal. |
| valueSampledData | object | The information determined as a result of making the observation, if the information has a simple value. |
| valuePeriod | object | The information determined as a result of making the observation, if the information has a simple value. |
| meta | object | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
| implicitRules | string | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that |
| category | array | A code that classifies the general type of observation being made. |
| device | object | The device used to generate the observation data. |
| effectiveInstant | string | The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either |
| status | string | The status of the result value. |
| resourceType | string |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/aetna/refs/heads/main/json-schema/aetna-observation.json",
"title": "Aetna FHIR R4 Observation",
"description": "JSON Schema for the FHIR R4 Observation resource as Aetna profiles it. Derived mechanically from the components.schemas of openapi/aetna-patient-access-api-openapi.yml, which is assembled from the Swagger 2.0 documents Aetna publishes at https://developerportal.aetna.com/managedcontent/yaml/. Not authored - every constraint here is Aetna's. $refs rewritten from #/components/schemas/ to #/$defs/.",
"x-provenance": {
"generated": "2026-08-30",
"method": "derived",
"source": "openapi/aetna-patient-access-api-openapi.yml"
},
"type": "object",
"required": [
"code",
"resourceType",
"status"
],
"properties": {
"valueBoolean": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"type": "boolean"
},
"partOf": {
"description": "A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"dataAbsentReason": {
"description": "Provides a reason why the expected value in the element Observation.value[x] is missing.",
"$ref": "#/$defs/CodeableConcept"
},
"note": {
"description": "Comments about the observation or the results.",
"type": "array",
"items": {
"$ref": "#/$defs/Annotation"
}
},
"valueTime": {
"pattern": "([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?",
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"type": "string"
},
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"type": "array",
"items": {
"$ref": "#/$defs/Extension"
}
},
"code": {
"description": "Describes what was observed. Sometimes this is called the observation \"name\".",
"$ref": "#/$defs/CodeableConcept"
},
"subject": {
"description": "The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.",
"$ref": "#/$defs/Reference"
},
"valueRange": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/Range"
},
"modifierExtension": {
"description": "May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"type": "array",
"items": {
"$ref": "#/$defs/Extension"
}
},
"focus": {
"description": "The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device.An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"language": {
"pattern": "[^\\s]+(\\s[^\\s]+)*",
"description": "The base language in which the resource is written.",
"type": "string"
},
"valueCodeableConcept": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/CodeableConcept"
},
"valueRatio": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/Ratio"
},
"specimen": {
"description": "The specimen that was used when this observation was made.",
"$ref": "#/$defs/Reference"
},
"derivedFrom": {
"description": "The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"_effectiveDateTime": {
"description": "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the \"physiologically relevant time\". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.",
"$ref": "#/$defs/DataAbsentReason"
},
"valueDateTime": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?",
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"type": "string"
},
"text": {
"description": "A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"$ref": "#/$defs/Narrative"
},
"id": {
"pattern": "[A-Za-z0-9\\-\\.]{1,64}",
"description": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"type": "string"
},
"issued": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))",
"description": "The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.",
"type": "string"
},
"valueInteger": {
"format": "int32",
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"type": "integer"
},
"basedOn": {
"description": "A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"valueQuantity": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/Quantity"
},
"identifier": {
"description": "A unique identifier assigned to this observation.",
"type": "array",
"items": {
"$ref": "#/$defs/Identifier"
}
},
"performer": {
"description": "Who was responsible for asserting the observed value as \"true\".",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"effectivePeriod": {
"description": "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the \"physiologically relevant time\". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.",
"$ref": "#/$defs/Period"
},
"effectiveTiming": {
"description": "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the \"physiologically relevant time\". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.",
"$ref": "#/$defs/Timing"
},
"method": {
"description": "Indicates the mechanism used to perform the observation.",
"$ref": "#/$defs/CodeableConcept"
},
"hasMember": {
"description": "This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"encounter": {
"description": "The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made.",
"$ref": "#/$defs/Reference"
},
"_issued": {
"description": "The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.",
"$ref": "#/$defs/DataAbsentReason"
},
"bodySite": {
"description": "Indicates the site on the subject's body where the observation was made (i.e. the target site).",
"$ref": "#/$defs/CodeableConcept"
},
"referenceRange": {
"description": "Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an \"OR\".In other words, to represent two distinct target populations, two `referenceRange` elements would be used.",
"type": "array",
"items": {
"$ref": "#/$defs/Observation_ReferenceRange"
}
},
"component": {
"description": "Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.",
"type": "array",
"items": {
"$ref": "#/$defs/Observation_Component"
}
},
"contained": {
"description": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"type": "array",
"items": {
"$ref": "#/$defs/Resource"
}
},
"valueString": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"type": "string"
},
"effectiveDateTime": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?",
"description": "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the \"physiologically relevant time\". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.",
"type": "string"
},
"interpretation": {
"description": "A categorical assessment of an observation value. For example, high, low, normal.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"valueSampledData": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/SampledData"
},
"valuePeriod": {
"description": "The information determined as a result of making the observation, if the information has a simple value.",
"$ref": "#/$defs/Period"
},
"meta": {
"description": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.",
"$ref": "#/$defs/Meta"
},
"implicitRules": {
"pattern": "\\S*",
"description": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.",
"type": "string"
},
"category": {
"description": "A code that classifies the general type of observation being made.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"device": {
"description": "The device used to generate the observation data.",
"$ref": "#/$defs/Reference"
},
"effectiveInstant": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))",
"description": "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the \"physiologically relevant time\". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.",
"type": "string"
},
"status": {
"description": "The status of the result value.",
"type": "string",
"enum": [
"registered",
"preliminary",
"final",
"amended",
"corrected",
"cancelled",
"entered-in-error",
"unknown"
]
},
"resourceType": {
"type": "string",
"enum": [
"Account",
"ActivityDefinition",
"AdverseEvent",
"AllergyIntolerance",
"Appointment",
"AppointmentResponse",
"AuditEvent",
"Basic",
"Binary",
"BiologicallyDerivedProduct",
"BodyStructure",
"Bundle",
"CapabilityStatement",
"CarePlan",
"CareTeam",
"CatalogEntry",
"ChargeItem",
"ChargeItemDefinition",
"Claim",
"ClaimResponse",
"ClinicalImpression",
"CodeSystem",
"Communication",
"CommunicationRequest",
"CompartmentDefinition",
"Composition",
"ConceptMap",
"Condition",
"Consent",
"Contract",
"Coverage",
"CoverageEligibilityRequest",
"CoverageEligibilityResponse",
"DetectedIssue",
"Device",
"DeviceDefinition",
"DeviceMetric",
"DeviceRequest",
"DeviceUseStatement",
"DiagnosticReport",
"DocumentManifest",
"DocumentReference",
"DomainResource",
"EffectEvidenceSynthesis",
"Encounter",
"Endpoint",
"EnrollmentRequest",
"EnrollmentResponse",
"EpisodeOfCare",
"EventDefinition",
"Evidence",
"EvidenceVariable",
"ExampleScenario",
"ExplanationOfBenefit",
"FamilyMemberHistory",
"Flag",
"Goal",
"GraphDefinition",
"Group",
"GuidanceResponse",
"HealthcareService",
"ImagingStudy",
"Immunization",
"ImmunizationEvaluation",
"ImmunizationRecommendation",
"ImplementationGuide",
"InsurancePlan",
"Invoice",
"Library",
"Linkage",
"List",
"Location",
"Measure",
"MeasureReport",
"Media",
"Medication",
"MedicationAdministration",
"MedicationDispense",
"MedicationKnowledge",
"MedicationRequest",
"MedicationStatement",
"MedicinalProduct",
"MedicinalProductAuthorization",
"MedicinalProductContraindication",
"MedicinalProductIndication",
"MedicinalProductIngredient",
"MedicinalProductInteraction",
"MedicinalProductManufactured",
"MedicinalProductPackaged",
"MedicinalProductPharmaceutical",
"MedicinalProductUndesirableEffect",
"MessageDefinition",
"MessageHeader",
"MolecularSequence",
"NamingSystem",
"NutritionOrder",
"Observation",
"ObservationDefinition",
"OperationDefinition",
"OperationOutcome",
"Organization",
"OrganizationAffiliation",
"Parameters",
"Patient",
"PaymentNotice",
"PaymentReconciliation",
"Person",
"PlanDefinition",
"Practitioner",
"PractitionerRole",
"Procedure",
"Provenance",
"Questionnaire",
"QuestionnaireResponse",
"RelatedPerson",
"RequestGroup",
"ResearchDefinition",
"ResearchElementDefinition",
"ResearchStudy",
"ResearchSubject",
"Resource",
"RiskAssessment",
"RiskEvidenceSynthesis",
"Schedule",
"SearchParameter",
"ServiceRequest",
"Slot",
"Specimen",
"SpecimenDefinition",
"StructureDefinition",
"StructureMap",
"Subscription",
"Substance",
"SubstanceNucleicAcid",
"SubstancePolymer",
"SubstanceProtein",
"SubstanceReferenceInformation",
"SubstanceSourceMaterial",
"SubstanceSpecification",
"SupplyDelivery",
"SupplyRequest",
"Task",
"TerminologyCapabilities",
"TestReport",
"TestScript",
"ValueSet",
"VerificationResult",
"VisionPrescription"
]
}
},
"$defs": {
"Address": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"country": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "Country - a nation as commonly understood or generally accepted.",
"type": "string"
},
"period": {
"description": "Time period when address was/is in use.",
"$ref": "#/$defs/Period"
},
"city": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The name of the city, town, suburb, village or other community or delivery center.",
"type": "string"
},
"use": {
"description": "The purpose of this address.",
"type": "string",
"enum": [
"home",
"work",
"temp",
"old",
"billing"
]
},
"line": {
"description": "This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.",
"type": "array",
"items": {
"pattern": "[ \\r\\n\\t\\S]+",
"type": "string"
}
},
"district": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The name of the administrative area (county).",
"type": "string"
},
"postalCode": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "A postal code designating a region defined by the postal service.",
"type": "string"
},
"text": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.",
"type": "string"
},
"state": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).",
"type": "string"
},
"type": {
"description": "Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.",
"type": "string",
"enum": [
"postal",
"physical",
"both"
]
}
}
}
]
},
"Age": {
"allOf": [
{
"$ref": "#/$defs/Quantity"
},
{
"type": "object"
}
]
},
"Annotation": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"required": [
"text"
],
"properties": {
"authorString": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The individual responsible for making the annotation.",
"type": "string"
},
"authorReference": {
"description": "The individual responsible for making the annotation.",
"$ref": "#/$defs/Reference"
},
"time": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?",
"description": "Indicates when this particular annotation was made.",
"type": "string"
},
"text": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The text of the annotation in markdown format.",
"type": "string"
}
}
}
]
},
"Attachment": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"data": {
"pattern": "(\\s*([0-9a-zA-Z\\+\\=]){4}\\s*)+",
"description": "The actual data of the attachment - a sequence of bytes, base64 encoded.",
"type": "string"
},
"size": {
"format": "int32",
"description": "The number of bytes of data that make up this attachment (before base64 encoding, if that is done).",
"type": "integer"
},
"language": {
"pattern": "[^\\s]+(\\s[^\\s]+)*",
"description": "The human language of the content. The value can be any valid value according to BCP 47.",
"type": "string"
},
"title": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "A label or set of text to display in place of the data.",
"type": "string"
},
"contentType": {
"pattern": "[^\\s]+(\\s[^\\s]+)*",
"description": "Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.",
"type": "string"
},
"url": {
"pattern": "\\S*",
"description": "A location where the data can be accessed.",
"type": "string"
},
"hash": {
"pattern": "(\\s*([0-9a-zA-Z\\+\\=]){4}\\s*)+",
"description": "The calculated hash of the data using SHA-1. Represented using base64.",
"type": "string"
},
"creation": {
"pattern": "([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?",
"description": "The date that the attachment was first created.",
"type": "string"
}
}
}
]
},
"BackboneElement": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"modifierExtension": {
"description": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"type": "array",
"items": {
"$ref": "#/$defs/Extension"
}
}
}
}
]
},
"CodeableConcept": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"coding": {
"description": "A reference to a code defined by a terminology system.",
"type": "array",
"items": {
"$ref": "#/$defs/Coding"
}
},
"text": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.",
"type": "string"
}
}
}
]
},
"Coding": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"system": {
"pattern": "\\S*",
"description": "The identification of the code system that defines the meaning of the symbol in the code.",
"type": "string"
},
"code": {
"pattern": "[^\\s]+(\\s[^\\s]+)*",
"description": "A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).",
"type": "string"
},
"userSelected": {
"description": "Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).",
"type": "boolean"
},
"display": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "A representation of the meaning of the code in the system, following the rules of the system.",
"type": "string"
},
"version": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.",
"type": "string"
}
}
}
]
},
"ContactDetail": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"name": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The name of an individual to contact.",
"type": "string"
},
"telecom": {
"description": "The contact details for the individual (if a name was provided) or the organization.",
"type": "array",
"items": {
"$ref": "#/$defs/ContactPoint"
}
}
}
}
]
},
"ContactPoint": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"period": {
"description": "Time period when the contact point was/is in use.",
"$ref": "#/$defs/Period"
},
"system": {
"description": "Telecommunications form for contact point - what communications system is required to make use of the contact.",
"type": "string",
"enum": [
"phone",
"fax",
"email",
"pager",
"url",
"sms",
"other"
]
},
"use": {
"description": "Identifies the purpose for the contact point.",
"type": "string",
"enum": [
"home",
"work",
"temp",
"old",
"mobile"
]
},
"rank": {
"format": "int32",
"description": "Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.",
"type": "integer"
},
"value": {
"pattern": "[ \\r\\n\\t\\S]+",
"description": "The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).",
"type": "string"
}
}
}
]
},
"Count": {
"allOf": [
{
"$ref": "#/$defs/Quantity"
},
{
"type": "object"
}
]
},
"DataAbsentReason": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"properties": {
"valueCode": {
"type": "string"
},
"url": {
"default": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
"type": "string"
}
}
}
]
},
"Distance": {
"allOf": [
{
"$ref": "#/$defs/Quantity"
},
{
"type": "object"
}
]
},
"Duration": {
"allOf": [
{
"$ref": "#/$defs/Quantity"
},
{
"type": "object"
}
]
},
"Element": {
"type": "object",
"properties": {
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"type": "array",
"items": {
"$ref": "#/$defs/Extension"
}
},
"id": {
"pattern": "[A-Za-z0-9\\-\\.]{1,64}",
"description": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
"type": "string"
}
}
},
"Extension": {
"allOf": [
{
"$ref": "#/$defs/Element"
},
{
"type": "object",
"required": [
"url"
],
"properties": {
"valueBase64Binary": {
"pattern": "(\\s*([0-9a-zA-Z\\+\\=]){4}\\s*)+",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "string"
},
"valueBoolean": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "boolean"
},
"valueCoding": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Coding"
},
"valueTime": {
"pattern": "([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "string"
},
"valueIdentifier": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Identifier"
},
"valueReference": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Reference"
},
"valueMoney": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Money"
},
"valueRange": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Range"
},
"valueSignature": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Signature"
},
"valueUri": {
"pattern": "\\S*",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) fo
# --- truncated at 32 KB (77 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/aetna/refs/heads/main/json-schema/aetna-observation.json
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/aetna-observation"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.