Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Code.profile.xml

Example OperationDefinition/Observation-lastn (Narrative)

Maturity Level : N/A
Modeling Responsible Owner: Orders and Methodology Observations Work Group Standards Status : Informative Compartments : Device , Encounter , Group , Patient , Practitioner , RelatedPerson
Raw

This is the narrative for the resource. See also see the XML Format Specification , JSON ) or Turtle format.

StructureDefinition

Note that this is the formal definition for code the lastn operation as an OperationDefinition on Observation. See the Operation documentation

<?xml version="1.0" encoding="UTF-8"?> Base StructureDefinition for code type: A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents <!-- Note: special primitive values have a FHIRPath system type. e.g. this is compiler magic (h) --> May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. <!-- Note: special primitive values have a FHIRPath system type. e.g. this is compiler magic (i) --> A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents <!-- Note: special primitive values have a FHIRPath system type. e.g. this is compiler magic (g) -->

Generated Narrative: OperationDefinition Observation-lastn </ StructureDefinition

>

URL: [base]/Observation/$lastn

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN max 0..1 positiveInt

max is an optional input parameter to the lastn query operation. It is used to specify the maximum number of Observations to return from each group. For example for the query "Fetch the last 3 results for all vitals for a patient" max = 3.

OUT return 1..1 Bundle

The set of most recent N Observations that match the lastn query search criteria.

The key differences between this query operation and simply searching Observation using the combination of _count and _sort parameters are:

  • The lastn query returns only the last N resource grouped by code. Using the _count query method doesn't restrict the total matches so you may need to page through several "A" Observations before getting to Observation "B".
  • The server is responsible for grouping the observations by codes. This frees the client from needing to determine which codes she should ask for.

This operation cannot be performed on observations that the user is not authorized to see. It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one. If there is no nominated patient (e.g. the operation is invoked at the system level) and the context is not associated with a single patient record, then the server should return an error. Specifying the relationship between the context, a user and patient records is outside the scope of this specification.

 

 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.