Implementation Guide for FFB messaging (FFB udvekslingsdatasæt)
1.0.0 - release Denmark flag

This page is part of the KLFFBMessaging (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: KLMessagingFFBAccountOwner - Mappings

Active as of 2023-08-27

Mappings for the kl-messaging-ffb-accountOwner resource profile.

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

KLMessagingFFBAccountOwner
Organization(also see master files messages)
   identifierXON.10 / XON.3
      useN/A
      typeCX.5
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   identifier (eanIdentifier)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   activeNo equivalent in HL7 v2
   typeNo equivalent in v2
   nameXON.1
   telecomORC-22?
   addressORC-23?
   partOfNo equivalent in HL7 v2
   contact
      namePID-5, PID-9
         useXPN.7, but often indicated by which field contains the name
         textimplied by XPN.11
         familyXPN.1/FN.1
         givenXPN.2 + XPN.3
         prefixXPN.5
         suffixXPN/4
         periodXPN.13 + XPN.14
      telecomPID-13, PID-14
         systemXTN.3
         valueXTN.1 (or XTN.12)
         useXTN.2 - but often indicated by field
         rankn/a
         periodN/A
      telecom (phone)PID-13, PID-14
         systemXTN.3
         valueXTN.1 (or XTN.12)
         useXTN.2 - but often indicated by field
         rankn/a
         periodN/A
      telecom (email)PID-13, PID-14
         systemXTN.3
         valueXTN.1 (or XTN.12)
         useXTN.2 - but often indicated by field
         rankn/a
         periodN/A
      addressPID-11

Mappings for RIM Mapping (http://hl7.org/v3)

KLMessagingFFBAccountOwner
OrganizationEntity. Role, or Act, Organization(classCode=ORG, determinerCode=INST)
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifier.scopes[Role](classCode=IDENT)
      idn/a
      extensionn/a
      useRole.code or implied by context
      typeRole.code or implied by context
      systemII.root or Role.id.root
      valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
      periodRole.effectiveTime or implied by context
      assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
   identifier (eanIdentifier)n/a, II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
   active.status
   type.code
   name.name
   alias.name
   telecom.telecom
   address.address
   partOf.playedBy[classCode=Part].scoper
   contact.contactParty
      idn/a
      extensionn/a
      modifierExtensionN/A
      purpose./type
      name./name
         idn/a
         extensionn/a
         useunique(./use)
         text./formatted
         family./part[partType = FAM]
         given./part[partType = GIV]
         prefix./part[partType = PFX]
         suffix./part[partType = SFX]
         period./usablePeriod[type="IVL<TS>"]
      telecom./telecom
         idn/a
         extensionn/a
         system./scheme
         value./url
         useunique(./use)
         rankn/a
         period./usablePeriod[type="IVL<TS>"]
      telecom (phone)./telecom
         idn/a
         extensionn/a
         system./scheme
         value./url
         useunique(./use)
         rankn/a
         period./usablePeriod[type="IVL<TS>"]
      telecom (email)./telecom
         idn/a
         extensionn/a
         system./scheme
         value./url
         useunique(./use)
         rankn/a
         period./usablePeriod[type="IVL<TS>"]
      address./addr
   endpointn/a

Mappings for ServD (http://www.omg.org/spec/ServD/1.0/)

KLMessagingFFBAccountOwner
OrganizationOrganization
   identifier./Identifiers
      system./IdentifierType
      value./Value
      period./StartDate and ./EndDate
      assigner./IdentifierIssuingAuthority
   identifier (eanIdentifier)Identifier
   active./Status (however this concept in ServD more covers why the organization is active or not, could be delisted, deregistered, not operational yet) this could alternatively be derived from ./StartDate and ./EndDate and given a context date.
   typen/a
   name.PreferredName/Name
   telecom./ContactPoints
   address./PrimaryAddress and ./OtherAddresses
   partOfn/a
   contact
      name
         use./NamePurpose
         family./FamilyName
         given./GivenNames
         prefix./TitleCode
         period./StartDate and ./EndDate
      telecom
         system./ContactPointType
         value./Value
         use./ContactPointPurpose
         period./StartDate and ./EndDate
      telecom (phone)
         system./ContactPointType
         value./Value
         use./ContactPointPurpose
         period./StartDate and ./EndDate
      telecom (email)
         system./ContactPointType
         value./Value
         use./ContactPointPurpose
         period./StartDate and ./EndDate

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

KLMessagingFFBAccountOwner
Organization
   identifierFiveWs.identifier
   activeFiveWs.status
   typeFiveWs.class