Generated Narrative: CodeSystem fhir-types Properties This code system defines the following properties for its concepts Name Code URI Type abstract-type abstract-type http://hl7.org/fhir/type-properties#abstract-type boolean kind kind http://hl7.org/fhir/type-properties#kind code interface interface http://hl7.org/fhir/type-properties#interface boolean Concepts This case-sensitive code system http://hl7.org/fhir/fhir-types defines the following codes in a Is-A hierarchy: Lvl Code Definition abstract-type kind interface 1 Base Base Type: Base definition for all types defined in FHIR type system. true 2 Element Element Type: Base definition for all elements in a resource. true datatype 3 BackboneElement BackboneElement Type: Base definition for all elements that are defined inside a resource - but not those in a data type. true datatype 3 DataType DataType Type: The base class for all re-useable types defined as part of the FHIR Specification. true datatype 4 Address Address Type: An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. The ISO21090-codedString may be used to provide a coded representation of the contents of strings in an Address. datatype 4 Annotation Annotation Type: A text note which also contains information about who made the statement and when. datatype 4 Attachment Attachment Type: For referring to data content defined in other formats. datatype 4 Availability Availability Type: Availability data for an {item}, declaring what days/times are available, and any exceptions. The exceptions could be textual only, e.g. Public holidays, or could be time period specific and indicate a specific years dates. datatype 4 BackboneType BackboneType Type: Base definition for the few data types that are allowed to carry modifier extensions. true datatype 5 Dosage Dosage Type: Indicates how the medication is/was taken or should be taken by the patient. datatype 5 DosageCondition DosageCondition Type: DosageCondition expresses a time or time period as relative to the time of an event defined in data types other than dateTime. datatype 5 DosageDetails DosageDetails Type: Indicates how the medication is/was taken or should be taken by the patient. datatype 5 DosageSafety DosageSafety Type: Safety Details about the usage of the medication. datatype 5 ElementDefinition ElementDefinition Type: Captures constraints on each element within the resource, profile, or extension. datatype 5 MarketingStatus MarketingStatus Type: The marketing status describes the date when an item is actually put on the market or the date as of which it is no longer available. datatype 5 ProductShelfLife ProductShelfLife Type: The shelf-life and storage information for a medicinal product item or container can be described using this class. datatype 5 RelativeTime RelativeTime Type: RelativeTime expresses a time or time period as relative to the time of an event defined in data types other than dateTime. datatype 5 Timing Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out. datatype 4 CodeableConcept CodeableConcept Type: A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. datatype 4 CodeableReference CodeableReference Type: A reference to a resource (by instance), or instead, a reference to a concept defined in a terminology or ontology (by class). datatype 4 Coding Coding Type: A reference to a code defined by a terminology system. datatype 4 ContactDetail ContactDetail Type: Specifies contact information for a person or organization. datatype 4 ContactPoint ContactPoint Type: Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. datatype 4 DataRequirement DataRequirement Type: Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data. datatype 4 Expression Expression Type: A expression that is evaluated in a specified context and returns a value. The context of use of the expression must specify the context in which the expression is evaluated, and how the result of the expression is used. datatype 4 ExtendedContactDetail ExtendedContactDetail Type: Specifies contact information for a specific purpose over a period of time, might be handled/monitored by a specific named person or organization. datatype 4 Extension Extension Type: Optional Extension Element - found in all resources. datatype 4 HumanName HumanName Type: A name, normally of a human, that can be used for other living entities (e.g. animals but not organizations) that have been assigned names by a human and may need the use of name parts or the need for usage information. datatype 4 Identifier Identifier Type: An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. datatype 4 Meta Meta Type: The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. datatype 4 MonetaryComponent MonetaryComponent Type: Financial line items use this datatype to commonly categorize the value, and other factors that may effect how the value should be interpreted. datatype 4 Money Money Type: An amount of economic utility in some recognized currency. datatype 4 Narrative Narrative Type: A human-readable summary of the resource conveying the essential clinical and business information for the resource. datatype 4 ParameterDefinition ParameterDefinition Type: The parameters to the module. This collection specifies both the input and output parameters. Input parameters are provided by the caller as part of the $evaluate operation. Output parameters are included in the GuidanceResponse. datatype 4 Period Period Type: A time period defined by a start and end date and optionally time. datatype 4 PrimitiveType PrimitiveType Type: The base type for all re-useable types defined that have a simple property. true datatype 5 base64Binary base64Binary Type: A stream of bytes primitive 5 boolean boolean Type: Value of "true" or "false" primitive 5 date date Type: A date or partial date (e.g. just year or year + month). There is no UTC offset. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates. primitive 5 dateTime dateTime Type: A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a UTC offset SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates. primitive 5 decimal decimal Type: A rational number with implicit precision primitive 5 instant instant Type: An instant in time - known at least to the second primitive 5 integer integer Type: A whole number primitive 6 positiveInt positiveInt type: An integer with a value that is positive (e.g. >0) primitive 6 unsignedInt unsignedInt type: An integer with a value that is not negative (e.g. >= 0) primitive 5 integer64 integer64 Type: A very large whole number primitive 5 string string Type: A sequence of Unicode characters primitive 6 code code type: A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents primitive 6 id id type: Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive. primitive 6 markdown markdown type: A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine primitive 5 time time Type: A time during the day, with no date specified primitive 5 uri uri Type: String of characters used to identify a name or a resource primitive 6 canonical canonical type: A URI that is a reference to a canonical URL on a FHIR resource primitive 6 oid oid type: An OID represented as a URI primitive 6 url url type: A URI that is a literal reference primitive 6 uuid uuid type: A UUID, represented as a URI primitive 4 Quantity Quantity Type: A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies. datatype 5 Age Age Type: A duration of time during which an organism (or a process) has existed. datatype 5 Count Count Type: A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies. datatype 5 Distance Distance Type: A length - a value with a unit that is a physical distance. datatype 5 Duration Duration Type: A length of time. datatype 4 Range Range Type: A set of ordered Quantities defined by a low and high limit. datatype 4 Ratio Ratio Type: A relationship of two Quantity values - expressed as a numerator and a denominator. datatype 4 RatioRange RatioRange Type: A range of ratios expressed as a low and high numerator and a denominator. datatype 4 Reference Reference Type: A reference from one resource to another. datatype 4 RelatedArtifact RelatedArtifact Type: Related artifacts such as dependencies, components, additional documentation, justification, or bibliographic references. datatype 4 SampledData SampledData Type: A series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data. datatype 4 Signature Signature Type: A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities. datatype 4 TriggerDefinition TriggerDefinition Type: A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element. datatype 4 UsageContext UsageContext Type: Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care). datatype 4 VirtualServiceDetail VirtualServiceDetail Type: The set of values required to describe a virtual service's connection details, including some limitations of the service. datatype 3 xhtml xhtml Type definition primitive 2 Resource This is the base resource type for everything. true resource 3 Binary A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. resource 3 Bundle A container for a collection of resources. resource 3 DomainResource A resource that includes narrative, extensions, and contained resources. true resource 4 Account A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc. resource 4 ActivityDefinition This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. resource 4 ActorDefinition The ActorDefinition resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays. resource 4 AdministrableProductDefinition A medicinal product in the final form which is suitable for administering to a patient (after any mixing of multiple components, dissolution etc. has been performed). resource 4 AdverseEvent An event (i.e. any change to current patient status) that may be related to unintended effects on a patient or research participant. The unintended effects may require additional monitoring, treatment, hospitalization, or may result in death. The AdverseEvent resource also extends to potential or avoided events that could have had such effects. There are two major domains where the AdverseEvent resource is expected to be used. One is in clinical care reported adverse events and the other is in reporting adverse events in clinical research trial management. Adverse events can be reported by healthcare providers, patients, caregivers or by medical products manufacturers. Given the differences between these two concepts, we recommend consulting the domain specific implementation guides when implementing the AdverseEvent Resource. The implementation guides include specific extensions, value sets and constraints. resource 4 AllergyIntolerance Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. resource 4 Appointment A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). resource 4 AppointmentResponse A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. resource 4 ArtifactAssessment This Resource provides one or more comments, classifiers or ratings about a Resource and supports attribution and rights management metadata for the added content. resource 4 AuditEvent A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. resource 4 Basic Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification. resource 4 BiologicallyDerivedProduct A biological material originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity. resource 4 BodyStructure Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. resource 4 CanonicalResource Common Interface declaration for conformance and knowledge artifact resources. true resource true 4 CapabilityStatement A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. resource 4 CarePlan Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. resource 4 CareTeam The Care Team includes all the people, organizations, and care teams who participate or plan to participate in the coordination and delivery of care. resource 4 Claim A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. resource 4 ClaimResponse This resource provides the adjudication details from the processing of a Claim resource. resource 4 ClinicalUseDefinition A single issue - either an indication, contraindication, interaction, undesirable effect or warning for a medicinal product, medication, device or procedure. resource 4 CodeSystem The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. resource 4 Communication A clinical or business level record of information being transmitted or shared; e.g. an alert that was sent to a responsible provider, a public health agency communication to a provider/reporter in response to a case report for a reportable condition. resource 4 CommunicationRequest A request to convey information from a sender to a recipient. resource 4 CompartmentDefinition A compartment definition that defines how resources are accessed on a server. resource 4 Composition A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and has traceability to the author who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). resource 4 ConceptMap A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. resource 4 Condition A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. resource 4 Consent A record of a healthcare consumer’s choices or choices made on their behalf by a third party, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. resource 4 Contract Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. resource 4 Coverage Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. resource 4 CoverageEligibilityRequest The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. resource 4 CoverageEligibilityResponse This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. resource 4 DetectedIssue Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc. resource 4 Device This resource describes the properties (regulated, has real time clock, etc.), administrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serial number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element. resource 4 DeviceAlert Describes a physiological or technical alert condition report originated by a device. The DeviceAlert resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable. resource 4 DeviceAssociation A record of association of a device. resource 4 DeviceDefinition This is a specialized resource that defines the characteristics and capabilities of a device. resource 4 DeviceMetric Describes a measurement, calculation or setting capability of a device. The DeviceMetric resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable. resource 4 DeviceRequest Represents a request a device to be provided to a specific patient. The device may be an implantable device to be subsequently implanted, or an external assistive device, such as a walker, to be delivered and subsequently be used. resource 4 DiagnosticReport The findings and interpretation of diagnostic tests performed on patients, groups of patients, products, substances, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. The report also includes non-clinical context such as batch analysis and stability reporting of products and substances. resource 4 DocumentReference A reference to a document of any kind for any purpose. While the term “document” implies a more narrow focus, for this resource this “document” encompasses any serialized object with a mime-type, it includes formal patient-centric documents (CDA), clinical notes, scanned paper, non-patient specific documents like policy text, as well as a photo, video, or audio recording acquired or used in healthcare. The DocumentReference resource provides metadata about the document so that the document can be discovered and managed. The actual content may be inline base64 encoded data or provided by direct reference. resource 4 Encounter An interaction between healthcare provider(s), and/or patient(s) for the purpose of providing healthcare service(s) or assessing the health status of patient(s). resource 4 Endpoint The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b, a REST endpoint for another FHIR server, or a s/Mime email address. This may include any security context information. resource 4 EnrollmentRequest This resource provides the insurance enrollment details to the insurer regarding a specified coverage. resource 4 EnrollmentResponse This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource. resource 4 EpisodeOfCare An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time. resource 4 EventDefinition The EventDefinition resource provides a reusable description of when a particular event can occur. resource 4 Evidence The Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence. resource 4 EvidenceVariable The EvidenceVariable resource describes an element that knowledge (Evidence) is about. resource 4 ExampleScenario A walkthrough of a workflow showing the interaction between systems and the instances shared, possibly including the evolution of instances over time. resource 4 ExplanationOfBenefit This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. resource 4 FamilyMemberHistory Significant health conditions for a person related to the patient relevant in the context of care for the patient. resource 4 Flag Prospective warnings of potential issues when providing care to the patient. resource 4 Goal Describes the intended objective(s) for a patient, group, or organizational care. Examples include a patient's weight loss, restoration of an activity of daily living for a patient, obtaining herd immunity via immunization for a group, meeting a process improvement objective for an organization, etc. resource 4 Group Represents a defined collection of entities that may be discussed or acted upon collectively but which are not typically expected to act collectively. These collections are also not typically formally or legally recognized. NOTE: Group may be used to define families or households, which in some circumstances may act collectively or have a degree of legal or formal recognition. This should be considered an exception. When Group is used for types of entities other than Patient or RelatedPerson, the expectation remains that the Group will not act collectively or have formal recognition - use Organization if these behaviors are needed. For example, it is possible for a 'family' Group to be a performer of an Observation or owner of a Task. However, this is not permitted for a Group made up of Practitioners, PractitionerRoles or Organizations. Organization or CareTeam would need to be used instead. A Group of Practitioners could, however, be a subject of an Observation. resource 4 GuidanceResponse A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken. resource 4 HealthcareService The details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices. resource 4 ImagingSelection A selection of DICOM SOP instances within a single Study and Series. This might include additional specifics such as a set of frames or an image region, allowing linkage to an Observation Resource. resource 4 ImagingStudy Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of images or other data objects (called Service-Object Pair Instances or SOP Instances) acquired or produced in a common context. resource 4 Immunization Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. resource 4 ImplementationGuide A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. resource 4 Ingredient An ingredient of a manufactured item or pharmaceutical product. resource 4 InsurancePlan Details of a Health Insurance plan provided by an organization under an InsuranceProduct. resource 4 InsuranceProduct Details of a Health Insurance product provided by an organization. resource 4 Invoice Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. resource 4 Library The Library resource is a general-purpose container for knowledge artifact definitions. It can be used to describe and expose existing knowledge artifacts such as logic libraries and information model descriptions, as well as to describe a collection of knowledge artifacts. resource 4 List A List is a curated collection of resources, for things such as problem lists, allergy lists, facility list, organization list, etc. resource 4 Location Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated. resource 4 ManufacturedItemDefinition The definition and characteristics of a medicinal manufactured item, such as a tablet or capsule, as contained in a packaged medicinal product. resource 4 Measure The Measure resource provides the definition of a quality measure. resource 4 MeasureReport The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. resource 4 Medication This resource is primarily used for the identification and definition of a medication, including ingredients, for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. resource 4 MedicationAdministration Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. This event can also be used to record waste using a status of not-done and the appropriate statusReason. resource 4 MedicationDispense Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order. resource 4 MedicationRequest An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. resource 4 MedicationStatement A record of a medication consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, patient representative (e.g., spouse, significant other, family member, caregiver), or a clinician. A common scenario where this information is captured is during the history taking process during a patient encounter or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. The primary difference between a MedicationStatement and a MedicationAdministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A MedicationStatement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the MedicationStatement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party. MedicationAdministration is more formal and is not missing detailed information. resource 4 MedicinalProductDefinition Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use, drug catalogs, to support prescribing, adverse events management etc.). resource 4 MessageDefinition Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. resource 4 MessageHeader The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. resource 4 MetadataResource Common Interface declaration for conformance and knowledge artifact resources. true resource true 4 NamingSystem A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types. resource 4 NutritionIntake A record of intake by a patient. A NutritionIntake may indicate that the patient may be consuming the food (i.e., solid and/or liquid), breastmilk, infant formula, supplements, enteral formula now or has consumed it in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food (i.e., solid and/or liquid), breastmilk, infant formula, supplements, enteral formula consumed. The consumption information may come from sources such as the patient's memory, from a nutrition label, or from a clinician documenting observed intake. resource 4 NutritionOrder A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to an individual or group. resource 4 NutritionProduct A food or supplement that is consumed by patients. resource 4 Observation Measurements and simple assertions made about a patient, device or other subject. resource 4 ObservationDefinition Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. resource 4 OperationDefinition A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). resource 4 OperationOutcome A collection of error, warning, or information messages that result from a system action. resource 4 Organization A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. resource 4 OrganizationAffiliation Defines an affiliation/assotiation/relationship between 2 distinct organizations, that is not a part-of relationship/sub-division relationship. resource 4 PackagedProductDefinition A medically related item or items, in a container or package. resource 4 Patient Demographics and other administrative information about an individual or animal that is the subject of potential, past, current, or future health-related care, services, or processes. resource 4 PaymentNotice This resource provides the status of the payment for goods and services rendered, and the request and response resource references. resource 4 PaymentReconciliation This resource provides the details including amount of a payment and allocates the payment items being paid. resource 4 Permission Permission resource holds access rules for a given data and access request context. resource 4 Person Demographics and administrative information about a person independent of a specific health-related context. resource 4 PlanDefinition This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, drug quality specifications, and drug manufacturing process. resource 4 Practitioner A person who is directly or indirectly involved in the provisioning of healthcare or related services. resource 4 PractitionerRole A specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time. resource 4 Procedure An action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing. resource 4 Provenance Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which MAY impact security, privacy, and trust policies. resource 4 Questionnaire A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. resource 4 QuestionnaireResponse A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. resource 4 RegulatedAuthorization Regulatory approval, clearance or licensing related to a regulated product, treatment, facility or activity that is cited in a guidance, regulation, rule or legislative act. An example is Market Authorization relating to a Medicinal Product. resource 4 RelatedPerson Information about a person that is involved in a patient's health or the care for a patient, but who is not the primary target of healthcare. resource 4 RequestOrchestration A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". resource 4 Requirements The Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays. resource 4 ResearchStudy A scientific study intended to increase health-related knowledge. For example, clinical trials are research studies that involve people. These studies may be related to new ways to screen, prevent, diagnose, and treat disease. They may also study certain outcomes and certain groups of people by looking at data collected in the past or future. resource 4 ResearchSubject A ResearchSubject is a participant or object which is the recipient of investigative activities in a research study. resource 4 RiskAssessment An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. resource 4 Schedule A container for slots of time that may be available for booking appointments. resource 4 SearchParameter A search parameter that defines a named search item that can be used to search/filter on a resource. resource 4 ServiceRequest A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. resource 4 Slot A slot of time on a schedule that may be available for booking appointments. resource 4 Specimen A sample to be used for analysis. resource 4 SpecimenDefinition A kind of specimen with associated set of requirements. resource 4 StructureDefinition A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. resource 4 StructureMap A Map of relationships between 2 structures that can be used to transform data. resource 4 Subscription The subscription resource describes a particular client's request to be notified about a SubscriptionTopic. resource 4 SubscriptionStatus The SubscriptionStatus resource describes the state of a Subscription during notifications. It is not persisted. resource 4 SubscriptionTopic Describes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic. resource 4 Substance A homogeneous material with a definite composition. resource 4 SubstanceDefinition The detailed description of a substance, typically at a level beyond what is used for prescribing. resource 4 Task A task to be performed as a part of a workflow and the related information like inputs, outputs and execution progress. resource 4 TerminologyCapabilities A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. resource 4 ValueSet A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements. resource 4 VisionPrescription An authorization for the provision of glasses and/or contact lenses to a patient. resource 3 Parameters This resource is used to pass information into and back from an operation (whether invoked directly from REST or within a messaging environment). It is not persisted or allowed to be referenced by other resources except as described in the definition of the Parameters resource. resource
This Code System is normative - it is generated based on the information defined in this specification. The definition will remain fixed across versions, but the actual contents will change from version to version
HL7 International / Clinical Decision Support
One of the types defined as part of this version of FHIR.
Base Type: Base definition for all types defined in FHIR type system.
Element Type: Base definition for all elements in a resource.
BackboneElement Type: Base definition for all elements that are defined inside a resource - but not those in a data type.
DataType Type: The base class for all re-useable types defined as part of the FHIR Specification.
Address Type: An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. The ISO21090-codedString may be used to provide a coded representation of the contents of strings in an Address.
Annotation Type: A text note which also contains information about who made the statement and when.
Attachment Type: For referring to data content defined in other formats.
Availability Type: Availability data for an {item}, declaring what days/times are available, and any exceptions. The exceptions could be textual only, e.g. Public holidays, or could be time period specific and indicate a specific years dates.
BackboneType Type: Base definition for the few data types that are allowed to carry modifier extensions.
Dosage Type: Indicates how the medication is/was taken or should be taken by the patient.
DosageCondition Type: DosageCondition expresses a time or time period as relative to the time of an event defined in data types other than dateTime.
DosageDetails Type: Indicates how the medication is/was taken or should be taken by the patient.
DosageSafety Type: Safety Details about the usage of the medication.
ElementDefinition Type: Captures constraints on each element within the resource, profile, or extension.
MarketingStatus Type: The marketing status describes the date when an item is actually put on the market or the date as of which it is no longer available.
ProductShelfLife Type: The shelf-life and storage information for a medicinal product item or container can be described using this class.
RelativeTime Type: RelativeTime expresses a time or time period as relative to the time of an event defined in data types other than dateTime.
Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
CodeableConcept Type: A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
CodeableReference Type: A reference to a resource (by instance), or instead, a reference to a concept defined in a terminology or ontology (by class).
Coding Type: A reference to a code defined by a terminology system.
ContactDetail Type: Specifies contact information for a person or organization.
ContactPoint Type: Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
DataRequirement Type: Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data.
Expression Type: A expression that is evaluated in a specified context and returns a value. The context of use of the expression must specify the context in which the expression is evaluated, and how the result of the expression is used.
ExtendedContactDetail Type: Specifies contact information for a specific purpose over a period of time, might be handled/monitored by a specific named person or organization.
Extension Type: Optional Extension Element - found in all resources.
HumanName Type: A name, normally of a human, that can be used for other living entities (e.g. animals but not organizations) that have been assigned names by a human and may need the use of name parts or the need for usage information.
Identifier Type: An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
Meta Type: The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
MonetaryComponent Type: Financial line items use this datatype to commonly categorize the value, and other factors that may effect how the value should be interpreted.
Money Type: An amount of economic utility in some recognized currency.
Narrative Type: A human-readable summary of the resource conveying the essential clinical and business information for the resource.
ParameterDefinition Type: The parameters to the module. This collection specifies both the input and output parameters. Input parameters are provided by the caller as part of the $evaluate operation. Output parameters are included in the GuidanceResponse.
Period Type: A time period defined by a start and end date and optionally time.
PrimitiveType Type: The base type for all re-useable types defined that have a simple property.
boolean Type: Value of "true" or "false"
date Type: A date or partial date (e.g. just year or year + month). There is no UTC offset. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates.
dateTime Type: A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a UTC offset SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
decimal Type: A rational number with implicit precision
instant Type: An instant in time - known at least to the second
positiveInt type: An integer with a value that is positive (e.g. >0)
unsignedInt type: An integer with a value that is not negative (e.g. >= 0)
integer64 Type: A very large whole number
string Type: A sequence of Unicode characters
code type: A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
id type: Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
markdown type: A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
time Type: A time during the day, with no date specified
uri Type: String of characters used to identify a name or a resource
canonical type: A URI that is a reference to a canonical URL on a FHIR resource
url type: A URI that is a literal reference
Quantity Type: A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
Age Type: A duration of time during which an organism (or a process) has existed.
Count Type: A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
Distance Type: A length - a value with a unit that is a physical distance.
Range Type: A set of ordered Quantities defined by a low and high limit.
Ratio Type: A relationship of two Quantity values - expressed as a numerator and a denominator.
RatioRange Type: A range of ratios expressed as a low and high numerator and a denominator.
Reference Type: A reference from one resource to another.
RelatedArtifact Type: Related artifacts such as dependencies, components, additional documentation, justification, or bibliographic references.
SampledData Type: A series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data.
Signature Type: A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities.
TriggerDefinition Type: A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element.
UsageContext Type: Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care).
VirtualServiceDetail Type: The set of values required to describe a virtual service's connection details, including some limitations of the service.
This is the base resource type for everything.
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.
A container for a collection of resources.
A resource that includes narrative, extensions, and contained resources.
A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.
This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.
The ActorDefinition resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.
A medicinal product in the final form which is suitable for administering to a patient (after any mixing of multiple components, dissolution etc. has been performed).
An event (i.e. any change to current patient status) that may be related to unintended effects on a patient or research participant. The unintended effects may require additional monitoring, treatment, hospitalization, or may result in death. The AdverseEvent resource also extends to potential or avoided events that could have had such effects. There are two major domains where the AdverseEvent resource is expected to be used. One is in clinical care reported adverse events and the other is in reporting adverse events in clinical research trial management. Adverse events can be reported by healthcare providers, patients, caregivers or by medical products manufacturers. Given the differences between these two concepts, we recommend consulting the domain specific implementation guides when implementing the AdverseEvent Resource. The implementation guides include specific extensions, value sets and constraints.
Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.
A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).
A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection.
This Resource provides one or more comments, classifiers or ratings about a Resource and supports attribution and rights management metadata for the added content.
A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.
Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.
A biological material originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.
Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.
Common Interface declaration for conformance and knowledge artifact resources.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
The Care Team includes all the people, organizations, and care teams who participate or plan to participate in the coordination and delivery of care.
A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement.
This resource provides the adjudication details from the processing of a Claim resource.
A single issue - either an indication, contraindication, interaction, undesirable effect or warning for a medicinal product, medication, device or procedure.
The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.
A clinical or business level record of information being transmitted or shared; e.g. an alert that was sent to a responsible provider, a public health agency communication to a provider/reporter in response to a case report for a reportable condition.
A request to convey information from a sender to a recipient.
A compartment definition that defines how resources are accessed on a server.
A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and has traceability to the author who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models.
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
A record of a healthcare consumer’s choices or choices made on their behalf by a third party, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.
Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.
The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy.
This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource.
Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc.
This resource describes the properties (regulated, has real time clock, etc.), administrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serial number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element.
Describes a physiological or technical alert condition report originated by a device. The DeviceAlert resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable.
This is a specialized resource that defines the characteristics and capabilities of a device.
Describes a measurement, calculation or setting capability of a device. The DeviceMetric resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable.
Represents a request a device to be provided to a specific patient. The device may be an implantable device to be subsequently implanted, or an external assistive device, such as a walker, to be delivered and subsequently be used.
The findings and interpretation of diagnostic tests performed on patients, groups of patients, products, substances, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. The report also includes non-clinical context such as batch analysis and stability reporting of products and substances.
A reference to a document of any kind for any purpose. While the term “document” implies a more narrow focus, for this resource this “document” encompasses *any* serialized object with a mime-type, it includes formal patient-centric documents (CDA), clinical notes, scanned paper, non-patient specific documents like policy text, as well as a photo, video, or audio recording acquired or used in healthcare. The DocumentReference resource provides metadata about the document so that the document can be discovered and managed. The actual content may be inline base64 encoded data or provided by direct reference.
An interaction between healthcare provider(s), and/or patient(s) for the purpose of providing healthcare service(s) or assessing the health status of patient(s).
The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b, a REST endpoint for another FHIR server, or a s/Mime email address. This may include any security context information.
This resource provides the insurance enrollment details to the insurer regarding a specified coverage.
This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource.
An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time.
The EventDefinition resource provides a reusable description of when a particular event can occur.
The Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence.
The EvidenceVariable resource describes an element that knowledge (Evidence) is about.
A walkthrough of a workflow showing the interaction between systems and the instances shared, possibly including the evolution of instances over time.
This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided.
Significant health conditions for a person related to the patient relevant in the context of care for the patient.
Prospective warnings of potential issues when providing care to the patient.
Describes the intended objective(s) for a patient, group, or organizational care. Examples include a patient's weight loss, restoration of an activity of daily living for a patient, obtaining herd immunity via immunization for a group, meeting a process improvement objective for an organization, etc.
Represents a defined collection of entities that may be discussed or acted upon collectively but which are not typically expected to act collectively. These collections are also not typically formally or legally recognized. NOTE: Group may be used to define families or households, which in some circumstances may act collectively or have a degree of legal or formal recognition. This should be considered an exception. When Group is used for types of entities other than Patient or RelatedPerson, the expectation remains that the Group will not act collectively or have formal recognition - use Organization if these behaviors are needed. For example, it is possible for a 'family' Group to be a performer of an Observation or owner of a Task. However, this is not permitted for a Group made up of Practitioners, PractitionerRoles or Organizations. Organization or CareTeam would need to be used instead. A Group of Practitioners could, however, be a subject of an Observation.
A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken.
The details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices.
A selection of DICOM SOP instances within a single Study and Series. This might include additional specifics such as a set of frames or an image region, allowing linkage to an Observation Resource.
Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of images or other data objects (called Service-Object Pair Instances or SOP Instances) acquired or produced in a common context.
Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.
A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.
An ingredient of a manufactured item or pharmaceutical product.
Details of a Health Insurance plan provided by an organization under an InsuranceProduct.
Details of a Health Insurance product provided by an organization.
Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.
The Library resource is a general-purpose container for knowledge artifact definitions. It can be used to describe and expose existing knowledge artifacts such as logic libraries and information model descriptions, as well as to describe a collection of knowledge artifacts.
A List is a curated collection of resources, for things such as problem lists, allergy lists, facility list, organization list, etc.
Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.
The definition and characteristics of a medicinal manufactured item, such as a tablet or capsule, as contained in a packaged medicinal product.
The Measure resource provides the definition of a quality measure.
The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation.
This resource is primarily used for the identification and definition of a medication, including ingredients, for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.
Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. This event can also be used to record waste using a status of not-done and the appropriate statusReason.
Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.
An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
A record of a medication consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, patient representative (e.g., spouse, significant other, family member, caregiver), or a clinician. A common scenario where this information is captured is during the history taking process during a patient encounter or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. The primary difference between a MedicationStatement and a MedicationAdministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A MedicationStatement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the MedicationStatement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party. MedicationAdministration is more formal and is not missing detailed information.
Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use, drug catalogs, to support prescribing, adverse events management etc.).
Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted.
The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types.
A record of intake by a patient. A NutritionIntake may indicate that the patient may be consuming the food (i.e., solid and/or liquid), breastmilk, infant formula, supplements, enteral formula now or has consumed it in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food (i.e., solid and/or liquid), breastmilk, infant formula, supplements, enteral formula consumed. The consumption information may come from sources such as the patient's memory, from a nutrition label, or from a clinician documenting observed intake.
A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to an individual or group.
A food or supplement that is consumed by patients.
Measurements and simple assertions made about a patient, device or other subject.
Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service.
A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
A collection of error, warning, or information messages that result from a system action.
A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action.
Defines an affiliation/assotiation/relationship between 2 distinct organizations, that is not a part-of relationship/sub-division relationship.
A medically related item or items, in a container or package.
Demographics and other administrative information about an individual or animal that is the subject of potential, past, current, or future health-related care, services, or processes.
This resource provides the status of the payment for goods and services rendered, and the request and response resource references.
This resource provides the details including amount of a payment and allocates the payment items being paid.
Permission resource holds access rules for a given data and access request context.
Demographics and administrative information about a person independent of a specific health-related context.
This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, drug quality specifications, and drug manufacturing process.
A person who is directly or indirectly involved in the provisioning of healthcare or related services.
A specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time.
An action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing.
Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which MAY impact security, privacy, and trust policies.
A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.
A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to.
Regulatory approval, clearance or licensing related to a regulated product, treatment, facility or activity that is cited in a guidance, regulation, rule or legislative act. An example is Market Authorization relating to a Medicinal Product.
Information about a person that is involved in a patient's health or the care for a patient, but who is not the primary target of healthcare.
A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".
The Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.
A scientific study intended to increase health-related knowledge. For example, clinical trials are research studies that involve people. These studies may be related to new ways to screen, prevent, diagnose, and treat disease. They may also study certain outcomes and certain groups of people by looking at data collected in the past or future.
A ResearchSubject is a participant or object which is the recipient of investigative activities in a research study.
An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome.
A container for slots of time that may be available for booking appointments.
A search parameter that defines a named search item that can be used to search/filter on a resource.
A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
A slot of time on a schedule that may be available for booking appointments.
A kind of specimen with associated set of requirements.
A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types.
A Map of relationships between 2 structures that can be used to transform data.
The subscription resource describes a particular client's request to be notified about a SubscriptionTopic.
The SubscriptionStatus resource describes the state of a Subscription during notifications. It is not persisted.
Describes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic.
A homogeneous material with a definite composition.
The detailed description of a substance, typically at a level beyond what is used for prescribing.
A task to be performed as a part of a workflow and the related information like inputs, outputs and execution progress.
A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [CodeSystem] definitions and their use in [coded elements](terminologies.html).
An authorization for the provision of glasses and/or contact lenses to a patient.
This resource is used to pass information into and back from an operation (whether invoked directly from REST or within a messaging environment). It is not persisted or allowed to be referenced by other resources except as described in the definition of the Parameters resource.