FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R3 R2

Structuredefinition-example

FHIR Infrastructure Work GroupMaturity Level: N/ABallot Status: InformativeCompartments: Not linked to any defined compartments

This is the narrative for the resource. See also the XML or JSON format. This example conforms to the profile StructureDefinition.

Generated Narrative with Details

id: example

url: http://hl7.org/fhir/StructureDefinition/example

identifier: 1.2.36.90146595217.4.2

version: 2

name: LipidProfileExample

title: Example Lipid Profile

status: draft

experimental: true

date: 12/05/2012

publisher: Health Intersections Pty Ltd

contact:

description: Describes how the lab report is used for a standard Lipid Profile - Cholesterol, Triglyceride and Cholesterol fractions. Uses LOINC codes

useContext:

jurisdiction: Austria (Details : {urn:iso:std:iso:3166 code 'AU' = 'Austria)

purpose: Provide an example to demonstrate how to use StructureDefinition

copyright: Creative Commons 0, per FHIR specification

keyword: Hyperlipidemia screening test (procedure) (Details: SNOMED CT code 314079002 = 'Hyperlipidaemia screening test', stated as 'Hyperlipidemia screening test (procedure)')

fhirVersion: 1.0.0

Mappings

-IdentityUriNameComment
*m1https://www.rcpa.edu.au/getattachment/0961c6d1-ec80-4500-8dc0-de516500e05b/Lipid-and-lipoprotein-testing.aspxRCPA Lipid Report recommendationsActual mappings haven't yet been filled out

kind: resource

abstract: false

type: DiagnosticReport

baseDefinition: http://hl7.org/fhir/StructureDefinition/DiagnosticReport

derivation: constraint

Snapshots

-Element
*todo-bundle

 

Other examples that reference this example:

  • MessageDefinition/Patient Link Notification
  • MessageDefinition/Patient Link Response

    •  

    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.