Procedure-BNet-Episiotomy

FHIR Resource information

FHIR Resource	🌍Procedure-BNet-Episiotomy. Based on 🌍 Procedure
Description	A procedure resource for an episiotomy.
Release status	LIVE
Cardinality	Single instance
Writing to Spine permitted	YES - for Spine Client Type (MAT)
Spine filters	None

Key FHIR Resource elements used

* id - Unique resource identifier

Summary	Unique resource identifier
Mandatory	Yes
Expected type	🌍string
Write allowed	No
Data Dictionary item	None

* status - Status of the episiotomy procedure. This item should be fixed to 'completed'

Summary	Status of the episiotomy procedure. This item should be fixed to 'completed'
Mandatory	Yes
Expected type	🌍code
Write allowed	Yes
Data Dictionary item	None

* category - Category to identify this procedure as an episiotomy

Summary	Category to identify this procedure as an episiotomy
Mandatory	Yes
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	None
Fixed value	Fixed code value: '85548006', CodeSystem: 'snomed'', Display: 'Episiotomy'

* code - Code to identify which episiotomy procedure took place

Summary	Code to identify which episiotomy procedure took place
Mandatory	Yes
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	EPIS_Type - Episiotomy type - DataSet: (NZHISOMAT2) New Zealand HISO Maternity data set (Phase 2) - Topic: (WomanPostBirth) Woman details immediatly after birth
Value set used	🌍ValueSet-BNet-Preg-EpisiotomyType

* reasonCode - Code to identify why episiotomy procedure took place

Summary	Code to identify why episiotomy procedure took place
Mandatory	Yes
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	EPIS_Reason - Episiotomy reason - DataSet: (NZHISOMAT2) New Zealand HISO Maternity data set (Phase 2) - Topic: (WomanPostBirth) Woman details immediatly after birth
Value set used	🌍ValueSet-BNet-Preg-EpisiotomyReason

reasonCode.text - If the reason for episiotomy is other or medical reason, the text is stored here

Summary	If the reason for episiotomy is other or medical reason, the text is stored here
Mandatory	No
Expected type	🌍string
Write allowed	Yes
Data Dictionary item	EPIS_ReasonOther - Episiotomy reason – ‘Other’ – detail - DataSet: (NZHISOMAT2) New Zealand HISO Maternity data set (Phase 2) - Topic: (WomanPostBirth) Woman details immediatly after birth

* subject - Reference back to root the baby patient resource. The root patient resource should have an ID of $“Patient/{LogicalID}”

Summary	Reference back to root the baby patient resource. The root patient resource should have an ID of $“Patient/{LogicalID}”
Mandatory	Yes
Value type	🌍Reference(Patient)
Write allowed	Yes
Data Dictionary item	None

performedDateTime - Refers to the date and time at which episiotomy took place

Summary	Refers to the date and time at which episiotomy took place
Mandatory	No
Expected type	🌍dateTime
Write allowed	Yes
Data Dictionary item	None

Example JSON when WRITING to the Spine

JSON

{
  "resourceType": "Procedure",
  "status": "completed",
  "category": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "85548006",
        "display": "Episiotomy"
      }
    ]
  },
  "code": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "71981000210106",
        "display": "Anterior"
      }
    ]
  },
  "subject": {
    "reference": "Patient/pfnmWUFWGSLHi6aneTz6oGtTq-h4BVgwlH.mvFTZT5kuK5c8QXyC7WeACnmTu.mD",
    "type": "Patient"
  },
  "performedDateTime": "2022-05-01T22:01:00+01:00",
  "reasonCode": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "249166003",
          "display": "Delay in second stage"
        }
      ]
    }
  ]
}

Example JSON when READING from the Spine

JSON

{
  "resourceType": "Procedure",
  "id": "4F62736572766174696F6E2D424E65742D4368696C642D436F6E67656E6974616C4D616C666F726D6174696F6E73",
  "meta": {
    "profile": [
      "https://fhir.clevermed.com/StructureDefinition/Procedure-BNet-Episiotomy"
    ]
  },
  "status": "completed",
  "category": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "85548006",
        "display": "Episiotomy"
      }
    ]
  },
  "code": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "71981000210106",
        "display": "Anterior"
      }
    ]
  },
  "subject": {
    "reference": "Patient/pfnmWUFWGSLHi6aneTz6oGtTq-h4BVgwlH.mvFTZT5kuK5c8QXyC7WeACnmTu.mD",
    "type": "Patient"
  },
  "performedDateTime": "2022-05-01T22:01:00+01:00",
  "reasonCode": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "249166003",
          "display": "Delay in second stage"
        }
      ]
    }
  ]
}

CONFIDENTIAL/COMMERCIAL IN CONFIDENCE

Confidentiality/document control

This document contains information that is confidential to System C Healthcare Ltd (System C) and is intended for our customers to use in connection with our products and services. It must not be used for any other purpose nor disclosed to any other party, either whole or in part, without the prior written consent of System C except as follows. A customer may permit those of its employees, advisors and agents having a need to know the contents of this platform to have access to such of the contents as are strictly necessary, but that customer shall ensure that such employees, advisors and agents are bound to it by an obligation, in similar term, to keep it confidential. A customer's acceptance of these obligations shall be indicated by that customer's use of any of the information contained in this document.

System C acknowledges that a customer may be bound by the Freedom of Information Act 2000 (FOIA). In such cases, System C considers that the contents of this document are confidential and exempt from disclosure pursuant to section 41 of the FOIA. A customer should consult System C before making any disclosure of information relating to System C under the FOIA. System C's business information, methodologies, solutions, as well as reference to System C clients and their projects, are always considered by System C to be exempt from disclosure by virtue of section 41 and 43 of the FOIA, whether indicated or not. 

Product Information: any descriptions of future functionality reflect current product direction, are for informational purposes only, and do not constitute a commitment to provide specific functionality. Timing and availability remain at System C’s discretion and are subject to change and applicable regulatory approvals.

Warning: Paper or PDF copies of this document are not version controlled and will automatically be considered obsolete and superseded at the time of printing or conversion.

Confidentiality/document control statement version number 2.0, QMSUID-0059