Generated Narrative: Composition CompositionUCSF3CARAPMP004PMLCDafalganSelfMedication Language: fr-CH Profile: PMLC Composition identifier: <a href="http://terminology.hl7.org/6.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt #xD;#xA;#xD;#xA;This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: #xD;#xA;#xD;#xA;Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:uuid:549fd427-6758-400e-ad63-46d0c43fbb0f status: Final type: Medication management plan (record artifact) date: 2026-01-24 14:48:55+0100 author: Device: type = Pharmaceutical information system application software (physical object) title: Plan de médication confidentiality: normal custodian: Organization Association CARA
Medication management plan (record artifact)
Ce plan de médication a été généré automatiquement par le service eMedication CARA le 14 décembre 2023 à 14:35:07 UTC. Tous les traitements actifs sont considérés.
The original representation as a PDF file
Generated Narrative: Patient PatientCARAPMP004 Profile: CH EMED EPR Patient Michaël Christopher Karce Male, DoB: 1973-12-25 ( Medical record number (use: official, )) Active: true Marital Status: unbekannt Other Ids: Medical record number/100001368 (use: secondary, ) Medical record number/CARAPMP004 (use: secondary, )
Generated Narrative: Device DevicePmp Profile: CH EMED EPR Device DeviceNames - Name Type * PMP CARA v0.1 Model name type: Pharmaceutical information system application software (physical object) Versions - Value * 8153cba owner: Organization Association CARA
Pharmaceutical information system application software (physical object)
Generated Narrative: Organization OrganizationCara Profile: CH EMED EPR Organization identifier: GLN/7601001407428 name: Association CARA address: Route de la Corniche 3a Épalinges Vaud 1066 CH
Generated Narrative: MedicationStatement MedicationStatementCardParacetamolSelfMedication Language: fr-CH Profile: PMLC MedicationStatement CH EMED Extension Treatment Plan id: <a href="http://terminology.hl7.org/6.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt #xD;#xA;#xD;#xA;This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: #xD;#xA;#xD;#xA;Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:uuid:cb13d6de-051f-4a3e-ab85-c05650fa254e externalDocumentId: <a href="http://terminology.hl7.org/6.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt #xD;#xA;#xD;#xA;This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: #xD;#xA;#xD;#xA;Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:uuid:a6deb711-dc0e-4a87-9ca9-f72bb9ecc858 CH EMED Extension Last Considered Document: <a href="http://terminology.hl7.org/6.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt #xD;#xA;#xD;#xA;This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: #xD;#xA;#xD;#xA;Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:uuid:a6deb711-dc0e-4a87-9ca9-f72bb9ecc858 identifier: <a href="http://terminology.hl7.org/6.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt #xD;#xA;#xD;#xA;This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: #xD;#xA;#xD;#xA;Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:uuid:0972e4a0-b4ce-4d1d-bffa-1172a58f499d status: Active medication: Medication DAFALGAN cpr eff 500mg subject: Michaël Christopher Karce Male, DoB: 1973-12-25 ( Medical record number (use: official, )) dateAsserted: 2026-01-22 14:50:55+0100 informationSource: Michaël Christopher Karce Male, DoB: 1973-12-25 ( Medical record number (use: official, )) reasonCode: J'ai souvent mal à la tête. dosage text: 1 comprimé en réserve, à avaler si besoin, à partir du 22 janvier 2026. timing: Once asNeeded: true route: À avaler DoseAndRates - Dose[x] * 1 comprimé (Details: SNOMED CT code732936001 = 'Tablet (unit of presentation)') Generated Narrative: Medication #MedicationParacetamolDafalganEff Language: fr-CH Profile: CH EMED EPR Medication code: DAFALGAN cpr eff 500mg form: Comprimé effervescent amount: 40 comprimé (Details: SNOMED CT code732936001 = 'Tablet (unit of presentation)')/1 plaquette (Details: SNOMED CT code732984005 = 'Blister (unit of presentation)') Ingredients - Item[x] IsActive Strength * Paracétamol true 500 mg (Details: UCUM codemg = 'mg')/1 comprimé (Details: SNOMED CT code732936001 = 'Tablet (unit of presentation)')
1 comprimé en réserve, à avaler si besoin, à partir du 22 janvier 2026.