Definition
FHIR (Fast Healthcare Interoperability Resources) is a next-generation healthcare interoperability standard released by HL7 (HL7 FHIR R4/R5), implemented using modern technologies such as RESTful API, JSON/XML, and RDF to achieve standardized exchange of medical data resources. FHIR defines over 150 resource types including Patient, ServiceRequest, Observation, and ImagingStudy, and supports access from web, mobile, IoT devices, and blockchain.
Compared with HL7 v2, HL7 v3, and CDA, FHIR is easier to implement, more flexible, and better suited for cloud-native architectures. Medical systems, health apps, wearable devices, and remote monitoring devices use FHIR for data exchange. IoT SIM cards provide secure connections for FHIR medical data exchange, meeting compliance requirements such as HIPAA, MLPS (Multi-Level Protection Scheme), and GDPR.
Technical Features
FHIR supports multiple interaction patterns, including REST, messaging, and documents. It has capabilities such as Extension, Reference, and Search. Combined with SMART on FHIR, it can achieve OAuth authorization and app interoperability. FHIR is widely adopted by the FDA, ONC, and health departments in various countries.
Use Cases
FHIR is applied in hospital information systems, electronic medical records, health management platforms, telemedicine, medical consortiums, medical insurance settlement, clinical trials, and more. Typical scenarios include patient information inquiry, electronic medical record sharing, mutual recognition of test results, health data reporting, and wearable device data integration. SimtoLink provides FHIR medical scenarios with VPDN private networks, dedicated APN, real-name verification, and smart medical solutions.
Resource Queries Crossing the Cellular Exit
How search and subscription differ in traffic
On an IoT SIM, FHIR means clinical resources are read and written at uniform resource addresses, not by inventing another private message on the link. Patient, lab observation, and imaging references are resources that can be fetched on their own. What leaves over cellular is usually a client on an off-campus gateway, a mobile clinician, or a home device. One query returns a page of resources. A subscription is a push from the server when a resource changes. They occupy the SIM very differently. A query is a burst and can be paused. A subscription holds a connection for a long time, with heartbeats and notifications mixed together.
The SIM does not interpret resource content. It only decides whether the request can reach the named host, and whether an address policy drops it on the way. Putting a full-library search on a small data plan makes the paging token chase the next page without stopping, and the traffic curve looks like a fault. For the older message standard, see HL7. When identifiable health information leaves the site or crosses a border, HIPAA-style privacy limits also apply. A path that "connects" is not by itself permission to send.
Conditions for pinning the host and the certificate
The host name is fixed, the certificate can be checked, and the client identity is separate from the patient authorization. The SIM allow-list should name hosts or address ranges, not the whole internet. A home device that reports only its own measurements should use a device credential. It must not carry an account that can walk every patient in the hospital. Catch-up after a disconnect needs a watermark: only changes after the last successful resource version, not a fresh pull from the first page on every reconnect.
Size the plan for notification counts plus occasional queries. Do not buy it from the call volume of the in-hospital interface. When a gateway aggregates several bedside devices, one SIM is the gateway, and the device id inside each resource must still be unique, so the platform does not write observations from different beds onto one timeline.
Paging that fills the plan
A common failure is a client that leaves the search criteria empty. On cellular that is equivalent to pouring the resource store outward. Retries with no backoff, during a certificate error, fill the link every second. After risk control pauses the SIM, a real critical-value notification cannot leave either. If subscription and query share one timeout, a slightly late notification is treated as a disconnect and rebuilt in full, and traffic and duplicate data appear together.
A wrong clock makes a "last updated" filter drop new records or insert old ones again. A personal token used on a production SIM during debugging, then written into a log, lets anyone who sees the usage detail or the log keep querying. Before go-live, check that an empty search is rejected, that reconnect pulls only the increment, and that patient names do not appear in the usage detail.
Subscription notices also have an order problem. Under jitter, a later observation can arrive first. If the platform overwrites "latest value" by arrival order, an old blood pressure covers a new one. Each resource should carry its own collection time and version, and a late old version must not cover a newer one. When a paging token expires, the client should narrow the time window and search again, not pull the whole history from page one. Otherwise one reconnect spends a small SIM's whole month. Do not mix a device credential and a user credential in one request. A device may submit only its own measurements. A user credential is what queries someone else, and only inside the authorized scope. When a gateway forwards several devices, each resource must still name the source device. It must not all be recorded as the gateway's SIM number. A SIM number in the audit is there to trace the path. It is not a clinical identifier for a patient or a device.
If the date in a search parameter uses a local time zone and the server uses another, observations from the same day are split across two adjacent days and look like missing data. The request should use the agreed zone, or an absolute time. When referring to another resource, send the identifier only. Do not embed the full referred object again. Otherwise one query grows with the nesting and fills a plan that was bought for small messages.