FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.omop
Resource TypeActorDefinition
IdActorDefinition-tgt.json
FHIR VersionR5
Sourcehttps://build.fhir.org/ig/HL7/fhir-omop-ig/ActorDefinition-tgt.html
URLhttp://hl7.org/fhir/uv/omop/ActorDefinition/tgt
Version2.0.0-ballot
Statusactive
Date2026-07-31
NameOMOP_Target_Instance
TitleOMOP Target Instance
Realmuv
Authorityhl7
DescriptionThe populated OMOP Common Data Model v5.4 database that is the output of the transformation. Conformance statements attached to this actor describe properties of the database state: what tables contain what kinds of records, what values are permitted in which fields, and what must or must not appear. These are checkable by data quality inspection independent of how the database was populated. Separating the Target Instance from the Transformation Engine matters because OMOP instances are often reused, merged, or incrementally extended. Properties attached to the Target Instance persist across transformation runs and across Engine versions. An OMOP instance populated by a non-conformant Engine can still be made conformant by post-processing; conversely, a conformant Engine operated against an unsuitable source can produce a non-conformant Target.
Typesystem

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ActorDefinition tgt

Actor: OMOP_Target_Instance OMOP Target InstanceType: system

Source1

{
  "resourceType": "ActorDefinition",
  "id": "tgt",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "brr"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 2,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/omop/ActorDefinition/tgt",
  "identifier": [
    {
      "system": "urn:ietf:rfc:3986",
      "value": "urn:oid:2.16.840.1.113883.4.642.40.77.12.3"
    }
  ],
  "version": "2.0.0-ballot",
  "name": "OMOP_Target_Instance",
  "title": "OMOP Target Instance",
  "status": "active",
  "experimental": false,
  "date": "2026-07-31",
  "publisher": "HL7 International / Biomedical Research and Regulation",
  "contact": [
    {
      "name": "HL7 International / Biomedical Research and Regulation",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/rcrim"
        }
      ]
    }
  ],
  "description": "The populated OMOP Common Data Model v5.4 database that is the output of the transformation. Conformance statements attached to this actor describe properties of the database state: what tables contain what kinds of records, what values are permitted in which fields, and what must or must not appear. These are checkable by data quality inspection independent of how the database was populated.\n\nSeparating the Target Instance from the Transformation Engine matters because OMOP instances are often reused, merged, or incrementally extended. Properties attached to the Target Instance persist across transformation runs and across Engine versions. An OMOP instance populated by a non-conformant Engine can still be made conformant by post-processing; conversely, a conformant Engine operated against an unsuitable source can produce a non-conformant Target.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "type": "system"
}