HeyDonto FHIR R4 API - Foundation (1.0)

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude

Foundation Framework

• Resource - Base resource definition
• DomainResource - Resource with narrative and extensions
• Basic - Generic resource for custom content
• Binary - Raw data content (images, PDFs, documents)
• Bundle - Container for collections of resources

Content Management Resources

• Questionnaire - Form definitions for data collection
• QuestionnaireResponse - Completed questionnaire answers
• List - Curated collection of resources
• Composition - Clinical document structure
• DocumentReference - Reference to external documents
• DocumentManifest - Collection of document references

Data Exchange Resources

• OperationOutcome - Operation results and error messages
• Parameters - Operation input/output parameters
• Subscription - Event notifications and subscriptions
• MessageHeader - Message metadata for routing
• MessageDefinition - Message structure definitions

Relationships with Other Modules

All the other modules depend on the Foundation module:

• The Exchange module builds on the foundation model by defining the recognized methods for exchange of resources
• The Terminology module provides the formal basis for using Concepts defined in Code Systems in the definitions
• The Conformance module provides the basis for extending the foundation for national and local use
• The Security & Privacy module provides the linking framework to external standards for security and privacy
• The Implementation Support module builds on the foundation to provide testing and reference implementations

Developmental Roadmap

Several components of the Foundation module have now reached normative status. The focus over the next 18-24 months as the 5th release of FHIR is prepared is to focus on some of the non-normative elements and move them towards normative status, such as Questionnaire, List, DocumentReference and Subscription. Exactly which resources will be candidates for normative release will be driven, in part, by the degree of implementation - and whether that implementation is communicated back to HL7.