electronic Case Reporting (eCR) Implementation Guide Release For Comment Ballot Version

This page is part of the electronic Case Reporting (eCR) (v0.1.0: STU 1 Ballot 1) based on FHIR R3. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

SD.4 StructureDefinition-eicr-condition

source file: source/pages/_includes/eicr-condition-intro.md

ECR Profile: eICR Condition Profile

Scope and Usage

The Electronic Case Reporting Condition profile is based on the US Core-Condition profile and establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:

  • Initial Case Report signs, symptoms and diagnoses related to an event.

Additional Profile specific implementation guidance:

  • None

Examples


SD.4.1 Formal Views of Profile Content

Description of Profiles, Differentials, and Snapshots.

The official URL for this profile is: http://fhir.hl7.org/us/ecr/StructureDefinition/eicr-condition

Published on Wed Nov 29 00:00:00 AEDT 2017 as a draft by .

This profile builds on US Core Condition (a.k.a Problem) Profile


Summary

Must-Support: 1 element

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition I0..*Signs, symptoms, or diagnosis.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Ids for this condition
... clinicalStatus ?!SΣI0..1codeactive | recurrence | inactive | remission | resolved
Binding: Condition Clinical Status Codes (required)
... verificationStatus ?!SΣI1..1codeprovisional | differential | confirmed | refuted | entered-in-error | unknown
Binding: ConditionVerificationStatus (required)
... category S1..*CodeableConceptproblem-list-item | encounter-diagnosis
Binding: US Core Condition Category Codes (preferred)
... severity 0..1CodeableConceptSubjective severity of condition
Binding: Condition/Diagnosis Severity (preferred)
... code SΣ1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: Problem Value Set (extensible)
... bodySite Σ0..*CodeableConceptAnatomical location, if relevant
Binding: SNOMED CT Body Structures (example)
... subject SΣ1..1Reference(US Core Patient Profile)Who has the condition?
... context Σ0..1Reference(Encounter), Reference(EpisodeOfCare)Encounter or episode when condition first asserted
... onset[x] SΣ0..1dateTime, Age, Period, Range, stringEstimated or actual date, date-time, or age
... abatement[x] I0..1dateTime, Age, boolean, Period, Range, stringIf/when in resolution/remission
... assertedDate Σ0..1dateTimeDate record was believed accurate
... asserter Σ0..1Reference(Practitioner), Reference(Patient), Reference(RelatedPerson)Person who asserts this condition
... stage I0..1BackboneElementStage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... summary I0..1CodeableConceptSimple summary (disease specific)
Binding: Condition Stage (example)
.... assessment I0..*Reference(ClinicalImpression), Reference(DiagnosticReport), Reference(Observation)Formal record of assessment
... evidence I0..*BackboneElementSupporting evidence
con-2: evidence SHALL have code or details
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... code ΣI0..*CodeableConceptManifestation/symptom
Binding: Manifestation and Symptom Codes (example)
.... detail ΣI0..*Reference(Resource)Supporting information found elsewhere
... note 0..*AnnotationAdditional information about the Condition

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON), Schema: XML Schematron

 

SD.4.2 Quick Start

Below is an overview of the required set of RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.

...todo...