# US 2026/0100270 A1 · Fast healthcare interoperability resources (fhir) extension integration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0100270 A1
- Document ID: US20260100270A1
- Status: Published application
- Kind: A1
- Application number: 19/216,545
- Filed: 2025-05-22
- Published: 2026-04-09
- Earliest claimed: 2024-10-09
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Anuj Kaushal; Aditya Kulraj Kunwar; Eng Keat Khor; Tuck Chang; Ravindran Sankaran; Srimant Misra
- Web page: https://patentgrep.com/patent/US20260100270A1

## CPC

- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 70/20: relating to practices or guidelines
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques are disclosed for simplifying extensions. A method comprises receiving data that comprises a standard resource that conforms to a Fast Healthcare Interoperability Resources (FHIR) standard, wherein the standard resource includes one or more standard data elements for representing and exchanging healthcare information; determining that the standard resource further includes an extension that incorporates a non-standard data element into the standard resource, wherein the non-standard data element is defined by a structure definition that is external from the data; converting the standard resource into a normalized resource that conforms with an integration model, wherein the converting includes normalizing the non-standard data element based on a schema of the integration model to generate a normalized extension element that includes an attribute that extends the standard resource, and wherein the normalized resource comprises the one or more standard data elements and the normalized extension element; and providing the normalized resource.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving data that comprises a standard resource that conforms to a Fast Healthcare Interoperability Resources (FHIR) standard, wherein the standard resource includes one or more standard data elements for representing and exchanging healthcare information;
determining that the standard resource further includes an extension that incorporates a non-standard data element into the standard resource, wherein the non-standard data element is defined by a structure definition that is external from the data;
converting the standard resource into a normalized resource that conforms with an integration model, wherein the converting includes normalizing the non-standard data element based on a schema of the integration model to generate a normalized extension element that includes an attribute that extends the standard resource, and wherein the normalized resource comprises the one or more standard data elements and the normalized extension element; and
providing the normalized resource.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein normalizing the non-standard data element comprises replacing one or more cells of an extension array of the extension with a concrete type data structure.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein determining that the standard resource further includes the extension is based on:
identifying, in the data, a reserved key that indicates an occurrence of the extension;
obtaining a uniform resource locator or address associated with the extension; and
retrieving the structure definition with the uniform resource locator or the address.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising determining a name of the attribute, from the data or the structure definition, that extends the standard resource.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising associating an annotation with the normalized extension element, wherein the annotation indicates that the normalized extension element is associated with the extension.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, further comprising:
converting the normalized resource to a second standard resource, wherein the converting comprises:
identifying an occurrence of the annotation associated with the normalized extension element; and
converting the normalized extension element to a second non-standard extension element according to a second schema associated with the standard resource, wherein the second schema defines the standard resource and a format of the extension.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein providing the normalized resource comprises generating a user interface (UI) and rendering within the UI a graphical display of the normalized resource.

### Claim 8

A system comprising:
one or more hardware processors; and
one or more non-transitory computer-readable media storing instructions which, when executed by the one or more hardware processors, cause the system to perform operations comprising:
determining an occurrence of a standard resource that includes one or more standard data elements and an extension that incorporates a non-standard data element within data that represents healthcare information, wherein the non-standard data element is defined by an external structure definition;
normalizing the non-standard data element based on an integration model to define a normalized extension element that includes an attribute that extends the standard resource;
converting the standard resource into a normalized resource that conforms with the integration model, wherein the normalized resource comprises the one or more standard data elements and the normalized extension element; and
performing one or more operations using the normalized resource.

### Claim 9 (depends on 8)

The system of claim 8, wherein normalizing the non-standard data element comprises replacing one or more cells of an extension array of the extension with a concrete type data structure.

### Claim 10 (depends on 8)

The system of claim 8, wherein determining the occurrence of the standard resource that includes the one or more standard data elements and the extension, is based on:
identifying a reserved key that indicates an occurrence of the extension;
obtaining a uniform resource locator or address associated with the extension; and
retrieving the external structure definition with the uniform resource locator or the address.

### Claim 11 (depends on 8)

The system of claim 8, the operations further comprising determining a name of the attribute, from the data or the external structure definition, that extends the standard resource.

### Claim 12 (depends on 8)

The system of claim 8, the operations further comprising associating an annotation with the normalized extension element, wherein the annotation indicates that the normalized extension element is associated with the extension.

### Claim 13 (depends on 12)

The system of claim 12, the operations further comprising:
converting the normalized resource to a second standard resource, wherein the converting comprises:
identifying an occurrence of the annotation associated with the normalized extension element; and
converting the normalized extension element to a second non-standard extension element according to a second schema associated with the standard resource, wherein the second schema defines the standard resource and a format of the extension.

### Claim 14 (depends on 8)

The system of claim 8, wherein performing the one or more operations using the normalized resource comprises generating a user interface (UI) and rendering within the UI a graphical display of the normalized resource.

### Claim 15

A non-transitory computer-readable medium storing instructions which, when executed by one or more processing systems, cause operations to be performed comprising:
determining an occurrence of a standard resource that includes one or more standard data elements and an extension that incorporates a non-standard data element within data that represents healthcare information, wherein the non-standard data element is defined by an external structure definition;
normalizing the non-standard data element based on an integration model to define a normalized extension element that includes an attribute that extends the standard resource;
converting the standard resource into a normalized resource that conforms with the integration model, wherein the normalized resource comprises the one or more standard data elements and the normalized extension element; and
performing one or more operations using the normalized resource.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein normalizing the non-standard data element comprises replacing one or more cells of an extension array of the extension with a concrete type data structure.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein determining the occurrence of the standard resource that includes the one or more standard data elements and the extension, is based on:
identifying a reserved key that indicates an occurrence of the extension;
obtaining a uniform resource locator or address associated with the extension; and
retrieving the external structure definition with the uniform resource locator or the address.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, the operations further comprising determining a name of the attribute, from the data or the external structure definition, that extends the standard resource.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, the operations further comprising associating an annotation with the normalized extension element, wherein the annotation indicates that the normalized extension element is associated with the extension.

### Claim 20 (depends on 19)

The non-transitory computer-readable medium of claim 19, the operations further comprising:
converting the normalized resource to a second standard resource, wherein the converting comprises:
identifying an occurrence of the annotation associated with the normalized extension element; and
converting the normalized extension element to a second non-standard extension element according to a second schema associated with the standard resource, wherein the second schema defines the standard resource and a format of the extension.
