Modules (open in new tab)
Patient Viewer

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 $everything operation against Patient.
Scenario Builder

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.
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.
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
ValueSet explorer Lets you view existing ValueSets. The builder works best with SNOMED (at the moment). ValueSets are stored on the Terminology Server
Query Tool Allows ad hoc queries against any FHIR server Can access any compliant FHIR server
Cancel Edit
Current servers
Data Server
Conformance Server
Terminology Server
{{message}} {{elapsed}}
Should all be the same FHIR version

Add Server
Last access from {{accessAudit.lastAccess.location['country_name']}} on {{ | date:'yyyy-MM-dd HH:mm'}} ({{ | getAgeSeconds}} ago.)
{{}} {{c.cnt}}