Entry Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 828702,
    "url": "https://info.mzalendo.com/api/v0.1/hansard/entries/828702/?format=api",
    "text_counter": 1305,
    "type": "speech",
    "speaker_name": "Seme, ODM",
    "speaker_title": "Hon. (Dr.) James Nyikal",
    "speaker": {
        "id": 434,
        "legal_name": "James Nyikal",
        "slug": "james-nyikal"
    },
    "content": " You know since I became a politician, I have learnt not to be emotional sometimes. We are fighting a war that does not exist. What invasive is doing, is actually limiting what the clinical officers will do. Procedures include suturing. My position would have been: Do procedures as per your training, then leave out the word “invasive”. It is the word “invasive” that is giving us problems. If we pass this with the word “invasive: there, then the next thing we are going to do is this: We are going to put a list. But if you say do procedures as per your training, everything is involved. I am not pre-empting debate but the next that I would have opposed is speciality. I would say: Do the procedures as per your training and speciality. Why are we putting words like “invasive”? So, in my opinion, we should leave out the word invasive and leave the clinical officers free to do everything they want to do according to their training."
}