SDC: Introduction
Understanding FHIR
This implementation guide is based on the HL7 FHIR R4 standard. It uses terminology, notations and design principles that are specific to FHIR. Before reading this implementation guide, it's important to be familiar with some of the basic principles of FHIR as well as general guidance on how to read FHIR specifications. Readers who are unfamiliar with FHIR are encouraged to read (or at least skim) the following prior to reading the rest of this implementation guide.
- FHIR overview
- Developer's introduction
- (or Clinical introduction)
- FHIR data types
- Using codes
- References between resources
- How to read resource & profile definitions
- Base resource
- RESTful operations
- Search
Feel free to explore other aspects of the FHIR specification that you feel may be relevant or of interest.
Resources
This implementation guide defines profiles on several resources. Implementers should follow the resource links in the table below to understand the data elements and general business rules associated with these resources. For convenience, the table below also lists the various profiles this implementation guide defines on the respective resources. The implementation expectations around these profiles are defined elsewhere in this guide, however they are all listed here to give a sense of various contexts in which each resource is used. Implementations will typically need to conform to at least some of these profiles to comply with this guide.
Based on FHIR Resource
SDC Profile(s)
Purpose
SDC Base Questionnaire Profile
Used to define form definitions that may be downloaded for manual and/or automatic population
Defines properties that must be supported for systems that support searching for and returning Questionnaires
Advanced Rendering Questionnaire Profile
Defines additional capabilities for controlling the rendering of the questionnaire
Advanced Behavior Questionnaire Profile
Defines additional capabilities for controlling data entry and calculating values within the questionnaire
Populatable Questionnaire - Observation Profile
Defines elements that support auto-population and pre-population of questionnaires using the Observation-based population mechanism
Populatable Questionnaire - Expression Profile
Defines elements that support auto-population and pre-population of questionnaires using the Expression-based population mechanism
Populatable Questionnaire - StructureMap Profile
Defines elements that support auto-population and pre-population of questionnaires using the Structure-based population mechanism
Extractable Questionnaire - Observation Profile
Defines elements that allow conversion of a QuestionnaireResponse to an Observation resource or Bundle of Observation resources using the Observation-based extraction mechanism
Extractable Questionnaire - Definition Profile
Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the Definition-based extraction mechanism
Extractable Questionnaire - StructureMap Profile
Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the StructureMap-based extraction mechanism
Adaptive Questionnaire Profile
Defines the metadata that should be present to embed an adaptive Questionnaire as part of a QuestionnaireResponse
Adaptive Questionnaire - search Profile
Defines the metadata that should be present to support searching for adaptive questionnaires
SDC Questionnaire Response Profile
Used to share instance data captured using questionnaire forms
Adaptive Questionnaire Response Profile
Represents a response to a questionnaire that is dynamically built as each question is answered
Used to define collections of allowed values for data elements and for questions in questionnaires
Used to define allowed values for data elements and for questions in questionnaires
Constraints on the codes and values of UsageContext to help ensure consistent usage in SDC Questionnaires
Additional resources such as Patient, Practitioner, Binary, ConceptMap, StructureMap, Provenance, AuditEvent and others are also likely to be used in SDC solutions, though no SDC-specific profiles have been created for them.