IHE MHD
E198796
IHE MHD (Mobile Access to Health Documents) is an IHE profile that defines a standardized, RESTful, FHIR-based way to access, query, and exchange clinical documents and metadata in healthcare systems.
All labels observed (3)
| Label | Occurrences |
|---|---|
| MHD | 2 |
| IHE MHD canonical | 1 |
| IHE MHD profile | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1776622 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: IHE MHD Context triple: [Integrating the Healthcare Enterprise, usesStandard, IHE MHD]
-
A.
MDH
MDH is the acronym for the Maryland Department of Health, the state agency responsible for public health services, policy, and regulation in Maryland.
-
B.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
-
C.
IHA
IHA is the commonly used abbreviation for Japan’s Imperial Household Agency, the government body responsible for matters concerning the Imperial Family.
-
D.
IHS
IHS is a U.S. federal agency within the Department of Health and Human Services that provides health services to American Indians and Alaska Natives.
-
E.
IHR
IHR refers to the International Health Regulations, a legally binding framework coordinated by the World Health Organization to prevent and respond to the international spread of disease.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: IHE MHD Target entity description: IHE MHD (Mobile Access to Health Documents) is an IHE profile that defines a standardized, RESTful, FHIR-based way to access, query, and exchange clinical documents and metadata in healthcare systems.
-
A.
MDH
MDH is the acronym for the Maryland Department of Health, the state agency responsible for public health services, policy, and regulation in Maryland.
-
B.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
-
C.
IHA
IHA is the commonly used abbreviation for Japan’s Imperial Household Agency, the government body responsible for matters concerning the Imperial Family.
-
D.
IHS
IHS is a U.S. federal agency within the Department of Health and Human Services that provides health services to American Indians and Alaska Natives.
-
E.
IHR
IHR refers to the International Health Regulations, a legally binding framework coordinated by the World Health Organization to prevent and respond to the international spread of disease.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IHE profile
ⓘ
health IT interoperability specification ⓘ |
| alignsWith |
IHE XCA
ⓘ
IHE XDR ⓘ IHE XDS ⓘ |
| basedOn |
IHE XDS
ⓘ
surface form:
IHE XDS document sharing concepts
|
| communicationStyle | RESTful ⓘ |
| definedBy | Integrating the Healthcare Enterprise ⓘ |
| defines |
FHIR-based transactions for document publication
ⓘ
FHIR-based transactions for document query ⓘ FHIR-based transactions for document retrieval ⓘ constraints on FHIR resources for document metadata ⓘ |
| domain |
health information exchange
ⓘ
healthcare interoperability ⓘ |
| ensures | consistent representation of document metadata across systems ⓘ |
| focusesOn |
document metadata
ⓘ
document sharing ⓘ mobile access ⓘ |
| fullName | Mobile Access to Health Documents ⓘ |
| governs | how clinical documents are exposed via FHIR APIs ⓘ |
| hasAbbreviation |
IHE MHD
self-linksurface differs
ⓘ
surface form:
MHD
|
| improves |
interoperability between EHR systems and mobile apps
ⓘ
standardization of document access APIs ⓘ |
| primaryPurpose |
access clinical documents
ⓘ
exchange clinical document metadata ⓘ exchange clinical documents ⓘ query clinical documents ⓘ |
| relatedTo | IHE IT Infrastructure domain ⓘ |
| specifies |
HTTP-based retrieval of document content
ⓘ
RESTful query operations for document discovery ⓘ profiles for document metadata representation ⓘ |
| supports |
cross-organization document access
ⓘ
cross-system document discovery ⓘ |
| supportsUseCase |
mobile and lightweight clients accessing document repositories
ⓘ
querying document registries via FHIR APIs ⓘ retrieving clinical documents over HTTP ⓘ |
| targetEnvironment |
lightweight clinical systems
ⓘ
mobile devices ⓘ web applications ⓘ |
| usesResourceType |
FHIR Binary
ⓘ
FHIR DocumentReference ⓘ FHIR Encounter ⓘ FHIR List ⓘ FHIR Organization ⓘ FHIR Patient ⓘ FHIR Practitioner ⓘ FHIR PractitionerRole ⓘ |
| usesStandard |
HL7 standards
ⓘ
surface form:
FHIR
REST API ⓘ
surface form:
REST
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: IHE MHD Description of subject: IHE MHD (Mobile Access to Health Documents) is an IHE profile that defines a standardized, RESTful, FHIR-based way to access, query, and exchange clinical documents and metadata in healthcare systems.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.