/
MDM T02 - careplan
MDM T02 - careplan
PKB are suggesting a separate careplan for each status it would seem better to build up a MyConditions replacement in HTML and just have a single PV MyConditions careplan if possible. This would complicate the transplant status syncing as it would require regenerating the HTML each time it is updated and probably require that the transplantstatus is stored in the UKRDC so that when other details change it is correctly included..unless the transplant status syncing is used as the update process for this panel.
Currently a careplan cannot be deleted using MDM T11.
Message Specification
Segment | Field | Component | Notes | Value | UKRDC DB Location |
---|---|---|---|---|---|
MSH | See MSH Page | ||||
PID | See PID Page | ||||
TXA | This segment contains metadata about the document. | ||||
TXA-2 | |||||
TXA-2.1 | Document type. Must be "CP" for a care plan. | CP | |||
TXA-4 | |||||
TXA-4.1 | Activity Timestamp | ||||
[ TXA-5 ] | Primary activity provider. If provided, at least the family name must be given. | N/A | |||
TXA-5.2 | Family name | N/A | |||
[ TXA-5.3 ] | Given name | N/A | |||
[ TXA-5.4 ] | Middle names | N/A | |||
[ TXA-5.6 ] | Title | N/A | |||
TXA-12 | |||||
TXA-12.1 | Unique id | ||||
TXA-17 | |||||
TXA-17.1 | Document completion status. Must be "AU" for authenticated | AU | |||
OBX | |||||
OBX-2 | |||||
OBX2.1 | Only "ED" supported. | ED | |||
OBX-3 | |||||
OBX-3.2 | Name - title of careplan "MyConditions"? | ||||
OBX-5 | |||||
OBX-5.2 | Only "TEXT" supported. | TEXT | |||
OBX-5.3 | Only "HTML" or "PDF" supported | HTML | |||
OBX-5.4 | Either "Base64" or "A" supported. Note: Use "Base64" when OBX-5.3 is "PDF". | A | |||
OBX-5.5 | The action plan content. | The HTML you want to appear in the Action Plan section. | Derived from repo fields/data | ||
PV1 | |||||
PV1-10 | |||||
PV1-10.1 | Hospital Service Code | Renal |