This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile ImplementationGuide.
Generated Narrative: ImplementationGuide
Resource ImplementationGuide "example"
url: http://hl7.org/fhir/us/daf
version: 0
name: DataAccessFrameworkDAF
title: Data Access Framework (DAF)
status: draft
experimental: false
date: 2015年01月01日
publisher: ONC / HL7 Joint project
contact: ONC: http://www.healthit.gov, HL7: http://hl7.org/fhir
description: The Data Access Framework (DAF) Initiative leverages the HL7 FHIR standards to standardize access to Meaningful Use Stage 2 structured information both within the organization and from external organizations
jurisdiction: United States of America (ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code#US)
copyright: Published by ONC under the standard FHIR license (CC0)
packageId: hl7.fhir.us.daf
license: CC0-1.0
fhirVersion: 5.0.0
definition
Groupings
- Name Description* test Base package (not broken up into multiple packages)Resources
- Reference Name Description Profile* Patient/test Test Example A test example to show how an implementation guide works http://hl7.org/fhir/us/core/StructureDefinition/patientpage
name:
patient-example.htmltitle: Example Patient Page
generation: html
Pages
- Name Title Generation*list.htmlValue Set Page htmlParameters
- Code Value* Apply Metadata Value (Details: http://hl7.org/fhir/guide-parameter-code code apply = 'Apply Metadata Value', stated as 'null') version
manifest
rendering: http://hl7.org/fhir/us/daf
Resources
- Reference Profile RelativePathPages
- Name Title Anchor* patient-example.html Test Patient Example patient-example, tx, umlimage: fhir.png
other: fhir.css
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.