Display resources for a specific patient, using a number of different views such as a list by resource type, json & tree views, encounters by condition, numeric Observation charting and graphical relationship views.
There is also the option to add a new patient, and to create sample data for that patient.
|Patient resources are stored on the Data Server. The server should support the Patient/$everything operation.|
|Server Query||Supports ad hoc queries against any FHIR server. Includes a simple query builder. The response can be displayed as Json or a Tree view, and FHIRPath is supported.||Can access any compliant FHIR server (must expose a Capability Statement)|
The Scenario Builder is used to join together the resources needed to represent a specific clinical scenario. It can use Core Resource types, Profiles and Logical models as it does this. The intention is to help people understand how resources can tell a clinical story, and to validate that the resource types available (including profiles) are sufficient.
Note that the builder still has issues with more complex resource types - this is a work in progress
|Patient information is on the Data Server. Profiles on the Conformance server. ValueSets on the Terminology server.|
|Logical Modeller||The Logical modeller allows the creation of a model that represents a particular interoperability requirement in a format that is easy to use. It uses FHIR datatypes, and can be based on an existing resource type or completely 'ad hoc'. It is intended to act as a 'bridge' between Modeller and User, and can act as the basis for the generation of the profiling components required by FHIR||Models are saved on the Conformance Server. Can reference ValueSets from the Terminology server.|
|Implementation Guide Browser||Display the contents of an Implementation Guide, and the relationships between the contents of the Guide.||The Implementation guide, profiles and Extension Definitions are on the Conformance Server, the terminology resources (eg ValueSet) are on the Terminology Server|
|Extension Definition builder||Views and builds extension definitions. These can be defined and applied to the Logical Model, which will allow them to be included in the generated Profile||Extension definitions are saved on the Conformance Server|
|CodeSystem builder||The CodeSystem defines a set of Concepts from which a ValueSet provides possible values for a resource element. The actual 'binding' between CodeSystem and element is done by the ValueSet. This component allows you to build (and edit) a CodeSystem, and optionally builds the ValueSet as well.||CodeSystems are saved on the Terminology Server.|
|ValueSet explorer||Lets you view existing ValueSets. The builder works best with SNOMED (at the moment).||ValueSets are stored on the Terminology Server|
|Concept Mapper||Edit concept maps.||R3 conformance server only|
|Implementation Guide Browser||Display the contents of an Implementation Guide, and the relationships between the contents of the Guide.|