eHealth Infrastructure
3.3.0 - ci-build Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 3.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

Profiles

Extensions

The following Extensions have been defined as part of this implementation Guide. A registry of standard extensions can be found in the FHIR specification and additional extensions may be registered on the HL7 FHIR registry at http://hl7.org/fhir/registry.

  • Action Trigger
  • Ehealth action guidance for
  • Ehealth action guidance type
  • Administrative status
  • Answer condition
  • Assigning careteam
  • Base environment
  • Base
  • Title
  • Careplan status history
  • Careplan status schedule
  • assessor-Organization
  • Careplan
  • Decision
  • Decision context
  • Media investigation item
  • View investigation item
  • Recipient careteam
  • Sender careteam
  • Author organization
  • Content
  • Creator
  • Description
  • Privately owned
  • Suppliers
  • Calibration expires
  • Properties
  • Qualities
  • Quality history
  • Template qualities
  • Context
  • Employee title
  • Condition Id
  • End meeting on end time
  • Caremanager organization
  • Status schedule
  • Careteam
  • ExternalIdentifier
  • General health condition
  • Group id
  • Guest PIN code
  • EpisodeOfCare
  • Guest PIN code
  • includeAsExtra
  • Intended audience
  • IT competence level
  • Legal basis
  • Ehealth Document manually deprecated
  • Max participants
  • Meeting URL
  • Modified role
  • Name and address protection
  • On behalf of
  • CVR Number
  • Municipality Code
  • Provider identifier
  • Region code
  • Related to
  • Organization Source
  • Organization specialty
  • Organization Synchronization status
  • Telecom Custodian
  • Telecom System
  • Telecom Value
  • Overview usage mode
  • Participant
  • Patient contact note
  • Performer
  • Performing organization
  • Period
  • Predecessor
  • Priority
  • Date/time of re-used entity
  • Purpose
  • Quality
  • Answer significance
  • Feedback
  • Help text
  • Questionnaire image
  • Questionnaire intended organization
  • Copyright item indicator
  • Questionnaire recommendation
  • Short text
  • Slider Step-value Decimal
  • Questionnaire type
  • Questionnaire response finding basis
  • recommendation
  • Reference range
  • Registration deadline
  • Releasable resource
  • Resolved timing
  • Responsible organization
  • Responsible
  • Restriction category
  • Reuse criteria
  • Revision
  • ServiceRequest status history
  • ServiceRequest status schedule
  • Sharing Approval Policy
  • Sharing policy
  • Status
  • Task category
  • EpisodeOfCare
  • Task responsible
  • Team history
  • Team schedule
  • Thread id
  • Title
  • triggerEnablementCode
  • Trigger Condition
  • Usage
  • useContext
  • Version
  • View for
  • View type
  • VMR URI
  • Interpreter required

    • Datatype Profiles

    The following profiles for FHIR datatypes have been defined for this implementation guide.

    FHIR Resources Used Without Profile

    The following foundation and base FHIR resources are used in the eHealth Infrastructure:

    These resources are used as defined in FHIR Core as no need for profiling has been identified.

    FHIR Resources Slated for Use or Profiling

    The following resources are considered for profiling and/or use in a coming release of the eHealth Infrastructure: None at this time.

    References to Unused FHIR Resources

    In accordance with the open modeling approach, references to FHIR Core resources have been left as-is in the current profiles/resources even when such resources cannot be created (and therefore not referenced) in the current eHealth Infrastructure. This has been done to lessen the impact of possible future use of those referenced resources, should usage scenarios arise. In cases where this causes unwanted complexity, references to certain resources have been removed. The following is a non-exhaustive list of such unused resources: