eHealth Infrastructure
latest - ci-build

eHealth Infrastructure - Local Development build (vlatest) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: Document Type (Experimental)

Official URL: http://ehealth.sundhed.dk/vs/document-type Version: latest
Active as of 2019-02-08 Computable Name: DocumentType

Document Type value set.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 16 concepts.

CodeSystemDisplayDefinition
  103140-0http://loinc.orgPersonal health attachment Document
  53576-5http://loinc.orgPersonal health monitoring report Document
  74468-0http://loinc.orgQuestionnaire form definition Document
  74465-6http://loinc.orgQuestionnaire response Document
  11502-2http://loinc.orgLaboratory report
  56446-8http://loinc.orgAppointment summary Document
  39290-2http://loinc.orgFollow-up (referred to) program, appointment date CPHS
  39289-4http://loinc.orgFollow-up (referred to) provider /specialist, appointment date CPHS
  81215-6http://loinc.orgCare plan - recommended C-CDA R2.0 and R2.1 sections
  57059-8http://loinc.orgPregnancy visit summary note Narrative
  28615-3http://loinc.orgAudiology study
  CMRurn:oid:1.2.208.184.100.1Clinical Mesurement Report

Clinical Mesurement Report

  PDCurn:oid:1.2.208.184.100.1Stamkort

Personal Data Card

  MADCurn:oid:1.2.208.184.100.1MADC

Graviditetskort

  69730-0http://loinc.orgInstructions
  48766-0http://loinc.orgInformation source

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code