Release 5 Preview #2

This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

6.2.13 Resource Consent - Mappings

Community Based Collaborative Care Work GroupMaturity Level: N/AStandards Status: InformativeSecurity Category: Patient Compartments: Patient

Mappings:

FiveWs Pattern Mapping

Workflow Pattern

HL7 v2 Mapping

Mappings for the consent resource (see Mappings to Other Standards for further information & status).

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

Consent
    identifierFiveWs.identifier
    statusFiveWs.status
    categoryFiveWs.class
    subjectFiveWs.subject[x]
    dateTimeFiveWs.recorded
    performerFiveWs.actor
    organizationFiveWs.witness

6.2.13.2 Workflow Pattern (http://hl7.org/fhir/workflow )

ConsentEvent
    identifierEvent.identifier
    statusEvent.status
    categoryEvent.code
    subjectEvent.patient
    dateTimeEvent.occurrence[x]
    performerEvent.performer.actor
    organizationEvent.performer

6.2.13.3 HL7 v2 Mapping (http://hl7.org/v2 )

ConsentCON
    identifierCON-4 (Consent Form Number – EI)
Note: An implementation-specific requirement will be needed
    statusCON-11 (Consent Status – CNE using table HL70498)
    scopeCON-2 (Consent Type - CWE using table HL70496)
Note: Scope can be derived from category if going from V2 to FHIR.
    categoryCON-2 (Consent Type - CWE using table HL70496)
    subject
    dateTimeCON-13 (Consent Decision Date/Time – DTM)
    performerCON-24 (Consenter ID) and CON-25 (Relationship to Subject)
Note, CON-25 is depending on the type of resource being referenced (a reference to a Patient equates to a relationship of 1 (self), a RelatedPerson equates to 2 or 3 depending on RelatedPerson.relationship, etc)
    organization
    sourceAttachmentPotential mappings to CON-5,6,7,8,16,19, 20-23
    sourceReferencePotential mappings to CON-5,6,7,8,16,19, 20-23
    policyCON-3 (Consent Form ID and Version – ST)
Note: An implementation-specific requirement will be needed
        authority
        uri
    policyRuleCON-3 (Consent Form ID and Version – ST)
Note: An implementation-specific requirement will be needed
    verification
        verified
        verificationType
        verifiedBy
        verifiedWith
        verificationDate
    provision
        type
        periodCON-14&15 (Consent Effective Date Time, Consent End DateTime)
        actor
            role
            reference
        action
        securityLabel
        purpose
        class
        code
        dataPeriod
        data
            meaning
            reference
        provision