Aetna FHIR R4 Encounter
JSON Schema for the FHIR R4 Encounter 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/.
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-encounter.json",
"title": "Aetna FHIR R4 Encounter",
"description": "JSON Schema for the FHIR R4 Encounter 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"
},
"allOf": [
{
"$ref": "#/$defs/DomainResource"
},
{
"type": "object",
"required": [
"class",
"status"
],
"properties": {
"serviceType": {
"description": "Broad categorization of the service that is to be provided (e.g. cardiology).",
"$ref": "#/$defs/CodeableConcept"
},
"identifier": {
"description": "Identifier(s) by which this encounter is known.",
"type": "array",
"items": {
"$ref": "#/$defs/Identifier"
}
},
"partOf": {
"description": "Another Encounter of which this encounter is a part of (administratively or in time).",
"$ref": "#/$defs/Reference"
},
"period": {
"description": "The time that the episode was in the specified status.",
"$ref": "#/$defs/Period"
},
"classHistory": {
"description": "The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.",
"type": "array",
"items": {
"$ref": "#/$defs/Encounter_ClassHistory"
}
},
"hospitalization": {
"description": "Details about the admission to a healthcare service.",
"$ref": "#/$defs/Encounter_Hospitalization"
},
"subject": {
"description": "The patient or group present at the encounter.",
"$ref": "#/$defs/Reference"
},
"length": {
"description": "Quantity of time the encounter lasted. This excludes the time during leaves of absence.",
"$ref": "#/$defs/Duration"
},
"reasonReference": {
"description": "Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"diagnosis": {
"description": "The list of diagnosis relevant to this encounter.",
"type": "array",
"items": {
"$ref": "#/$defs/Encounter_Diagnosis"
}
},
"appointment": {
"description": "The appointment that scheduled this encounter.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"type": {
"description": "Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"priority": {
"description": "Indicates the urgency of the encounter.",
"$ref": "#/$defs/CodeableConcept"
},
"participant": {
"description": "The list of people responsible for providing the service.",
"type": "array",
"items": {
"$ref": "#/$defs/Encounter_Participant"
}
},
"statusHistory": {
"description": "The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.",
"type": "array",
"items": {
"$ref": "#/$defs/Encounter_StatusHistory"
}
},
"serviceProvider": {
"description": "The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy.",
"$ref": "#/$defs/Reference"
},
"location": {
"description": "List of locations where the patient has been during this encounter.",
"type": "array",
"items": {
"$ref": "#/$defs/Encounter_Location"
}
},
"episodeOfCare": {
"description": "Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"reasonCode": {
"description": "Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"class": {
"description": "Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.",
"$ref": "#/$defs/Coding"
},
"basedOn": {
"description": "The request this encounter satisfies (e.g. incoming referral or procedure request).",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"account": {
"description": "The set of accounts that may be used for billing for this Encounter.",
"type": "array",
"items": {
"$ref": "#/$defs/Reference"
}
},
"status": {
"description": "planned | arrived | triaged | in-progress | onleave | finished | cancelled +.",
"type": "string",
"enum": [
"planned",
"arrived",
"triaged",
"in-progress",
"onleave",
"finished",
"cancelled",
"entered-in-error",
"unknown"
]
}
}
}
],
"$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"
}
]
},
"Distance": {
"allOf": [
{
"$ref": "#/$defs/Quantity"
},
{
"type": "object"
}
]
},
"DomainResource": {
"allOf": [
{
"$ref": "#/$defs/Resource"
},
{
"type": "object",
"properties": {
"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"
}
},
"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"
}
},
"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"
}
},
"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"
}
}
}
]
},
"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"
}
}
},
"Encounter_ClassHistory": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"required": [
"class",
"period"
],
"properties": {
"period": {
"description": "The time that the episode was in the specified class.",
"$ref": "#/$defs/Period"
},
"class": {
"description": "inpatient | outpatient | ambulatory | emergency +.",
"$ref": "#/$defs/Coding"
}
}
}
]
},
"Encounter_Diagnosis": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"required": [
"condition"
],
"properties": {
"condition": {
"description": "Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.",
"$ref": "#/$defs/Reference"
},
"use": {
"description": "Role that this diagnosis has within the encounter (e.g. admission, billing, discharge \u2026).",
"$ref": "#/$defs/CodeableConcept"
},
"rank": {
"format": "int32",
"description": "Ranking of the diagnosis (for each role type).",
"type": "integer"
}
}
}
]
},
"Encounter_Hospitalization": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"properties": {
"specialArrangement": {
"description": "Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"reAdmission": {
"description": "Whether this hospitalization is a readmission and why if known.",
"$ref": "#/$defs/CodeableConcept"
},
"origin": {
"description": "The location/organization from which the patient came before admission.",
"$ref": "#/$defs/Reference"
},
"destination": {
"description": "Location/organization to which the patient is discharged.",
"$ref": "#/$defs/Reference"
},
"dietPreference": {
"description": "Diet preferences reported by the patient.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"preAdmissionIdentifier": {
"description": "Pre-admission identifier.",
"$ref": "#/$defs/Identifier"
},
"specialCourtesy": {
"description": "Special courtesies (VIP, board member).",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
},
"dischargeDisposition": {
"description": "Category or kind of location after discharge.",
"$ref": "#/$defs/CodeableConcept"
},
"admitSource": {
"description": "From where patient was admitted (physician referral, transfer).",
"$ref": "#/$defs/CodeableConcept"
}
}
}
]
},
"Encounter_Location": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"required": [
"location"
],
"properties": {
"period": {
"description": "Time period during which the patient was present at the location.",
"$ref": "#/$defs/Period"
},
"physicalType": {
"description": "This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.",
"$ref": "#/$defs/CodeableConcept"
},
"location": {
"description": "The location where the encounter takes place.",
"$ref": "#/$defs/Reference"
},
"status": {
"description": "The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.",
"type": "string",
"enum": [
"planned",
"active",
"reserved",
"completed"
]
}
}
}
]
},
"Encounter_Participant": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"properties": {
"period": {
"description": "The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.",
"$ref": "#/$defs/Period"
},
"individual": {
"description": "Persons involved in the encounter other than the patient.",
"$ref": "#/$defs/Reference"
},
"type": {
"description": "Role of participant in encounter.",
"type": "array",
"items": {
"$ref": "#/$defs/CodeableConcept"
}
}
}
}
]
},
"Encounter_StatusHistory": {
"allOf": [
{
"$ref": "#/$defs/BackboneElement"
},
{
"type": "object",
"required": [
"period",
"status"
],
"properties": {
"period": {
"description": "The time that the episode was in the specified status.",
"$ref": "#/$defs/Period"
},
"status": {
"description": "planned | arrived | triaged | in-progress | onleave | finished | cancelled +.",
"type": "string",
"enum": [
"planned",
"arrived",
"triaged",
"in-progress",
"onleave",
"finished",
"cancelled",
"entered-in-error",
"unknown"
]
}
}
}
]
},
"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) for a list).",
"type": "string"
},
"valueDistance": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Distance"
},
"valueUrl": {
"pattern": "\\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"
},
"valueContactDetail": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/ContactDetail"
},
"valueMeta": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Meta"
},
"valueUuid": {
"pattern": "urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "string"
},
"valueCodeableConcept": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/CodeableConcept"
},
"valueRatio": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Ratio"
},
"valueMarkdown": {
"pattern": "[ \\r\\n\\t\\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"
},
"valueAttachment": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/Attachment"
},
"valueUsageContext": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/UsageContext"
},
"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": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "string"
},
"valueInteger": {
"format": "int32",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "integer"
},
"valueUnsignedInt": {
"format": "int32",
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"type": "integer"
},
"valueHumanName": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).",
"$ref": "#/$defs/HumanName"
},
"valueQuantity": {
"description": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for
# --- truncated at 32 KB (65 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/aetna/refs/heads/main/json-schema/aetna-encounter.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-encounter"
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.