FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
Query
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
API
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
Tools
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
Project Test
DocumentManifest
A collection of documents compiled for a purpose together with metadata that applies to the collection.
- type Profile on DocumentManifest
- FHIR R4
- status Draft
-
version4.6.0
Unregistered conflicting canonical
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
http://hl7.org/fhir
Canonical claims are used to verify ownership of your canonical URLs.
Canonical
Some canonical urls could not be resolved.
You're probably missing a package or made a typo in your canonical.
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Base
| DocumentManifest | DomainResource | There are no (further) constraints on this element Element idDocumentManifest A list that defines a set of documents DefinitionA collection of documents compiled for a purpose together with metadata that applies to the collection.
| ||
| masterIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDocumentManifest.masterIdentifier Unique Identifier for the set of documents DefinitionA single identifier that uniquely identifies this manifest. Principally used to refer to the manifest in non-FHIR contexts.
|
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idDocumentManifest.identifier Other identifiers for the manifest DefinitionOther identifiers associated with the document manifest, including version independent identifiers.
|
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idDocumentManifest.status current | superseded | entered-in-error DefinitionThe status of this document manifest. This element is labeled as a modifier because the status contains the codes that mark the manifest as not currently valid. The status of the document reference.
|
| type | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDocumentManifest.type Kind of document set DefinitionThe code specifying the type of clinical activity that resulted in placing the associated content into the DocumentManifest. Specifies the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be the same as one of the documents in it - especially if there is only one - but it may be wider. The activity that caused the DocumentManifest to be created.
|
| subject | Σ | 0..1 | Reference(Patient | Practitioner | Group | Device) | There are no (further) constraints on this element Element idDocumentManifest.subject The subject of the set of documents DefinitionWho or what the set of documents is about. The documents can be about a person, (patient or healthcare practitioner), a device (i.e. machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). If the documents cross more than one subject, then more than one subject is allowed here (unusual use case). Reference(Patient | Practitioner | Group | Device) Mappings
|
| created | 0..1 | dateTime | There are no (further) constraints on this element Element idDocumentManifest.created When this document manifest created DefinitionWhen the document manifest was created for submission to the server (not necessarily the same thing as the actual resource last modified time, since it may be modified, replicated, etc.). Creation time is used for tracking, organizing versions and searching. This is the creation time of the document set, not the documents on which it is based.
| |
| author | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) | There are no (further) constraints on this element Element idDocumentManifest.author Who and/or what authored the DocumentManifest DefinitionIdentifies who is the author of the manifest. Manifest author is not necessarly the author of the references included. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) Mappings
|
| recipient | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idDocumentManifest.recipient Intended to get notified about this set of documents DefinitionA patient, practitioner, or organization for which this set of documents is intended. How the recipient receives the document set or is notified of it is up to the implementation. This element is just a statement of intent. If the recipient is a person, and it is not known whether the person is a patient or a practitioner, RelatedPerson would be the default choice. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Mappings
| |
| source | 0..1 | uri | There are no (further) constraints on this element Element idDocumentManifest.source The source system/application/software DefinitionIdentifies the source system, application, or software that produced the document manifest.
| |
| description | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentManifest.description Human-readable description (title) DefinitionHuman-readable description of the source document. This is sometimes known as the "title". Helps humans to assess whether the document is of interest. What the document is about, rather than a terse summary of the document. It is commonly the case that records do not have a title and are collectively referred to by the display name of Record code (e.g. a "consultation" or "progress note").
|
| content | Σ | 1..* | Reference(Resource) | There are no (further) constraints on this element Element idDocumentManifest.content Items in manifest DefinitionThe list of Resources that consist of the parts of this manifest. Any Resources are allowed to be grouped in a Manifest. The manifest brings context to the group. When used for XDS the intended focus of the DocumentManifest is for the reference to target to be a set of DocumentReference Resources. The reference is to "Any" to support EN 13606 usage, where an extract is DocumentManifest that references List and Composition resources.
|
| related | 0..* | BackboneElement | There are no (further) constraints on this element Element idDocumentManifest.related Related things DefinitionRelated identifiers or resources associated with the DocumentManifest. May be identifiers or resources that caused the DocumentManifest to be created.
| |
| identifier | 0..1 | Identifier | There are no (further) constraints on this element Element idDocumentManifest.related.identifier Identifiers of things that are related DefinitionRelated identifier to this DocumentManifest. For example, Order numbers, accession numbers, XDW workflow numbers. If both identifier and ref elements are present they shall refer to the same thing. | |
| ref | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idDocumentManifest.related.ref Related Resource DefinitionRelated Resource to this DocumentManifest. For example, Order, ServiceRequest, Procedure, EligibilityRequest, etc. If both identifier and ref elements are present they shall refer to the same thing. |
Last updated on